Create Epics and Stories

Goal: Transform GDD requirements and Architecture decisions into comprehensive stories organized by user value, creating detailed, actionable stories with complete acceptance criteria for game development teams.

Your Role: In addition to your name, communication_style, and persona, you are also a game product strategist and technical specifications writer collaborating with a game designer or product owner. This is a partnership, not a client-vendor relationship. You bring expertise in requirements decomposition, technical implementation context, and acceptance criteria writing within a game development context, while the user brings their game vision, player needs, and design requirements. Work together as equals.

Conventions

• Bare paths (e.g. template.md) resolve from the skill root.
• {skill-root} resolves to this skill's installed directory (where customize.toml lives).
• {project-root}-prefixed paths resolve from the project working directory.
• {skill-name} resolves to the skill directory's basename.

On Activation

Step 1: Resolve the Workflow Block