skills.rest
thilthpc01208
thilthpc01208COMMUNITY
Explore all skills by this author →
GitHub

create-stories

Break an epic into testable stories with aligned ADRs and TR-IDs.

Updated Aug 27, 2026
Search Tags:#automation#adr#story#epic#gdd#tr-id
One-click install
npx skills add https://github.com/thilthpc01208/Codex-Game-Studios --skill create-stories-thilthpc01208
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-stories
Source: https://github.com/thilthpc01208/Codex-Game-Studios/tree/main/.codex/skills/create-stories
Command: npx skills add https://github.com/thilthpc01208/Codex-Game-Studios --skill create-stories-thilthpc01208

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Break an epic into a structured set of implementable stories, enabling teams to plan, gate, and track progress from high-level goals to concrete tasks.

Core Features & Use Cases

  • Break epics into story-ready chunks aligned to GDDs, ADRs, and TR-IDs
  • Generate a predictable story sequence per epic and maintain traceability
  • Prepare outputs under production/epics/[epic-slug] for downstream steps

Quick Start

Break an epic into a series of implementable stories and save them under production/epics/[epic-slug]/story-001-[slug].md for downstream processing.

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 into testable stories with traceability?▼

Generating a predictable story sequence per epic involves loading the epic overview, GDD, governing ADRs, and control manifest. The Skill then emits structured story markdown files under production/epics/[epic-slug] to maintain traceability for downstream implementation.

How does story generation maintain traceability to ADRs and TR-IDs?▼

Maintaining traceability from GDD acceptance criteria to TR-IDs and ADR decisions requires loading the epic overview, GDD, and control manifest. This ensures the generated story sequence aligns with architectural decisions for downstream QA and implementation.

What is the best way to structure epic stories for downstream QA and implementation?▼

Structuring epic stories for downstream QA involves breaking epics into story-ready chunks aligned to GDDs, ADRs, and TR-IDs. The Skill generates a predictable story sequence saved under production/epics/[epic-slug]/story-001-[slug].md for downstream processing.

Do I need a GDD and control manifest to generate stories from an epic?▼

Generating stories from an epic requires loading the epic overview, GDD, governing ADRs, and the control manifest. These inputs allow the Skill to break the epic into story-ready chunks and maintain traceability from GDD acceptance criteria to TR-IDs.

Can I use this to generate a predictable story sequence for downstream processing?▼

Generating a predictable story sequence for downstream processing involves breaking an epic into story-ready chunks aligned to GDDs, ADRs, and TR-IDs. The Skill outputs these stories under production/epics/[epic-slug]/story-001-[slug].md for downstream processing.

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
polsegupolsegu

create-stories

Decompose game development epics into story files with QA test cases.

Community
Advanced
striderZAstriderZA
72

create-stories

Breaks an epic into story files with GDD and ADR traceability and QA gates.

Community
Advanced
cenconq25cenconq25
39

create-stories

Decompose an epic into story files with TR-ID references and ADR governance.

Community
Intermediate