story-implement

story-implement is a command for Claude Code from drobins25/craft. It costs 22 tokens per session (12,741 once invoked), scanned A, original, MIT.

A story-implementation command that sends each prepared chunk to an implementation agent and validates the result synchronously.

In plain words
What is it for?
Use it to implement stories whose chunks are already designed, including per-chunk tests or other checks and fixes for validation failures.
Why use it?
It enforces a structured path from designed work to completed code, with validation before progress is accepted.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: mentions subagents; names the AskUserQuestion tool; mentions Claude Code.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the craft plugin — 11 skills, 33 commands, 27 agents, 7 hooks, 1 MCP server shipped together

Good fit Use it to implement stories whose chunks are already designed, including per-chunk…

Compare 6 commands from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add drobins25/craft
Claude Code
/plugin install craft

Made for: Claude Code.

Or install craft, the plugin that ships this one along with the rest of its 11 skills, 33 commands, 27 agents, 7 hooks, 1 MCP server.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for story-implement

README.md
[![agentmods](https://agentmods.dev/badge/commands/drobins25/craft/craft-story-implement.svg)](https://agentmods.dev/commands/drobins25/craft/craft-story-implement)
Your own site
<a href="https://agentmods.dev/commands/drobins25/craft/craft-story-implement"><img src="https://agentmods.dev/badge/commands/drobins25/craft/craft-story-implement.svg" alt="Measured on agentmods" height="20"></a>
Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 12,741 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00022 $0.12741
Opus 5 $0.00011 $0.06370
Sonnet 5 $0.00004 $0.02548
Haiku 4.5 $0.00002 $0.01274

Measured 7d ago against content hash 6da03dd462b3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

story-implement scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

commands/craft-story-implement.md · 1,150 lines

How it starts

The opening of the file, as written. The whole thing — 1,150 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Story Implement

CRITICAL: YOU ARE THE ORCHESTRATOR, NOT THE IMPLEMENTER

You must NOT write implementation code directly. For EVERY chunk, you MUST use the Task tool to invoke the implementer agent:

Task tool:
  subagent_type: "craft:implementer"
  description: "Implement chunk N of [story]"
  prompt: [chunk details, story context, TDD requirement]

If you find yourself about to write code → STOP → use Task tool instead.


CRITICAL: VALIDATION CHAIN IS INLINE

Do NOT invoke the validate-chunk skill (craft:validate-chunk) during the implementation loop. The validate-chunk skill exists for manual user invocation only. story-implement owns the validation chain directly:

  • Invoke chunk-validator agent via Task tool
  • Route PASSED/PARTIAL inline
  • Route FAILED via Read ${CLAUDE_PLUGIN_ROOT}/commands/references/validate-fix-loop.md

CRITICAL: ALL VALIDATION RUNS SYNCHRONOUSLY

NEVER use run_in_background: true for test, typecheck, lint, or build commands. All validation must complete synchronously — results confirmed before marking any chunk or story done. This applies to:

  • Per-chunk validation (Step 4)
  • Quality gates (Step 5)
  • Any "verify nothing broke" test runs

Background test runs cause orphaned failure notifications that appear after stories are already marked complete. If a command is slow, wait for it.


Implement a story that's already been designed. This is pure Implement Phase — chunks exist, decisions are locked, just execute.

Project Root

All .craft/ paths in this command are relative to $CRAFT_PROJECT_ROOT (set at session start). Use ${CRAFT_PROJECT_ROOT:-.} as prefix when constructing paths. Pass the project root to all subagents.

Prerequisites & Status Guards

Before implementation, validate story location and status:

Location check:

  • If story is in .craft/backlog/ → BLOCK:

Use AskUserQuestion:

question: "This story is in the backlog. Assign it to a cycle first?"
header: "Assign"
options:
  - label: "Assign to [active cycle] (Recommended)"
    description: "Add to current cycle and implement"
  - label: "Create new cycle for it"
    description: "Start a new cycle with this story"
  - label: "Cancel"
    description: "Go back"

Read the full file on GitHub · 1,150 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 7d ago First seen · 1,150 lines · 22 tokens per session scan A 6da03dd462b3

Subscribe to this mod's changes

story-implement is a command published in the GitHub repository drobins25/craft (53 stars, last pushed today), licensed MIT. It adds 22 tokens to every session and 12,741 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.