What problem does it solve? Exploratory coding often sprawls into unscoped work with no record of what was tried or learned. This Skill keeps spikes focused on a single outcome within a timebox and captures a running journal so the learning survives even when the code does not. ## Core Features & Use Cases - Timeboxed Exploration: Enforces a defined timebox with at most one 50% extension before forcing a land decision. - Running Journal: Maintains a dated spike-journal.md recording what was tried, what broke, what surprised, and the current best guess. - Graduation Triggers: Detects signals like sharing requests, auth needs, or file sprawl that mean the work has outgrown spike territory. - Use Case: You want to test whether a new API can power your feature. Run a two-day spike, journal each attempt, then hand the code and journal to the land step for a Keep, Toss, or Promote decision. ## Quick Start Start a spike to test whether the payments API supports recurring charges, timeboxed to one day, and keep a journal of everything you try.