design-decide

Convert reconciled verdict evidence into DesignPrinciple and DesignDecision artifacts.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/speplinski/hackathon-opus-47 --skill design-decide
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-decide
Source: https://github.com/speplinski/hackathon-opus-47/tree/main/skills/design-decide
Command: npx skills add https://github.com/speplinski/hackathon-opus-47 --skill design-decide

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turning evidence from reconciled verdicts and user feedback into auditable, actionable product decisions by producing one reusable DesignPrinciple and one surface-specific DesignDecision, each traceable to supporting evidence.

Core Features & Use Cases

  • Emits one DesignPrinciple per cluster that can guide future design work across surfaces.
  • Emits one DesignDecision per cluster detailing a concrete before/after change and the heuristics it resolves.
  • Ensures auditability by linking outputs to specific review_ids and reconciled_heuristics for downstream governance.

Quick Start

Provide the cluster context and reconciled verdict, then generate a DesignPrinciple and a DesignDecision with concrete before/after snapshots.

Frequently Asked Questions about design-decide

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

FAQPage Schema
How do I turn user review evidence into concrete design decisions?

To turn user review evidence into concrete design decisions, you provide cluster context and reconciled verdicts to generate one reusable DesignPrinciple and one surface-specific DesignDecision with before/after changes.

What is a DesignPrinciple and how does it guide future product design?

A DesignPrinciple is a reusable guideline generated per evidence cluster to guide future product design across multiple surfaces. It is traceable to specific review IDs and reconciled heuristics for downstream auditability.

How do I ensure design traceability for UX audit governance?

To ensure design traceability for UX audit governance, link your generated DesignDecision artifacts directly to specific member review IDs, reconciled heuristics, and PriorityScores that ground the outputs in evidence.

What inputs do I need to generate auditable design actions from verdicts?

To generate auditable design actions from verdicts, you need cluster context, member review IDs, top-ranked heuristics from the reconciled verdict, and the PriorityScore to ground the outputs in evidence and impact.

Can I process multiple evidence clusters at once for design decisions?

You cannot process multiple clusters at once; the design decision process applies to one evidence cluster at a time within the Auditable Design pipeline to ensure focused principle and decision generation.

What is the best way to document before and after design changes for an audit?

The best way to document before and after design changes for an audit is to generate a DesignDecision artifact per cluster, which details the concrete before/after snapshots and the specific heuristics it resolves.