design-briefing

Distill raw design context into a structured brief.md document.

Updated Mar 11, 2026

Search Tags:#design #requirements #product management #synthesis #ux #briefing

Ready to run

npx skills add https://github.com/rodh/QuickFlow --skill design-briefing

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: design-briefing
Source: https://github.com/rodh/QuickFlow/tree/main/skills/design-briefing
Command: npx skills add https://github.com/rodh/QuickFlow --skill design-briefing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill transforms messy, raw input like tickets, Slack threads, or research notes into a clear, actionable design brief, ensuring a solid foundation before design exploration begins.

Core Features & Use Cases

Input Triage: Assesses raw context and asks targeted questions to fill information gaps.
Brief Synthesis: Generates a structured brief including problem statement, user context, constraints, knowns, open questions, and a first instinct.
Use Case: A product manager provides a raw ticket describing a new feature request. The skill asks clarifying questions about user impact and technical constraints, then synthesizes this into a brief.md file ready for a designer.

Quick Start

Use the design-briefing skill with the provided ticket text to generate a design brief.

Frequently Asked Questions about design-briefing

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

FAQPage Schema

How do I turn raw product tickets and research notes into an actionable design brief?▼

To create a design brief from raw context, you need to distill unstructured tickets and research notes into a focused document. This process clarifies the problem statement, user context, and constraints to form a solid foundation before design exploration begins.

What sections should be included when synthesizing UX requirements for a new feature?▼

When synthesizing UX requirements, the brief should include specific sections for the problem statement, user context, constraints, knowns, open questions, and a first instinct. This structure ensures all critical design parameters are captured.

Can I use unstructured Slack threads as input for clarifying product design constraints?▼

Yes, unstructured Slack threads can be used as input for clarifying product design constraints. The input triage process assesses this raw context and asks targeted questions to fill information gaps before generating the brief.

What is the best way to document open questions and knowns before starting design exploration?▼

The best way to document knowns and open questions is by generating a structured brief.md file. This document synthesizes raw context into distinct sections, ensuring teams address open questions and leverage knowns before design work starts.

Does generating a design brief require answering clarifying questions about user impact?▼

Yes, generating a design brief requires answering clarifying questions about user impact and technical constraints. This input triage step fills information gaps from the initial raw context to ensure the synthesized brief is actionable.