gsd-spike

To validate feasibility before building, you run structured spikes that convert vague ideas into experiential, evidence-backed knowledge. This reduces the risk of building the wrong thing by verifying risks and missing pieces through focused exploration.

Spike planning in product discovery is a structured method to explore proposed ideas and validate feasibility before real implementation. You use it when you need to assess risks, identify missing pieces, and generate verified knowledge for complex features.

You document and hand off verified knowledge by persisting spike outputs under a dedicated directory and following structured commit patterns. This ensures your experimentation findings drive the real build by maintaining state tracking and verification workflows.

Yes, you can run a quick spike for simple ideas that bypasses full decomposition and alignment. This allows you to rapidly validate a proposed idea and generate verified knowledge without the overhead of complete workflow-gated execution.

The best way to identify gaps in an existing spike landscape is to analyze it using a frontier mode approach. This evaluates your current experimentation efforts and proposes the next best spikes to close integration gaps and improve overall coverage.

Prior spike checks and observability assessment are required to ensure workflow-gated execution produces reliable, verified knowledge. This structured approach orders research and risks appropriately, guaranteeing that feasibility validation is thorough before real implementation.