メニュー
Use when orienting in an unfamiliar area — fans out exploration across structure, knowledge, and history, then synthesizes one orientation map.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
Use when exploring or changing the codebase: read AGENTS.md first, use .context/CONTEXT.md for detail, keep intent docs succinct.
Load before writing or revising human-facing text. Choose words deliberately, ground the piece in the reader's context, and remove default LLM phrasing before the final draft.
Use when validating markdown links or Mermaid diagrams.
User-invoked pause before reporting to check intent vs literal completion, surface adjacent wins, and route knowledge capture.
| name | zoom-out |
| description | Use when orienting in an unfamiliar area — fans out exploration across structure, knowledge, and history, then synthesizes one orientation map. |
Load /qi-layer if it isn't already loaded.
Orient in an unfamiliar area by exploring multiple angles — each covering a different lens — then synthesizing the findings into one orientation map. A single angle sees one slice; zoom-out covers structure 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."
Explore each angle independently, scoped to one question each:
Scope each exploration to its angle with concrete path or topic targets. Don't let one pass cover two angles — the value is independent coverage.
Read the findings and produce one orientation map, not four stitched-together dumps:
When findings 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.
