design-discovery

Guide design discovery workflows and generate design briefs with approval gates.

234|55|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/Owl-Listener/designpowers --skill design-discovery
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-discovery
Source: https://github.com/Owl-Listener/designpowers/tree/main/skills/design-discovery
Command: npx skills add https://github.com/Owl-Listener/designpowers --skill design-discovery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Discovery is essential to prevent premature design decisions and misaligned outcomes by clarifying intent, constraints, users, and context before any design work.

Core Features & Use Cases

  • Quick Discovery: for fast tasks, ask a few essential questions conversationally, then generate the brief and create the design-state.md.
  • Full Discovery: for complex tasks, follow a structured process to understand context, explore intent, and define the design brief before any UI work.
  • Design State & Gatekeeping: after approval, automatically create design-state.md and prepare for the next skill, ensuring alignment and traceability.
  • Integration & Governance: supports an onboarding welcome sequence and staged handoffs between discovery and strategy or writing tasks.

Quick Start

Describe the project goal and constraints, then trigger the discovery workflow to generate the brief and design state.

Frequently Asked Questions about design-discovery

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

FAQPage Schema
How do I create a design brief to align stakeholders before starting UI work?

To create a design brief and align stakeholders, this skill guides you through a structured discovery process. It clarifies intent, constraints, users, and context, then outputs an approved design brief to gate subsequent UI work.

What is the design discovery process and when do I need it?

The design discovery process is a structured method to define project intent and context before design execution. You need it to prevent premature design decisions and misaligned outcomes by enforcing stakeholder alignment early.

How do I run a quick discovery workflow for fast design tasks?

To run a quick discovery workflow for fast tasks, the skill asks a few essential questions conversationally. It then immediately generates the design brief and creates a design-state document to track constraints.

Can I enforce design gatekeeping to prevent premature design decisions?

Yes, you can enforce design gatekeeping by requiring explicit approvals. The skill gates subsequent work behind these approvals and automatically creates a design-state.md document to ensure alignment and traceability.

Does the design discovery workflow support handoffs to strategy or writing tasks?

Yes, the discovery workflow supports staged handoffs to strategy or writing tasks. After approval, it prepares the design state for the next skill, ensuring seamless integration and governance across the workflow.

What is the best way to document design state and constraints for a complex project?

The best way to document design state is through a full discovery workflow. It explores project context and intent thoroughly, then outputs a design-state.md file that prepares the project for downstream strategy and writing tasks.