dev-story

Read a story file and implement code and tests in src/ and tests/.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/naxoruto/TE-limonchero-3d --skill dev-story-naxoruto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-story
Source: https://github.com/naxoruto/TE-limonchero-3d/tree/main/.claude/skills/dev-story
Command: npx skills add https://github.com/naxoruto/TE-limonchero-3d --skill dev-story-naxoruto

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 a story file in full, assembles all context a programmer needs, routes to the correct specialist agent, and drives implementation to completion — including writing the test.
  • Supports a sprint-based workflow: /qa-plan sprint, /story-readiness [path], /dev-story [path], /code-review [files], /story-done [path], and a final /team-qa sprint for sign-off.
  • Outputs: Source code and test file in the project's src/ and tests/ directories.

Quick Start

Provide the path to the story file to implement by invoking /dev-story [path].

Frequently Asked Questions about dev-story

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

FAQPage Schema
How do I implement a story file into source code and tests?

You implement a story file by invoking the skill with the file path, which loads full context, routes to the correct programmer agent, and writes source and test files into src/ and tests/ directories.

What is a sprint-based development workflow for story implementation?

A sprint-based workflow for story implementation is a sequential process spanning readiness checks, coding, testing, code review, and final QA sign-off to verify acceptance criteria before delivery.

Does story implementation require ADR guidelines and a control manifest?

Yes, story implementation requires ADR guidelines and a control manifest. The process loads these alongside the story file and GDD requirements to enforce layer-specific rules and guide the programmer agent.

Can I run story implementation before story readiness checks are complete?

No, you should not run story implementation before readiness checks. The workflow specifies running story readiness first to assemble context, followed by implementation, code review, and story completion.

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

The best way to verify acceptance criteria during story implementation is to route to the correct programmer agent, generate matching test files, and execute tests to confirm each criterion before code review.