create-stories

Generate story markdown files from epics with GDD and ADR validation.

14|1|Updated Apr 12, 2026

Search Tags:#qa #adr #story #pipeline #epic #game #gdd

Ready to run

npx skills add https://github.com/Euraika-Labs/Codex-Code-Game-Studios --skill create-stories-euraika-labs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-stories
Source: https://github.com/Euraika-Labs/Codex-Code-Game-Studios/tree/main/.agents/skills/create-stories
Command: npx skills add https://github.com/Euraika-Labs/Codex-Code-Game-Studios --skill create-stories-euraika-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers need a reliable way to turn high‑level epics into concrete, traceable story files that align with GDD requirements, ADR decisions, and test evidence, reducing manual planning effort.

Core Features & Use Cases

Epic parsing: Reads the EPIC.md, associated GDD sections, and governing ADRs.
Validation: Ensures all referenced ADR files exist before proceeding.
Story classification: Assigns story types (Logic, Integration, Visual/Feel, UI, Config/Data) and links each to a TR‑ID.
QA integration: Generates QA test case sections and invokes the QL‑STORY‑READY gate.
File generation: Writes standardized story markdown files and updates the epic overview.

Quick Start

Run $create-stories combat to generate story files for the combat 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 story files linked to GDD requirements?▼

To break epics into implementable story files, the skill parses an EPIC.md file alongside its associated GDD sections and governing ADRs. This generates standardized story markdown files linked to specific TR-IDs for development.

What is the best way to generate QA test cases for story files?▼

Generating QA test cases for story files is done by classifying story types and invoking the QL-STORY-READY gate. This approach automatically produces QA test case sections adhering to defined validation gates within the markdown.

Do I need ADR files before generating story files from an epic?▼

Yes, you need ADR files before generating story files from an epic. The process validates that all referenced ADR files exist before proceeding, ensuring story implementation aligns with established architectural decisions.

How does epic parsing classify story types for a game pipeline?▼

Epic parsing classifies story types for a game pipeline by assigning categories like Logic, Integration, Visual/Feel, UI, and Config/Data. Each classified story is then linked to a specific TR-ID for traceable implementation.

Can I use a control manifest to update an epic overview with new story markdown files?▼

Yes, you can use a control manifest to update an epic overview with new story markdown files. The process reads the control manifest to produce the files and automatically updates the epic overview upon completion.