create-stories

Convert an epic and GDD acceptance criteria into traceable story markdown files.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/WindXRan/y3td --skill create-stories-windxran
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-stories
Source: https://github.com/WindXRan/y3td/tree/main/.claude/skills/create-stories
Command: npx skills add https://github.com/WindXRan/y3td --skill create-stories-windxran

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a large epic/GDD into small, implementable, fully traceable story files so teams can plan and execute without losing architectural decisions or acceptance-criteria coverage.

Core Features & Use Cases

  • Epic-to-stories decomposition: Reads an epic’s GDD requirements and groups acceptance criteria into focused stories with clear ordering.
  • Traceability and governance: Embeds TR-IDs from the TR registry and links governing ADRs (including BLOCKED handling for Proposed ADRs).
  • QA readiness scaffolding: Coordinates QA-lead assessment, optionally imports an existing QA plan, and generates embedded QA test cases (automated vs manual) for developer execution guidance.

Quick Start

Run the skill to break an epic into stories by calling /create-stories combat and approving the generated story files.

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 an epic and GDD acceptance criteria into implementable story files?

To break down an epic into implementable story files, this Skill reads the epic's GDD requirements, classifies story types, and groups acceptance criteria into focused, ordered markdown files with embedded traceability.

How do I add traceability for architectural decisions and TR-IDs when generating story files?

Adding traceability for story files involves embedding TR-IDs from the TR registry and linking governing ADRs, which includes validating ADR file existence and handling BLOCKED statuses for Proposed ADRs.

Can I generate QA test cases alongside story files for a controlled development workflow?

Yes, you can generate QA test cases by coordinating a QA-lead assessment, optionally importing an existing QA plan, and embedding automated versus manual test evidence requirements directly into the story files.

What inputs do I need to decompose a game project epic into traceable markdown stories?

Decomposing a game project epic requires loading the epic, the design GDD, governing ADRs, and a control manifest to validate architectural decisions and ensure proper story generation.

Does epic-to-story decomposition work for game project planning with ADR governance?

Yes, epic-to-story decomposition is specifically designed for game project planning where each story must be mapped to TR-IDs and governed by ADR decisions for controlled development workflows.

What is the best way to structure story files so they retain acceptance-criteria coverage and architectural decisions?

The best way to structure story files is to write production markdown files with clear ordering, embed TR-IDs and governing ADR links, and update epic and index metadata for full traceability.