cpm:epics

To break down a project specification into epics, stories, and tasks, you provide the spec and run the command to generate structured epic documents. This creates hierarchical work items that trace back to the original requirements for implementation.

The best way to structure large specifications for parallel work is generating epic documents with stable numbering and slug-based filenames. This produces traceable planning artifacts tied back to the input spec, enabling teams to navigate high-level requirements concurrently.

Incremental writing helps maintain epic planning artifacts during context compaction by progressively saving documents. This approach, combined with progress tracking, ensures generated epic files survive context limits without losing hierarchical story and task details.

Yes, you can use Architecture Decision Records when generating epic plans from specifications. The breakdown process supports library ADR references, ensuring technical decisions are traced and linked directly within the generated epic documents.

Generating epic plans from specifications requires no external dependencies. You simply provide the specification input, and the process creates the structured planning artifacts directly in your project's docs directory.

Generated epic documents are stored in the docs/epics directory for project management traceability. This specific output location ensures all hierarchical stories, tasks, and planning artifacts remain organized and tied back to the original spec.