create-stories

Decompose game development epics into story files with QA test cases.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Breaks large design epics into small, traceable, implementable story files so developers have clear acceptance criteria, test cases, and ADR-guided implementation notes. It prevents untestable requirements, missing ADRs, and disconnected TR-ID traceability that cause rework during implementation.

Core Features & Use Cases

  • Automated decomposition: Reads an epic, its GDD, governing ADRs, control manifest, and TR registry to derive story units from acceptance criteria.
  • Governance & validation: Confirms ADR files exist, embeds ADR decisions and engine risk, assigns TR-IDs, and flags blocked stories when ADRs are proposed.
  • QA integration: Classifies story types, spawns a QA readiness gate per review mode, and embeds QA test cases or manual checks directly into each story file.
  • Artifact generation: Writes production/epics/[epic-slug]/story-NNN-[slug].md files and updates the epic's EPIC.md Stories table for sprint planning.

Quick Start

Run /create-stories [epic-slug] to decompose the chosen epic into story files and present them for review.

Frequently Asked Questions about create-stories

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

FAQPage Schema
How do I decompose game development epics into testable stories?

Decomposing epics involves loading the EPIC.md, GDD, governing ADRs, control manifest, and TR registry to break acceptance criteria into sized stories. Each story receives a TR-ID, QA readiness gate, and embedded test cases.

What is an ADR validation gate in story decomposition?

ADR validation confirms that Architecture Decision Record files exist before decomposing an epic. When ADRs are only proposed, stories are flagged as blocked to prevent untestable requirements and implementation rework.

How do I assign TR-IDs to stories generated from an epic?

TR-IDs are assigned during decomposition by loading the TR registry alongside the epic and GDD. Each generated story file embeds its TR-ID for traceability between GDD requirements and implementation.

Can I generate QA test cases directly inside story files?

Yes, story decomposition classifies story types and spawns a QA readiness gate per review mode. QA test cases or manual checks are embedded directly into each story-NNN-[slug].md file alongside manifest metadata.

Do I need a GDD and control manifest to break down epics into stories?

Yes, epic decomposition requires loading the GDD, control manifest, governing ADRs, and TR registry to derive story units. Without these inputs, stories cannot be tied to requirements or validated against decisions.

Why are my decomposed stories flagged as blocked during generation?

Stories are flagged as blocked when governing ADRs are proposed but not finalized. This prevents generating stories with untestable requirements or missing architectural decisions that cause implementation rework.