implement

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

2|Updated Jun 21, 2026
One-click install
npx skills add https://github.com/IsKenKenYa/skills --skill implement-iskenkenya
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/IsKenKenYa/skills/tree/main/skills/engineering/implement
Command: npx skills add https://github.com/IsKenKenYa/skills --skill implement-iskenkenya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a written spec or a set of tickets into finished, verified code is error-prone when done ad hoc: tests get skipped, type errors slip through, and the final work goes unreviewed. This Skill enforces a disciplined implementation workflow so the work is built, tested, reviewed, and committed consistently. ## Core Features & Use Cases - Spec/Ticket-Driven Implementation: Builds the work exactly as described by the user-provided spec or ticket set. - 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: Hands the finished work to a code review pass and commits it to the current branch. - Use Case: You have a feature spec and three tickets for a new API endpoint. Invoke this Skill to implement the changes test-first, verify types and tests, review the diff, and land the commit on your branch. ## Quick Start Ask the agent 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 with an AI coding agent?

Provide the spec or tickets and invoke the implement skill. The agent builds the work test-first at pre-agreed seams, runs typechecking and tests during development, reviews the result, and commits it to the current branch.

How does test-driven development fit into an implementation workflow?

TDD is applied at pre-agreed seams, meaning tests are written at the module boundaries agreed upon before coding starts. Single test files run regularly during work, and the full test suite runs 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, only typechecking and individual test files run regularly to keep feedback fast.

Can the implement skill commit code automatically?

Yes, after implementation and code review are complete, 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 when there is no clear spec or ticket set, since the workflow depends on defined requirements. For exploratory prototyping or open-ended design work, a design or prototyping skill is a better fit.