silverresearchlisted

# /silver:research — Tech Decisions, Architecture Spikes, Comparisons SB orchestrator for technology decisions, architecture spikes, tech comparisons, and competitive intelligence. Research always precedes implementation — findings are written to `.planning/research/` and referenced by the receiving workflow. **Routing note:** `silver:research` takes precedence over any other matched workflow — research informs the implementation workflow. If an instruction matches both research and feature/devops, run research first, then hand off. By default, research runs directly in the current host session using repository context, local artifacts, official docs, primary sources, and other concrete evidence available through the host/runtime. MultAI is optional and is used only when the user explicitly requests multi-AI perspectives in the current task. After research is complete, hand off to the appropriate implementation workflow. ## Mandatory dependency execution Before any local research write-up or handoff, the execution trace must show the dependency chain for this workflow. At minimum: 1. Invoke `silver:clarify` 2. Run the selected research path in the current host session; invoke MultAI only when the user explicitly requested it in the current task 3. Invoke `silver:clarify` 4. Handoff to `silver:feature` or `silver:devops` only after the research artifact exists If any required downstream skill cannot be invoked, stop immediately and notify the user. If the user explicitl