i-shape

Guide structured discovery interviews and convert insights into a design brief.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design teams often jump into UI sketches without deeply understanding user needs and constraints. i-shape provides a structured discovery process and outputs a ready-to-implement design brief that guides implementation.

Core Features & Use Cases

  • Structured discovery interview to elicit context and requirements.
  • Uses a Context Gathering Protocol to ensure alignment before design.
  • Produces a design brief that directs implementation for planning and execution.

Quick Start

Initiate a discovery session for a new feature and generate a design brief.

Frequently Asked Questions about i-shape

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

FAQPage Schema
How do I create a UX design brief before starting UI development?

To create a UX design brief, you need a structured discovery process that gathers user context and requirements. This skill guides discovery interviews and converts those insights directly into a production-ready brief to align stakeholders before implementation.

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

Structured discovery in UX planning is a protocol for eliciting context and requirements before design begins. You need it when adding new features to ensure teams understand constraints and align on deliverables before jumping into UI sketches.

How do I conduct a discovery interview for a new product feature?

Conducting a discovery interview involves using a context gathering protocol to ask targeted questions. This skill streamlines the session, capturing necessary constraints and user needs, and outputs a formal design brief directing subsequent execution.

Can I use this design planning process for any product team?

Yes, you can use this design planning process for any product team. It is applicable to new features across various products, enabling context gathering and stakeholder alignment without depending on specific platforms or external tools.

Why does my design team need a formal design brief?

Your design team needs a formal brief to prevent jumping into UI sketches without understanding constraints. It provides structured deliverables and actionable context, driving implementation and ensuring stakeholder alignment before coding begins.