shape

Conduct a structured interview to gather context and produce a design brief.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/wukangcheng2944/claude-skills --skill shape-wukangcheng2944
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shape
Source: https://github.com/wukangcheng2944/claude-skills/tree/main/shape
Command: npx skills add https://github.com/wukangcheng2944/claude-skills --skill shape-wukangcheng2944

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning a feature's UX/UI before coding prevents misalignment, scope creep, and wasted effort by ensuring decisions are documented upfront.

Core Features & Use Cases

  • Discovery Interview: Guides teams to gather context, goals, constraints, and user needs before design.
  • Design Brief Output: Produces a clear, implementable brief to guide product, UX, and engineering.
  • Scope & Guardrails: Enforces a planning phase that stops any coding until design decisions are captured.

Quick Start

Initiate a discovery session for your feature and generate a design brief to align the team.

Frequently Asked Questions about shape

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

FAQPage Schema
How do I plan UX and UI for a feature before coding?

To plan UX before coding, you conduct a structured discovery interview to gather context, constraints, and user needs, producing a formal design brief that guides implementation and prevents scope creep.

What is a discovery-led design brief in product planning?

A discovery-led design brief is a formal document generated from a structured interview that captures goals, constraints, and user needs to align product, UX, and engineering teams before implementation begins.

Why should I define scope and guardrails before starting feature design?

Defining scope and guardrails during feature design enforces a planning phase that stops coding until design decisions are documented upfront, preventing misalignment, scope creep, and wasted development effort.

Can I use this to create a design brief for early product discovery?

Yes, you can use this during early product discovery to guide your team through context gathering and constraints definition, outputting a clear, implementable design brief to inform subsequent work.

What's the best way to document UX decisions for engineering handoff?

The best way to document UX decisions for handoff is generating a formal design brief that captures context and constraints upfront, ensuring product, UX, and engineering teams have a clear guide for implementation.

When do I need a formal design brief for feature planning?

You need a formal design brief for feature planning when you must satisfy requirements for context gathering and constraints definition, ensuring decisions are documented to guide subsequent product and engineering work.