split-into-featureslisted

Split an EPIC into Feature files. Use when the user asks to split / decompose / break down an epic into features, asks to create features under an epic, or invokes /tandem:split-into-features. Operates as PM hat. Reads an Epic file and writes FEAT-NN.M-<slug>.md files in 31-Features/EPIC-NN/, then updates the Epic's Features section with relative links.
DATA-AI-XYZ/Tandem · ★ 0 · Data & Documents · score 70

Install: claude install-skill DATA-AI-XYZ/Tandem

# Tandem: split-into-features (PM hat) Operate as **PM hat**. The user has an approved Epic and needs to decompose it into Features that can each ship in 1–2 weeks of solo work. This skill is the slash-command wrapper for the kit's canonical feature-decomposition prompt. The prompt is the source of truth; this file is the entry point. ## Source of truth @_00-Project-Management/92-Prompts/03-split-epic-into-features.md Follow that prompt verbatim. The sections below add only the slash-command-specific glue — do not re-declare the prompt's content here. ## Inputs needed - Path to the source Epic file under the `epics` folder (resolve via the path map: `node _00-Project-Management/93-Scripts/lib/pm-paths.js resolve epics`; e.g. `_00-Project-Management/01-EPIC/EPIC-NN-<slug>.md`). - If the user didn't supply one, ask: "Which Epic file should I decompose? Paste the path or the EPIC-NN id." ## Load into context Use `Read` / `Glob` to detect existence. Treat missing files as "not present" rather than throwing. Folder locations are resolved through the path map (`pm-paths.js` / `pm-paths.json`) rather than hardcoded. - **Source Epic** — at the resolved path above. Read it fully — especially the `## Features` outline (high-level titles the Epic already proposed) and `## In scope` / `## Out of scope`. - **SOP** — `_00-Project-Management/90-Standards/SOP.md` for DoR + estimation rules. - **Project context** — `_00-Project-Management/90-Standards/PROJECT-CONTEXT.md`. - **Featur