design-exploration

Structure design decision problems and define user goals to surface viable options.

3|Updated Dec 7, 2025
One-click install
npx skills add https://github.com/Grimblaz/agent-orchestra --skill design-exploration-grimblaz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-exploration
Source: https://github.com/Grimblaz/agent-orchestra/tree/main/skills/design-exploration
Command: npx skills add https://github.com/Grimblaz/agent-orchestra --skill design-exploration-grimblaz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consolidates design exploration into a repeatable workflow that helps teams surface viable options, compare trade-offs, and lock in a recommended direction before planning.

Core Features & Use Cases

  • Gather the current context from issues, requirements, and constraints to ground decisions.
  • Load adjacent guidance and reference material only when it changes decision quality.
  • Prepare a durable design payload with decisions, rationale, acceptance criteria, and testing scope.
  • Run a 3-pass design challenge to stress-test options and surface decision questions for stakeholder alignment.

Quick Start

Describe your design goal and constraints, then request 2–3 viable options with trade-offs and rationale.

Frequently Asked Questions about design-exploration

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

FAQPage Schema
How do I structure design exploration to compare trade-offs for product design decisions?

Design exploration consolidates context from requirements and constraints to surface viable options, compare trade-offs, and lock in a recommended direction. It outputs a durable payload with decisions, rationale, acceptance criteria, and testing scope.

What is the best way to document design rationale and acceptance criteria for UI changes?

Document design rationale and acceptance criteria by preparing a durable design payload after exploring viable options. This payload captures the recommended direction, trade-offs, and testing scope to align stakeholders before planning.

How do I stress-test design options during a product design review?

Stress-test design options by running a 3-pass design challenge. This workflow surfaces decision questions and evaluates trade-offs to ensure stakeholder alignment and confirm the viability of the recommended direction.

When do I need a structured workflow for design decision-making and feature negotiations?

You need a structured workflow for design decision-making when trade-offs matter, such as during feature negotiations or UI changes. It grounds decisions by gathering current context, constraints, and adjacent guidance to improve decision quality.

Can I use this design exploration workflow for UX feature negotiations before planning?

Yes, you can use this workflow for UX feature negotiations. By identifying the core design problem and defining user goals, it surfaces viable options and rationale, enabling teams to converge on a direction before planning begins.

What limitations should I expect when consolidating design trade-offs and decision rationale?

The workflow relies on gathering accurate current context and constraints to ground decisions. You should expect limitations if adjacent guidance is not loaded when it changes decision quality, potentially impacting the accuracy of the final design payload.