Go from ignorance to vague familiarity across a whole name-dropping domain — "just deep enough to hurt." The breadth-first sibling to /study: point it at a domain you don't know (often just a name), and it researches the terms worth recognizing, teaches them in batched 1-2-paragraph lessons with a quiz per item, and leaves a durable one-line-each summary you re-skim before the room. Recognition, not reconstruction. Replaces "three hours on Google." Distinct from /study (deep, one system, reconstruct-under-pressure) and /refresh (re-warm what you already learned). Usually user-invoked; agent may suggest it when "make sure I recognize these next time" intent appears.
Assess the current state of a feature, system, or area. Produces a durable assessment doc that downstream skills (/draft, /plan) can consume. Use --capacity to include napkin math (QPS, storage, bandwidth).
Create a working design document for collaborative iteration. Use when scoping a feature, system change, or workflow — the doc is the conversation artifact, not a summary.
Session startup. Walks the .meta/ tree to load user and domain context, orients to the current project, and gives a brief status summary so we can hit the ground running.
Lightweight session start — the sparse floor below /hello. Does a minimal tree walk (signpost-flag inheritance + root WORKFLOW.md) then reads the local .meta/ — but no full state read and no network. Auto-escalates to /hello for domain/neighborhood/full-state context; never runs MCP/API/calendar or hello.check. Use when you want to get moving fast without the full orientation.
Pre-merge review. Diffs the session's work against the base branch, resolves its review dimensions (configurable via signpost `review.dimensions`/`extra-dimensions`, else inferred from the medium — code default: bugs/efficiency/redundancy/architecture — with `redundancy` the recommended-but-configurable example), always runs the structural dimensions (design/track/merge reconciliation), then presents fixes for approval before committing.
Session retrospective and calibration. Use mid-session (1-2 questions) when you hit a specific friction point or made a judgment call you're unsure about. User invokes with /retro for a fuller end-of-session retrospective.
Lightweight iteration mode for grab-bag branches. Creates a track file, enforces note-before-code for non-trivial changes, and uses /defer as the scope-escalation escape hatch. Always user-invoked.