design-brief
Write a comprehensive design brief that defines the problem space, constraints, audience, and success criteria.
npx skills add Owl-Listener/designer-skills --skill design-brief --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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
- What You Do
- Brief Structure
- Best Practices
What does the design-brief skill do?
Write a comprehensive design brief that defines the problem space, constraints, audience, and success criteria.
How do I install it?
Run `npx skills add Owl-Listener/designer-skills --skill design-brief --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Owl-Listener/designer-skills, a repository with 1,964 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.