prototype

Rapid prototyping validates product ideas by turning them into isolated throwaway code and a structured report. This approach enforces isolation, avoids production code, and captures decisions in memory_bank through gated phases and review artifacts.

Documenting API contracts during concept exploration is best handled by generating a structured prototype report. This captures decisions in memory_bank artifacts and uses gate-driven workflows to record evaluation outcomes for future reference.

Yes, you can prototype game concepts and technology choices using this workflow. It targets these specific areas by guiding rapid exploration, evaluation, and handoff through isolated development and structured decision-records.

To start the prototype workflow, invoke the command `/prototype [concept-description]`. This initiates the gate-driven process, generating throwaway code and a structured report with clear next steps for evaluation.

Gate checks and decision records are required in rapid prototyping to maintain governance and reduce resource waste. They ensure isolated development phases are properly reviewed and captured in memory_bank artifacts for future reference.

Throwaway code for prototype validation is strictly isolated and avoids production code entirely. This limitation ensures concepts are tested fast without architectural overhead, yielding a structured report and clear handoff steps rather than a deployable application.