skills.rest
johnatas-henrique
johnatas-henriqueCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

create-stories

Decompose game development epics into traceable stories with TR-IDs and acceptance criteria.

Updated Jul 16, 2026
Search Tags:#game development#epic breakdown#sprint planning#story decomposition#adr compliance#gdd traceability#qa test cases
One-click install
npx skills add https://github.com/johnatas-henrique/overdrive --skill create-stories-johnatas-henrique
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-stories
Source: https://github.com/johnatas-henrique/overdrive/tree/main/.opencode/skills/create-stories
Command: npx skills add https://github.com/johnatas-henrique/overdrive --skill create-stories-johnatas-henrique

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Game development teams often struggle to convert large, high-level epics into small, implementable developer stories that are fully traceable to design documents and architecture decisions, leading to misalignment, rework, and unclear completion criteria.

Core Features & Use Cases

  • Automated Story Decomposition: Splits epic acceptance criteria into sized, typed stories (Logic, Integration, Visual/Feel, UI, Config/Data) with clear implementation boundaries.
  • Full Requirement Traceability: Embeds GDD TR-IDs, governing ADR guidance, and control manifest rules directly into each story to ensure alignment with project standards.
  • QA-Ready Output: Integrates with QA leads to generate pre-defined test cases for each story, eliminating ambiguity about what "done" looks like for developers.
  • Use Case: For a 90s F1 racing game epic covering "car physics", this skill generates individual stories for each physics requirement, each with linked test specs, ADR implementation notes, and dependency tracking.

Quick Start

Invoke the create-stories skill with your target epic slug to generate fully traceable, QA-ready dev stories aligned to your game's GDD and architecture decisions.

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 game development epics into actionable developer stories?▼

To break down game development epics into actionable stories, you can use automated story decomposition to split epic acceptance criteria into sized, typed stories like Logic, Integration, Visual, UI, or Config/Data with clear implementation boundaries.

What is the best way to ensure story traceability to GDD requirements and ADRs?▼

Ensuring story traceability to GDD requirements and ADRs involves embedding GDD TR-IDs, governing ADR implementation guidance, and control manifest rules directly into each generated story file to maintain alignment with project standards.

How do I generate QA test cases during sprint planning for game systems?▼

Generating QA test cases during sprint planning is achieved by integrating story decomposition with QA workflows to produce pre-defined test cases for each story, eliminating ambiguity about completion criteria for developers.

Can I use automated story decomposition for complex game physics epics?▼

Automated story decomposition supports complex game physics epics by generating individual stories for each physics requirement, complete with linked test specs, ADR implementation notes, and dependency tracking.

Does epic decomposition work without existing architecture decision records?▼

Epic decomposition is specifically designed for structured workflows utilizing GDDs and ADRs. Without existing architecture decision records, the generated stories will lack the embedded ADR implementation guidance needed for consistent implementation.

Why do my game developer stories lack clear completion criteria?▼

Game developer stories often lack clear completion criteria when they are not decomposed with embedded QA test cases. Generating stories with pre-defined test specs eliminates ambiguity about what done looks like for developers.

Related Skills

Explore More Software Engineering Skills→
adolfoaranaes12adolfoaranaes12
2

breakdown-epic

Break down epics into user stories with acceptance criteria and sprint groupings.

Community
Advanced
levnikolaevichlevnikolaevich
534

ln-221-story-creator

Generate 8-section Story documents from IDEAL plans and export to Linear.

Community
Advanced
emcconnellemcconnell

story-done

Verifies completed stories' acceptance criteria, design consistency, and prepares completion reports.

Community
Advanced
MichaelSolatiMichaelSolati

create-stories

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

Community
Advanced