nav-brief

# Navigator Intent Brief Skill Front-load the scope negotiation. When a prompt is task-shaped but ambiguous, render a one-screen INTENT BRIEF and get confirmation **before** writing code — turning 2-4 correction exchanges into 1 confirmation exchange. ## Why This Exists Ambiguity is not complexity. A small task can be highly ambiguous ("fix the bug" — which bug?) while a large one can be fully specified. The expensive failure mode is implementing on guessed scope: rework burns tokens on undo/redo, pollutes context with dead ends, and forces mid-feature compacts. ## When This Fires **Hook contract**: render a brief ONLY when this turn's injected context contains a `NAV-BRIEF` reminder block (emitted by the `prompt_brief` op — `hooks/ops/prompt_brief.py`, dispatched by `nav_dispatch.py` — on UserPromptSubmit when ambiguity score >= threshold). Never self-trigger from your own judgment alone — the hook is the single trigger source, so behavior stays predictable and tunable via config. Config (`.agent/.nav-config.json`): ```json "brief_hook": { "enabled": true, "ambiguity_threshold": 0.5, "memory_budget_chars": 1200 } ``` ## Rendering the Brief Use the template below. Pre-fill every field you can from the injected `## Relevant Memories` section and current session context; mark assumptions explicitly. ``` ┌─ BRIEF: <short title> ──────────────────────────────┐ │ Goal <outcome, one line> │ │ Scope <files/dirs/endpoints — concrete> ...