Design Brief

owl-listener/designer-skills/ux-strategy/skills/design-brief

by owl-listener9a6930cf84a8No license2.8K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 4 weeks ago

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`.

Instructions onlyProductivity & Workflow

AI-generated overview

Writes a project design brief covering problem, audience, constraints, and success criteria.

What it does: Produces a structured design brief for a single project, organized into seven sections: project overview, problem statement, target audience, goals and success criteria, scope and constraints, context and inputs, and deliverables and timeline. It also lists best practices such as keeping the brief concise, focusing on the problem rather than a predetermined solution, and getting stakeholder sign-off. The output is a written brief document; no scripts or files are included.
When to use it: Use at project kickoff when a team needs a focused, agreed-upon brief for one specific project. It suits framing the problem space, audience, constraints, and measurable success criteria before work begins. For long-horizon aspirations or reusable decision rules, other skills are suggested instead.
Requirements: None beyond the agent; instructions only, with no scripts, tools, or credentials required.

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

Project Overview — Name, summary, business context, stakeholder
Problem Statement — What, who, evidence, consequences
Target Audience — Primary/secondary users, characteristics, personas
Goals and Success Criteria — Design goal, metrics, qualitative indicators
Scope and Constraints — In/out of scope, technical/brand/timeline/legal
Context and Inputs — Research, competitive refs, previous attempts
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

Source and attribution

Source:owl-listener/designer-skillsinux-strategy/skills/design-briefat commit9a6930c

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

Design Brief

Design Brief

What You Do

Brief Structure

Best Practices

Source and attribution

More from owl-listener/designer-skills

Zeigarnik Effect

Teslers Law

Von Restorff Effect

State Machine

Visual Hierarchy

Serial Position Effect

More in Productivity & Workflow

Dd Meeting Prep

Dd Checklist

Deal Tracker

Client Review

Morning Note

Notion Spec To Implementation