What problem does it solve?
Teams often debate feasibility, fit, or approach choices without evidence, wasting weeks on ideas that fail late. This Skill settles open technical questions by building the smallest artifact that could falsify a hypothesis, ending in a PROVEN, DISPROVEN, or CONDITIONAL verdict backed by reproducible evidence.
Core Features & Use Cases
- Falsifiable Framing: Converts vague questions into precise hypotheses with pre-committed kill criteria and verdict boundaries before any code is written.
- Isolated Experimentation: Runs spike code in a dedicated git worktree that never opens a PR, keeping disposable experiments away from production branches.
- Evidence-Based Verdicts: Produces a structured spike report with observed evidence, verdict provenance, limits, and routing recommendations for the decision.
- Use Case: When asked "can our schema support real-time collaboration without a migration", the Skill frames a falsifiable claim, builds a minimal probe against the real schema, stress-tests it, and delivers a verdict with the evidence stored for anyone to re-check.
Quick Start
Ask the agent to spike whether a specific idea is feasible, for example: spike whether we can stream large query results through our current API layer without hitting memory limits.