handbooksDefinition & planning sub-skill: Planning
Turns the product definition into business requirements and a technical architecture, in that order, as one flat skill.
Claude CodeLast reviewed September 3, 2026
In one minute
- A sub-skill of Definition & planning, invoked last of its four, after Product definition.
- Covers two internal steps, business requirements then architecture, in one file, not two.
- Step 2, architecture, needs a budget and timeline before it can size a stack sensibly, which is exactly what step 1 produces.
- Confirms the whole plan with the user before handing off. This is the last sub-skill in the phase, so it is the last checkpoint before anything gets built.
SKILL.md
.claude/skills/planning/SKILL.md
yaml
---
name: planning
description: Turns the product definition into business requirements and a technical architecture, in that order. Use as the fourth and last step of definition-and-planning, after product-definition.
---
## Steps
1. Read docs/product/definition.md. If it does not exist, stop and invoke /product-definition first.
2. Business requirements: draft a budget range, target timeline, and the specific person or role who approves scope changes.
3. Architecture: propose a stack and component breakdown sized to the budget and timeline from step 2. Flag the riskiest technical decision explicitly, do not bury it.
Write both as one file, docs/product/planning.md. Confirm the plan with the user before invoking /implementation.Where it fits
Invoked by Definition & planning, last of its four sub-skills, after Product definition. Once docs/product/planning.md exists and the user has confirmed it, Definition & planning hands off to Implementation.
Last reviewed September 3, 2026