create-stories

Break epics into implementable stories from GDD, ADRs, and control manifests.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/packetalien/cursor-game-studios --skill create-stories-packetalien
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-stories
Source: https://github.com/packetalien/cursor-game-studios/tree/main/.cursor/skills/create-stories
Command: npx skills add https://github.com/packetalien/cursor-game-studios --skill create-stories-packetalien

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Break epics down into concrete, implementable stories by outlining GDD requirements, governing ADRs, and control manifests, so teams can plan and track delivery with clear dependencies.

Core Features & Use Cases

  • Converts high-level epics into discrete story units aligned to TR-IDs and ADR decisions
  • Reads epic-level design docs and ADRs to generate traceable work items
  • Supports gating, QA readiness, and artifact generation as part of the workflow

Quick Start

Run /create-stories for your chosen epic to generate foundational story files ready for review.

Frequently Asked Questions about create-stories

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

FAQPage Schema
How do I break epics into developer-ready stories?

To break epics into developer-ready stories, this skill reads your epic's GDD, ADRs, and control manifest to generate production-ready story files. It converts high-level requirements into discrete, traceable work items mapped to TR-IDs.

What is the best way to map project stories to TR-IDs and ADR decisions?

Mapping project stories to TR-IDs and ADR decisions requires aligning generated story files with governing ADRs and control manifests. This skill enforces gating, QA readiness, and artifact generation rules to maintain traceability across epics.

Do I need a GDD and control manifest before generating stories?

You need an epic-level Game Design Document (GDD), governing ADRs, and a control manifest before generating stories. The skill reads these foundational artifacts to produce traceable, testable tasks that conform to project conventions.

How does story generation handle QA readiness and gating?

Story generation handles QA readiness and gating by applying the phase workflow and project conventions defined in the skill. It ensures generated story files meet production-ready gating requirements before developers begin implementation.

Can I convert high-level epics into testable tasks across multiple epics?

You can convert high-level epics into testable tasks across multiple epics by reading epic-level design docs and ADRs. The skill produces traceable work items that enforce artifact generation rules defined by the phase workflow.