skills.rest
scomofo
scomofoCOMMUNITY
Explore all skills by this author →
GitHub

create-stories

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

Updated Mar 28, 2026
Search Tags:#epics#traceability#markdown generation#story decomposition#architecture decision records#qa gates#godot project
One-click install
npx skills add https://github.com/scomofo/dragon-forge --skill create-stories-scomofo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-stories
Source: https://github.com/scomofo/dragon-forge/tree/main/.agents/skills/create-stories
Command: npx skills add https://github.com/scomofo/dragon-forge --skill create-stories-scomofo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the manual, error-prone work of translating an epic and its technical requirements into small, traceable story files that engineers can start implementing immediately.

Core Features & Use Cases

  • Epic-to-story decomposition: Breaks an epic into focused, implementable stories ordered for dependency flow.
  • Traceability and governance: Embeds GDD TR-IDs, acceptance criteria, governing ADR guidance (including Proposed/Blocked handling), and control-manifest rules into each story file.
  • QA-ready output: Coordinates a QA lead readiness gate and embeds required QA test cases into logic/integration stories (automated spec format) or manual verification steps (UI/visual/feel).

Quick Start

Use the create-stories skill to decompose epic combat into ready-to-review story files under production/epics/combat by running the command with the epic slug.

Frequently Asked Questions about create-stories

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decompose an epic into implementable stories with traceability?▼

Epic decomposition breaks an epic into ordered, implementable story markdown files by validating governing ADRs, embedding TR-IDs from tr-registry.yaml, and writing to production/epics/[epic-slug]/ with acceptance criteria and QA gates.

What is the best way to generate QA-ready markdown stories from a game design document?▼

Generating QA-ready stories involves classifying story types from acceptance criteria risk, embedding automated spec test cases for logic stories, and spawning the QA lead readiness gate QL-STORY-READY in full mode.

How does story decomposition handle architecture decision records and blocked proposals?▼

Story decomposition handles ADRs by validating referenced ADR file existence and embedding governing ADR guidance directly into each story file, including specific instructions for Proposed or Blocked ADR statuses.

Does epic-to-story generation work for Godot projects using a control manifest?▼

Epic-to-story generation applies to production workflows using a Godot project's control manifest and GDD, optionally supporting review-mode overrides to classify stories and validate QA gate readiness.

Why do my generated story files fail the QA readiness gate?▼

Generated story files fail the QA readiness gate when acceptance criteria risk classification is incomplete, required ADR file references are missing, or TR-IDs from tr-registry.yaml are not properly embedded.

When do I need to generate traceable story files with embedded TR-IDs?▼

You need to generate traceable story files when translating an epic and its technical requirements into small, implementable units for engineers, ensuring dependencies flow correctly and governance rules from the control manifest are applied.

Related Skills

Explore More Software Engineering Skills→
epieczkoepieczko

story.write

Convert decomposed epic items into formatted user story Markdown files.

Community
Intermediate
scomofoscomofo

dev-story

Implement sprint stories into production code with required automated tests.

Community
Advanced
polsegupolsegu

create-stories

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

Community
Advanced
adolfoaranaes12adolfoaranaes12
2

breakdown-epic

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

Community
Advanced