Wayfinder Maps
Plan a huge chunk of work — more than one agent session can hold — as a shared map of investigation tickets, and resolve them one at a time until the way to the destination is clear.
Improve Codebase Architecture
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
Grill With Docs
A relentless interview to sharpen a plan or design, which also creates docs (ADRs and glossary) as we go.
Handoff
Compact the current conversation into a handoff document so a fresh agent can continue the work.
Grill Me
A relentless interview to sharpen a plan or design — one question at a time until every branch of the decision tree is resolved.
Prototype
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
To Spec
Turn the current conversation into a spec, saved to `.plan/` — no interview, just synthesis of what you've already discussed.
Verify
Build, launch and drive wayfinder-maps to verify a change end-to-end (server + headless browser).
To Tickets
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, saved to `.plan/`.
Codebase Design
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
Writing Great Skills
Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.
Research
Investigate a question against high-trust primary sources and capture the findings as a cited Markdown file. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated.
Review Code
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating spec/PRD asked for?). Use when the user wants to review a branch, work-in-progress changes, or asks to "review since X".