dev-story

Load story context, route to programmer agents, and implement code with tests.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/polsegu/Claude-Code-Game-Dev --skill dev-story-polsegu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-story
Source: https://github.com/polsegu/Claude-Code-Game-Dev/tree/main/.claude/skills/dev-story
Command: npx skills add https://github.com/polsegu/Claude-Code-Game-Dev --skill dev-story-polsegu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Read a story file and implement it. Loads the full context (story, GDD requirement, ADR guidelines, control manifest), routes to the right programmer agent for the system and engine, implements the code and test, and confirms each acceptance criterion. The core implementation skill — run after /story-readiness, before /code-review and /story-done.

Core Features & Use Cases

  • Route to the appropriate programmer agent based on story layer, type, and system name.
  • Load and validate full context (story file, TR registry, ADR, control manifest) before implementation.
  • Implement code and write tests according to ADR guidelines; ensure tests cover acceptance criteria.
  • Provide an implementation summary and follow up with code-review and story-done phases.

Quick Start

Implement the dev-story workflow by loading full context, routing to the correct programmer agent, implementing code and tests, and validating acceptance criteria.

Frequently Asked Questions about dev-story

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

FAQPage Schema
How do I automate story implementation from requirements to code and tests?

Story implementation is automated by loading full context including the story file, ADR guidelines, and control manifest, then routing to the appropriate programmer agent to generate code and complete test files. The workflow validates acceptance criteria before signaling readiness for code review.

What is the best way to route programming tasks to the right agent for different system layers?

Programmer routing is handled by evaluating the story layer, type, and system name to select the appropriate programmer agent, including engine specialists when needed. This routing mechanism applies across UI, gameplay, AI, networking, and data or config tasks.

Does this workflow automation enforce architecture decisions during code implementation?

Architecture decisions are enforced during code implementation by loading ADR guidelines into the full context and adhering to the control manifest throughout the process. The programmer agents follow these constraints while generating code and tests.

When do I need to load ADR guidelines and a control manifest for end-to-end story execution?

ADR guidelines and a control manifest are needed before end-to-end story execution begins, as they provide the architectural constraints and control parameters for the programmer agents. Loading this full context happens prior to routing to any implementation agent.

Can I use this story implementation workflow for both UI and networking tasks?

Story implementation workflow supports Foundation, Core, and Feature stories across UI, gameplay, AI, networking, and data or config tasks. The workflow routes each task type to the appropriate programmer agent or engine specialist based on the system name.