implement

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

Updated Sep 13, 2026
One-click install
npx skills add https://github.com/U1traVeno/skills --skill implement-u1traveno
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/U1traVeno/skills/tree/main/profiles/matt/implement
Command: npx skills add https://github.com/U1traVeno/skills --skill implement-u1traveno

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, executing the test suite, and reviewing the result. This Skill guides the AI through that full implementation workflow so nothing gets skipped. ## Core Features & Use Cases - Spec-Driven Implementation: Builds the work described in a spec or set of tickets provided by the user. - Test-Driven Development: 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 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 on your branch. ## Quick Start Implement the work described in this ticket using TDD, 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 ticket with AI?▼

Provide the spec or ticket text and invoke the implement workflow. The AI builds the described work using test-driven development at agreed seams, runs typechecking and tests, reviews the changes, and commits to the current branch.

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

TDD is applied at pre-agreed seams, meaning tests are written at the boundaries you define before the implementation. Typechecking and individual test files run regularly during development, with the full test suite executed once at the end.

Does the implement 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 a remote; it commits locally on whatever branch is checked out.

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 unsuitable when you cannot run tests or typechecking in the project environment.