develop-design-rationale

Document UX design decisions with context, options, and trade-offs.

527|69|Updated Jan 9, 2026

Search Tags:#design #documentation #trade-offs #rationale #design-system #stakeholders #design-decision

Ready to run

npx skills add https://github.com/product-on-purpose/pm-skills --skill develop-design-rationale

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: develop-design-rationale
Source: https://github.com/product-on-purpose/pm-skills/tree/main/skills/develop-design-rationale
Command: npx skills add https://github.com/product-on-purpose/pm-skills --skill develop-design-rationale

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Design decisions are often poorly documented, leading to misinterpretations, repeated debates, and loss of crucial context. This Skill provides a structured way to capture the rationale behind design choices so future teams understand the "why" behind decisions.

Core Features & Use Cases

Structured decision records: Capture context, alternatives considered, evaluation criteria, and trade-offs in a single, reusable artifact.
Governance and onboarding support: Use in design reviews, architecture discussions, and design-system governance to accelerate alignment.
Audit-ready documentation: Maintain a traceable history for knowledge transfer, compliance, and future reference.

Quick Start

Create a design rationale document for a recent UX decision, including the problem statement, explored options, the chosen approach, assessment criteria, and next steps. Attach the rationale to the design review and reference it from the design-system repository.

Frequently Asked Questions about develop-design-rationale

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

FAQPage Schema

What is design rationale documentation and when do I need it?▼

Design rationale documentation captures the context, options considered, and trade-offs behind design decisions. You need it during UX reviews, system evolutions, and governance to prevent repeated debates and loss of crucial context.

How do I document design decisions for a design system repository?▼

To document design decisions, create a structured record including the problem statement, explored options, chosen approach, assessment criteria, and next steps. Attach this rationale to design reviews and reference it from the design-system repository.

What's the best way to capture UX trade-offs for stakeholder alignment?▼

The best way to capture UX trade-offs is using a structured decision record that details evaluation criteria and context. This ensures stakeholders understand the reasoning behind choices and accelerates alignment during reviews.

Can I use structured design rationale for audit and onboarding processes?▼

Yes, you can use structured design rationale for audit and onboarding processes. It maintains a traceable history of decisions for knowledge transfer and compliance, helping new teams understand the context behind design choices.

What should a design decision record include to prevent misinterpretation?▼

A design decision record should include the problem context, alternatives considered, evaluation criteria, final decisions, and follow-up actions. This structure ensures future teams understand the context and prevents misinterpretations.