skills.rest
wsman
wsmanCOMMUNITY
Explore all skills by this author →
GitHub

create-stories

Break an epic into ordered story files with traceable requirements and governance context.

18|5|Updated Nov 25, 2025
Search Tags:#requirements traceability#adr#cdd#epic decomposition#story generation#qa gating
One-click install
npx skills add https://github.com/wsman/MY-DOGE-MICRO --skill create-stories-wsman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-stories
Source: https://github.com/wsman/MY-DOGE-MICRO/tree/main/.agents/skills/create-stories
Command: npx skills add https://github.com/wsman/MY-DOGE-MICRO --skill create-stories-wsman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a single epic into a clear set of implementable story files, reducing architectural ambiguity and making work ready for development.

Core Features & Use Cases

  • Epic Decomposition: Splits one epic into smaller stories in dependency order so teams can build in the right sequence.
  • Traceable Story Writing: Captures each story’s CDD requirement, governing ADR, story type, and test evidence path for auditability.
  • Review Workflow Support: Checks referenced ADRs, prepares QA-ready acceptance criteria, and updates the epic’s story table.

Quick Start

Use the create-stories skill to break the specified epic into story files and update its epic document.

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 implementable development stories?▼

Epic decomposition breaks a single epic into smaller story files arranged in dependency order. This workflow captures each story's CDD requirement, governing ADR, and test evidence path to ensure work is build-ready and auditable.

How do I add requirements traceability to generated user stories?▼

Requirements traceability is added to user stories by embedding TR-IDs, CDD requirements, and governing ADRs directly into each story file. This ensures every generated story maintains a clear link to its architectural and product governance context.

What do I need before generating build-ready stories from an epic?▼

Generating build-ready stories requires reading the epic, its CDD, governing ADRs, and control manifest. These documents provide the TR-IDs, architectural context, and governance constraints needed to produce traceable story files.

Does epic decomposition support QA gating and acceptance criteria?▼

Epic decomposition supports QA gating by preparing QA-ready acceptance criteria and defining test evidence paths for each story. It checks referenced ADRs to ensure generated stories meet governance and quality standards before development.

Can I update the epic document automatically after story generation?▼

Yes, you can update the epic document automatically after story generation. The workflow updates the epic's story table to reflect the newly created, ordered story files, maintaining synchronization between the epic and its decomposed stories.

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
DKSangDKSang
2

des-dev-task-breakdown

Convert ready implementation stories into ordered developer tasks with acceptance criteria and tests.

Community
Intermediate
wsmanwsman
18

create-epics

Generate epics from CDDs and architecture artifacts with ADR alignment and requirement tracing.

Community
Advanced
epieczkoepieczko

story.write

Convert decomposed epic items into formatted user story Markdown files.

Community
Intermediate