dev-story

Reads a story file and routes it to the correct programmer agent for implementation with tests.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/JunnnnyWon/Codex-Game-Studios --skill dev-story-junnnnywon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-story
Source: https://github.com/JunnnnyWon/Codex-Game-Studios/tree/main/.claude/skills/dev-story
Command: npx skills add https://github.com/JunnnnyWon/Codex-Game-Studios --skill dev-story-junnnnywon

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

  • Bridges planning and code by reading a story, assembling context, routing to the correct specialist agent, and driving implementation to completion — including writing the test.
  • Orchestrates the sprint and QA workflow: /qa-plan, /story-readiness, /dev-story, /code-review, /story-done.
  • Ensures acceptance criteria are met and the test file is produced alongside implementation.

Quick Start

Run /dev-story [story-path] to implement the given story and produce the test alongside the code.

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 and route development tasks to the right programmer?

Story implementation is automated by reading a story file, assembling full context like ADR guidelines and control manifests, and routing the task to the correct specialist programmer agent to write the code and test end-to-end.

How does workflow orchestration work for coding and testing phases?

Workflow orchestration guides the sprint sequence across /qa-plan, /story-readiness, /dev-story, /code-review, and /story-done, ensuring acceptance criteria are satisfied and a test file is produced alongside the implementation.

What is the best way to ensure acceptance criteria are met during code generation?

Acceptance criteria are met by loading full context including GDD requirements and ADR guidelines, routing to the correct programmer agent, and confirming each criterion is satisfied before completing the workflow.

Do I need to run story readiness checks before implementing a story file?

Yes, story readiness checks are required beforehand. The dev-story workflow runs after /story-readiness and before /code-review and /story-done to ensure proper context assembly and programmer routing.

Can I use this workflow orchestration to generate tests alongside the implementation code?

Yes, test generation is a core feature. The workflow ensures a test file is produced alongside the implementation code, driving the development process to completion while satisfying acceptance criteria.

Why does routing to a programmer agent require ADR and control manifest guidelines?

ADR and control manifest guidelines are required to provide full context for the programmer agent, ensuring the generated code and tests align with architectural decisions and sprint control parameters.