create-stories

Convert epic GDD acceptance criteria and ADRs into traceable story markdown files.

1|Updated May 5, 2026
One-click install
npx skills add https://github.com/XGanQAQ/Unity-Claude-Code-Game-Studios --skill create-stories-xganqaq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-stories
Source: https://github.com/XGanQAQ/Unity-Claude-Code-Game-Studios/tree/main/.claude/skills/create-stories
Command: npx skills add https://github.com/XGanQAQ/Unity-Claude-Code-Game-Studios --skill create-stories-xganqaq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It converts a large epic—along with its GDD requirements, governing ADRs, and control manifest rules—into small, fully traceable story documents that teams can implement without losing design intent or decision context.

Core Features & Use Cases

  • Epic-to-story decomposition: Breaks an epic’s GDD acceptance criteria into right-sized, self-contained stories in the correct dependency order.
  • Traceability and governance: Embeds each story’s TR-ID, governing ADR guidance, status (including BLOCKED for Proposed ADRs), and required evidence/test expectations.
  • Quality gate orchestration: Spawns a QA lead readiness assessment (in full review mode) and requires Adequate criteria before allowing story files to be written.

Quick Start

Run create-stories with the epic slug to generate story files under the epic’s production/epics folder, then review and approve the story list when prompted.

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?

To decompose an epic into implementable stories, this Skill breaks down the epic's GDD acceptance criteria and governing ADRs into small, self-contained markdown story files in the correct dependency order.

What is epic-to-story traceability in game development?

Epic-to-story traceability in game development embeds each story's TR-ID, governing ADR guidance, and required test expectations directly into the story files, ensuring teams do not lose design intent or decision context during implementation.

How do I generate story files from a GDD using an epic slug?

You generate story files from a GDD by running the Skill with an epic slug. It loads the epic overview, GDD, confirmed ADR files, and control manifest rules to classify story types and produce story markdown files under the production epics folder.

Do I need confirmed ADR files to create traceable story files?

Yes, you need confirmed ADR files to create traceable story files. The Skill requires loading confirmed ADRs to embed decision context, and it will mark stories as BLOCKED if it encounters Proposed ADRs instead.

Can I bypass the QA gate when decomposing epics into stories?

You can override the QA gate using optional review-mode overrides. In full review mode, the Skill spawns a QA lead readiness assessment and requires Adequate criteria before allowing story files to be written.

Why are my generated story files marked as BLOCKED?

Generated story files are marked as BLOCKED when the Skill encounters Proposed ADRs instead of confirmed ADRs during epic decomposition, preventing teams from implementing stories without finalized architectural decision context.