create-stories

Decompose game-development epics into implementable story files with requirements and acceptance criteria.

47|12|Updated Jun 14, 2026
One-click install
npx skills add https://github.com/nuoyanruoshui/GodotGameFramework --skill create-stories-nuoyanruoshui
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-stories
Source: https://github.com/nuoyanruoshui/GodotGameFramework/tree/main/Godot/.claude/skills/create-stories
Command: npx skills add https://github.com/nuoyanruoshui/GodotGameFramework --skill create-stories-nuoyanruoshui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill transforms a large game-development epic into focused, implementable stories while preserving traceability to GDD requirements, architecture decisions, control-manifest rules, and QA evidence.

Core Features & Use Cases

  • Epic Decomposition: Breaks acceptance criteria into appropriately sized stories ordered by dependency and implementation priority.
  • Traceability and Governance: Links each story to stable requirement IDs, governing ADRs, engine risks, control-manifest rules, and implementation guidance.
  • QA Readiness: Classifies story types and produces automated test specifications or manual verification steps appropriate to each type.
  • Workflow Integration: Updates epic and project indexes, validates referenced ADRs, supports review modes, and guides the next readiness and implementation steps.
  • Use Case: For a Godot game epic such as combat, use this Skill to create a complete set of dependency-ordered stories with acceptance criteria, test evidence requirements, and architecture guidance ready for development.

Quick Start

Run the create-stories skill for an epic slug or epic path, optionally specifying full, lean, or solo review mode.

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 a Godot game development epic into implementable stories?

Epic decomposition for Godot projects breaks large features into ordered, implementable stories with acceptance criteria, architecture guidance, and test evidence. This process uses GDDs and ADRs to maintain dependency priority and traceability.

How do I link game development stories to GDD requirements and architecture decisions?

Linking stories to GDD requirements and ADRs involves mapping stable requirement IDs and validating referenced architecture decisions within each story. This governance ensures traceability to control-manifest rules and engine risks throughout implementation.

What is the best way to generate QA test specifications for game development stories?

Generating QA test specifications for game stories requires classifying story types first, then producing automated test specs or manual verification steps appropriate to each. This classification ensures accurate test evidence and readiness for development.

Can I use epic planning files and traceability registries to manage story dependencies?

Yes, epic planning files and traceability registries can manage story dependencies by updating project indexes and validating referenced ADRs. This structured workflow integration ensures ordered implementation and tracks readiness across the project.

Do I need ADRs and control manifests to decompose game epics into test-ready stories?

ADRs and control manifests are required to decompose epics into test-ready stories, as they provide architecture decisions and governance rules. Validating these references ensures stories contain accurate implementation guidance and QA evidence.