implement

Implements work from specs or tickets using TDD, parallel workers, and code review.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Fatih0234/mattpocock-skills-pi --skill implement-fatih0234
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/Fatih0234/mattpocock-skills-pi/tree/main/skills/engineering/implement
Command: npx skills add https://github.com/Fatih0234/mattpocock-skills-pi --skill implement-fatih0234

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a spec or a set of tickets into working code requires coordinating test-driven development, typechecking, code review, and multi-ticket builds without conflicts. This Skill orchestrates that entire implementation workflow so tickets are built, reviewed, and integrated correctly. ## Core Features & Use Cases - Ticket-Based Implementation: Executes work described in a spec or tickets, dispatching independent tickets to fresh ticket-worker agents in isolated git worktrees. - TDD and Verification: Follows the tdd skill at pre-agreed seams, runs typechecking and single test files regularly, and runs the full test suite once at the end. - Structured Code Review: Loads the code-review skill with separate fresh-context Standards and Spec reviewers that inspect the actual worker checkout. - Use Case: Given a dependency-aware set of five tickets, the parent agent computes the ready frontier, dispatches each independent ticket to a worker, integrates commits sequentially, and resolves conflicts by intent. ## Quick Start Ask the agent to implement the work described in your spec or ticket list and let it coordinate workers, tests, and reviews.

Frequently Asked Questions about implement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement multiple tickets in parallel with AI agents?

The parent agent computes the dependency-aware ready frontier and dispatches each independent ticket to a fresh ticket-worker with its own git worktree. Workers commit their ticket and the parent integrates commits sequentially, resolving conflicts by intent.

How does test-driven development fit into ticket implementation?

The workflow loads and follows the tdd skill at pre-agreed seams during implementation. Typechecking and single test files run regularly, while the full test suite runs once at the end before review.

Can two agents work in the same git checkout at once?

No, two writers never run in one checkout. Multi-ticket builds give each worker its own worktree, while single tickets run in the current checkout only when owned by the session.

How is code review handled after implementation?

After implementation, the code-review skill runs with Standards and Spec reviewers as separate fresh contexts. Inside a ticket-worker they inherit the worker cwd so they review the actual implementation rather than a clean checkout.

What happens when worker commits conflict during integration?

The parent agent integrates worker commits sequentially and resolves conflicts by intent. It also owns tracker state and runs the combined verification across all integrated work.