creative-brief

# Creative Brief Bridges discovery and execution. Translates "we want a website" into a brief a designer, developer, or AI agent can actually run with. --- ## When to use - Starting a new project (website, app, brand, campaign) - Kicking off a redesign or rebrand - Handing work to a designer, developer, or AI agent - Aligning a team that has drifted off course - Turning a vague idea into something buildable ## When NOT to use - The user is asking a one-off design question (use `design-standards`) - The user wants a PRD or dev ticket (use `pm-spec-writing`) - The user is doing initial research and has not decided what they are building (use `brand-discovery` first) - The user just wants you to write copy (use `content-and-copy`) - The user already has scope and constraints settled and needs deeper aesthetic direction specifically (use `creative-direction` for the structured aesthetic axes) --- ## Required inputs A brief needs answers to ten questions. Before writing, confirm you have answers (or can elicit them) for: 1. What is the project? 2. Why does it exist? What problem does it solve? 3. Who is the audience? 4. What do you want them to do, feel, or know? 5. What is the personality? How does it sound? 6. What is the visual direction? How does it look? 7. What is in scope? What is out? 8. What are the constraints (time, budget, technical, brand)? 9. What does success look like? 10. Who approves? If you have fewer than five of these, run a quick intake first. See ...