shape

Name: shape
Availability: InStock
Author: kireevkit15-sys

Run a structured discovery interview and generate a design brief.

Updated Apr 5, 2026

Search Tags:#design #planning #discovery #feature #ux #design-brief

Ready to run

npx skills add https://github.com/kireevkit15-sys/-1 --skill shape-kireevkit15-sys

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: shape
Source: https://github.com/kireevkit15-sys/-1/tree/main/skills/shape
Command: npx skills add https://github.com/kireevkit15-sys/-1 --skill shape-kireevkit15-sys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning UX and UI for a feature before coding, by running a structured discovery interview and producing a design brief that guides implementation.

Core Features & Use Cases

Phase 1: Discovery Interview to understand goals, stakeholders, and constraints.
Phase 2: Design Brief generation that codifies output into actionable design direction and requirements for implementation.
Use Case: For a new feature, you gather context and produce a design brief that informs product, design, and engineering teams.

Quick Start

Initiate a discovery interview for a feature and produce 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 create a design brief for a new feature?▼

A design brief is generated by running a structured discovery interview to gather context on goals, stakeholders, and constraints, then codifying that output into actionable design direction and requirements for implementation.

Why do I need a discovery interview before planning UX?▼

A discovery interview is needed before planning UX to establish design direction, understand constraints, and define strategy, ensuring all product, design, and engineering teams have aligned requirements before any code is written.

What is the best way to plan UI for a feature before coding?▼

The best way to plan UI before coding is to use a structured discovery phase that produces a design brief, guiding implementation by defining strategy and constraints upfront.

Can I use this to gather context for UX planning?▼

Yes, you can use this to gather context for UX planning by invoking a discovery interview that collects goals and constraints to inform the final design brief output.

Does planning a design brief require invoking other tools?▼

Yes, planning a design brief requires invoking /impeccable to properly gather context and produce the final design brief for implementation.

When should I not use a structured design brief approach?▼

You should not use a structured design brief approach if your feature planning phase is already complete or if implementation has already begun, as this process is designed to establish direction before any code is written.