What problem does it solve? Open-ended research stalls software projects because investigations expand without a clear stopping point. This Skill converts a blocking unknown into a focused, timeboxed question, investigates just enough to decide, and routes the answer back to the phase that asked for it. ## Core Features & Use Cases - Focused spike questions: Sharpens vague research requests into one specific, answerable question with a clear "enough to decide" threshold. - Timeboxed investigation: Sets an explicit timebox based on complexity and stops the investigation once the question is answered, preventing scope creep. - Structured results with confidence levels: Returns a finding, a High/Medium/Low confidence rating, and the implication for the calling phase, then hands control back. - Use Case: During planning, you are unsure whether a third-party API's rate limits support your expected load. Run a spike to check the API documentation and limits, then return a decision on whether the architecture is viable. ## Quick Start Run a research spike on whether the payment provider's API supports recurring billing with our expected transaction volume before we commit to this architecture.
