gds-create-story

Generates comprehensive developer-ready story files from epics, architecture, and sprint status.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/ArchaonHW/MingGoRTS --skill gds-create-story-archaonhw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gds-create-story
Source: https://github.com/ArchaonHW/MingGoRTS/tree/main/.agents/skills/gds-create-story
Command: npx skills add https://github.com/ArchaonHW/MingGoRTS --skill gds-create-story-archaonhw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents LLM developer mistakes such as reinventing existing code, using wrong libraries, breaking regressions, and vague implementations by producing a story file containing all context a dev agent needs for implementation. ## Core Features & Use Cases - Story Discovery: Auto-detects the next backlog story from sprint-status.yaml or accepts an explicit epic-story identifier like 2-4. - Exhaustive Context Analysis: Loads epics, GDD, architecture, UX docs, project-context rules, previous story learnings, and git history to build developer guardrails. - Quality Validation: Validates the generated story against a competitive review checklist and updates sprint status to ready-for-dev. - Use Case: A game development team using the BMAD method asks the agent to create the next story; the skill analyzes all planning artifacts and outputs a complete implementation guide for the dev agent. ## Quick Start Ask the agent to create the next story, or specify a story such as "create story 2-4", and it will generate the full story file in the implementation artifacts folder.

Frequently Asked Questions about gds-create-story

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

FAQPage Schema
How do I create the next story from my sprint backlog?

Run the create-story workflow with no arguments and it reads sprint-status.yaml, finds the first story with backlog status, and generates the story file automatically. You can also pass an explicit epic-story number like 2-4.

What documents does the story creation workflow analyze?

It loads the epics file, GDD, architecture document, UX design, and project-context.md from the planning artifacts folder. It also reads the previous story's dev notes and recent git commits when available.

Can I customize the create-story workflow behavior?

Yes, customize.toml supports activation steps, persistent facts, and an on_complete hook. Team and user override files under _bmad/custom merge with the defaults using structural merge rules.

What happens if no sprint status file exists?

The workflow halts and asks you to either run sprint-planning first to initialize sprint-status.yaml, provide an explicit epic-story number, or supply a path to story documents.

How is the generated story validated before development?

The workflow validates the story file against checklist.md, which re-analyzes all source documents to find critical omissions, enhancement opportunities, and LLM optimization improvements before marking the story ready-for-dev.