advisor-consultation

# Consulting the Advisor Use a tool-free Opus advisor to improve a decision, not to outsource exploration or execution. The main agent remains responsible for repository inspection, scope, security, implementation, verification, and the final decision. ## Trigger decision | Situation | Action | | --- | --- | | User explicitly requests an advisor, second opinion, or Opus review | Consult once. | | Cross-crate/API contract, event/prompt/tool boundary, security-sensitive, concurrency/lifecycle decision, or two credible options with material trade-offs | Consult after exploration. | | Two reasonable investigations failed to distinguish the root cause | Consult after recording their outcomes. | | Local, reversible change with a clear tested path | Do not auto-consult. | | Advisor would need to inspect the repository to answer | Gather the missing evidence first; do not ask it to guess. | For an extreme-risk decision, the main agent may collect the advisor's requested minimum evidence and consult again. Do not loop merely to seek agreement. ## Prepare the decision packet Before dispatching `.claude/agents/advisor.md`, inspect the relevant code, tests, contracts, and current diff. Send only the smallest packet that lets a tool-free advisor reason correctly: ```markdown # Advisor Decision Packet ## Task contract - Goal: - Success criteria: - In scope / out of scope: - Constraints, deadline, and risk: ## Evidence - Code facts: `path:symbol` plus necessary excerpts. - Tests, e...