Dev Plan Generator
Overview
Create a focused implementation plan that fixes scope, prevents uncontrolled expansion, and gives the project a checkbox-based execution history.
Workflow
- Read relevant local docs first:
README.md,AGENTS.md,CLAUDE.md,docs/*.md, and existingdev-plan/*.md. - Clarify the goal, scope, non-goals, constraints, and verification expectations.
- Create a new file under
dev-plan/implement_YYYYMMDD_HHMMSS.mdunless the user explicitly asks to update an existing plan. - Keep the plan implementation-oriented, not a PRD or meeting note.
- Break the work into phases with checkboxes.
- Add self-tests and done criteria for every phase.
- Update checkboxes to match real progress while implementing.
Required Sections
Every plan should include:
개발 목적개발 범위제외 범위참조 문서공통 진행 규칙Phase 상태 요약- one or more
Phasesections
Use references/dev-plan-template.md when a full skeleton is needed.
Rules
- Do not overwrite old plan files.
- Do not add features outside the stated scope.
- Put ambiguous or risky work into a separate phase or follow-up section.
- If parallel implementation is likely, include ownership boundaries and merge order.
- If engineering review is requested, add an
Engineering Reviewsection or call theplan-eng-reviewskill separately.
Script
Use scripts/new_dev_plan.py to scaffold a timestamped plan:
python3 path/to/scripts/new_dev_plan.py --dir dev-plan --title "Short goal"