Research Decision Room

Takes your pile of interview notes, support tickets, and survey snippets and builds a single HTML page that puts evidence, themes, a confidence heatmap, and a decision memo in one place. It's not a slide deck. It's a working room where you can see which signals are strong, which opportunities have real backing, and what experiment to run next. Useful when you need to move from "we talked to users" to "here's what we should build and why" without inventing certainty or burying the contradictions. The artifact includes an evidence ledger with filtering, an opportunity matrix with scores, and a reversible next step.

skills.sh installs: 2.3K
GitHub stars: 106.9K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add nexu-io/open-design --skill research-decision-room --agent claude-code

Installs into .claude/skills of the current project.

Files

Research Decision Room Skill

Create a single-page HTML decision artifact that helps a product or design team turn messy evidence into a clear next move. The output is not a decorative research deck. It is a working room for debate: evidence, themes, confidence, tradeoffs, and recommended experiments stay visible together.

Resource map

research-decision-room/
├── SKILL.md
├── example.html
└── references/
    ├── checklist.md
    └── evidence-model.md

Read references/evidence-model.md before synthesis and run references/checklist.md before emitting the artifact.

When to use this skill

Use this skill when the user has any mix of:

Interview notes, usability-test observations, support tickets, sales call notes, app-store reviews, NPS comments, survey open text, analytics snippets, or product-decision context.
A decision that needs evidence: "Should we build X?", "Which onboarding path should we try?", "Why are users dropping off?", "What do customers actually mean by slow?"
A need to share findings with stakeholders who will not read a long research report.

SKILL.md on GitHub