Menu
Use when orienting in an unfamiliar area: fans out parallel explorers across code, knowledge, and history, then synthesizes one orientation map.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when grilling should be grounded primarily in project artifacts. Loads `/grill`, checks project vocabulary and prior decisions first, and spawns bounded explorers when the answer should come from docs.
Load for large human-facing outputs: reports, docs, multi-section explanations, artifacts. Choose the right form for each beat (prose, diagram, table, mockup) and put the answer first, depth behind it. If the medium allows, use progressive disclosure.
Use when deciding where knowledge goes or reading/writing durable docs: AGENTS.md, .context/, KB, docs/, and work directories.
Anchor work in a work item: artifacts on disk, not in context.
Investigate and engage concurrently: don't block on evidence before surfacing your read.
Use when exploring or changing the codebase: read AGENTS.md first, use .context/CONTEXT.md for detail, keep intent docs succinct.
| name | zoom-out |
| type | mode-shift |
| description | Use when orienting in an unfamiliar area: fans out parallel explorers across code, knowledge, and history, then synthesizes one orientation map. |
| user-invocable | true |
| model-invocable | true |
Load /qi-layer if it isn't already loaded.
Orient in an unfamiliar area by fanning out parallel explorers, each covering a different angle, then synthesizing their reports into one orientation map. A single explorer sees one slice; zoom-out covers code and knowledge and history at once, so the picture isn't skewed by one lens.
Use when starting in an unfamiliar subsystem, picking up someone else's work, or when the user says "orient me" / "what's the lay of the land here."
Spawn in parallel, each scoped to one angle and one question. Drain with meridian spawn wait.
@explorer): callers, dependencies, module boundaries, entry points, where behavior actually lives.@explorer over the KB, meridian context kb): what's been written about this area, including architecture, guides, synthesized research.@session-miner): why it's shaped this way. Prior choices, rejected alternatives, constraints discovered. Skip when there's no relevant session history.@explorer): the vocabulary in use (KB vocab pages, .context/CONTEXT.md, AGENTS.md).Scope each prompt to its angle with concrete path or topic targets. Don't let one explorer cover two angles: the value is independent coverage.
Read the reports and produce one orientation map, not four stitched-together dumps:
When reports contradict each other, resolve it rather than listing both: code is ground truth; a doc that disagrees is stale (note it). Keep the map tight: the goal is a reader who can now navigate the area, not an exhaustive transcript.