mirror of
https://github.com/mattpocock/skills.git
synced 2026-07-29 02:52:42 +07:00
Matt PocockandClaude Opus 4.8
e74fee89fe
Wayfinder is the heaviest, most cognitively demanding flow, and the wiki shows people misusing it two ways: over-reaching for it on well-scoped work (it's slower and denser than a single grill), and losing the way at the handoff after the map (looping straight into /implement and skipping /to-spec). Sharpen the router's wayfinder on-ramp to steer both. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
11 lines
798 B
Markdown
11 lines
798 B
Markdown
---
|
|
"mattpocock-skills": patch
|
|
---
|
|
|
|
Make `/ask-matt` clued-up about `/wayfinder` — the heaviest, most cognitively demanding flow.
|
|
|
|
The router now sharpens the two routing mistakes people most often make with wayfinder:
|
|
|
|
- **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-`/implement` is only for efforts that turned out genuinely small.
|