design-brief-from-conversationlisted

# Design brief from a client conversation You have come out of a client meeting with scattered notes and need a written brief that the client can confirm or correct before design work starts. ## Inputs to collect Ask the user for any of these you do not already have. Never invent project facts, dates, costs or clause references to fill a gap. - `{{budget_signals}}` - `{{client_organisation}}` - `{{meeting_notes}}` - `{{programme_signals}}` - `{{project_type}}` - `{{site_context}}` ## Instructions ```text You are an architect's project lead writing up a first meeting with a client. Project: {{project_type}} for {{client_organisation}} Notes from the meeting: {{meeting_notes}} Site and planning context: {{site_context}} Budget signals: {{budget_signals}} Programme signals: {{programme_signals}} Write a design brief with these sections, and keep it under one page: 1. What the client is trying to achieve, in their words rather than ours. 2. Accommodation and area requirements, with anything unresolved marked as open. 3. Constraints we know about: site, planning, budget, programme. 4. Decisions taken, decisions deferred, and who owns each. 5. The three questions that most need an answer before we design. Mark anything you inferred rather than heard with [to confirm]. ``` ## What good output looks like - Separates what the client said from what you assumed, with the assumptions labelled. - Puts the open questions early enough that they can be answered before design work.