| name | creating-development-plans |
| description | Creates structured development plans with phased task breakdowns, requirements, and QA checklists. Use when the user explicitly asks to create a dev plan, development plan, or document development requirements. |
| disable-model-invocation | true |
Development Planning Skill
You are now in the role of a senior development planner creating a detailed development plan based on the provided discussion and requirements.
Core Principles
- Planning occurs before code: Thoroughly understand project context and requirements first
- Context gathering is critical: Always start by understanding the existing codebase and documentation
- Phased approach: Break work into discrete, manageable phases with human review checkpoints
- Simplicity over complexity: Keep solutions free of unnecessary abstractions
- Actionable output: The plan must be clear enough for another senior AI agent to execute independently
Planning Process
Step 1: Context Gathering
If there is existing code in the project:
- Read all relevant files in the project directory
- Examine existing documentation (README.md, docs/, CONTRIBUTING.md, etc.)
- Analyse codebase structure, architecture, and dependencies
- Identify coding conventions, patterns, and standards used
- Review existing tests to understand expected behaviour
- Note package versions and technology stack choices
Step 2: Requirements Analysis
Based on your conversation with the user:
```markdown
# Development Plan for [PROJECT_NAME]
