Design Brief

Write a project brief — problem space, constraints, audience, and success criteria. Use at kickoff for one specific project. For long-horizon aspiration use `north-star-vision`; for reusable decision rules use `design-principles`.

3,414 stars 447 forksWriting & Content Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add Owl-Listener/designer-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add Owl-Listener/designer-skills --skill design-brief
Manual install
git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git /tmp/designer-skills
mkdir -p ~/.claude/skills
cp -r /tmp/designer-skills/ux-strategy/skills/design-brief ~/.claude/skills/design-brief

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Design Brief
You are an expert in writing design briefs that set teams up for focused, effective work.
## What You Do
You create briefs defining problem, audience, constraints, and success criteria.
## Brief Structure
1. **Project Overview** — Name, summary, business context, stakeholder
2. **Problem Statement** — What, who, evidence, consequences
3. **Target Audience** — Primary/secondary users, characteristics, personas
4. **Goals and Success Criteria** — Design goal, metrics, qualitative indicators
5. **Scope and Constraints** — In/out of scope, technical/brand/timeline/legal
6. **Context and Inputs** — Research, competitive refs, previous attempts
7. **Deliverables and Timeline** — Outputs, milestones, review points, deadline
## Best Practices
- Concise but complete
- Focus on problem, not predetermined solution
- Include measurable success criteria
- Get stakeholder sign-off before starting
- Reference throughout the project
Read the full skill on GitHub

Details

Skill name
design-brief
Path
ux-strategy/skills/design-brief/SKILL.md
License
MIT
Repo updated
5 September 2026

FAQ

What does the Design Brief skill do?

Write a project brief — problem space, constraints, audience, and success criteria. Use at kickoff for one specific project. For long-horizon aspiration use `north-star-vision`; for reusable decision rules use `design-principles`.

How do I install the Design Brief skill?

Claude Code plugin: /plugin marketplace add Owl-Listener/designer-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Design Brief popular?

It lives in Owl-Listener/designer-skills, which has 3,414 GitHub stars and 447 forks.

Related skills

A B Test Design

3.4k

Owl-Listener/designer-skills

Design an A/B experiment — hypothesis, variants, primary metric, and sample size. Use when a change can be measured quantitatively at scale. For observing behaviour qualitatively, use `test-scenario`.

Testing & QA447

Accessibility Audit

3.4k

Owl-Listener/designer-skills

Audit an existing interface against WCAG, producing findings with severity ratings and remediation steps. Use when you have a design or build to assess now. Not for planning future sessions with assistive-technology users — use `accessibility-test-plan` (prototyping-testing).

Frontend & Design447

Accessibility Test Plan

3.4k

Owl-Listener/designer-skills

Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol. Use when scheduling testing with real AT users. Not for evaluating a design yourself — use `accessibility-audit` (design-systems).

Testing & QA447

Design Rationale

3.4k

Owl-Listener/designer-skills

Write rationale connecting decisions to user needs, business goals, and principles. Use when a decision needs defending in writing. For a live conversation, use `design-negotiation`.

Writing & Content447

Dark Mode Design

3.4k

Owl-Listener/designer-skills

Adapt an existing palette to dark mode — surface elevation, contrast rebalancing, and desaturation rules. Use when you already have a light palette to translate. For building the base palette first, use `color-system`.

Writing & Content447

Documentation Template

3.4k

Owl-Listener/designer-skills

Generate a reusable documentation scaffold for components, patterns, or guidelines. Use when standardising how the system is documented. For the content of one component's spec, use `component-spec`.

Writing & Content447

Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.