implement

Implements work items from specs or tickets using test-driven development.

Updated Aug 22, 2026
One-click install
npx skills add https://github.com/falentio/cimi --skill implement-falentio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/falentio/cimi/tree/main/.agents/skills/skills/implement
Command: npx skills add https://github.com/falentio/cimi --skill implement-falentio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a written spec or ticket into working, reviewed code requires discipline: writing tests first, running typechecks, and reviewing the result. This Skill guides the AI through that structured implementation workflow so nothing gets skipped. ## Core Features & Use Cases - Spec-Driven Implementation: Builds the work described in a spec or set of tickets directly in the current branch. - 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 invoking 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 types and the test suite, review the diff, and commit the result. ## Quick Start Ask the AI to implement the work described in your spec or ticket 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 or ticket with AI?

Provide the spec or ticket and invoke the implement skill. It builds the described work using test-driven development at pre-agreed seams, runs typechecking and tests, then reviews and commits the result to the current branch.

What is the workflow for test-driven development with this skill?

The skill applies TDD at pre-agreed seams, runs typechecking and individual test files regularly during development, and executes the full test suite once at the end before review and commit.

Does the implement skill commit code automatically?

Yes. After implementation and a code review pass, the skill 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 defining the work, since the skill implements what is described rather than designing solutions. It also relies on companion review and TDD skills being available.