Verified:GitHub

implement

Implements work from a spec or tickets using TDD and code review.

Updated Nov 10, 2013

Search Tags:#testing #tdd #code review #spec #tickets #git commit #implement

One-click install

npx skills add https://github.com/bnferguson/dotfiles --skill implement-bnferguson

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/bnferguson/dotfiles/tree/main/.agents/skills/implement
Command: npx skills add https://github.com/bnferguson/dotfiles --skill implement-bnferguson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a written spec or set of tickets into working, tested code requires discipline: writing tests first, running typechecks, and reviewing the result. This Skill guides the AI through that disciplined implementation workflow so nothing gets skipped. ## Core Features & Use Cases - Spec-Driven Implementation: Builds the work described in a spec or ticket set, following test-driven development at pre-agreed seams. - Continuous Verification: Runs typechecking and single test files regularly, then the full test suite once at the end. - Built-In Review and Commit: Finishes by running a code review over the changes and committing the work to the current branch. - Use Case: You have a ticket describing a new API endpoint. Invoke this Skill to implement it with tests, verify the suite passes, review the diff, and commit it to your branch. ## Quick Start Ask the AI to implement the work described in your spec or tickets using this Skill.

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 with AI?▼

Provide the spec or tickets and invoke this Skill. It implements the described work using test-driven development at pre-agreed seams, then reviews and commits the changes to the current branch.

How does test-driven development work in this workflow?▼

The Skill applies TDD where possible at pre-agreed seams, writing tests alongside the implementation. It runs typechecking and individual test files regularly, then the full test suite once at the end.

Does this Skill commit code automatically?▼

Yes, after implementation and code review it commits the work to the current branch. It does not create new branches or push to remotes on its own.

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

Avoid it for exploratory spikes or throwaway prototypes where tests and review add overhead without value. It is best suited for well-defined tickets or specs with clear acceptance criteria.