Verified:GitHub

implement

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

Updated Jul 12, 2025

Search Tags:#testing #tdd #code review #spec #tickets #implement #typechecking

One-click install

npx skills add https://github.com/kpayakv2/check-products --skill implement-kpayakv2

Or copy as Structured Prompt for Agent▼

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

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 structured implementation workflow so nothing is 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. - Review and Commit: Finishes by invoking a code review pass and committing the work to the current branch. - Use Case: You have a feature ticket describing a new API endpoint. Invoke this Skill to implement it with TDD, verify types and tests, review the diff, and commit the finished change. ## Quick Start Ask the AI to implement the work described in your spec or tickets using the implement 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 using AI?▼

Provide the spec or tickets and invoke this Skill. It implements the described work using test-driven development, runs typechecking and tests along the way, then reviews and commits the result to the current branch.

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

Tests are written at pre-agreed seams before the implementation code. Single test files run regularly during development, and the full test suite runs once at the end to confirm everything passes.

Does this Skill commit code automatically?▼

Yes. After the implementation passes review, the work is committed 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 prototyping or spikes where requirements are unclear, since the workflow assumes a defined spec or tickets. It also expects an existing test setup to support TDD.