shape

Guide structured discovery interviews and produce a design brief for feature implementation.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Pacha-e/claude-ALL-IN-SETUP --skill shape-pacha-e
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: shape
Source: https://github.com/Pacha-e/claude-ALL-IN-SETUP/tree/main/skills/shape
Command: npx skills add https://github.com/Pacha-e/claude-ALL-IN-SETUP --skill shape-pacha-e

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Shape UX and UI for a feature before coding, ensuring a structured discovery process and a clear design brief to guide implementation.

Core Features & Use Cases

  • Guided discovery interviews to elicit context and requirements.
  • A formal design brief that defines scope, constraints, and strategic direction.
  • A repeatable planning workflow that supports handoff to design and engineering.

Quick Start

Invoke /impeccable to start the design discovery workflow and generate the design brief.

Frequently Asked Questions about shape

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

FAQPage Schema
How do I create a design brief before starting UI implementation?▼

Creating a design brief before UI implementation requires running guided discovery interviews to elicit project context and requirements, which are then structured into a formal document defining scope, constraints, and strategic direction.

What is structured discovery for UX planning and when do I need it?▼

Structured discovery for UX planning is a phased interview process that elicits context and requirements before coding. You need it to ensure a formal design brief is produced to direct implementation and handoff.

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

Plan UX and UI for a feature by invoking the workflow to start guided discovery interviews. This produces a design brief that directs implementation across planning and handoff phases.

Can I use a generated design brief to hand off to engineering?▼

Yes, you can use the generated design brief to hand off to engineering. The brief defines scope and strategic direction, satisfying requirements for a formal planning workflow that supports handoff to design and engineering teams.

Does this UX discovery workflow require any external dependencies?▼

No, this UX discovery workflow requires no external dependencies. It operates independently to guide structured discovery interviews and produce a design brief that can be used by any implementation skill.

When should I not use a formal design brief for feature planning?▼

A formal design brief for feature planning should be bypassed when rapid prototyping is needed without mandatory preparation. This workflow enforces a phased discovery process, which may be excessive for minor scope adjustments.