create-stories

Breaks an epic into story files with GDD and ADR traceability and QA gates.

72|7|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/striderZA/OpenCodeGameStudios --skill create-stories-striderza
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-stories
Source: https://github.com/striderZA/OpenCodeGameStudios/tree/main/.opencode/skills/create-stories
Command: npx skills add https://github.com/striderZA/OpenCodeGameStudios --skill create-stories-striderza

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It converts a single large epic into smaller, traceable story files so developers can implement work in focused, GDD/ADR-aligned sessions with clear acceptance criteria and QA evidence paths.

Core Features & Use Cases

  • Epic-to-stories decomposition: Reads the epic overview, the epic’s GDD, governing ADRs, and the control manifest, then generates story files in the required production/epics/[epic-slug]/ structure.
  • Traceability by design: Each story embeds the specific GDD requirement TR-ID, links to governing ADR guidance, and includes acceptance criteria and test evidence expectations.
  • Gate-based readiness workflow: Applies review-mode rules and spawns a QA lead readiness gate before writing story files, with blocked/proposed ADR handling.
  • Outputs for the next step: Prepares stories for downstream /story-readiness and /dev-story execution without starting implementation.

Quick Start

Run create-stories for the epic “combat” by issuing the command: /create-stories combat.

Frequently Asked Questions about create-stories

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

FAQPage Schema
How do I decompose a game development epic into implementable story files?

Epic decomposition breaks a single epic into smaller, traceable story files by parsing the epic overview, GDD sections, and governing ADRs, generating story-NNN-[slug].md files with full traceability to acceptance criteria and ADR decisions.

How does story generation maintain traceability to GDD requirements and ADR decisions?

Story generation maintains GDD traceability by embedding the specific GDD requirement TR-ID and linking to governing ADR guidance within each story file, validating that referenced ADR files exist before writing.

What is the best way to generate stories in the correct dependency order from an EPIC.md file?

Generating stories in the correct dependency order requires applying control-manifest rules to parse the EPIC.md file, classifying story types, and sequencing the output story-NNN-[slug].md files according to the established production workflow.

Do I need a QA readiness gate before writing story files during workflow planning?

Yes, a QA readiness gate is required before writing story files; the workflow applies review-mode rules and spawns a QA lead readiness gate, handling blocked or proposed ADRs to ensure production readiness.

Can I start implementation immediately after generating story files from an epic?

No, story file generation prepares stories for downstream /story-readiness and /dev-story execution by outputting acceptance criteria and test evidence expectations, but it does not start implementation itself.

What limitations apply when creating stories from epics with missing ADR files?

Creating stories requires validating that referenced ADR files exist; missing ADRs trigger blocked or proposed ADR handling within the gate-based readiness workflow, preventing story file generation until governance is resolved.