shape

Plan feature UX and UI through discovery interviews and design briefs.

Updated Jan 10, 2026
One-click install
npx skills add https://github.com/serguei9090/Agentic-Governance-Framework --skill shape-serguei9090
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shape
Source: https://github.com/serguei9090/Agentic-Governance-Framework/tree/main/MasterPrompts/.agents/skills/shape
Command: npx skills add https://github.com/serguei9090/Agentic-Governance-Framework --skill shape-serguei9090

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan the UX and UI for a feature before writing code to ensure design decisions are grounded in discovery and context.

Core Features & Use Cases

  • Phase 1: Discovery Interview to gather goals, constraints, and user context
  • Phase 2: Design Brief generation that guides implementation
  • Output: A reusable design brief that informs design and engineering work

Quick Start

Run the initial discovery interview to collect design context, then generate 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 coding?

To plan UX and UI for a feature before coding, run a structured discovery interview to gather goals and constraints, then generate a design brief that guides implementation and prevents misalignment.

What is a design brief and why do I need one for feature planning?

A design brief is a reusable artifact produced during early planning that maintains clear context, constraints, and strategy to satisfy design governance needs and guide implementation work.

How do I run a discovery interview to gather design context?

Running a discovery interview involves a structured phase to collect user context, goals, and constraints, which then feeds directly into the generation of a reusable design brief.

Can I use a design brief to align engineering and design teams?

Yes, you can use a design brief to align engineering and design teams by maintaining clear context and strategy in a reusable artifact that informs both design and implementation work.

What's the best way to prevent design misalignment before implementation?

The best way to prevent design misalignment is to apply a structured planning phase early to produce a design brief, ensuring all implementation decisions are grounded in discovery and context.

When should I start the UX planning process for a new feature?

You should start the UX planning process during early planning phases, before writing any code, to run a structured discovery interview and produce a design brief that guides implementation.