Made for Architects
Run Your First Brief-Clarification Meeting
Also useful for: Project Managers, people in Creative
Build a meeting plan, ask targeted questions about requirements and adjacencies, settle conflicting statements, and send a written record of decisions and open items.
We'll use them to write your prompt.
Make Your Play
Give us the situation. We’ll build the prompt.
You prevent vague requirements from turning into design rework.
Your answers save as you type.
What you'll do
This is the plan inside your prompt. Add your details first. Then follow these steps with ChatGPT or Claude.
Make Your Play
Run Your First Brief-Clarification Meeting
Tell us what the prompt needs to know
Start with the questions below. Each answer personalizes the playbook and builds the prompt you’ll use at the end.
Your situation
Describe your project, its purpose, location context, scale, and the immediate design work ahead.
0/10000
Choose your current stage so your questions stay appropriate to the decisions available now.
List who will attend, what each person knows, and what each person can approve.
0/10000
Paste your known requirements, room list, goals, operational needs, or prior instructions.
0/10000
List your known site, existing-building, budget, schedule, approval, technical, or operational limits.
0/10000
List unclear terms, missing decisions, competing requests, and statements that may conflict.
0/10000
Enter the total number of minutes available for your meeting.
This playbook was updated. Review your inputs before copying.
What you'll do
Check a step when you finish it.
Fill in the fields above to generate your prompt preview.
Assembled prompt
Beginner instructions
You can paste rough notes instead of a polished brief. Before your meeting, highlight the five questions that could most affect area, circulation, cost, approvals, or schedule. During your meeting, read back each decision before moving on.
Advanced instructions
You can add traceable requirement IDs, source references, confidence levels, and downstream design effects. Separate binding constraints from preferences, test each major adjacency against operational flow, and flag decisions that require consultant, authority, or client validation.
Use this when
Use this before concept design, after receiving an incomplete brief, when stakeholder requests conflict, or when your team can't tell which requirements should guide the next design move.
You'll need
- Project summary
- Project stage
- Meeting participants
- Current brief
- Known constraints
- Open issues
- Meeting length
You'll get
- A timed agenda, prioritized questions, and clear decision goals
- Requirements, constraints, stakeholders, and adjacencies tested
- Each decision, conflict, owner, and due date recorded
- A follow-up record ready to send, with confirmed points clearly separated from unresolved items.
By the end of this playbook
You will have:
- A timed agenda, prioritized questions, and clear decision goals
- Requirements, constraints, stakeholders, and adjacencies tested
- Each decision, conflict, owner, and due date recorded
- A follow-up record ready to send, with confirmed points clearly separated from unresolved items.