skills.rest
dawn840705
dawn840705COMMUNITY
Explore all skills by this author →
GitHub

create-stories

Break down an epic into Markdown story files with metadata and acceptance criteria.

Updated Aug 27, 2026
Search Tags:#workflow#adr#story#manifest#traceability#epic#gdd
One-click install
npx skills add https://github.com/dawn840705/claude-code-game-studios --skill create-stories-dawn840705
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-stories
Source: https://github.com/dawn840705/claude-code-game-studios/tree/main/skills/create-stories
Command: npx skills add https://github.com/dawn840705/claude-code-game-studios --skill create-stories-dawn840705

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Breaks down a single epic into concrete, implementable story files that map to the GDD, ADRs, and a control manifest.

Core Features & Use Cases

  • Transforms epics into a sequence of ready-to-implement stories with TR-IDs, ADR guidance, acceptance criteria, and test-evidence paths.
  • Ensures traceability from epic to story through design documents and governing decisions.
  • Outputs provenance-ready Markdown stories at production/epics/[epic-slug]/story-NNN-[slug].md for downstream QA and development.

Quick Start

Run /create-stories with an epic slug to generate per-epic story files under production/epics, then proceed with /story-readiness and /dev-story for each generated story.

Frequently Asked Questions about create-stories

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

FAQPage Schema
How do I break down an epic into implementable stories with traceability?▼

To break down an epic into implementable stories, the Skill reads the epic overview and governing documents to output Markdown story files with acceptance criteria, TR-IDs, ADR references, and test evidence paths.

What is the best way to map story files to GDD requirements and ADRs?▼

Mapping story files to GDD requirements and ADRs is achieved by attaching TR-IDs and ADR references directly to each generated story file, enforcing traceability from epic to implementation.

How do I generate story files for a specific epic slug?▼

Generating story files for a specific epic slug involves running the workflow command with that slug to produce provenance-ready Markdown files under the production/epics/[epic-slug]/ directory.

Can I use generated stories to guide downstream QA and development gates?▼

Generated stories can guide downstream QA and development gates by providing structured acceptance criteria and test-evidence paths that feed directly into subsequent readiness and implementation workflows.

Do I need a control manifest to turn epics into ready-to-implement stories?▼

A control manifest is needed to turn epics into ready-to-implement stories because the Skill maps each story to this manifest alongside GDD and ADRs to maintain provenance and traceability.

Related Skills

Explore More Software Engineering Skills→
adolfoaranaes12adolfoaranaes12
2

breakdown-epic

Break down epics into user stories with acceptance criteria and sprint groupings.

Community
Advanced
AhmedKaram50AhmedKaram50

bmad-dev-story

Load the next ready story and execute its Dev Story Workflow steps.

Community
Intermediate
CaptainCrouton89CaptainCrouton89
497

Testing Code

Automate software tests to verify functionality against acceptance criteria.

Community
Basic
juicesharpjuicesharp
581

blueprint

Decompose features into vertical slices and generate phased implementation plans.

Community
Advanced