skills.rest
frabcd
frabcdCOMMUNITY
Explore all skills by this author →
GitHub

create-stories

Decomposes a game development epic into traceable, implementable story files with acceptance criteria.

13|Updated Jul 30, 2026
Search Tags:#game development#adr#acceptance criteria#user stories#agile planning#epic decomposition#gdd
One-click install
npx skills add https://github.com/frabcd/codex-ai-game-studio --skill create-stories-frabcd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-stories
Source: https://github.com/frabcd/codex-ai-game-studio/tree/main/plugins/ai-game-studio/skills/create-stories
Command: npx skills add https://github.com/frabcd/codex-ai-game-studio --skill create-stories-frabcd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Breaking a large game development epic into small, implementable stories is error-prone: stories lose traceability to design requirements, miss architectural guidance, or lack testable acceptance criteria. This Skill automates that decomposition while enforcing traceability to GDD requirements, ADR decisions, and control manifest rules. ## Core Features & Use Cases - Epic-to-Story Decomposition: Reads an epic, its GDD, governing ADRs, and the control manifest, then groups acceptance criteria into right-sized stories (~2-4 hour sessions) classified by type (Logic, Integration, Visual/Feel, UI, Config/Data). - Traceability Enforcement: Each story embeds its TR-ID from the tr-registry, governing ADR guidance, engine risk level, and required test evidence path; stories blocked by Proposed ADRs are flagged automatically. - QA Gate Integration: Optionally spawns a qa-lead gate (QL-STORY-READY) to validate testability, generating Given/When/Then test specs or manual verification steps embedded in each story file. - Use Case: After running create-epics for a combat system, run this Skill to produce story-001 through story-00N files under production/epics/combat/, each ready for story-readiness and dev-story implementation. ## Quick Start Ask the AI to run $ai-game-studio:create-stories for your epic slug, for example: break the combat epic into implementable stories.

Frequently Asked Questions about create-stories

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

FAQPage Schema
How do I break a game development epic into user stories?▼

Run $ai-game-studio:create-stories with the epic slug or path, for example $ai-game-studio:create-stories combat. It reads the epic, GDD, and governing ADRs, groups acceptance criteria into right-sized stories, and writes story files to production/epics/[epic-slug]/ after your approval.

How are stories traced back to GDD requirements and ADRs?▼

Each story embeds its TR-ID looked up from docs/architecture/tr-registry.yaml, plus the governing ADR with a decision summary and implementation notes. Stories governed by a Proposed ADR are marked Blocked until the ADR is advanced.

What happens if an epic references an ADR file that does not exist?▼

The skill stops immediately before decomposing any story and reports the missing ADR file. You must fix the filename in the epic's Governing ADRs list or create the ADR with the architecture-decision skill before continuing.

Does create-stories generate test cases for each story?▼

Yes. For Logic and Integration stories it produces Given/When/Then test specs per acceptance criterion; for Visual/Feel and UI stories it produces manual verification steps. These are embedded in each story's QA Test Cases section, and existing QA plan specs can be reused.

What is the difference between full, lean, and solo review modes?▼

The review mode controls whether the QL-STORY-READY qa-lead gate runs. In full mode the gate spawns normally; in lean and solo modes it is skipped and stories go straight to the presentation step. The mode is read from production/review-mode.txt or a --review flag.

When should I not use create-stories for a task?▼

Do not use it before epics exist — run create-epics first, since stories are decomposed per epic. It also never starts implementation; it stops at writing story files, and implementation begins with story-readiness and dev-story.

Related Skills

Explore More Product & Management Skills→
naxorutonaxoruto

create-epics

Map approved GDDs and architecture into module epics with ADR coverage.

Community
Advanced
JunnnnyWonJunnnnyWon

dev-story

Reads a story file and routes it to the correct programmer agent for implementation with tests.

Community
Advanced
JunnnnyWonJunnnnyWon

story-readiness

Validate software story files for GDD references, ADR status, and acceptance criteria.

Community
Advanced
rakhnianskii9rakhnianskii9

qa-plan

Convert GDDs and stories into structured QA plans with test coverage.

Community
Advanced