What problem does it solve? Breaking an approved Feature into work-sized Stories often produces orphan Stories with no test coverage, or Testplans written later that drift from the acceptance criteria. This Skill enforces a mandatory Story-to-Testplan pairing rule: both artefacts are drafted, validated, and written to disk in the same response, or nothing is written at all. ## Core Features & Use Cases - Paired Story and Testplan generation: Every Story file (STORY-NN.M.PP) ships with a lockstep-numbered Testplan (TESTPLAN-NN.M.PP) where each acceptance criterion maps to at least one test case with a runnable command. - Structural abort on untestable criteria: If an acceptance criterion is not machine-testable, the Skill stops, flags the offending AC, and writes nothing rather than leaving an orphan Story. - Template and path-map driven output: Uses STORY.template.md and TESTPLAN.template.md verbatim, resolves folders via pm-paths.js, fills frontmatter (status, epic, feature, type_of_work), and runs a usage-estimate script per story. - Use Case: After approving FEAT-03.2, ask the Skill to decompose it; it reads the Feature's acceptance criteria, proposes the fewest Stories that carry the testable claims, shows the file tree for approval, then writes Stories, Testplans, and updates the Feature's Stories section. ## Quick Start Ask the assistant to split the approved Feature file FEAT-03.2 into Stories with paired Testplans using the tandem split-into-stories command.
