shape

Conduct a structured discovery interview and produce a design brief.

1|1|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/joncoronel/skillstack --skill shape-joncoronel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shape
Source: https://github.com/joncoronel/skillstack/tree/main/.agents/skills/shape
Command: npx skills add https://github.com/joncoronel/skillstack --skill shape-joncoronel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams align UX/UI direction before coding by conducting a structured discovery interview and producing a formal design brief that defines goals, constraints, and strategy.

Core Features & Use Cases

  • Structured Discovery Interview: guides a comprehensive conversation to surface goals, users, constraints, and success metrics.
  • Design Brief Output: generates a structured document that informs implementation and design decisions.
  • Planning for Implementation: translates insights into actionable design direction for engineers and product managers.

Quick Start

Initiate the discovery interview for a new feature and generate a design brief to guide implementation.

Frequently Asked Questions about shape

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

FAQPage Schema
What is a design brief and why do I need one before coding?

A design brief defines UX/UI goals, constraints, and strategy before coding. You need one to align design and engineering teams on feature scope and success metrics, preventing misalignment during implementation.

How do I conduct a discovery interview for UX planning?

Conduct a discovery interview for UX planning by following a structured conversation guide that surfaces user goals, constraints, and metrics. This process translates early product insights into an actionable design brief.

What's the best way to plan product UX direction across teams?

The best way to plan product UX direction is generating a formal design brief from a structured discovery interview. This documents evaluation criteria and strategy to guide both engineers and product managers.

Can I use a design brief to define feature scope and constraints?

Yes, you can use a design brief to define feature scope and constraints. It documents planning insights and evaluation criteria gathered during discovery, directly informing implementation and design decisions.

When should I not use a discovery interview for UX planning?

You should not use a discovery interview for UX planning if your feature scope and evaluation criteria are already fully defined across design and engineering teams, making a new design brief redundant.