43 lines
2.8 KiB
Markdown
43 lines
2.8 KiB
Markdown
---
|
|
status: resolved
|
|
parent: "[[040-implement-skill-matt-skills-discovery-research]]"
|
|
claimed-by: "019fbb66-80d0-7a01-8ac9-01255adfc7b2"
|
|
claimed-at: "2026-07-31T23:47:59-04:00"
|
|
blocked-by:
|
|
- "[[040-implement-skill-matt-skills-discovery-research]]"
|
|
tags:
|
|
- ticket/research
|
|
---
|
|
|
|
# Implement skill Matt implement research
|
|
|
|
## Question
|
|
|
|
What should the migrated local `implement` skill preserve, adapt, or reject from Matt Pocock's `skills/engineering/implement` skill?
|
|
|
|
## Findings
|
|
|
|
Matt Pocock's `implement` skill is explicitly invoked and disabled for model invocation, like the old local skill.
|
|
It accepts "a spec or set of tickets" rather than a single required task-file path.
|
|
The migrated local skill should keep explicit invocation, but decide whether to allow maps, specs, or multiple tickets or to preserve one-ticket execution for Wayfinder claim safety.
|
|
Source: `https://raw.githubusercontent.com/mattpocock/skills/main/skills/engineering/implement/SKILL.md`.
|
|
|
|
Matt's skill says to implement the work described by the user in the spec or tickets, use `/tdd` where possible at pre-agreed seams, run typechecking regularly, run single test files regularly, and run the full test suite once at the end.
|
|
This aligns with the old local workflow and should be preserved.
|
|
Source: `https://raw.githubusercontent.com/mattpocock/skills/main/skills/engineering/implement/SKILL.md`.
|
|
|
|
Matt's skill reviews with `/code-review` once done and commits work to the current branch.
|
|
It does not prescribe syncing `main`, creating a branch, staging specifically, pushing, opening a PR, or closing out a ticket artifact.
|
|
The migrated skill should not import this omission wholesale because Wayfinder task lifecycle and old local guardrails need stronger state handling.
|
|
Source: `https://raw.githubusercontent.com/mattpocock/skills/main/skills/engineering/implement/SKILL.md`.
|
|
|
|
There is no packaged local `implement` counterpart yet, so the practical local counterpart is the old dotfiles `/implement` skill.
|
|
Compared with Matt's minimal version, the old local skill owns branch creation, blocker reachability checks, review report reuse, task-file closeout, commit convention discovery, push, PR creation, and final reporting.
|
|
The migration should deliberately choose which of those local responsibilities remain in the packaged skill rather than defaulting to Matt's current-branch commit-only model.
|
|
Sources: `/home/alexion/wrk/dotfiles/modules/agents/claude-code/skills/implement/SKILL.md`, `/home/alexion/wrk/skills/skills`.
|
|
|
|
## Conclusion
|
|
|
|
Matt's `implement` is useful as a simplicity reference: implement from an explicit spec or tickets, use TDD at agreed seams, verify regularly, review, and commit.
|
|
The migrated local skill should remain stricter than Matt's around Wayfinder claiming, branch setup, artifact closeout, and PR or handoff reporting.
|