create-stories

Break epics into auditable stories with TR-ID and ADR references.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/rakhnianskii9/God-Godot --skill create-stories-rakhnianskii9
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-stories
Source: https://github.com/rakhnianskii9/God-Godot/tree/main/.github/skills/create-stories
Command: npx skills add https://github.com/rakhnianskii9/God-Godot --skill create-stories-rakhnianskii9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Breaks down large epics into manageable, auditable stories aligned with GDD requirements and ADR governance.

Core Features & Use Cases

  • Converts epics into discrete, traceable stories mapped to TR-IDs and ADR decisions.
  • Automatically suggests story types and governance notes to streamline planning.
  • Updates production/epics documentation and prepares ready-to-write story files.

Quick Start

Run this skill for each epic to generate production/epics/story files and update the epic documentation.

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 actionable stories for project management?▼

To break epics into actionable stories, you need to decompose large production epics into discrete, traceable stories mapped to GDD requirements and ADR governance. This process ensures each story includes TR-ID references and ADR-derived implementation notes for full auditability.

How do I generate stories aligned with GDD requirements and ADR governance?▼

Generating stories aligned with GDD requirements and ADR governance involves converting production epics into concrete story files. Each generated story automatically includes TR-ID references, relevant ADR decisions, and governance notes to streamline the planning and QA process.

What is the best way to map TR-ID references and ADR decisions to epic stories?▼

The best way to map TR-ID references and ADR decisions to epic stories is by using a dedicated story-generation workflow that automatically suggests story types and extracts ADR-derived implementation notes, ensuring every story is traceable to specific governance decisions.

Does this story-generation workflow work for the God-Godot pipeline?▼

Yes, this story-generation workflow is specifically designed for production epics in the God-Godot pipeline. It is built to be used during the story-writing phase and evaluated by the QA lead gate to ensure all generated stories meet project governance requirements.

How do I update epic documentation after creating actionable stories?▼

To update epic documentation after creating actionable stories, run the story-generation skill for each epic. It automatically prepares ready-to-write story files and updates the existing production/epics documentation to reflect the newly generated, auditable stories.

Why include ADR-derived implementation notes when breaking down epics?▼

Including ADR-derived implementation notes when breaking down epics ensures architectural decisions are enforced during the story-writing phase. It provides the QA lead gate with auditable governance criteria, verifying that each story aligns with established architecture decision records.