The workshop. Every component from the stack map and every phase from the pipelines, tagged in one place. Done = export as a Markdown action list, paste back into Claude, build sprints.
The map shows dozens of things. You can't act on that many things. Triage compresses the map into a focused action list. You tag each component or pipeline phase with one of six labels. The export turns that into Markdown or a Claude prompt for sprint planning.
It works. Don't touch it. Tagging these clears them off your radar so you can focus on the rest.
e.g. Morning brief, Stripe billing, MCP server itself.
Broken, unreliable, or wastes time. Works "if you remember to avoid the bad path." Highest-leverage fixes.
e.g. Portal Bridge 401, empty client_health tables, Notion-Supabase sync gap.
Overlaps something else. Two systems carry the same truth and drift. Decide which is canonical and collapse the other.
e.g. Tooling Directory (now deprecated — map won).
Would become reliable if a skill existed. Right now it's tribal knowledge or one-off.
e.g. Phase 08 refresh cadence, Pattern Cloud adoption.
Works, but requires manual steps that could be automated. Different from Skill: the procedure is clear, the wiring isn't done.
e.g. Notion-to-Supabase company sync.
You see the problem but it's not worth fixing now. Tagging Defer is permission to stop thinking about it this pass.
e.g. Claude in Chrome (deferred 2026-05-24).
Tags persist in your browser (localStorage). Come back anytime.