create-stories

Break epics into traceable story markdown files with QA test cases.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/emcconnell/nova-scout --skill create-stories-emcconnell
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-stories
Source: https://github.com/emcconnell/nova-scout/tree/main/.claude/skills/create-stories
Command: npx skills add https://github.com/emcconnell/nova-scout --skill create-stories-emcconnell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns high-level epics, GDD requirements, and governing ADRs into a prioritized set of traceable, developer-ready story files so engineering teams can pick up well-scoped work without ambiguity or rework.

Core Features & Use Cases

  • Automated decomposition: Reads an epic, its GDD, referenced ADRs, control manifest rules, and TR-ID registry to decompose acceptance criteria into discrete stories.
  • Governance & validation: Confirms ADR existence, embeds ADR guidance and engine risk, and blocks work when required artifacts are missing or Proposed ADRs are present.
  • QA integration: Classifies story types, requests QA Lead readiness gates in full review mode, and embeds QA test cases and test evidence requirements into each story file.
  • Use Case: Product owners and lead programmers run this after creating epics to produce production/epics/[epic-slug]/story-NNN-[slug].md files with ready-to-implement acceptance criteria and QA specs.

Quick Start

Run the skill by issuing /create-stories [epic-slug] to generate a full set of story markdown files for that epic.

Frequently Asked Questions about create-stories

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I break epics into implementable user stories with traceable acceptance criteria?

Epic decomposition breaks epics into discrete user stories by reading the epic's GDD, ADRs, control manifest, and TR-ID registry to map acceptance criteria into ordered, traceable story markdown files. This ensures engineering teams receive well-scoped, developer-ready work.

What is the process for embedding ADR guidance and TR-IDs into user story files?

Embedding ADR guidance and TR-IDs into user story files involves validating ADR existence from the epic references, classifying story types, and injecting the TR-ID registry mappings and ADR risk guidance directly into standardized story markdown outputs.

How do I generate story markdown files from an epic slug for my production environment?

Generating story markdown files from an epic slug requires running the automated decomposition process, which reads the epic and its governing artifacts, then writes standardized story files with embedded QA test cases and dependencies under the production/epics directory.

Does epic decomposition block work when required ADRs are missing or only proposed?

Epic decomposition governance blocks work when required artifacts are missing or when Proposed ADRs are present. It validates ADR existence upfront to ensure no story files are generated without confirmed architectural decisions and governing manifests.

Can I automate QA readiness gates and test case generation when creating user stories from epics?

QA readiness gates and test case generation are automated during story creation by classifying story types, requesting QA Lead readiness gates in full review mode, and embedding required QA test cases and test evidence specifications into each story file.

What artifacts do I need to prepare before decomposing an epic into developer-ready stories?

Before decomposing an epic into developer-ready stories, you must prepare a design GDD, governing ADR references, the control manifest, and the TR-ID registry. These artifacts provide the acceptance criteria and traceability mappings required for story generation.