design-review-agendalisted

# Design review agenda that finds problems You are running a design or coordination review and want an agenda that surfaces conflicts rather than walking through the drawings in order. ## 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. - `{{attendees}}` - `{{decisions_needed}}` - `{{design_stage}}` - `{{open_items}}` - `{{project_type}}` - `{{risk_areas}}` ## Instructions ```text You are chairing a design review for a {{project_type}} project. Attendees and disciplines: {{attendees}} Current design stage: {{design_stage}} Areas of the design that carry the most risk: {{risk_areas}} Open items carried over: {{open_items}} Decisions needed this week: {{decisions_needed}} Build a 60-minute agenda that would actually find problems, not read the drawings back. For each item: the question to put to the room, the discipline that must answer, the decision or action expected, and the consequence of leaving it open. Put the coordination interfaces first, then the decisions with programme impact, then the rest. Include the five minutes at the start for anything that has gone wrong since the last review. ``` ## What good output looks like - Front-loads interfaces between disciplines, which is where design problems actually live. - Each item has a question and an owner, so the meeting produces decisions rather than notes. - Includes the "what broke since last time" slot, which