doc-driven:milestone-planning
Milestone Planning
Plan roadmap structure before task-local spec work begins.
This skill decides Milestone -> optional Module -> Task shape. It owns roadmap-layer docs/tasks/ structure and governance, not task-local specs or implementation flow.
Composition
- Entry: reached from
doc-driven-spec-workflowafter scope is clear enough to plan delivery structure. - Owns: milestone boundaries, optional module grouping, roadmap-layer task breakdown, backlog/handoff governance, planning-stage
docs/tasks/documents. - Does not own: repository scaffold bootstrap, task-local
spec.md, task-localplan.md, readiness checks, implementation, verification, branch closing. - Handoff: use
doc-driven:task-spec-executiononly after the current concrete task is selected and the user wants to enter spec-first execution.
Core Rules
Delivery Boundary
More from adol1111/doc-driven-spec-workflow
doc-driven-spec-workflow
Use when a docs-driven repository request is unclear about whether the next step is scaffold initialization, clarification, roadmap decomposition, or current-task execution.
36milestone-planning
Use when a request or repository needs roadmap decomposition before spec writing because milestone boundaries, module grouping, or independently reviewable tasks are unclear.
35task-spec-execution
Use when older prompts, installed workflows, or tests still refer to task-spec-execution and need a compatibility redirect into the split task-preparation or task-execution-simple stages.
35docs-workflow-bootstrap
Use when initializing, bootstrapping, creating, or scaffolding the minimum docs-driven workflow layout for a repository before roadmap planning, specs, or implementation tasks exist.
33task-execution-simple
Use when task-local spec or plan work is complete and a concrete docs/tasks task should be implemented through the repository's simple direct execution path.
11task-preparation
Use when a docs-driven repository has a selected or selectable concrete docs/tasks task and needs task-local spec or plan governance before code execution.
10