Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →donchitos/dev-story
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.
Passed 17 of 20 test cases with the skill, and 8 of 20 without it.
and 11 more in the full report
10 fixed7 passed either way2 still failing1 broke4 errored
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
When starting implementation without passing a story path, we check session state and find no active story defined in production/session-state/active.md. What specific lookup should be executed next?
| Checked | Without skill | With skill |
|---|---|---|
| Searches for story files using glob production/epics/**/*.md. | Missed | Passed |
| Lists candidate stories that have Status set to Ready. | Missed | Passed |
The instructions your model reads when the skill loads.
!bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys automation,workflow,story_granularity,qa.level,testing.strict,system_overrides
Resolved above — use as-is. No block → defaults in
.claude/docs/config-resolution.md.
This skill bridges planning and code. It reads a story file in full, assembles all the context a programmer needs, routes to the correct specialist agent, and drives implementation to completion — including writing the test.
The loop for every story:
/qa-plan sprint ← define test requirements before sprint begins
/story-readiness [path] ← validate before starting
/dev-story [path] ← implement it (this skill)
/code-review [files] ← review it
/story-done [path] ← verify and close it
At workflow: minimal the loop is /dev-story [path] → /story-done [path]:
no QA plan, readiness check or sprint. /story-done names the next story.
With a sprint plan, after all sprint stories are done: run /team-qa sprint to execute the full QA cycle and get a sign-off verdict before advancing the project stage.
Output: Source code under the project's code root + test file under the engine's test root (tests/ Godot, Assets/Tests/ Unity, Source/<Module>/Private/Tests/ Unreal — .claude/docs/directory-structure.md). Resolve the code root from engine.name (src/ Godot, Assets/ Unity, Source/<Module>/ Unreal) per .claude/docs/code-root-resolution.md.
Every AskUserQuestion call follows .claude/docs/automation-modes.md
(collaborative asks always · guided major-only · autonomous logs and proceeds;
automation_always_ask categories always prompt).
Workflow tier: resolved per the story's system (per
.claude/docs/workflow-modes.md) — the GDD filename stem of the story's
GDD: path (design/gdd/<stem>.md → <stem>), with the [system] segment of
its TR-[system]-NNN ID accepted only as a fallback alias: use the
system_overrides row for that system if the block lists one, else the
project value. Resolve it at the start of Phase 2 (the story header is
read there) and apply it to the prerequisite gate.
test cases passed, vs 8 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.