ux-research-synthesis
UX Research Synthesis
Overview
Use this skill to transform fragmented research inputs into coherent and prioritized product/design direction.
Scope Boundaries
- Multiple research sources exist but implications are unclear or conflicting.
- Teams need to prioritize design actions using evidence, not intuition.
- Product or design planning requires confidence-weighted insight summaries.
Templates And Assets
- Synthesis mapping template:
assets/ux-synthesis-mapping-template.md
Inputs To Gather
- Research transcripts, usability findings, analytics, and support signals.
- Product goals, current hypotheses, and design constraints.
- Segment definitions and sampling limitations.
Deliverables
- Insight clusters with evidence links and confidence level.
- Prioritized design implications with expected user impact.
- Open questions and follow-up research recommendations.
Workflow
- Normalize incoming evidence and remove duplicate observations.
- Cluster findings by user goal, failure pattern, and context.
- Separate facts, interpretations, and assumptions.
- Resolve contradictions by checking source quality and representativeness.
- Rank implications by severity, frequency, and strategic impact.
- Publish synthesis with confidence, limitations, and recommended actions.
Quality Standard
- Each implication is linked to evidence and confidence level.
- Contradictions are documented with explicit uncertainty.
- Prioritization logic is transparent and repeatable.
- Output is actionable for design and product planning.
Failure Conditions
- Stop when evidence traceability is missing.
- Stop when confidence cannot be estimated due to weak data quality.
- Escalate when synthesis results conflict with critical business constraints.
More from kentoshimizu/sw-agent-skills
graph-algorithms
Graph algorithm workflow for modeling entities/relations and selecting traversal, path, ordering, or flow strategies. Use when correctness or performance depends on graph representation and algorithm choice; do not use for schema-only modeling or deployment topology planning.
14bash-style-guide
Style, review, and refactoring standards for Bash shell scripting. Trigger when `.sh` files, files with `#!/usr/bin/env bash` or `#!/bin/bash`, or CI workflow blocks with `shell: bash` are created, modified, or reviewed and Bash-specific quality controls (quoting safety, error handling, portability, readability) must be enforced. Do not use for generic POSIX `sh`, PowerShell, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
11architecture-clean-architecture
Clean Architecture workflow for enforcing dependency direction, stable domain boundaries, and use-case-centered application design. Use when teams must separate business rules from frameworks and delivery mechanisms; do not use for isolated module cleanup without boundary implications.
11powershell-style-guide
Style, review, and refactoring standards for PowerShell scripting. Trigger when `.ps1`, `.psm1`, `.psd1` files, or CI workflow blocks with `shell: pwsh` or `shell: powershell` are created, modified, or reviewed and PowerShell-specific quality controls (error handling, parameter validation, readability, operational safety) must be enforced. Do not use for Bash, generic POSIX `sh`, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
10github-codeowners-management
Govern CODEOWNERS rules so review routing reflects real ownership and risk boundaries on GitHub. Use when repository ownership mapping or mandatory reviewer rules must be defined, updated, or audited; do not use for non-GitHub runtime architecture or data-layer design.
9security-authentication
Security workflow for authentication architecture, credential lifecycle, and session/token assurance. Use when login, identity proofing, MFA, or session security decisions are required; do not use for authorization policy design or non-security quality tuning.
9