Installs into .claude/skills of the current project.
Are you the author of Implement?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/alexisbalayre-implement)
---
name: implement
description: "Implement a piece of work based on a spec or set of tickets."
disable-model-invocation: true
---
Implement the work described by the user in the spec or tickets.
If the user passes a ticket reference, fetch it from the configured tracker (or its file under `docs/plans/` when there is no tracker, by absolute path into the main checkout: `docs/plans/` is never committed, so a worktree has none) and state its title before starting. If the reference is ambiguous, ask.
Call the Skill tool with "tdd" where possible, at pre-agreed seams.
Run typechecking regularly (`TYPECHECK_CMD`), single test files regularly, and the full test suite (`TEST_CMD`) once at the end. Both commands live in `.claude/project.env`; an empty key means that check is off.
Once done, review the diff against the spec or tickets: every acceptance criterion met, nothing built beyond them.
Commit your work to the current branch. If that branch is the trunk (`GIT_TRUNK` in `.claude/project.env`, default `main`), create a branch with `scripts/worktree-create.sh <name>` and commit there instead.
