Design Brief
- 961 installs
- 1.9k repo stars
- Updated June 14, 2026
- owl-listener/designer-skills
design-brief is a design skill that produces a stakeholder-aligned design brief covering problem space, audience, constraints, and success criteria for developers and designers starting visual or product work.
About
design-brief is a designer-skills agent skill from owl-listener/designer-skills that writes a structured design brief before visual or product execution. The brief spans six sections: project overview, problem statement, target audience, goals and success criteria, scope and constraints, plus supporting context so teams share one definition of the problem. Developers and designers reach for design-brief when kicking off UI, UX, or product design and need documented alignment on who the work serves and how success is measured. The output is a focused planning document that reduces rework from ambiguous requirements or missing stakeholder context.
- 7-section design brief template covering overview through deliverables
- Forces focus on problem definition instead of jumping to solutions
- Requires measurable success criteria and stakeholder sign-off
- References competitive research, constraints, and prior attempts
- Serves as living reference throughout the entire project
Design Brief by the numbers
- 961 all-time installs (skills.sh)
- +44 installs in the week ending Jul 29, 2026 (Skillselion tracking)
- Ranked #486 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Jul 31, 2026 (Skillselion catalog sync)
npx skills add https://github.com/owl-listener/designer-skills --skill design-briefAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 961 |
|---|---|
| repo stars | ★ 1.9k |
| Security audit | 3 / 3 scanners passed |
| Last updated | June 14, 2026 |
| Repository | owl-listener/designer-skills ↗ |
How do you write a design brief before UI work?
Create a focused design brief that aligns stakeholders before starting visual or product work.
Who is it for?
Product and design leads who need a shared brief before wireframes, tokens, or component work starts.
Skip if: Teams that already have signed-off PRDs and visual specs and only need implementation guidance.
When should I use this skill?
The user needs a design brief, project alignment doc, or pre-visual stakeholder summary.
What you get
Structured design brief with problem statement, audience definition, goals, metrics, and scope boundaries.
- Design brief document
- Success criteria list
- Scope and constraints outline
Files
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
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.645k185kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.547k185k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.466kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).466kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.466kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.465kFAQ
What sections does design-brief include?
design-brief produces six core sections: project overview, problem statement, target audience, goals and success criteria, scope and constraints, plus supporting context. Each section forces explicit evidence, metrics, and boundaries before visual work.
When should a team use design-brief?
design-brief fits the start of visual or product design when stakeholders still need shared problem, audience, and success definitions. The brief prevents ambiguous handoffs into wireframes, tokens, or component libraries.
Is Design Brief safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.