iterative:spike

To validate technical feasibility, run a lightweight spike by scoping uncertain questions and building throwaway artifacts. This process tests ideas and captures learnings in a durable spike document before you commit resources to a specific PRD direction.

A spike is a structured, lightweight framework to validate uncertain requirements by building minimal experiments. You should use a spike when exploring a new UX pattern or technical option to experience the approach and decide whether to pursue it further.

Create a spike document on your original branch to define your spike goal and scope uncertain questions. You can then build optional in-code or static HTML prototypes to illustrate the approach and record your validation learnings upstream.

Yes, running a lightweight validation spike requires a spike template to structure your experiments. You use this template to create a durable spike document on the original branch, ensuring your throwaway artifacts and learnings are properly captured.

Yes, you can build optional static HTML prototypes or in-code artifacts to validate ideas without heavy engineering. These throwaway artifacts allow you to experience and test technical options or UX concepts before committing to a full implementation direction.

You should avoid using a spike when the requirements are already certain or when heavy engineering is justified for immediate production. Spikes are specifically designed for lightweight validation of uncertain questions, not for building durable, final implementation artifacts.