Capability Map

Capability Map

What this skill does

capability-map produces the product's considered capability set — one README.md per capability — by decomposing product/vision.md. It owns the "is this one capability or three" judgment, and it promotes the provisional capability stubs change-scope created during bootstrap into considered capabilities. It produces the decomposition as a PROPOSAL for human approval; on approval it applies the map, migrating the change history of any capability it reshapes. It is the last pipeline skill.

Where the state tree lives

Generic skill — hard-codes no path. Resolve the state-tree root from the project's CLAUDE.md (project-declared paths, DESIGN_PRODUCT_PIPELINE.md §2); default docs/, and say which you used. {capabilities-root} means {declared-root}/capabilities (default docs/capabilities), and product/vision.md means {declared-root}/product/vision.md.

STOP — how this skill works

Before producing a capability map you MUST, in order:

1. CHECK THE VISION. Read product/vision.md. It must exist and be status: approved. If there is no vision, or it is unapproved — STOP. You cannot decompose a product that has not been defined; run product-vision first.
2. READ THE CURRENT STATE. Read vision.md in full and every existing capability README.md (provisional and considered) with its changes/ history.
3. DECOMPOSE the product into a considered capability set (see "The decomposition").
4. PRODUCE THE PROPOSAL — the considered map plus every merge / split / rename it implies against the current capabilities (see "The proposal").
5. SEEK HUMAN APPROVAL of the proposal. Nothing is rewritten before approval.
6. APPLY the approved map (see "Applying the map"), migrating reshaped capabilities.

Hard rules: