Don’t argue about the abstract — have an agent build the cheap version and refine that.
The team friction Refinement debates the unbuilt: people argue past each other about a feature nobody can see, estimating in the dark, discovering the real questions only once someone finally starts coding — days later, alone, far from the team. The team’s shared understanding forms after the decisions are already made.
The pattern Someone has an agent throw together a rough prototype first, then brings it to refinement as the discussion object. The team reacts to something concrete — clicks it, sees the edge cases, finds the real hard parts — and refines against reality. The bring it to the team half is the pattern: a solo prototype is just an experiment; refining it together is the collaboration.
Why it works with AI A throwaway prototype used to cost days, so you debated instead. Agents make it an afternoon — so the cheapest way to resolve a team disagreement is often to build the thing badly and look at it together. Concrete artifacts align people that abstract tickets never will.
Watch-outs The prototype is a conversation starter, not a head start on production — say so, or it quietly becomes the foundation nobody chose. Throw it away on purpose.
Related Gap analysis: prototype vs. product · Executable specs · Agent backlog analysis