By name: planning description: 'Decompose a high-level request into a detailed specification and plan with goals, non-goals, proposed design, task breakdown, and acceptance criteria. Use at the start of SDD cycles or before major features.'
Planning Skill
Use this skill to break a high-level request into a clear, comprehensive specification before coding. Create the following sections:
- Overview – Summarise the problem and its context. Describe what the change or feature is about.
- Goals – Define what the solution must achieve. List functional requirements and outcomes.
- Non‑Goals – Clarify what is explicitly out of scope for this change to avoid scope creep.
- Proposed Design – Outline the high-level architecture, modules, data flows and interfaces. Indicate technologies and patterns to be used.
- Task Breakdown – List the discrete tasks or steps needed to implement the design. Each task should be small and actionable.
- Acceptance Criteria – Describe measurable conditions for completion. They should be testable and cover positive and negative scenarios.
- Risks & Mitigations – Identify potential challenges, assumptions or unknowns and how to address them.
Ensure acceptance criteria are specific and that every requirement is covered. Ask clarifying questions if information is missing. Do not write code during planning.