Write a result someone can verify
Name the user, the task and the observable result. For an appointment site, “a visitor can book an available slot and receive one confirmation” is more useful than “a modern website”. Include the empty, loading, error and retry states that affect that result.
Make ownership and operations explicit
List the information that must persist, who can see it and who can edit it. A public site also needs a plan for content updates, privacy, accessibility, backups and deployment. Mark each item as a confirmed requirement, a proposed default or an unresolved decision.
Review the handoff before coding
QERA collects your project answers into a protected brief for your chosen coding tool. Read that brief before sharing it. Check that the user, scope, exclusions and important integrations survived the handoff. Ask the coding agent to identify gaps and confirm its first milestone before it implements anything.
Check before handing it over
- One primary user and outcome
- Scope and explicit exclusions
- Data, roles and integrations
- Failure and recovery behavior
- Acceptance checks and open decisions