create-story

Generate implementation-ready development story Markdown files with acceptance criteria.

Updated Aug 23, 2026

Search Tags:#automation #planning #epics #docs #game-design #story-generation

Ready to run

npx skills add https://github.com/igot-ai/os-twin --skill create-story-igot-ai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-story
Source: https://github.com/igot-ai/os-twin/tree/main/.agents/skills/roles/game-designer/create-story
Command: npx skills add https://github.com/igot-ai/os-twin --skill create-story-igot-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating a consistent, implementation-ready development story from epic guidance, ensuring teams have a single source of truth for acceptance criteria and context.

Core Features & Use Cases

Generate a complete story document with epic reference, story metadata, and acceptance criteria.
Ingest contextual artifacts from existing epics, GDD, UX design, and architecture notes to maintain alignment.
Output ready-to-run story files at .output/planning/stories/E{N}-{N}-{title}.md for immediate handoff to engineers and planners.

Quick Start

Run the skill to generate the next ready-for-dev story file for the current epic.

Frequently Asked Questions about create-story

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

FAQPage Schema

How do I generate implementation-ready development stories from epics?▼

You can auto-generate complete dev stories by ingesting contextual artifacts from your epics, GDD, UX, and architecture documents. This produces an implementation-ready Markdown file containing epic references, story metadata, and acceptance criteria.

What is the best way to maintain consistent acceptance criteria across game design stories?▼

Maintaining consistent acceptance criteria across game design stories requires applying standardized epic-to-story templates. By automatically wiring in guidance from your GDD, UX, and architecture documents, you ensure a single source of truth for your engineering team.

How do I automate the creation of Markdown story files for engineering handoff?▼

Automating Markdown story files for engineering handoff involves processing your design docs to output ready-to-run files. The generated Markdown includes story metadata and acceptance criteria, formatted at .output/planning/stories/E{N}-{N}-{title}.md for immediate use.

Does this story generation tool work with GDD and UX design documents?▼

Yes, story generation works directly with GDD and UX design documents. The tool ingests these contextual artifacts alongside architecture notes and epic guidance to maintain alignment and populate the complete development story file.

Can I use auto-generated dev stories for rapid engineering team handoff?▼

Yes, you can use auto-generated dev stories for rapid engineering team handoff. The process produces implementation-ready story files containing full context and acceptance criteria, allowing engineers and planners to bypass manual document assembly.

What format are the generated development stories saved in?▼

Generated development stories are saved as Markdown files at the path .output/planning/stories/E{N}-{N}-{title}.md. This specific file structure ensures the implementation-ready stories are organized and accessible for engineers and planners.