creative-brief skill
✓ VerifiedCreate or refine a structured creative brief to align stakeholders and provide clear direction for designers, developers, or AI agents.
- GitHub stars
- 1,066
- Files
- 5
- Last commit
- Nov 8, 2026
- License
- MIT
- Allowed tools
- —
What does the creative-brief skill do?
creative-brief creates or refine a structured creative brief to align stakeholders and provide clear direction for designers, developers, or AI agents.
Summary generated from the skill's SKILL.md.
About the creative-brief skill
Turning a vague project idea into a concrete plan for designers, developers, or AI agents is what this skill accomplishes. It acts as a bridge between initial discovery and actual execution by translating high-level goals into a structured markdown document. This is particularly useful for teams starting a new website, app, or brand redesign, or for stakeholders who need to align on direction before work begins.
An agent should load this skill when a user mentions a project kickoff, a design brief, or a need to scope a project. The process involves identifying gaps in the ten required inputs, such as audience, objectives, and constraints, and running a targeted intake to elicit missing information. The final output is a concise creative-brief.md file saved to the project root. It differs from other tools by focusing on strategic alignment rather than writing copy, creating technical specifications, or providing deep aesthetic direction.
What an agent can do with it
- 1Align a drifting teamProvide a central source of truth to get stakeholders back on the same page regarding project goals.
- 2Convert vague ideas into buildable plansAsk targeted questions to turn an unformed thought into a professional brief with clear deliverables.
- 3Define measurable project successEnsure every project objective is paired with a specific, measurable signal for tracking progress.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the creative-brief skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the creative-brief skill in Plugin
/plugin marketplace add rampstackco/claude-skills /plugin install rampstack-skills@rampstack
Install the creative-brief skill in Claude Code
~/.claude/skills/creative-brief/SKILL.md
$ npx degit rampstackco/claude-skills/skills/creative-brief ~/.claude/skills/creative-briefInstall the creative-brief skill in Claude Code (project)
.claude/skills/creative-brief/SKILL.md
$ npx degit rampstackco/claude-skills/skills/creative-brief .claude/skills/creative-briefInstall the creative-brief skill in Codex
~/.agents/skills/creative-brief/SKILL.md
$ npx degit rampstackco/claude-skills/skills/creative-brief ~/.agents/skills/creative-briefInstall the creative-brief skill in Gemini CLI
~/.gemini/skills/creative-brief/SKILL.md
$ npx degit rampstackco/claude-skills/skills/creative-brief ~/.gemini/skills/creative-briefInstall the creative-brief skill in Claude.ai
npx degit rampstackco/claude-skills/skills/creative-brief creative-brief && zip -r creative-brief.zip creative-brief # claude.ai → Customize → Skills → + → Create skill → Upload a skill → creative-brief.zip
Automated checks
Ran Nov 15, 2026Full report →Passed our automated checks. That is not a security audit: read the scripts before you let an agent run them. How checks work
- Source repository linked and reachablerampstackco/claude-skills/skills/creative-brief is public and reachablegithub.com/rampstackco/claude-skills/tree/HEAD/skills/creati ↗Pass
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit 2026-11-08github.com/rampstackco/claude-skills/commits ↗Pass
- No download-and-run or credential theft in scriptsNo scripts in the skill folderPass
- No hidden instructions in SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/rampstackco/claude-skills/blob/HEAD/skills/creati ↗Pass
- Pre-approved tools are scopedNo pre-approved tools; the agent asks before using onegithub.com/rampstackco/claude-skills/blob/HEAD/skills/creati ↗Pass
- SKILL.md follows the Agent Skills formatValid name and description; says when to use it; 159 linesgithub.com/rampstackco/claude-skills/blob/HEAD/skills/creati ↗Pass
SKILL.md
View on GitHubCreative 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-discoveryfirst) - 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-directionfor the structured aesthetic axes)
Required inputs
A brief needs answers to ten questions. Before writing, confirm you have answers (or can elicit them) for:
- What is the project?
- Why does it exist? What problem does it solve?
- Who is the audience?
- What do you want them to do, feel, or know?
- What is the personality? How does it sound?
- What is the visual direction? How does it look?
- What is in scope? What is out?
- What are the constraints (time, budget, technical, brand)?
- What does success look like?
- 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.
2. Audience
Primary audience first. Include who they are, what they are trying to do, what is blocking them today, and where you reach them. Add secondary audiences only if they materially change the work.
3. Objectives
What success looks like. Pair every objective with a measurable signal.
Objective: drive trial signups. Signal: 3 percent conversion from homepage to signup within 30 days of launch.
4. Key message
The one thing you want a visitor to walk away knowing. If they see only the homepage hero and bounce, what should they remember? One sentence.
5. Voice and tone
Pick three to five adjectives. Pair each with what you are NOT (e.g. "confident, not arrogant"). See references/voice-and-tone-guide.md for frameworks and worked examples.
6. Visual direction
Mood, palette, type, and imagery direction. Three to five reference URLs are worth more than 500 words. Note what you like AND what you would reject.
7. Scope and deliverables
A bulleted list of what is being made. Be specific. "Homepage" is not a deliverable. "Homepage with hero, three feature blocks, testimonial carousel, and contact CTA" is.
8. Constraints
Time. Budget. Technical (existing stack, required integrations, hosting). Brand (logo, colors, fonts that must be used). Legal (compliance, accessibility level required).
9. Inspiration and competitors
Three to five sites or brands you want to feel like, three to five you want to feel different from. Note WHY for each.
10. Approval
Who signs off. What artifact triggers sign-off (a Figma file, a staging URL, a PDF). What happens if there is no sign-off by a deadline.
Eliciting missing info
If the user comes with a partial answer (e.g., "I want a website for my coffee shop"), do not just write a generic brief. Ask. Use these prompts.
For audience
- Who is the single most likely person to land on this site? Walk me through their day.
- If you could pick one type of customer to fill your inbox, who?
- Who do you NOT want to attract?
For objectives
- Pretend it is six months after launch. What number tells you it worked?
- What is the one action you most want a visitor to take?
For voice
- Pick three brands or people whose tone you would want to borrow.
- If your site were a person at a dinner party, what would they sound like?
For visuals
- Show me three sites you love. What do you love about them?
- Show me one site you hate. Why?
For scope
- If you only got one page, which one?
- What would you cut if the budget were halved?
Do not ask all of these. Pick the ones that fill the actual gaps.
Workflow
- Read the conversation. Pull every fact already given. Do not ask questions you can answer from context.
- Identify gaps. Which of the ten required inputs are missing or thin?
- Run intake. Ask three to five targeted questions to fill the gaps. Group related questions to keep the conversation tight.
- Draft the brief. Use
references/creative-brief-template.mdas the structure. Keep it under 1500 words. - Stress-test. Before delivering, check the brief against the failure patterns below. If any apply, revise before showing the user.
- Deliver. Save as
creative-brief.mdin the project root. Offer to make it a Word doc or PDF if the user wants something to share with stakeholders. - Hand off for aesthetic depth (optional). For projects where sections 5 (voice and tone) and 6 (visual direction) need more rigor than this brief surfaces, run
creative-directionnext. It produces a structured aesthetic brief using four directional axes (tone register, aesthetic philosophy, audience relationship, sensory ambition) that content, copy, and art-direction skills consume directly.
Failure patterns
When the user's input matches one of these patterns, push back before writing.
- "We want to be the [giant brand] of [our niche]." Ask what specifically about that brand they want to borrow. Probably one or two things, not the whole thing.
- Audience as "men and women 18-65." This is not an audience. Ask for the single most valuable customer type and start there.
- "Increase awareness" with no metric. Awareness of what, by whom, measured how? Push for a number.
- "Modern, clean, minimalist." These words are meaningless. Ask for three specific URLs they think look right.
- Twenty pages of context, no clear ask. Ask: "If a designer reads only one paragraph, what should it be?" Then make that the snapshot.
Output format
Default output is a markdown file at creative-brief.md in the project root. Structure follows the template exactly.
If the project is large, split: keep the main brief under 1500 words and put detail in linked appendices (audience-research.md, brand-guidelines.md, etc.). Briefs that try to be everything end up read by no one.
Reference files
references/creative-brief-template.md- Fillable template. Copy and use as the starting point.references/voice-and-tone-guide.md- Voice frameworks, brand archetypes, and worked patterns.references/example-brief.md- A worked example for a fictional B2B SaaS, showing what a "good" filled brief looks like.
Read the template before drafting. Read the voice guide if the user has not already specified a voice. Read the example if you are unsure how filled-out a section should be.
Files in this skill
5creative-brief skill questions
How do I install the creative-brief skill in Claude Code?
Run npx degit rampstackco/claude-skills/skills/creative-brief ~/.claude/skills/creative-brief. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the creative-brief skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.
When should I use the creative brief skill?
Use this skill when starting a new project, kicking off a redesign, handing work to a designer or developer, or turning a vague idea into a concrete plan.
What information is required to write a brief?
A complete brief requires answers to ten key questions including project purpose, audience, objectives, personality, visual direction, scope, constraints, success metrics, and approval processes.
What should I do if I only have a vague idea for a project?
The skill can help turn vague ideas into something buildable by running a targeted intake process to fill information gaps.