shape

Plan UX and UI by conducting a structured discovery interview and producing a design brief.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/rattamnoon/our-third-story --skill shape-rattamnoon
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: shape
Source: https://github.com/rattamnoon/our-third-story/tree/main/.agents/skills/shape
Command: npx skills add https://github.com/rattamnoon/our-third-story --skill shape-rattamnoon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan UX and UI for a feature before any code is written, ensuring teams align on goals and constraints upfront to prevent rework.

Core Features & Use Cases

  • Structured discovery interview: guide conversations to surface requirements, risks, and design goals.
  • Design brief output: generate a comprehensive artifact that informs implementation and evaluation.
  • Review and handoff: provide a clear brief for designers, engineers, and stakeholders to reference during build.

Quick Start

Describe the feature context to shape, then request 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
How do I plan UX and UI for a feature before writing any code?▼

To plan UX and UI before coding, conduct a structured discovery interview to surface requirements and risks. This generates a formal design brief that aligns teams on goals and constraints upfront, preventing rework during implementation.

What is a design brief and when do I need it for product design?▼

A design brief is a comprehensive artifact that formalizes UI and UX goals, constraints, and risks discovered during planning. You need it before implementation to ensure designers, engineers, and stakeholders share a single source of truth.

Can I use a structured design brief to hand off to engineers directly?▼

Yes, a structured design brief is explicitly designed for handoff. It captures the discovery interview outputs, allowing designers and engineers to reference a formal document during the build phase and feeding directly into implementation skills.

What is the best way to conduct a discovery interview for UI planning?▼

The best way to conduct UI discovery is using a structured interview framework that guides conversations to surface design goals, constraints, and risks, ultimately producing a comprehensive design brief to guide implementation.

Why does my team experience rework during the UI implementation phase?▼

Teams experience UI rework when they skip the planning phase and fail to align on goals and constraints upfront. Conducting a structured discovery interview before coding produces a design brief that prevents this misalignment.