Break epics into story files with TR-ID and ADR traceability.
npx skills add https://github.com/kay6198835/Game-RPG --skill create-stories-kay6198835
Please help me install this Agent Skill. Skill: create-stories Source: https://github.com/kay6198835/Game-RPG/tree/main/.claude/skills/create-stories Command: npx skills add https://github.com/kay6198835/Game-RPG --skill create-stories-kay6198835
Break a single epic into implementable story files by reading the epic, its GDD, governing ADRs, and the control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.
Run this skill after /create-epics for each epic to generate story files
High-intent search queries and answers about installing and using this skill.
To break epics into actionable stories, load the epic overview, governing ADRs, and control manifest. This validates ADR existence and maps each story to GDD requirements using TR-IDs, generating ready-to-implement story files.
The best way to ensure alignment is to validate ADR existence before decomposition. By embedding governing ADR guidance and GDD criteria directly into each generated story file, you guarantee full architectural traceability for implementation.
You map GDD requirement TR-IDs by loading the Game Design Document and control manifest during story generation. The skill automatically embeds the TR-ID, acceptance criteria, and test evidence path into each story file.
You need to generate story files from epics after creating epics and before story readiness checks. This workflow sequence ensures epics are fully decomposed into implementable tasks mapped to ADRs and GDDs prior to development.
No, you cannot generate production-ready stories without existing ADRs or GDDs. The process validates ADR existence and ensures GDD criteria alignment before producing any story files under the production/epics directory.
Automated story generation outputs ready-to-commit markdown files. These files are structured as story-NNN-[slug].md and placed under the production/epics/[epic-slug]/ directory to maintain organized implementation tracking.
easonlaoGenerate bounded epic definitions per architectural module from approved GDDs and ADRs.
CarlosQ96Validate story files for implementation readiness against GDD, ADR, and acceptance criteria.
Euraika-LabsDetect and report ADRs impacted by revised game design documents.
adolfoaranaes12Break down epics into user stories with acceptance criteria and sprint groupings.
