i-shape

Conduct a structured discovery interview and generate a formal design brief.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan UX/UI for a feature before writing code by running a structured discovery interview and producing a design brief to guide implementation.

Core Features & Use Cases

  • Phase 1: Discovery Interview prompts to understand purpose, users, constraints, data, and design goals.
  • Phase 2: Design Brief generation that structures requirements, constraints, and implementation guidance for the team.
  • Use Case: A product team uses this to align design direction before coding, reducing rework and clarifying success criteria.

Quick Start

Initiate Phase 1 by conducting a structured discovery interview using the provided prompts, then synthesize the results into Phase 2's design brief.

Frequently Asked Questions about i-shape

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

FAQPage Schema
What is a structured discovery interview for UX design?

A structured discovery interview captures design context and requirements by exploring purpose, users, constraints, data, and goals before coding. It synthesizes findings into a formal design brief to guide implementation and minimize rework.

How do I create a design brief before feature planning?

Create a design brief by conducting a structured discovery interview to gather requirements, then synthesizing those results into formal documentation. This process structures constraints and implementation guidance for the product team.

Can I use this for stakeholder interviews to align product design?

Yes, this workflow uses structured discovery prompts to interview stakeholders, capturing purpose, users, and constraints. The synthesized design brief aligns the product team on direction and clarifies success criteria before development.

What's the best way to plan UX/UI features to reduce development rework?

The best way to reduce rework is enforcing an end-to-end workflow: run a discovery interview to capture requirements, then generate a design brief. This structured approach clarifies scope and design goals before implementation begins.

Does this design planning workflow require any specific tools or dependencies?

No specific tools or dependencies are required. The workflow operates through two phases: discovery interview prompts to gather context, followed by design brief generation to structure requirements and implementation guidance.