contexts

# Context Command Auto-router for pre-implementation context gathering. Classify the input as codebase-oriented, doc-oriented, or both; invoke the appropriate workflow; emit a `detected:` acknowledgement as the first output line. ## When to Apply / NOT **Apply:** - Any request for context, background, or orientation before implementing, fixing, or refactoring - "How does X work", "get me context on Y", "what's the architecture of Z" **NOT apply:** - Bug reproduction or root-cause investigation: use a debugging workflow - Already-in-progress implementation: gather context first, then proceed - Analysis-only output with no pre-implementation intent ## Detected Mode Acknowledgement [LOAD-BEARING] First output line before ANY work: ``` detected: <mode> — scope=<paths|libs|both> sources=<brief summary> ``` Mode values: `code-ref`, `doc-ref`, `both`, `ambiguous`. For `both` mode, also append: `(sequential dispatch: codebase first, then external)` ## Input Classifier First-match wins. Check in order: `both` must come before leaf modes so mixed-signal inputs are reachable. | Priority | Mode | Minimum condition | |----------|------|-------------------| | 1 | `both` | Repo-local signal (path, glob, symbol, or module) AND external signal (library, framework, SDK, API, CLI, or service name) both present and non-trivial | | 2 | `code-ref` | Repo-local signal present; no external signal | | 3 | `doc-ref` | External signal present; no repo-local signal | | 4 | `ambiguous` | Neit...