Task Planning
Overview
Two leaves run from approved spec to a plan a team can commit to: the vertical-slice task list with dependencies and done conditions, then the estimate, cadence, risk register and build-vs-buy decisions that sit on top of it.
When to use
- Slicing a spec, feature or epic into mergeable, ordered tasks.
- Producing an estimate or date-range forecast with stated confidence.
- Choosing a process cadence, building a risk register, making a build-vs-buy call.
When not to use
- Writing the spec, stories or acceptance criteria themselves — outside this skill.
- Choosing the system's structure or its modules — outside this skill.
- Deciding step sizes while writing the code — outside this skill.
Precedence
The deepest loaded instruction governs its uniquely-claimed scope; every
scope:string is claimed by exactly one file in this tree; no leaf may widen a prohibition declared by an ancestor — leaves narrow, never override upward.
Subskill index
| Leaf | Task | Trigger |
|---|---|---|
subskills/task-breakdown.md |
Spec into ordered vertical tasks | "break this into tasks" |
subskills/planning.md |
Estimates, cadence, risks, build-vs-buy | "how long will this take" |
See also
subskills/task-breakdown.md— the slicing half.subskills/planning.md— the estimating and risk half.