setup-matt-pocock-skills

Topics in the source

• Setup Matt Pocock's Skills
• Process
• 1. Explore
• 2. Present findings and ask
• 3. Confirm and edit
• 4. Write
• 5. Done

Scaffold the per-repo configuration that the engineering skills assume: Issue tracker — where issues live (GitHub by default; local markdown is also supported out of the box) Triage labels — the strings used for the five canonical triage roles Domain docs — where CONTEXT.md and ADRs live, and the consumer rules for reading them This is a prompt-driven skill, not a deterministic script. Explore, present what you found, confirm with the user, then write. Look at the current repo to understand its starting state. Read whatever exists; don't assume: git remote -v and .git/config — is this a GitHub repo? Which one? AGENTS.md and CLAUDE.md at the repo root — does either exist? Is there already an ## Agent skills section in either? CONTEXT.md and CONTEXT-MAP.md at the repo root docs/adr/ and any src//docs/adr/ directories docs/agents/ — does this skill's prior output already exist? .scratch/ — sign that a local-markdown issue tracker convention is already in use Summarise what's present and what's missing. Then walk the user through the three decisions one at a time — present a section, get the user's answer, then move to the next. Don't dump all three at once. Assume the user does not kn

This is an excerpt. Refer to the complete source and its current requirements.