Milestones
Organize release-shaped work; plan and critique milestone scope.
What it is
Section titled “What it is”Organize release-shaped work; plan and critique milestone scope. This practice is a skill-mapped TTP: when, why, and which command—not a full copy of the skill. Open the skill to execute.
Why it works
Section titled “Why it works”Time-boxed outcomes beat endless backlogs. Milestones group issues toward a releasable slice—compatible with small batches and visible progress (DORA value-stream visibility). Critique/narrow keeps milestone WIP honest.
When to use it
Section titled “When to use it”When the situation matches the one-liner above and Orientation (or your project path) says this is the fire to touch now.
- Invoke the skill; follow its safety rules
- Keep one write owner; collect evidence before claiming done
- With only a milestone identifier (± details), execute completion on the critical-path issue — don’t menu admin commands
- After explicit admin shaping, offer to execute (
recon issue #N, diagnose/fix,merge-it, thenstage-it/ship-it) - Hand off to the next practice instead of boiling the ocean
- Skip orientation when you’re lost
- Spawn overlapping agents to “go faster”
- Treat the practice as done without evidence
Related concepts
Section titled “Related concepts”08-vision-tied-goals, 03-smallest-next-step
Further reading
Section titled “Further reading”See also the handbook Sources & grounding bibliography.
Agent skill
Section titled “Agent skill”milestones