Agent skill · research science · nexu-io
research-decision-room
Turn messy user research notes, interviews, support tickets, surveys, and product context into an evidence-backed decision room: a single HTML artifact with an evidence ledger, theme map, confidence heatmap, opportunity matrix, decision memo, and experiment queue. Use when teams need to move from qualitative signals to product or design decisions without fabricating certainty.
Why this skill is useful
Provides a structured method for synthesizing qualitative research into actionable insights, which the AI wouldn't reliably generate on its own.
What it needs
About 4k tokens when loaded. Last updated 2026-08-07. 84,236 stars on the source repository.
What this skill does
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 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. Do not use it for pure visual inspiration, campaign ideation, or brand moodboards. Workflow Step 1 - Establish the decision frame Identify the decision scope from the user's prompt. If the user did not give a decision, derive one from the evidence and label it as inferred. Write a short frame with: Decision question. Audience or segment. Time horizon. Known constraints. What this artifact will not decide. If key context is missing and the task is not blocked, proceed with labelled assumptions instead of asking a broad question. Step 2 - Build the evidence ledger Normalize every useful signal into ledger rows using the model in references/evidence-model.md. Each ledger row must include: id: short stable id, such as I-03, T-14, M-02. sourcetype: interview, usability, support, survey, analytics, sales, field note, or stakeholder. segment: user type or "unknown". signal: one-sentence observation. quoteormetric: direct quote, metric, or "not provided". strength: strong, medium, or weak. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills nexu-io/research-decision-room