What problem does it solve? Some design decisions cannot be settled by reading code or docs — they need to be seen running. This Skill builds disposable prototypes (an interactive state harness or several UI variants) so a human can react and the decision gets resolved, without polluting the main codebase. ## Core Features & Use Cases - Two prototype shapes: an interactive harness that drives a state machine by hand for logic questions, or three to four radically different UI variants switchable on one screen for look-and-feel questions. - Throwaway discipline: prototypes live on a named throwaway branch beside what they prototype, run with one command, keep state in memory, and skip tests and polish. - Verdict landing: folds the validated decision into the real code or ticket, posts the verdict on the ticket via the tracker adapter, and points at the branch instead of pasting code. - Use Case: A team cannot agree whether a wizard's state model handles back-navigation correctly. Build a small harness that steps through the tricky transitions, show it to the team, and record the settled decision on the ticket. ## Quick Start Ask the agent to prototype the stuck design question as throwaway code on a scratch branch so you can react to it and settle the decision.