shape

Conduct a guided discovery interview and produce a design brief.

10|3|Updated Apr 1, 2018

Search Tags:#design #discovery #stakeholder #ux #design-brief #shape

Ready to run

npx skills add https://github.com/kaishin/redalemeden.com --skill shape-kaishin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: shape
Source: https://github.com/kaishin/redalemeden.com/tree/main/.agents/skills/shape
Command: npx skills add https://github.com/kaishin/redalemeden.com --skill shape-kaishin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan the UX/UI for a feature before code is written by guiding a structured discovery interview and producing a design brief that informs implementation decisions.

Core Features & Use Cases

Discovery Interview Protocol: A guided conversation to elicit goals, constraints, and success criteria.
Design Brief Output: A structured artifact detailing feature scope, design direction, constraints, and validation criteria to guide implementation.
Open Collaboration: Provides a clear handoff to implementation skills and teams.

Quick Start

Conduct a guided discovery interview for a feature and generate a comprehensive design brief.

Frequently Asked Questions about shape

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

FAQPage Schema

How do I plan UX/UI design before implementation?▼

Plan UX/UI design by conducting a guided discovery interview to elicit goals and constraints, then producing a structured design brief that aligns product, design, and engineering teams on implementation decisions.

What is a design brief and when do I need one for feature discovery?▼

A design brief is a structured artifact detailing feature scope, design direction, constraints, and validation criteria. You need one during planning phases to align cross-functional teams on success criteria before code is written.

How do I conduct a stakeholder discovery interview for UX design?▼

Conduct a stakeholder discovery interview using a guided protocol to elicit project goals, constraints, and success criteria. This context gathering phase informs the formal design brief detailing scope and interaction models.

What sections should be included in a UX design brief?▼

A UX design brief should include Feature Summary, Primary User Action, Design Direction, Layout Strategy, Key States, Interaction Model, Content Requirements, References, and Open Questions to guide implementation decisions.

Can I use a structured design brief to align product, design, and engineering teams?▼

Yes, a structured design brief aligns product, design, and engineering teams by providing a clear handoff artifact that documents design direction, constraints, and open questions across the entire feature scope.

What is the best way to document design direction and constraints for a feature?▼

The best way to document design direction and constraints is generating a formal design brief after a discovery interview, capturing layout strategy, key states, and interaction models to inform implementation.