i-shape

Conduct a structured discovery interview and synthesize a design brief.

1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/ohnotnow/agentic-stuff --skill i-shape-ohnotnow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: i-shape
Source: https://github.com/ohnotnow/agentic-stuff/tree/main/skills/i-shape
Command: npx skills add https://github.com/ohnotnow/agentic-stuff --skill i-shape-ohnotnow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Shape a feature's UX and UI by conducting a structured discovery interview and then producing a design brief that guides implementation, aligning stakeholders before any code is written.

Core Features & Use Cases

  • Discovery Interview Protocol: Systematically surfaces goals, user roles, success criteria, constraints, and context to inform design decisions.
  • Design Brief Output: Produces a structured brief that defines direction, scope, constraints, and evaluation criteria for implementation and handoffs to other skills.
  • Guardrails for Planning: Keeps the activity strictly planning-focused, avoiding premature UI decisions and coding.

Quick Start

Begin Phase 1 with a structured discovery for a given feature and then synthesize Phase 2 outputs into 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 design brief for a new feature?

A design brief guides feature implementation by synthesizing discovery interview insights into structured direction, scope, and evaluation criteria, aligning stakeholders before any code is written.

What is a discovery interview in UX planning?

A UX discovery interview is a structured protocol that systematically surfaces project goals, user roles, success criteria, and constraints to inform design decisions before UI work begins.

How do I conduct a UX discovery phase without making UI decisions?

Enforce Phase 1 rules during your UX discovery phase to prohibit coding and premature UI decisions, focusing strictly on gathering user context to shape the design brief.

Can I use this skill to align stakeholders before implementation?

Yes, you can align stakeholders before implementation by producing a structured design brief that defines direction, scope, constraints, and evaluation criteria for handoffs.

When do I need a design brief for handoffs?

You need a design brief for handoffs when transitioning from feature planning to implementation, ensuring downstream skills receive structured direction, scope definitions, and evaluation criteria.

What constraints should a feature design brief include?

A feature design brief should include constraints gathered during the discovery interview, such as user context, success criteria, and project goals, referencing the Context Gathering Protocol.