# Creative Brief

Create or refine a creative brief that bridges discovery and execution.

- Repository: https://github.com/rampstackco/claude-skills (1014 stars)
- Category: Design
- License: MIT
- Last updated: 2026-10-27
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add rampstackco/claude-skills --skill creative-brief -g -a claude-code -y`
Codex: `npx skills add rampstackco/claude-skills --skill creative-brief -g -a codex -y`
Cursor: `npx skills add rampstackco/claude-skills --skill creative-brief -g -a cursor -y`
Gemini CLI: `npx skills add rampstackco/claude-skills --skill creative-brief -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add rampstackco/claude-skills`

## Description

Create or refine a creative brief that bridges discovery and execution. Use this skill whenever the user is starting a new project, kicking off a website, beginning a brand build or redesign, briefing a designer or developer or AI agent, or trying to align a team before building. Triggers on creative brief, design brief, brand brief, project kickoff, kicking off, briefing the team, project intake, design direction, brief the designer, brief the dev, where do we start, how do we start, write a brief, project overview, scope this project, align on direction. Also triggers when the user has a vague idea and needs to make it concrete enough to hand off, even if they do not say 'brief' explicitly.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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 "Eliciting missing info" below.

---

## The framework: brief structure

Output a markdown brief with these ten sections. Keep each section tight. A good brief is two pages, not ten.

### 1. Snapshot
One paragraph answering: what, who, why, when. The kind of thing you would say at a kickoff in thirty seconds.

The rest: https://github.com/rampstackco/claude-skills/blob/HEAD/dist/codex/.agents/skills/creative-brief/SKILL.md