Verified:GitHub

implement

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

Updated Jul 31, 2026

Search Tags:#testing #tdd #code review #implementation #tickets #git commit #typechecking

One-click install

npx skills add https://github.com/julianckt/adoptarun --skill implement-julianckt

Or copy as Structured Prompt for Agent▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a written spec or set of tickets 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-to-Code Implementation: Builds the work described in a spec or ticket set directly on 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 completed 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 full suite passes, review the changes, and commit them. ## 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 a ticket or spec with AI assistance?▼

Provide the spec or tickets and invoke the implement skill. It builds the work using test-driven development at pre-agreed seams, runs typechecking and tests along the way, then reviews and commits the result.

How does test-driven development fit into the implementation workflow?▼

The skill applies TDD at pre-agreed seams, meaning tests are written alongside the implementation at defined boundaries. 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, after the work is implemented and reviewed, the skill commits the changes to the current branch. It does not create new branches or push to remotes on its own.

When should I not use a spec-based implementation workflow?▼

Avoid it for exploratory prototyping or unclear requirements where no spec or tickets exist yet. The skill expects defined work items; ambiguous goals should be refined into tickets first.