alexion/ai-artifacts
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add artifact vault contents

Browse Source
This commit is contained in:
alexion
2026-08-01 14:05:09 -04:00
parent 361bde2621
commit 3230f9395b
78 changed files with 6156 additions and 42 deletions
Download Patch File Download Diff File Expand all files Collapse all files

56
projects/skills/040-implement-skill-matt-skills-discovery-research.md Normal file
View File

@@ -0,0 +1,56 @@
---
status: resolved
parent: "[[038-implement-skill-map]]"
claimed-by: "019fbb66-80d0-7a01-8ac9-01255adfc7b2"
claimed-at: "2026-07-31T23:42:05-04:00"
blocked-by: []
tags:
- ticket/research
---
# Implement skill Matt skills discovery research
## Question
Which Matt Pocock `mattpocock/skills` skills are relevant primary sources for migrating `implement`, and which ones need dedicated follow-up research tickets?
## Findings
The primary repository is `mattpocock/skills`, described by GitHub as "Skills for Real Engineers. Straight from my .agents directory." and organized under `skills/engineering`, `skills/productivity`, `skills/in-progress`, `skills/misc`, and `skills/deprecated`.
The engineering directory contains `implement`, `to-tickets`, `tdd`, `code-review`, and `wayfinder`, which are directly relevant to an implementation workflow that consumes tickets, builds code, tests, reviews, and understands Wayfinder semantics.
Source: `https://api.github.com/repos/mattpocock/skills`, `https://api.github.com/repos/mattpocock/skills/contents/skills/engineering?ref=main`.
Matt Pocock's `implement` skill is the closest direct comparison.
It implements work from a spec or set of tickets, uses `/tdd` where possible at pre-agreed seams, runs typechecking and tests, reviews with `/code-review`, and commits to the current branch.
It is much shorter and less prescriptive than the local old `/implement`, so it needs dedicated research to decide what simplicity to import and what local guardrails to keep.
Source: `https://raw.githubusercontent.com/mattpocock/skills/main/skills/engineering/implement/SKILL.md`.
Matt Pocock's `to-tickets` skill is relevant because it defines the producer side of ticket implementation work.
It creates tracer-bullet tickets, blocking edges, a frontier concept, tracker publication, and a wide-refactor expand-contract exception.
It needs dedicated research to compare its ticket assumptions with local `slice` and Wayfinder task artifacts.
Source: `https://raw.githubusercontent.com/mattpocock/skills/main/skills/engineering/to-tickets/SKILL.md`.
Matt Pocock's `tdd` skill is relevant because both Matt's and the old local implementation workflows delegate test-first mechanics to TDD.
It emphasizes pre-agreed seams, one test and one minimal implementation per cycle, and defers refactoring to review.
It needs dedicated research because the local TDD skill differs by using a test-writer sub-agent and more detailed anti-tautology mechanics.
Source: `https://raw.githubusercontent.com/mattpocock/skills/main/skills/engineering/tdd/SKILL.md`.
Matt Pocock's `code-review` skill is relevant because Matt's `implement` uses it as the review gate.
It reviews a branch against a fixed point with Standards and Spec axes in parallel sub-agents, whereas the old local review skill reviews uncommitted changes and also includes a Risk axis.
It needs dedicated research for deciding which review gate a migrated `implement` skill should require.
Source: `https://raw.githubusercontent.com/mattpocock/skills/main/skills/engineering/code-review/SKILL.md`.
Matt Pocock's `wayfinder` skill is relevant because it is the upstream-like version of the planning map workflow.
It uses issue trackers, labels, child issues, assignees, and native blocking relationships, while the local Wayfinder uses AI-artifacts Markdown, metadata claims, wikilinks, and self-resolving tickets.
It needs dedicated research only for contrast, so the migrated `implement` skill does not accidentally import tracker-specific assumptions.
Source: `https://raw.githubusercontent.com/mattpocock/skills/main/skills/engineering/wayfinder/SKILL.md`.
The productivity `handoff` and in-progress `claude-handoff` skills are adjacent but not central.
They summarize a conversation for a fresh agent and can suggest skills, but they do not define implementation execution, task lifecycle, review, branch, worktree, or PR policy.
They do not need dedicated follow-up research for this map unless a later decision expands the destination to session handoff automation.
Sources: `https://raw.githubusercontent.com/mattpocock/skills/main/skills/productivity/handoff/SKILL.md`, `https://raw.githubusercontent.com/mattpocock/skills/main/skills/in-progress/claude-handoff/SKILL.md`.
## Conclusion
Create dedicated follow-up research tickets for Matt Pocock's `implement`, `to-tickets`, `tdd`, `code-review`, and `wayfinder` skills.
Do not create follow-up research for Matt's handoff skills unless the map later expands into session handoff automation.