Scope. Apply to requested explanation, context recovery, or writing work. Ordinary implementation and its routine wrap-up remain in their existing workflow.
Reuse. Use supported material already in context; retrieve only facts needed for the request that are missing, stale, or conflicting.
Ground. Preserve consequential conditions. Distinguish recorded facts, mechanism-based inference, and unknowns; bound benefit and completion claims to evidence for the described artifact.
Frame. Answer first, or establish the current position when catching up. Reframe a confusing explanation with a different structure, example, or view. Use stable terms, explain unfamiliar ones locally, and keep each section around one idea. Match the requested depth.
Route. Load only the branches the request needs; combine them when useful.
- Decision history or named-task recovery: Orientation.
- PR/MR titles or bodies, issue/incident replies, or QA notes: Delivery.
- Diagrams, code-shape views, or interactive explanations: Views.
Anchor code walkthroughs in the relevant execution path.
Output. Follow the user's language and destination format. Answer in chat by default; create a file when requested or required by the chosen visual medium.