skills.rest
FrancisVarga
FrancisVargaCOMMUNITY
Explore all skills by this author →
GitHub

create-stories

Generates story files from epic GED requirements and ADR decisions with QA-ready acceptance criteria.

Updated May 13, 2026
Search Tags:#game development#epic decomposition#story generation#qa readiness#gdd traceability#adr governance
One-click install
npx skills add https://github.com/FrancisVarga/the-dream-machine --skill create-stories-francisvarga
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-stories
Source: https://github.com/FrancisVarga/the-dream-machine/tree/main/.claude/skills/create-stories
Command: npx skills add https://github.com/FrancisVarga/the-dream-machine --skill create-stories-francisvarga

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents a single AI session from producing unstructured or untraceable game development work by converting an epic’s GDD and architecture decisions into small, implementable story files tied to requirements and ADRs.

Core Features & Use Cases

  • Epic-to-story decomposition with traceability: Breaks an epic into focused stories, each mapped to specific GDD acceptance criteria and TR-IDs for discovery and verification.
  • Architecture and risk alignment: Embeds governing ADR guidance (including engine compatibility and risk) so implementation follows approved patterns and engine constraints.
  • QA-ready story outputs: Produces story files that include required QA evidence instructions and, in appropriate review modes, coordinates gate-based QA readiness before writing.

Quick Start

Run create-stories for the epic "combat" with a lean review mode to generate production/epics/combat/story-NNN-slug.md files.

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 traceable stories?▼

Epic decomposition converts GDD requirements and ADR decisions into implementable story files mapped to acceptance criteria and TR-IDs, ensuring each story is traceable to its governing architecture decisions.

How do I generate QA-ready stories from game design documents?▼

Generating QA-ready stories from a GDD involves validating referenced ADR files, loading control manifest data, and running gate-based QA readiness checks to produce story files with embedded evidence instructions.

What is needed to break down epics in dependency order for game studio planning?▼

Breaking down epics in dependency order requires reading the EPIC.md, the epic GDD file, validating all referenced ADR files exist, and loading TR registry data before generating story files.

Can I align story implementation with engine compatibility and architecture risk?▼

Yes, story outputs embed governing ADR guidance including engine compatibility and risk factors so implementation follows approved patterns and respects engine constraints.

What's the best way to prepare game development epics for QA readiness?▼

The best way to prepare epics for QA readiness is running a lean review mode during story generation, which coordinates gate-based QA checks and produces story files with explicit evidence expectations.

Why does story generation require validating ADR files and loading control manifest data?▼

Story generation validates ADR files and loads control manifest data to ensure architecture and risk alignment, preventing unstructured work by tying each story to approved architectural decisions.

Related Skills

Explore More Software Engineering Skills→
polsegupolsegu

create-stories

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

Community
Advanced
emcconnellemcconnell

create-stories

Break epics into traceable story markdown files with QA test cases.

Community
Advanced
rakhnianskii9rakhnianskii9

architecture-decision

Document architectural decisions using a standardized ADR workflow.

Community
Advanced
MichaelSolatiMichaelSolati

create-stories

Decompose game development epics into traceable story files with QA test specifications.

Community
Advanced