anvil-implement

Implements work from specs or tickets using TDD and code review.

1|Updated Aug 27, 2026
One-click install
npx skills add https://github.com/rogerznts/anvil --skill anvil-implement-rogerznts
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: anvil-implement
Source: https://github.com/rogerznts/anvil/tree/main/anvil/.claude/skills/anvil-implement
Command: npx skills add https://github.com/rogerznts/anvil --skill anvil-implement-rogerznts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a written spec or set of tickets into committed, reviewed code requires coordinating test-driven development, typechecking, and review steps that are easy to skip or do inconsistently. ## Core Features & Use Cases - Spec-driven implementation: Executes the work described in a spec or ticket set on the current branch. - TDD at agreed seams: Applies test-driven development where pre-agreed, running typechecks and single test files regularly plus the full test suite at the end. - Built-in review and commit: Hands the finished work to a code review step and commits it to the current branch. - Use Case: After planning a feature with tickets, invoke this skill to implement the tickets with TDD, verify the full test suite passes, review the diff, and commit the result. ## Quick Start Implement the work described in the current spec and tickets, then review and commit it on this branch.

Frequently Asked Questions about anvil-implement

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

FAQPage Schema
How do I implement a feature from a spec or tickets with Claude Code?▼

Invoke the anvil-implement skill with the spec or ticket set as input. It implements the described work using TDD at pre-agreed seams, runs typechecking and tests, reviews the result, and commits to the current branch.

How does this skill apply test-driven development?▼

It delegates to the anvil-tdd skill where possible, but only at pre-agreed seams rather than everywhere. Typechecking and single test files run regularly during implementation, with the full test suite executed once at the end.

Does the implementation get reviewed before committing?▼

Yes. After implementation completes, the skill invokes anvil-code-review to review the work. Only after that review step does it commit the changes to the current branch.

When should I not use spec-driven implementation?▼

Avoid it when there is no written spec or ticket set to work from, since the skill expects described work as input. For exploratory changes or quick fixes, implement directly instead of routing through the full implement-review-commit workflow.