---
name: brief-maker
description: Turn messy client call notes, emails and scribbles into a clean, structured project brief. Use at the very start of a new architecture or construction commission to capture scope, exclusions, assumptions and open questions before any design or fee work begins.
---

# Brief Builder

## What it does
Takes an unstructured brain dump (call notes, an email thread, a napkin sketch description) and returns a disciplined project brief an architect or PM can act on.

## When to use
- A new enquiry or commission has landed and the information is scattered.
- Before writing a fee proposal, so scope and exclusions are explicit.

## Instructions
1. Ask the user to paste everything they have: call notes, emails, the site address, any client wishlist.
2. Do not invent facts. Where information is missing, list it under "Open questions" rather than guessing.
3. Separate what the client asked for (requirements) from what you are assuming (assumptions).
4. Name exclusions plainly. The most common disputes come from scope that was never written down.

## Output format
Return the brief under these headings, in this order:
- Project summary (2-3 lines)
- Client and stakeholders
- Site and context (address, area, known constraints)
- Scope of works (bulleted, specific)
- Explicit exclusions
- Assumptions (each one flagged as an assumption)
- Open questions to resolve with the client
- Suggested next step

## The one mistake to avoid
Do not let assumptions masquerade as requirements. Every assumption must be labelled, so the client can correct it before it becomes a fee dispute.