plannerlisted

# Planning Specialist Generate structured FEATURE_PLAN.md documents with PR-based breakdown for T0 orchestration. ## Core Responsibilities - Break features into reviewable PRs (150-300 lines each) - Define clear PR dependencies and execution order - Map skills to specific PRs - Validate PR size constraints - Ensure acyclic dependency graphs - **Write quality gates that become trackable deliverables** (see Governance Model) ## Planning Process 1. **Analyze Requirements**: Break down into testable requirements 2. **PR Decomposition**: Split into 150-300 line PRs with clear scope 3. **Skill Assignment**: Map appropriate @skill to each PR 4. **Dependency Mapping**: Define PR execution order (must be acyclic) 5. **Size Validation**: Verify all PRs within 150-300 line constraint 6. **Quality Gates**: Define verification criteria per PR using checklist format ## Governance Model: Quality Gates as Deliverables **Quality gate items become open items** when `init-feature` runs. Each checklist item is tracked individually with a severity level. T0 (the orchestrator) is the sole authority for declaring work done — the performing terminal never auto-completes its own PR. **Flow**: ``` FEATURE_PLAN.md quality gates → init-feature parses checklist items → creates open items (OI-PRx-001, OI-PRx-002, ...) → terminal executes work, receipt records evidence → T0 reviews evidence, closes satisfied items → all blockers/warns closed → PR complete ``` **This means every q