What problem does it solve? Breaking a large Epic into shippable slices is error-prone when done ad hoc: features end up oversized, overlapping, or missing acceptance criteria, and the Epic document loses track of its children. This Skill decomposes an approved Epic into consistently structured Feature files, each scoped to 1–2 weeks of solo work, and keeps the Epic's Features section linked and up to date. ## Core Features & Use Cases - Epic-to-Feature decomposition: Reads an Epic's Features outline and writes one FEAT-NN.M-<slug>.md file per feature under the Epic's folder, numbered sequentially. - Template-enforced structure: Uses FEATURE.template.md verbatim so every Feature has Goal, User value, Scope, testable Acceptance criteria, Dependencies, Data touched, and Risks. - Split governance: Applies an artefact-economy gate to avoid under- or over-decomposition, proposes merging or splitting oversized features, and asks for confirmation before writing. - Use Case: After approving EPIC-03 for a new onboarding flow, run the command to generate FEAT-03.1 through FEAT-03.4 with linked frontmatter and an updated Epic Features section, ready for story breakdown. ## Quick Start Ask the assistant to split EPIC-03 into features using /tandem:split-into-features and confirm the proposed file tree before anything is written.
