aiwfx-plan-milestones

Decomposes an approved aiwf epic into sequenced, independently-shippable milestones with allocated ids.

Updated May 9, 2026
One-click install
npx skills add https://github.com/23min/aiwf --skill aiwfx-plan-milestones-23min
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aiwfx-plan-milestones
Source: https://github.com/23min/aiwf/tree/main/internal/skills/embedded-rituals/plugins/aiwf-extensions/skills/aiwfx-plan-milestones
Command: npx skills add https://github.com/23min/aiwf --skill aiwfx-plan-milestones-23min

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Breaking a large epic into ordered, deliverable chunks is error-prone when done ad hoc: ids collide, dependencies get lost, and planning state scatters across chats. This Skill drives the decomposition conversation while the aiwf CLI owns id allocation, dependency tracking, and one-commit-per-milestone provenance. ## Core Features & Use Cases - Milestone decomposition: Splits an epic spec into independently-shippable milestones of 1-3 days each, with testable acceptance criteria and explicit forward-only dependencies. - aiwf-backed allocation: Allocates each M-NNNN id via aiwf add milestone, scaffolds specs from the milestone template, creates AC entities via aiwf add ac, and declares dependencies with aiwf milestone depends-on. - Planning finalization: Updates the epic's milestone list, regenerates ROADMAP.md with trailered commits, and merges the planning branch to main. - Use Case: After approving an epic for a new authentication system, ask the assistant to break E-0007 into milestones; it sequences foundational work first, allocates ids, and lands the plan on main. ## Quick Start Ask the assistant to break epic E-NNNN into milestones and sequence the work for it.

Frequently Asked Questions about aiwfx-plan-milestones

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I break an epic into milestones with aiwf?

Read the epic spec, decompose it into independently-shippable milestones of 1-3 days each, then allocate each with `aiwf add milestone --epic E-NNNN`. Fill each spec body from the milestone template and commit via `aiwf edit-body`.

How do I declare milestone dependencies in aiwf?

Pass `--depends-on M-NNNN,M-NNNN` at allocation time, or run `aiwf milestone depends-on M-NNNN --on ...` afterward. Never hand-edit the `depends_on` frontmatter; untrailered commits trip the provenance check.

When should acceptance criteria be created for a milestone?

Create AC entities at plan time using `aiwf add ac M-NNNN`, before merging planning to main. This prevents milestones from landing on main with zero ACs or empty AC bodies, which the `milestone-draft-incomplete-acs` check flags.

Does this skill write full milestone specs up front?

No. It produces the milestone list and shape only; deep spec detail is drafted just-in-time when each milestone starts via `aiwfx-start-milestone`. Front-loading detail is an explicit anti-pattern because early specs rot.

What happens if the epic does not exist yet?

The skill requires an existing epic spec under work/epics. If none exists, run the `aiwfx-plan-epic` skill first to create and approve the epic before decomposing it into milestones.