skills.rest
solace-ill
solace-illCOMMUNITY
Explore all skills by this author →
GitHub

create-stories

Decompose project epics into implementable story files with ADR validation.

Updated Apr 26, 2026
Search Tags:#adr#epics#workflow-automation#gdd#story-decomposition#tr-registry
One-click install
npx skills add https://github.com/solace-ill/vector-flow --skill create-stories-solace-ill
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-stories
Source: https://github.com/solace-ill/vector-flow/tree/main/.claude/skills/create-stories
Command: npx skills add https://github.com/solace-ill/vector-flow --skill create-stories-solace-ill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams convert a single epic into a set of actionable, maintainable story files, ensuring traceability from GDD requirements to ADR guidance and test evidence paths.

Core Features & Use Cases

  • Breaks epics into focused stories aligned with GDD criteria and ADR decisions.
  • Reads epic overviews, design requirements, ADRs, and control manifest to ensure consistent story generation.
  • Outputs production-ready story files under production/epics/[epic-slug]/ with clear progression guidance for QA and development.

Quick Start

Provide the epic slug to begin breaking it into 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 project epics into implementable user stories?▼

Breaking down epics involves reading the epic overview, GDD requirements, and ADRs to generate traceable story files under production/epics/[epic-slug]/, ensuring alignment with design criteria and architectural decisions.

What is story decomposition in agile workflow automation?▼

Story decomposition splits a high-level epic into focused, implementable stories that embed TR-IDs, ADR guidance, acceptance criteria, and test evidence paths to drive appropriate QA gates.

Do I need ADR files created before generating stories from epics?▼

Yes, you need ADR files created beforehand. The story generation process validates ADR file existence before processing to ensure all architectural references are present and accurately embedded.

How does traceability from GDD requirements to test evidence paths work?▼

Traceability works by embedding each generated story with TR-IDs from the TR-registry, ADR guidance, acceptance criteria, and test evidence paths, linking high-level design requirements directly to QA validation.

Can I classify stories by type to drive specific QA gates?▼

Yes, you can classify stories by type during decomposition. The generated story files include a story type classification which drives appropriate QA gates and development progression guidance.

What is the best way to automate epic to story workflow generation?▼

The best way to automate this workflow is using a dedicated decomposition tool that reads the control manifest and epic overview to output production-ready story files with clear progression guidance.

Related Skills

Explore More Software Engineering Skills→
Euraika-LabsEuraika-Labs
14

dev-story

Read a story file and implement its feature with code and tests.

Official
Advanced
scomofoscomofo

create-stories

Creates SKILL.md summaries and a README for your repository's folders and files.

Community
Advanced
adolfoaranaes12adolfoaranaes12
2

breakdown-epic

Break down epics into user stories with acceptance criteria and sprint groupings.

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