skills.rest
CarlosQ96
CarlosQ96COMMUNITY
Explore all skills by this author →
GitHub

create-stories

Break epics into implementable story files with acceptance criteria and ADR guidance.

Updated Apr 9, 2026
Search Tags:#automation#workflow#qa#adr#story#epic#gdd
One-click install
npx skills add https://github.com/CarlosQ96/robot-crawler --skill create-stories
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-stories
Source: https://github.com/CarlosQ96/robot-crawler/tree/main/.agents/skills/create-stories
Command: npx skills add https://github.com/CarlosQ96/robot-crawler --skill create-stories

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Break down an epic into actionable, implementable stories that engineers can execute from GDD and ADR guidance.

Core Features & Use Cases

  • Reads epics, GDDs, governing ADRs, and the control manifest to surface actionable stories.
  • Embeds GDD requirements, ADR guidance, acceptance criteria, story type, and test evidence paths into each story.
  • Outputs structured story files at production/epics/[epic-slug]/story-NNN-[slug].md after running /create-stories.

Quick Start

Run /create-stories [epic-slug] to begin turning an epic into implementable, ready-to-code stories.

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 actionable user stories for engineering?▼

Breaking down an epic involves decomposing it into ready-to-code story files using architecture-driven workflows. The process reads the epic, its GDD, governing ADRs, and control manifest to produce structured, implementable stories for engineering execution.

How do I enforce traceability when creating stories from epics?▼

Enforcing traceability when creating stories involves embedding TR-ID, ADR guidance, acceptance criteria, story type, and test evidence paths directly into each story file. This ensures every story maps back to its epic and architectural decisions.

Do I need architecture decision records before generating stories from epics?▼

Yes, ADRs are required before generating stories. The workflow validates ADR presence before story creation to ensure that each story receives the necessary architecture decision guidance for implementation.

What is the best way to convert epics into ready-to-implement stories for QA?▼

The best way to convert epics into ready-to-implement stories is by reading the epic alongside its GDD, ADRs, and control manifest to output structured story files. These files embed acceptance criteria and test evidence paths for QA validation.

How are generated story files structured and where are they saved?▼

Generated story files are saved as structured markdown at production/epics/[epic-slug]/story-NNN-[slug].md. Each file embeds GDD requirements, ADR guidance, acceptance criteria, story type, and test evidence paths for engineering reference.

Can I generate stories from an epic without a Game Design Document?▼

Generating stories relies on reading the GDD alongside ADRs and the control manifest to embed requirements. Without the GDD, the workflow cannot surface the necessary requirements and acceptance criteria for ready-to-code story files.

Related Skills

Explore More Software Engineering Skills→
rakhnianskii9rakhnianskii9

create-epics

Translate approved GDDs and architecture into one epic per architectural module.

Community
Advanced
dnkrowdnkrow
1

qa-plan

Generate QA test plans from sprint, feature, or story scopes.

Community
Advanced
solace-illsolace-ill

story-done

Validate acceptance criteria, surface DoD and ADR deviations, and update story status to Complete.

Community
Advanced
LucaDeLeoLucaDeLeo
1

bmad-bmm-create-epics-and-stories

Decompose natural-language project goals into epics and user stories with acceptance criteria.

Community
Intermediate