Job
Name the actor, the trigger and the finished state. One observable workflow is more useful than a platform manifesto.
Write the brief before you pick the builder.
Six sections turn a vision or a prompt into a buying instrument: the job, its boundaries, the exceptions, the evidence you will inspect and the handover you expect. Tool choice comes after the work is legible.
No account requiredAnswers stay in your browserNothing is sent to a serverAbout ten minutes
0 of 6 sections started
How the brief is used
The brief is the first product.
A builder—or a model—cannot invent the operating answers for you. Fill every section, including the ones that stay “not decided yet.” Empty sections are signals. Invented certainty is worse.
Boundaries
Write the data, actions and systems the first slice must not touch so a demo cannot expand the job midstream.
Exceptions
Unusual cases already exist. For each, name the owner, the evidence they need and how work returns to a known state.
Success evidence
Decide what you will inspect on review day in the real systems. Prefer completed tasks over a feeling that it was faster.
Handover
Say who holds access, documentation, maintenance, incidents and change approval before launch pressure arrives.
Open questions
List unknowns honestly, including what must remain exportable if you change partners later.