| name | unfold |
| description | Understand, diagnose, change, or review an unfamiliar codebase through one evidence-backed mission. Use when learning architecture, tracing a feature, investigating a bug, implementing a real change with guided or agent execution, reviewing a diff or PR, or checking whether tests and the built artifact prove the intended behavior. Prefer over prose-only repository explanations and ungrounded debugging. |
| compatibility | Requires repository read access. Repository writes depend on the selected mode and user authorization. Mermaid rendering and a structured ask-user tool are optional enhancements. |
Unfold
Turn one maintenance mission into a navigable mental model, an evidence-backed change, and proof proportional to the work. Reuse what has already been established instead of restarting the repository tour at every phase.
1. Establish the mission
Frame one concrete question or outcome:
How does [operation or symptom] travel from [entry] to [outcome], and what evidence would prove the result?
Read existing .unfold/ artifacts before broad exploration. Compare their recorded commit with HEAD and reverify decisive anchors against current source.
Read references/protocol.md for the shared evidence and artifact contract.
2. Select the earliest incomplete mode
Choose one primary mode. Load only its reference.
