create-stories

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

Updated Jul 22, 2025
One-click install
npx skills add https://github.com/MichaelSolati/mkai --skill create-stories-michaelsolati
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-stories
Source: https://github.com/MichaelSolati/mkai/tree/main/profiles/game-dev/skills/create-stories
Command: npx skills add https://github.com/MichaelSolati/mkai --skill create-stories-michaelsolati

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually breaking down game development epics into small, implementable stories is time-consuming and often leads to missing critical traceability to GDD requirements, architectural decisions, and QA test coverage, causing rework and implementation delays.

Core Features & Use Cases

  • Automated Story Decomposition: Breaks epic GDD acceptance criteria into properly sized, typed stories (Logic, Integration, Visual/Feel, UI, Config/Data) aligned with development sprint capacity.
  • Full Traceability Embedding: Each story includes links to its source GDD requirement, governing ADR guidance, acceptance criteria, and required test evidence paths.
  • QA Integration: Enforces QA readiness gates, integrates existing QA plans to avoid duplicate work, and auto-generates test case specifications for logic and integration stories.
  • Use Case: For a game combat epic, this skill generates individual stories for each core mechanic, each tagged with the relevant GDD requirement ID, ADR implementation guidance, and pre-defined test cases for developers to implement against.

Quick Start

Use the create-stories skill to break the combat epic into implementable, traceable story files for your game development team.

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

Automated story decomposition breaks epic acceptance criteria into properly sized, typed stories like Logic, Integration, Visual, UI, and Config/Data aligned with sprint capacity. This ensures each story is correctly typed and sized for development.

What is story traceability in agile game development workflows?

Story traceability links individual stories back to source GDD requirements, governing ADR guidance, and required test evidence paths. This strict mapping prevents missing critical requirements and reduces implementation rework.

How do I generate QA test cases for logic and integration stories?

Generating QA test cases for logic and integration stories requires enforcing QA readiness gates and auto-generating test case specifications. This integrates existing QA plans to avoid duplicate work and ensures developers have pre-defined tests.

Does story decomposition support ADR validation for game mechanics?

Story decomposition supports ADR validation by embedding governing architectural decision records directly into each story file. This ensures implementation guidance for game mechanics aligns with established architectural decisions.

Can I use automated story decomposition for game combat epics?

Automated story decomposition works for game combat epics by generating individual stories for each core mechanic. Each story is tagged with relevant GDD requirement IDs, ADR implementation guidance, and pre-defined test cases.

What are the limitations of manual epic breakdown in game development?

Manual epic breakdown in game development is time-consuming and often leads to missing critical traceability to GDD requirements and QA test coverage. This lack of automated enforcement ultimately causes implementation delays and rework.