implement · Skill Details

Mechanism

When It Triggers · How It Works · What It Produces

Breaks down how the skill works and what it produces, so you can quickly judge whether it fits your scenario and value.

Trigger: User-invoked when a spec or ticket set is ready and the agent needs to execute the actual coding work. In /ask-matt's main flow, it follows /to-tickets. Can also be invoked standalone to process a user-provided spec/ticket.
Mechanism: Read the spec/ticket → use /tdd at pre-agreed seams (red→green→refactor loop), one vertical slice per cycle → regularly run typechecking and single-file tests → call /code-review for two-axis review → commit to current branch. The skill only defines the workflow; actual coding and testing logic is delegated to /tdd and /code-review.
Output: Working code changes committed to the current branch after typechecking, tests, and code review. Each vertical slice is delivered as a complete, functional unit.

Use Cases

Two Typical Use Cases

Scenario 01

Implementing a feature from a ticket

A development ticket is marked ready-for-agent. The developer invokes `/implement` with the ticket reference. The skill reads the ticket content, starts /tdd at pre-agreed seams using a red-green-refactor loop for each vertical slice, regularly runs typechecking and unit tests to prevent regressions, then invokes /code-review for a two-axis review before committing to the current branch.

Scenario 02

Building a new module from a spec

A product manager completes a spec. The developer invokes `/implement` pointing to the spec document. The skill first explores the current codebase state, identifies testing seams, then implements each user story from the spec as a vertical slice covering schema, API, UI, and tests. It runs typechecking and tests regularly to ensure each slice is functional, then performs a full /code-review.

Skill Relationships

Which Skills I Use · Which Skills Use Me

Dependency relationships read as "the upper tier points to the lower tier." The current Skill sits in the middle tier — above are Skills that depend on it, below are Skills it depends on.

Tier 1 · These Skills Use Me

ask-mattWorkflow

Tier 2 · Current Skill

implementWorkflow

Tier 3 · I Use These Skills

Full Relationship Graph

Browse this skill's relationships within its skillset. Click a node to switch the side panel; use the search box to jump to any skill.

Skill File

SKILL.md

Open in GitHub ↗

SKILL.mdLoading from GitHub…

Skill Composition

Open in GitHub ↗

SKILL.md50.0%
other50.0%

▸skills/implement/
▸implement
- ·SKILL.md
- ▸agents
  - ·openai.yaml

Per the Agent Skills spec, SKILL.md is the only required file. The colored bars classify the rest into the three spec-aligned optional directories (scripts / references / assets) and an 'other' bucket. The full directory tree is below.

Related in Skillset

You May Also Need These Skills

ask-matt

A router skill for the entire skillset: when the user can't remember which skill to use or which flow fits their situation, they invoke this to get a recommendation. It describes the main "idea → ship" flow (grill-with-docs → to-spec/to-tickets → implement), plus on-ramps (triage, diagnosing-bugs, wayfinder), codebase health (improve-codebase-architecture), vocabulary layers (domain-modeling, codebase-design), and standalone skills (grill-me, prototype, research, teach). Following its map leads users to the correct workflow entry point.

Workflow

code-review

A two-axis code review skill: reviews a diff (from a fixed point to HEAD) along both Standards (coding standards + Fowler smell baseline) and Spec (faithful implementation of the originating issue/PRD). Both axes run as parallel sub-agents to avoid context pollution. The report aggregates findings without merging conclusions, ensuring "passes standards but implements the wrong thing" and "implements the right thing but breaks conventions" are both surfaced independently.

Workflow

codebase-design

A shared vocabulary skill for deep module design: provides a precise set of design terms (Module, Interface, Depth, Seam, Adapter, Leverage, Locality) guiding agents and developers to design "deep modules" — a lot of behaviour behind a small interface. Includes design principles (the deletion test, the interface is the test surface) and testability guidelines. A reference skill consumed by other skills (e.g., improve-codebase-architecture, tdd) and invoked directly by engineers.

Style Guide

diagnosing-bugs

A disciplined diagnosis loop for hard bugs and performance regressions. The core idea is to first build a tight feedback loop — no hypothesis phase without one. Six phases: build feedback loop → reproduce + minimise → generate 3-5 falsifiable hypotheses → instrument by prediction → fix + regression test → cleanup + post-mortem. If the codebase architecture can't lock down the bug, it recommends handing off to the improve-codebase-architecture skill.

Workflow