dev-story

Coordinate end-to-end story implementation across programmer agents with validation and testing.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill consolidates the end-to-end delivery of user stories by loading full project context (story, GDD requirements, ADR guidance, and control checklists), routing work to the appropriate programmer agents, and ensuring code and tests align with acceptance criteria.

Core Features & Use Cases

  • Context integration: loads all essential story context (story text, TR requirements, ADR references, and checklists) to frame implementation.
  • Smart routing: maps stories to the most suitable programmer agents based on level, type, and system names.
  • Parallel implementation & testing: drives concurrent coding and testing tasks to meet acceptance criteria, with ADR-guided guidelines.
  • Compliance & validation: validates TR registry and ADR alignment before story completion.

Quick Start

Supply the path to a user story to begin the end-to-end implementation workflow.

Frequently Asked Questions about dev-story

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

FAQPage Schema
How do I orchestrate end-to-end user story implementation with ADR and GDD context?

End-to-end story implementation orchestration loads full project context including story text, GDD requirements, ADR guidance, and checklists, routing tasks to appropriate programmer agents for concurrent coding and testing.

What is the best way to ensure user story delivery aligns with acceptance criteria and TR registry requirements?

User story delivery alignment validates TR registry and ADR compliance before story completion, driving parallel implementation and testing tasks to meet acceptance criteria while flagging dependencies and risks.

Can I route specific user stories to different programmer agents based on system names?

Story routing maps user stories to the most suitable programmer agents based on level, type, and system names, ensuring implementation tasks are distributed to agents matching the story requirements.

How do I validate ADR alignment and TR registry compliance before marking a story complete?

ADR alignment and TR registry validation checks run during the review and testing stages before story completion, ensuring outputs include created source and test files with explicit attention to acceptance criteria.

Does user story workflow orchestration support parallel coding and testing tasks?

Story workflow orchestration drives concurrent coding and testing tasks with ADR-guided guidelines, coordinating parallel implementation to meet acceptance criteria efficiently.

What context do I need to supply to start end-to-end story implementation?

End-to-end story implementation requires supplying the path to a user story, which triggers loading of full project context including story text, TR requirements, ADR references, and control checklists.