Removes the five docs-page-only changesets (quickstart drop, grill-me pass, four-section spine, rewrite-to-standard, writing-for-agents pass) — the changelog reports on the shipped skills, not on the site pages. Merges the clusters that describe one change each: ask-matt routing, the grilling round-by-round rework, prototype, wayfinder, wizard and writing-for-agents. 27 changesets become 15. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2.5 KiB
mattpocock-skills
| mattpocock-skills |
|---|
| patch |
Sharpen /ask-matt — the router now covers phase boundaries, the two wayfinder mistakes, and two skills it never mentioned.
Phase boundaries. A phase is a chunk of work inside a session — the grilling, the implementation, the QA — and the boundary between two of them is where you decide what to do with the context you've built. The two-bullet Crossing sessions section is replaced by a decision tree carrying all five options in order (continue, /clear, /handoff, subagent, /compact), with the reasoning disclosed in a new PHASE-BOUNDARIES.md. Three fixes come with it:
/handoffwas oversold. It read as the general bridge between context windows. It's narrow: you need it only when something has to travel — a new harness, a new directory, a colleague, or a side task forked mid-phase. What it buys is portability./compactis the default, not the first reach. It sits at the bottom of the tree, after the four cheaper or more precise questions above it. Starting there produces a session that's confidently wrong about whatever the summary flattened.- Two branches were missing entirely. Continue is the one to rule out first — it's the only move that keeps the conversation as a primary source rather than a summary of one — and a subagent handles anything scoped tightly enough to run AFK.
Context hygiene's escape hatch now says /compact rather than /handoff (same harness, same directory, at a boundary — the handoff clause doesn't apply), and the smart zone figure is updated from ~120k to ~150k tokens.
Wayfinder routing. The two mistakes people most often make with the heaviest, most cognitively demanding flow:
- Over-reaching for it. It's slower and denser than a single grill, so it's flagged as the heaviest flow and reserved for the idea that genuinely won't fit one session — a well-scoped feature belongs on
/grill-with-docs, not here. - Losing the way at the handoff. When the map clears, wayfinder hands off, it doesn't build: merge onto the main flow at
/to-spec(which collapses the map's linked decisions into a buildable plan) rather than looping the map straight into/implement. Straight-to-/implementis only for efforts that turned out genuinely small.
Missing routes. /grilling and /resolving-merge-conflicts were absent from the router altogether and are now in it, and grill-me splits from grill-with-docs on whether you are in a working directory.