Project scoping: an AI that asks questions is better than one that guesses

A founder sums up the problem in one sentence: without a real specification, the tool designs things its own way and they spend their time catching up. Scoping through questions solves this before the first line of code, provided someone asks them.

Scoping a project begins with the questions the tool asks before making assumptions for you. A founder describes it on Reddit (r/vibecoding, June 2026): 'When I don't give it a real specification, it designs things its own way, and I spend my time catching up.'

What happens when the tool guesses

An AI told you want 'software to manage my customers' does not stay stuck: it chooses. It decides a customer has a name, email, and phone number, can be deleted in one click, and is accessible to one user. Each decision is reasonable in isolation, and none came from you. You discover them through use, often three weeks later when your partner asks where the archived customers went. Corrections then arrive out of order, each resting on foundations nobody documented, and the rework bill exceeds construction. The same author names the difficulty plainly: their weakness, they write, is not knowing how to write that initial design. The blockage concerns that document, which the machine gladly produces alone when nobody provides it.

The questions that change the outcome

Useful scoping consists of a dozen short questions asked in a sensible order. 'Who will use this software, how many people, with what permissions?' 'What happens when a file is cancelled after payment?' 'What information must you retrieve in two years for an inspection?' 'What would make you say in three months that the product failed?' They force decisions while a decision still costs a sentence instead of a week of rework. Technical vocabulary is irrelevant: you answer in your business terms, the tool translates, and the translation is reviewed. A dozen written answers are worth more than thirty pages copied from a template because each comes from you. We expanded this elsewhere, for when the exact words to describe an idea are missing.

Who already asks questions

The market is beginning to do this, and some do it well. Replit starts projects with serious scoping, the best we encountered among browser-based tools, and we wrote that without reservation. Several generators offer a mode where the assistant presents a plan before building. The limit is what happens next: the plan appears in a conversation, scrolls away, and nothing guarantees the delivered code follows it three screens later. A question asked and then forgotten is as good as never asked.

The document proposed to you, not demanded of you

At Maestro, the first agent is Margaux and her only job is scoping through questions. She asks, you answer in everyday French, and she proposes a brief you read. Nothing starts until you say 'Looks good to me': the document is a proposal, never a given. Victor then takes over the specification, with the same gate to cross. This reversal matters: most methods ask you to bring a specification you do not know how to write, while a proposed first draft can be corrected in an hour. Beware the opposite trap, which cost a founder nine months of work (r/startups, July 2026): an approved document is not an agreement if people nodded without reading it.

Try it tonight

Take the tool you already use and, before describing your idea, ask it to ask ten questions about it and wait for your answers. Note the questions you cannot answer: those are the real ambiguities it would have filled for you. Answer them away from the machine, with your partner or accountant, then return. If the tool proceeds to code without waiting anyway, you know what is missing, and an hour on a specification will cost less than three weeks of corrections. Keep your answers in a document you reread at every stage: it will settle matters when two teammates remember the same decision differently.