---
name: Communicate spike scope upfront
description: User feedback - draw the line on spike vs real implementation earlier, don't let throwaway code become the design surface
type: feedback
---

When running a spike/proof-of-concept, explicitly state the exit criteria upfront and redirect when feedback shifts from "does this work?" to "make this look right." The user shouldn't have to ask "when should I stop suggesting changes?" - that's a sign the scope boundary wasn't communicated.

**Why:** User iterated on spike polish that would be thrown away when building the real thing. Time spent polishing throwaway code is building twice.

**How to apply:** At the start of any spike, state: "This spike validates [specific question]. Once we confirm [X works], we move to real implementation. Visual polish belongs in the real build." Redirect when feedback crosses from validation to design.