Menu
Transform raw research into actionable insights that inform design decisions. Use during Define phase after completing research.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Assess assumptions on certainty and risk to prioritize validation efforts. Use at project start or before phase transitions.
Test whether assumptions are true before making commitments. Use when assumptions have low certainty and high risk.
Create structured visualizations of stakeholder perspectives (says, thinks, does, feels) to build deep understanding. Use when conducting user research or validating assumptions.
Assess solution ideas on impact and feasibility to prioritize prototyping. Use during Ideate phase when deciding which ideas to pursue.
Distinguish user wants from underlying needs to guide solution design. Use when stakeholders make feature requests or during Define phase.
Create clear leadership presentations that communicate findings and enable good decisions. Use at end of each phase or before major commitments.
| name | insight-synthesis |
| description | Transform raw research into actionable insights that inform design decisions. Use during Define phase after completing research. |
Transform raw research data into actionable insights that inform design decisions.
Collect from projects/[project_name]/insights/:
Look across research for:
An insight is NOT just a finding. Transform observations into understanding:
Observation: "Users check their work 3-4 times" Insight: "Users lack confidence in the system's accuracy, creating anxiety and inefficiency"
Observation: "Users prefer mobile for field work" Insight: "Context switching between devices disrupts workflow because data doesn't sync reliably"
Good insights answer "why" and have implications for design.
For each insight:
For each insight, ask:
Create synthesis document in insights/ folder and update currentstate.json:
{
"id": "i1",
"title": "Lack of system confidence creates inefficiency",
"description": "Users check work multiple times due to past system errors, creating anxiety and wasted time",
"confidence": "high",
"sources": ["insights/observation_001.md", "insights/interview_003.md"],
"implications": "Reliability and clear feedback are more important than features"
}
Pattern: What we observed across multiple sources Insight: Why it happens and what it means Implication: What we should do about it
Pattern: 6 out of 8 field techs use paper notes despite having mobile devices
Insight: Mobile interface requires too many steps and focus for field context where attention is divided and conditions are suboptimal (gloves, sunlight, distractions)
Implication: Design for quick capture with minimal interaction; offline-first; large touch targets; high contrast for outdoor visibility