spec-implement

Implements features from LiveSpec plans with TDD, visual baselines, and spec traceability anchors.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/julien-m/livespec --skill spec-implement-julien-m
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-implement
Source: https://github.com/julien-m/livespec/tree/main/.agent-sync/skills/spec-implement
Command: npx skills add https://github.com/julien-m/livespec --skill spec-implement-julien-m

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a written implementation plan into working, tested code is error-prone: steps get skipped, tests are written after the fact, and the link between requirements and code is lost. This Skill automates the full implementation pipeline from plan.md to tested, documented code with enforced traceability. ## Core Features & Use Cases - Plan-driven execution: Reads spec.md, plan.md, constitution, and stack files, then executes each plan step through a blocking Step Gate with persistent progress.md checkpoints and --resume support. - Strict TDD and review gates: Enforces RED-GREEN-REFACTOR with resolved test commands, dispatches steps to implementer/spec-reviewer/code-quality-reviewer sub-agents, and requires @spec anchors linking every FR to source code. - Visual and Penflow gates: Captures Playwright visual baselines for UI features, validates Penflow UI contracts, and blocks completion until the visual gate passes. - Use Case: After running /spec-plan for a notifications feature, invoke /spec-implement to generate migrations, API endpoints, UI components, and tests step by step, producing implementation.md that maps every FR/AC to code anchors. ## Quick Start Ask the AI to run /spec-implement for your planned feature, for example by saying: implement the 005-notifications feature from its plan with tests and spec anchors.

Frequently Asked Questions about spec-implement

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

FAQPage Schema
How do I implement a feature from a spec plan automatically?

Run /spec-implement with the feature name after creating spec.md and plan.md. The command analyzes the spec, executes each plan step with TDD, runs targeted tests, and writes progress.md checkpoints until all steps are Done.

How does spec-implement enforce traceability between code and requirements?

Every source file implementing a functional requirement must contain an inline @spec anchor comment with a deep link to the spec.md section. The Spec Reviewer sub-agent verifies these anchors before any step is approved.

Can I resume an interrupted implementation run?

Yes, use the --resume flag. It reads .specs/features/<feature>/progress.md and continues at the first step not marked Done, which is why writing the checkpoint file after every step is mandatory.

Does spec-implement handle UI visual testing?

Yes, for features with a Screens section it captures Playwright visual baselines into the feature's baselines directory and runs a mandatory visual gate. A UI feature cannot reach Implemented status without a passing Visual Gate Verdict.

What happens when a step's tests keep failing?

The Step Gate retries within iteration limits, then marks the step Blocked, records the failing context in progress.md, and stops progression. You fix the issue and re-run with --resume to continue.

What are the prerequisites for running spec-implement?

The feature directory must contain spec.md and plan.md with no unresolved decision markers, test commands must be resolved, and required tooling must be available. A preflight safety contract and light preflight check block execution if these fail.