dev-story

Read story files, assemble programmer context, and route implementation to specialist agents.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/CarlosQ96/robot-crawler --skill dev-story-carlosq96
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-story
Source: https://github.com/CarlosQ96/robot-crawler/tree/main/.agents/skills/dev-story
Command: npx skills add https://github.com/CarlosQ96/robot-crawler --skill dev-story-carlosq96

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

  • Reads the full story file and assembles all required context for a programmer.
  • Routes to the correct specialist agent and drives end-to-end implementation plus tests.
  • Enforces acceptance criteria and ADR guidance throughout the lifecycle.

Quick Start

Use the dev-story skill to implement a given story by providing its path to /dev-story.

Frequently Asked Questions about dev-story

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

FAQPage Schema
How do I turn a story plan into working code and tests?

To turn a story plan into working code, provide the story file path so the full context is loaded. The system routes to the correct specialist agent to implement source code and tests while enforcing acceptance criteria.

How does an ADR-driven workflow ensure implementation aligns with architecture guidelines?

ADR-driven workflow ensures alignment by loading Architecture Decision Records alongside story requirements and control manifests. The implementation agent checks that all generated source code and tests conform to these established ADR guidelines.

How do I implement a story file end-to-end from qa-plan to story-done?

Implement a story file end-to-end by running the skill after story readiness checks. It coordinates the sprint loop from qa-plan to story-done, routing requirements to specialist agents that produce code and tests.

Can I use manifest-driven requirements to route programming tasks to specialist agents?

Yes, manifest-driven requirements are assembled with story and ADR context to route programming tasks. The system selects the correct specialist agent for the target engine and system to drive implementation and testing.

Do I need a story readiness check before implementing code and tests?

Yes, a story readiness check is required before implementation. Running readiness checks first ensures all required GDD requirements, ADR guidelines, and control manifests are loaded for the programmer agent.

What is the best way to automate acceptance criteria validation during story implementation?

Automate acceptance criteria validation by using a programming-agent workflow that reads the full story plan. The agent implements the code and tests, then confirms each criterion aligns with ADR and manifest guidelines.