implement

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

2|Updated May 12, 2026

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

One-click install

npx skills add https://github.com/tajo9128/BioDockify-Pharma-AI --skill implement-tajo9128

Or copy as Structured Prompt for Agent▼

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

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 work is completed, verified, and committed consistently. ## Core Features & Use Cases - Spec-Driven Implementation: Builds the work described in a spec or set of tickets rather than ad-hoc instructions. - 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 a code review pass 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 the 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 work from a spec or tickets with AI?▼

Provide the spec or tickets and invoke the implement skill. It builds the described work, applies TDD at pre-agreed seams, runs typechecking and tests, reviews the result, and commits to the current branch.

How does the implement skill use test-driven development?▼

It applies TDD where possible at pre-agreed seams, meaning tests are written around defined boundaries before or alongside the implementation. Single test files run regularly during work, and the full test suite runs once at the end.

Does the implement skill commit code automatically?▼

Yes, the workflow ends by committing the completed work to the current branch after the code review step. It does not create branches or push to remotes on its own.

When should I not use the implement skill?▼

Avoid it for exploratory work without a spec or tickets, since it expects defined work to build. It is also not suited for tasks outside a code repository with typechecking and a test suite.