Design Brief — Orchestrator

Produce a graphic-design brief for a single visual asset — social posts, thumbnails, banners, OG cards, hero illustrations, OOH, ad creative. Emits an image-gen prompt or designer-handoff spec; does NOT render (not for user flow / wireframe — use map-user-flow). Capability metadata: routing.yaml. Agents + 4 downstream routes + 8-dim rubric: references/agent-manifest.md. Methodology: references/playbook.md.

Core question: Could a designer or image-gen tool execute this asset on-brand and on-platform without follow-up questions?

Critical Gates — load first

• Do NOT render. Brief only — spec + reference direction + image-gen prompt. Rendering happens downstream.
• Do NOT proceed without brand anchors. Missing brand/BRAND.md or brand/DESIGN.md → NEEDS_CONTEXT, recommend create-brand. Hard gate fires BEFORE Cold Start (survives --fast).
• Do NOT invent tokens, fonts, or motion specs. Every visual decision traces to DESIGN.md. Gap → flag, don't guess.
• Reference realized surfaces, not just tokens. Before writing reference direction, pull ≥1 realized surface (live page screenshot · shipped HTML · approved exploration · existing exemplar) and design the concept against it — tokens are the floor, the realized surface is the taste. No surface available → record the explicit token-only fallback line. Silent token-only design fails the rubric. Contract: references/_shared/realized-surface-grounding.md.
• Do NOT use stock-AI defaults. No purple-blue gradients, centered-on-white, faux-3D bevels, glassmorphism — unless DESIGN.md specifies. 13-pattern detector scores explicitly.
• Do NOT skip the brief approval gate. Brief is a candidate, not a delivery — user reviews before rendering.
• Platform spec mandatory. Every brief includes aspect ratio, safe zones, mobile readability, file format, file-size cap.

Quality Gate — 8 dimensions + AI-aesthetic check