Write your requirements in conversation, and submit them when they read right

Project Discovery could already show you what your requirement document held. Now it writes it with you.

What changed

Tell it what you need and it puts the words down as you go. The document on screen fills in turn by turn — it is the version that is actually saved, not a summary of the conversation, so what you see is what is there. Come back tomorrow, or start a new conversation about the same request, and your draft is waiting.

Anything it worked out for itself rather than heard from you is marked inferred, with the reason next to it. Tell it that it got something wrong and it rewrites that section — the marking comes off, because the words are now yours. Alongside the document it also states plainly what it added that you did not say, so nothing arrives in a finished document as a surprise.

Submitting is yours

Nothing is sent until you say so, and saying “that looks right” is not the same as sending it. The assistant asks, you authorise, and only then does the document go for review. From there it goes to quality review and into the pool experts bid from, exactly as it does from the requirements page.

What it does not write

The service, timing, budget and the other details on your request belong to the request itself. The assistant will tell you which of those are still empty and why they matter to the experts pricing your work, but they are recorded on your requirements page rather than in the conversation.

Your requirements page still works exactly as it did — there is one document, whichever way you choose to write it.