MCPInstall

implement

Implement a piece of work based on a spec or set of tickets.

Installs
127
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/tt-a1i/matt-skills-with-to-goal --skill implement
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads implement automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Implement the work described by the user in the spec or tickets.

If the user passes a ticket reference, fetch it from the issue tracker 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, single test files regularly, and the full test suite once at the end.

Once done, call the Skill tool with "code-review" to review the work.

Commit your work to the current branch.

FAQ

What does the implement skill do?

Implement a piece of work based on a spec or set of tickets.

How do I install implement?

Run npx skills add https://github.com/tt-a1i/matt-skills-with-to-goal --skill implement in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/implement/ (personal) or .claude/skills/implement/ (project).

Which AI agents can use implement?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is implement safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains implement?

It is published by tt-a1i in tt-a1i/matt-skills-with-to-goal. It has 127 recorded installs.

More from tt-a1i/matt-skills-with-to-goal

View all →

to-goal

tt-a1i/matt-skills-with-to-goal

Open the skill to read its SKILL.md instructions.

147 installs

goal-crafter

tt-a1i/matt-skills-with-to-goal

Open the skill to read its SKILL.md instructions.

145 installs

domain-modeling

tt-a1i/matt-skills-with-to-goal

Open the skill to read its SKILL.md instructions.

132 installs

grilling

tt-a1i/matt-skills-with-to-goal

Open the skill to read its SKILL.md instructions.

131 installs

grill-with-docs

tt-a1i/matt-skills-with-to-goal

Open the skill to read its SKILL.md instructions.

Docs & Writing131 installs

codebase-design

tt-a1i/matt-skills-with-to-goal

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

Popular code quality & workflow skills

View category →

grill-me

mattpocock/skills

A relentless interview to sharpen a plan or design.

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

handoff

mattpocock/skills

Compact the current conversation into a handoff document for another agent to pick up.

domain-modeling

mattpocock/skills

Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

codebase-design

mattpocock/skills

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

diagnosing-bugs

mattpocock/skills

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.