mattpocock/skills at 9603c1cc, reviewed July 18, 2026. Repository license: MIT.
Representative artifacts
Issue-tracker output is the default model, with a local
.scratch/<feature>/issues/ fallback for ticket files. to-tickets favors vertical slices and uses expand, migrate, and contract for broad refactors that do not fit that grain.
Workflow and task grain
to-spec focuses on decisions and testing seams. It generally avoids exact file paths and large code snippets unless a prototype excerpt carries an important decision. to-tickets turns the accepted specification into independently useful work with explicit dependencies. wayfinder handles earlier uncertainty by separating decisions, questions, agent research, human input, and work that is not precise enough to schedule.
The domain-modeling skill recommends a very small ADR only for a surprising, hard-to-reverse tradeoff. A separate CONTEXT.md can preserve preferred terms and terms to avoid.
Inspect the same-case output
Inspect the generated specification and 11 local tickets for reliable webhook delivery. The run completed the specification and dependency-aware local-ticket flow without creating remote issues.Choose these skills when
- the team wants composable procedures rather than a required end-to-end method;
- an issue tracker is the shared planning memory;
- uncertain work should be mapped before it becomes implementation tickets; and
- outcome-focused tickets are more useful than code-level instructions.
CONTEXT.md example exists in the linked Course Video Manager project, but that repository has no clear reuse license; this site links and paraphrases it rather than copying it.
See the AI coding plan template, ADR formats, and coding-agent handoff template.
Reviewed July 19, 2026. Researched and maintained by the Plannotator documentation team. Matt Pocock’s name is used for identification; Plannotator is not affiliated with or endorsed by him.