implement

Implements work from a spec or tickets using test-driven development and code review.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a written spec or set of tickets into working, verified code requires discipline: writing tests first, running typechecks, and reviewing the result. This Skill structures that implementation workflow so the work is built, tested, reviewed, and committed in a consistent order. ## Core Features & Use Cases - Spec-Driven Implementation: Builds the work described by the user in a spec or set of tickets. - Test-Driven Workflow: Applies /tdd at pre-agreed seams, runs typechecking and single test files regularly, and runs the full test suite once at the end. - Review and Commit: Finishes by running /code-review on the work and committing it to the current branch. - Use Case: You have a ticket describing a new API endpoint. Invoke this Skill to implement it with TDD, verify it with typechecks and tests, review the changes, and commit them to your branch. ## Quick Start Implement the work described in my spec or tickets using test-driven development, then review and commit it.

Frequently Asked Questions about 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 an AI agent?▼

Provide the spec or tickets and invoke the implement Skill. It builds the work using test-driven development at pre-agreed seams, runs typechecks and tests along the way, reviews the result, and commits it to the current branch.

How does test-driven development fit into this implementation workflow?▼

The Skill applies /tdd where possible at pre-agreed seams, meaning tests are written alongside the implementation at defined boundaries. Typechecking and single test files run regularly, with the full test suite executed once at the end.

Does the implement Skill run code review automatically?▼

Yes. Once the implementation is done, the Skill invokes /code-review to review the work before committing. This ensures the changes are inspected before they land on the current branch.

When should I not use a spec-driven implementation workflow?▼

Avoid it for exploratory prototyping or spikes where requirements are unclear, since the workflow expects a defined spec or tickets. It is also heavier than needed for trivial one-line fixes that do not warrant TDD and review steps.