skills.rest
Negentropy-Laby
Negentropy-LabyOFFICIAL
Explore all skills by this author →
GitHub

create-stories

Convert epics into story files with CDD TR-IDs and ADR guidance.

3|Updated Jun 3, 2026
Search Tags:#automation#workflow#adr#story#gates#cdd#epic
One-click install
npx skills add https://github.com/Negentropy-Laby/Constitution-Driven-Development --skill create-stories-negentropy-laby
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-stories
Source: https://github.com/Negentropy-Laby/Constitution-Driven-Development/tree/main/.agents/skills/create-stories
Command: npx skills add https://github.com/Negentropy-Laby/Constitution-Driven-Development --skill create-stories-negentropy-laby

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Break a single epic into implementable story files. Reads the epic, its CDD, governing ADRs, and control manifest. Each story embeds its CDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.

Core Features & Use Cases

  • Break epics into discrete stories that map to CDD requirements and ADR decisions.
  • Generate production-ready story files under production/epics/[epic-slug]/, with metadata for TR-IDs and testing paths.
  • Enforce gating and traceability by capturing ADR guidance and control manifest constraints.

Quick Start

Invoke /create-stories [epic-slug | epic-path] to generate ready-to-write story files for that epic.

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 executable software stories?▼

To break epics into executable software stories, you decompose an epic into ready-to-write story files linked to CDD requirements and governing ADRs. Each story embeds TR-ID mappings, acceptance criteria, and test evidence paths under production/epics/[epic-slug]/.

How do I map ADR decisions and CDD requirements to individual user stories?▼

Mapping ADR decisions and CDD requirements to user stories involves generating story files that embed CDD requirement TR-IDs and ADR guidance. This enforces gating and traceability across software governance workflows from concept to QA.

What is the best way to enforce gating and traceability when decomposing epics?▼

Enforcing gating and traceability when decomposing epics requires capturing ADR guidance and control manifest constraints within each story file. This ensures alignment with the control manifest and TR registry throughout implementation.

Do I need an existing control manifest and epic files to generate story files?▼

Yes, you need existing control manifest and epic files to generate story files. The process reads the epic, its CDD, governing ADRs, and control manifest to output production-ready stories under production/epics/[epic-slug]/ with proper metadata.

Can I automate workflow story generation for memory_bank artifacts across teams?▼

Yes, you can automate workflow story generation for memory_bank artifacts across teams. The workflow applies to software governance processes where epics are decomposed from concept to QA and gate checks with traceable test evidence paths.

Why are my generated stories missing TR-ID mappings and acceptance criteria?▼

Generated stories missing TR-ID mappings and acceptance criteria indicate a failure to read the CDD and governing ADRs properly. Ensure the epic path correctly links to the control manifest and TR registry before decomposition.

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
CarlosQ96CarlosQ96

create-stories

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

Community
Advanced
cenconq25cenconq25
39

create-epics

Transform approved PRDs and architecture into Epic artifacts with TR-ID grouping.

Community
Advanced
wsmanwsman
18

create-stories

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

Community
Advanced