rig-spikelisted

# Research Spike A spike is a **time-boxed investigation** whose deliverable is *knowledge*, not shipped code. You answer a specific question, surface the trade-offs, and recommend a path — so the team can plan implementation with confidence instead of guessing. Use a spike when the work is *uncertain*: feasibility is unknown, there are multiple viable approaches, an unfamiliar API/library is in play, or scope can't be estimated until something is prototyped. If the path is already clear and it's just work to be done, skip the spike and go straight to implementation planning. ## Configuration Reads `.rig/config.json`: - `sourceScope[0]` — the default code scope explorers map first (default: `src`). - `tracker.provider` — `linear` | `github` | `none` (default: `none`). When `none`, skip all tracking-ticket steps and deliver the writeup in chat only. When set, optionally create a `Spike:` tracking ticket and post findings back to it. - `tracker.team` / `tracker.project` — where a Linear tracking ticket is filed, when the provider is `linear`. - `agents.architect` — the project's name for the canonical `architect` role (default: `architect`). `Explore` and `Plan` are Claude Code built-ins and are used as-is. If the file is absent, use the defaults above (treat the tracker as `none`) and note you're running unconfigured. **Core rules of a spike** - **Time-box it.** Decide the budget up front (default: half a day / ~4h of effort). The goal is *enough* signa