skills.rest
j172
j172COMMUNITY
Explore all skills by this author →
Website𝕏@j172GitHub

implement

Implement code changes from specs or tickets using test-driven development.

Updated Jul 30, 2026
Search Tags:#tdd#code review#spec#tickets#git commit#implement#typechecking
One-click install
npx skills add https://github.com/j172/bid --skill implement-j172
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/j172/bid/tree/main/.agents/skills/implement
Command: npx skills add https://github.com/j172/bid --skill implement-j172

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a written spec or set of tickets into working, verified code requires disciplined execution: writing tests first, running typechecks, and reviewing the result. This Skill guides the AI through that implementation workflow so work is completed, tested, and committed consistently. ## Core Features & Use Cases - Spec-Driven Implementation: Builds the work described in a spec or set of tickets provided by the user. - 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. - 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 types and the test suite, review the diff, and commit the result to your branch. ## Quick Start Implement the work described in the attached spec using test-driven development, then review and commit it to the current branch.

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 the implement Skill. It builds the described work using test-driven development at pre-agreed seams, runs typechecking and tests along the way, then reviews and commits the changes.

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

The Skill applies TDD at pre-agreed seams, meaning tests are written around defined boundaries before the implementation. It runs single test files regularly during development and the full test suite once at the end.

Does the implement Skill run the full test suite?▼

Yes, the full test suite runs once at the end of the implementation. During development it runs typechecking and individual test files regularly to catch issues early without the cost of repeated full-suite runs.

Does the implement Skill commit code automatically?▼

Yes, after completing the implementation and running a code review pass, 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 the implement Skill?▼

Avoid it when there is no clear spec or ticket describing the work, since it implements what is described rather than defining requirements. Use a planning or spec-writing step first for ambiguous requests.

Related Skills

Explore More Software Engineering Skills→
Evolutionary-LeadershipEvolutionary-Leadership

implement

Implements tickets from a spec by working the unblocked frontier with TDD and reporting.

Official
Intermediate
dwaynepartondwayneparton
1

simplify

Reviews changed code on the current branch for reuse, quality, and efficiency, then fixes issues found.

Community
Intermediate
filipas123filipas123

Verification Loop Skill

Run build, type checking, linting, tests, and security scans on code.

Community
Advanced
arbazkhan971arbazkhan971
26

think

Generate a validated .godmode/spec.md with up to three implementation approaches.

Community
Advanced