design-brief

Define and document a design brief with problem space, audience, constraints, and success criteria.

2.0k|325|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/Owl-Listener/designer-skills --skill design-brief-owl-listener
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-brief
Source: https://github.com/Owl-Listener/designer-skills/tree/main/ux-strategy/skills/design-brief
Command: npx skills add https://github.com/Owl-Listener/designer-skills --skill design-brief-owl-listener

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured template to articulate and sign off on a design problem, audience, constraints, and success criteria, reducing ambiguity at kickoff.

Core Features & Use Cases

  • Structured problem framing that guides discovery, design, and stakeholder alignment.
  • Template coverage for project overview, problem statement, audience, goals, scope, inputs, deliverables, and timeline.
  • Use Case: when starting a new design initiative, produce a complete brief that informs research plans and design decisions.

Quick Start

Draft a complete design brief outlining project overview, problem statement, audience, goals, scope, inputs, deliverables, and timeline.

Frequently Asked Questions about design-brief

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a design brief that aligns stakeholders on scope and deliverables?

To write a design brief that aligns stakeholders, document the project overview, problem statement, target audience, goals, scope, constraints, inputs, deliverables, and timeline in a structured template to eliminate ambiguity at project kickoff.

What should be included in a design problem statement for a new product initiative?

A design problem statement should define the specific problem space, identify the target audience, outline constraints, and establish clear success criteria. This framing guides discovery, design decisions, and stakeholder alignment throughout the initiative.

When do I need a structured design brief for my design-thinking process?

You need a structured design brief when starting a new design initiative from discovery to sign-off. It enables teams to align on scope, goals, and deliverables, ensuring research plans and subsequent design decisions are properly informed.

Can I use a design brief template for both small and large product design initiatives?

Yes, a design brief template works for product design initiatives of any scale by providing structured sections for project overview, problem statement, audience, goals, scope, constraints, inputs, deliverables, and timeline to ensure consistent stakeholder alignment.

What is the best way to define success criteria and constraints in a design brief?

The best way to define success criteria and constraints in a design brief is to document them within dedicated sections for goals, scope, and constraints. This structured approach captures measurable metrics and project boundaries for stakeholder sign-off.