prototype

Rapid prototyping validates feasibility by planning a focused hypothesis, isolating throwaway code in a dedicated directory, and producing a structured report. It ensures teams answer the core concept question with minimal overhead before investing in production-grade rigor.

The best way to isolate throwaway code is to create a dedicated prototypes/[concept-name]/ folder filled with intentionally simple, non-production code. This directory keeps experimental builds separate from the main source tree.

Structure a testing plan for rapid prototyping by defining a focused concept question upfront, executing an isolated throwaway build, and capturing metrics with lessons learned in a structured REPORT.md file for stakeholders.

A prototype report recommends next steps for stakeholders by capturing the hypothesis, approach, results, metrics, recommendation, and lessons learned in REPORT.md. This structured reporting ensures stakeholders understand the outcome and next move clearly.

No, rapid prototyping does not require production-grade code rigor. It intentionally uses simple, non-production throwaway code to validate concepts quickly without the overhead of a full production implementation.

Avoid throwaway code for concept validation when production-grade rigor or permanent implementation is required. Throwaway prototypes are intentionally simple, non-production builds meant for quick feasibility confirmation rather than main source tree integration.