gds-create-story

Generate a ready-for-dev story file from epics, GDD, architecture, and UX inputs.

212|23|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/bmad-code-org/bmad-module-game-dev-studio --skill gds-create-story-bmad-code-org
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gds-create-story
Source: https://github.com/bmad-code-org/bmad-module-game-dev-studio/tree/main/src/workflows/4-production/gds-create-story
Command: npx skills add https://github.com/bmad-code-org/bmad-module-game-dev-studio --skill gds-create-story-bmad-code-org

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill orchestrates the creation of a complete "story" document for the BMad Method, ensuring the dev agent has all context, guardrails, and artifacts needed to implement a story flawlessly.

Core Features & Use Cases

  • Automated story generation: synthesizes epics, GDD, architecture, UX, and project context into a single ready-to-use file.
  • Guardrails and guard contexts: embeds developer guardrails, project conventions, and historical learnings to prevent mistakes.
  • End-to-end guidance: includes dev notes, previous story learnings, and latest technical details to enable rapid development.
  • Use Case: A team wants a single, production-grade story file to drive implementation across Unity/Unreal/Godot engines with consistent standards.

Quick Start

Provide a target epic-story identifier and request generation of a ready-for-dev story file.

Frequently Asked Questions about gds-create-story

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

FAQPage Schema
How do I generate a ready-for-dev story file from epics and architecture docs?

To generate a ready-for-dev story file, provide a target epic-story identifier and the skill synthesizes epics, GDD, architecture, UX, and project context into a single ready-to-use document with embedded guardrails and developer context.

What is automated story generation for dev automation workflows?

Automated story generation is the process of synthesizing project context, architecture, and UX inputs into a complete ready-for-dev story file that guides implementation with embedded guardrails and historical learnings.

How do I ensure developer guardrails and project context are included in implementation artifacts?

Include developer guardrails and project context by generating story files that automatically embed project conventions, historical learnings, and technical details to prevent implementation mistakes and ensure consistency.

Can I use auto-generated story guides for game development across different engines?

Yes, auto-generated story guides produce production-grade story files designed to drive implementation across Unity, Unreal, and Godot engines with consistent standards and project context rules.

What do I need to provide to create a complete story document for implementation?

You need to provide a target epic-story identifier and have existing epics, GDD, architecture, UX, and project context available for synthesis into the complete story document.

What's the best way to maintain consistency across multiple dev-story files in a project?

The best way to maintain consistency is to auto-generate each story file by synthesizing the same project context, architecture, and GDD inputs, ensuring all stories share identical guardrails and conventions.