implement-feature

Implements one spec criterion with token-tagged tests, a checks-gate, and a commit.

1|Updated Jul 9, 2026
One-click install
npx skills add https://github.com/matthewalton/speccle --skill implement-feature-matthewalton
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implement-feature
Source: https://github.com/matthewalton/speccle/tree/main/packages/plugin/skills/implement-feature
Command: npx skills add https://github.com/matthewalton/speccle --skill implement-feature-matthewalton

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? It turns an already-written, linted SPEC.md into working code one criterion at a time, preventing bloated sessions that try to build an entire feature in a single pass and ensuring every change is test-backed, gated, and committed. ## Core Features & Use Cases - Single-criterion red-green loop: Picks the next unclaimed criterion via the speccle oracle, writes failing token-tagged tests first, then makes them green. - Tracer selection: On a slice with nothing built yet, guides choosing the criterion whose test exercises the thinnest complete path through every layer. - Deterministic checks-gate: Runs lint, claims, verify, and the full project test suite before committing, with a stop rule when a check fails the same way twice. - Use Case: Given a checkout/ feature folder with a linted SPEC.md, ask the agent to implement CHECKOUT-2; it writes the tagged tests, makes them pass, runs the gate, and commits naming the criterion. ## Quick Start Ask the agent to implement the next criterion of the feature folder, for example by saying "implement CHECKOUT-2" or "make the next criterion of the checkout slice green".

Frequently Asked Questions about implement-feature

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

FAQPage Schema
How do I implement a spec criterion with tests first?▼

Name the criterion or let the oracle's next command pick the first unclaimed one in document order. Write tests carrying the [KEY-n] token in their full concatenated name, watch them fail, then write only the code those tests demand before running the checks-gate.

What is a tracer criterion in test-driven development?▼

A tracer is the first criterion built on a slice with nothing claimed yet, chosen so its passing test exercises the thinnest complete path through every layer the feature touches. Pick for path length, not importance; edge cases and rejections are never tracers.

Can I use this skill on a feature that has no SPEC.md?▼

No. The skill requires an existing linted SPEC.md and verifies the precondition with the oracle lint command. For a feature with no spec, use the feature or spec-feature pipeline to draft and lint the contract first.

Why does the claims command exit 1 mid-slice?▼

Mid-slice, claims exits 1 because criteria you were never asked to build are still unclaimed, which is correct. Gate only on this criterion's claimed field being true and unknownClaims being empty, not on the exit code.

What happens when a checks-gate check keeps failing?▼

A check that fails the same way twice stops the session: show the human what is stuck and commit nothing. A malformed check exits 2 with no report, which means the repo's configuration is broken, not the criterion.