design-brief · owl-listener — Claude Code skill: what it does, how to install
Drafts a project brief covering problem space, audience, constraints, and success criteria. Built for kicking off a specific task or feature.
npx skills add Owl-Listener/designer-skills --skill design-brief -a claude-codeWhat design-brief does
The skill helps teams prepare a design brief before launching a specific task. It organizes inputs into seven sections: project overview, problem statement with evidence, target audience, measurable goals, scope boundaries, historical context, and deliverable deadlines. The format keeps attention strictly on the problem.
It demands measurable success criteria and stakeholder sign-off prior to execution. This skill covers only one standalone project. For long-horizon goals the author recommends north-star-vision, while reusable rules belong in design-principles.
What it helps with
- draft a structured design brief for a project kickoff
- define project boundaries alongside technical and legal constraints
- establish measurable success metrics and qualitative indicators
- document target audience characteristics and user personas
Example prompts for the agent
- Write a design brief for the checkout flow redesign.
- Draft a project brief covering the problem space, target audience, and constraints for our new search feature.
How to install design-brief
1Skills CLI (Vercel)
npx skills add Owl-Listener/designer-skills --skill design-brief -a claude-code2Manually: put the files in place
~/.claude/skills/design-brief/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/design-brief/
1Skills CLI (Vercel)
npx skills add Owl-Listener/designer-skills --skill design-brief -a codex2Manually: put the files in place
.agents/skills/design-brief/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Owl-Listener/designer-skills --skill design-brief -a cursor2Manually: put the files in place
.cursor/skills/design-brief/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Owl-Listener/designer-skills design-brief2Manually: put the files in place
.github/skills/design-brief/SKILL.md1Skills CLI (Vercel)
npx skills add Owl-Listener/designer-skills --skill design-brief -a gemini-cli2Platform CLI
gemini skills install https://github.com/Owl-Listener/designer-skills --path ux-strategy/skills/design-briefManually: put the files in place
.devin/skills/design-brief/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add Owl-Listener/designer-skills --skill design-brief -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about design-brief
How to install design-brief in Claude Code?
Run npx skills add Owl-Listener/designer-skills --skill design-brief -a claude-code. You can also manually place the skill file in ~/.claude/skills/design-brief/SKILL.md.
What does design-brief do?
It generates a project brief outlining problem evidence, target personas, project constraints, and milestone timelines.
When should I use north-star-vision instead?
Use design-brief when kicking off an individual project. For long-horizon aspirations, the author recommends north-star-vision.
Source text
SKILL.md · MIT
--- name: design-brief description: 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`. --- # 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
© Owl-Listener · MIT · Owl-Listener/designer-skills
Similar skills
Everything for Design →design-brief by other authors comes first.
