dev-planner

---

name: dev-planner description: Used when Product-Spec.md is complete and needs to be planned into development phases. Also used to update existing development plans after Spec changes. Outputs DEV-PLAN.md. version: 1.1.0 updated: 2026-05-26 requires: []

[Task] Generation Mode: Read Product-Spec.md (and Design-Brief.md, if present), analyze feature dependency relationships, WebSearch to validate technology choices, output a phased development plan DEV-PLAN.md.

**Iteration Mode**: When the Product Spec changes, analyze the scope of impact, update the Phase breakdown and file inventory in DEV-PLAN.md. Completed Phases (marked with [x]) remain untouched.

[Not For] - Writing actual code -> use /dev-builder instead - Gathering requirements -> use /product-spec-builder instead - Fixing bugs -> use /bug-fixer instead

[Dependency Check] Executed automatically as the first step when the Skill starts:

Required:
- Product-Spec.md -> if missing, prompt user to call /product-spec-builder first
- Product-Spec.md must include completed **§ Idea Stage Exit Criteria** (three questions) — if missing or `TBD`, route back to `/product-spec-builder` before generating DEV-PLAN

Optional (degradation mode):
- Design-Brief.md -> if missing, mark as "no design specification mode", visual details annotated as [TBD by Design Brief]
- Design tool MCP -> if not connected or no files, rely only on text descriptions, mark as "no design draft mode"
- Existing project code -> if present, scan existing structure as constraints, enter iteration mode

[First Principles] Plan 前必读 references/first-principles.md Tech Stack: 规划前读 .forge/dev-map.md 的技术栈节，确保 DEV-PLAN.md 的技术栈与 dev-map 一致。

[Shared Discipline] Karpathy 四原则 → ../_shared/karpathy-discipline.md

[HARD-GATE] Until DEV-PLAN.md saved and user explicitly confirms → write .forge/plan-confirmed.json → MUST NOT invoke /dev-builder. Chat "looks good" ≠ confirm. Prerequisites: Product-Spec.md must exist. Rationalizations → references/plan-hard-gate-rationalization.md

[File Structure] dev-planner/ ├── SKILL.md ├── commands/dev-planner.md └── references/ ├── first-principles.md ├── analysis-dimension-checklist.md ├── analysis-strategies.md ├── workflow.md ├── architecture-health-pass.md └── plan-hard-gate-rationalization.md ../_shared/

[Output Style] → ../_shared/output-style-concise.md（Plan 额外要求：每 Phase 可独立编译运行；Task 列具体文件路径；禁止 TBD） → DEV-PLAN 完成必须附加 ../_shared/output-status-protocol.md

[Gotchas] Unrealistic Phasing: Each Phase must produce compilable, runnable output — split if no visible outcome. Missing dependency order: infrastructure → data → API → UI. Tech stack without WebSearch: Confirm versions before writing DEV-PLAN. Ignoring existing code: Iteration mode — scan structure first. Missing MVP Scope: Fill ## MVP Scope before Phase 1.

[Output Artifacts] - DEV-PLAN.md — Phased development plan (created in generation mode, updated in iteration mode) - changes/<change-name>/tasks.md — Task breakdown (filled when /change-manager apply invokes dev-planner for that change only — not by product-spec-builder iteration) - .forge/content-verify.json — (optional, recommended) forge-verify contract base generated from Phase requirements. Produced by Step 6 of Output Phase when user confirms plan. See references/generate-contracts.md.