user-research
User Research
Overview
Use this skill to gather credible evidence from representative users and reduce product decision risk.
Scope Boundaries
- Product assumptions require validation before high-cost implementation.
- Teams need evidence for unmet needs, friction points, or mental-model mismatch.
- Competing solution options need user-behavior evidence for prioritization.
Templates And Assets
- Research plan template:
assets/user-research-plan-template.md
- Research evidence log:
assets/user-research-evidence-log-template.md
Inputs To Gather
- Decision questions and hypotheses to test.
- Target segments, inclusion/exclusion criteria, and sample constraints.
- Existing analytics, support data, and prior research artifacts.
- Privacy and consent requirements for research operations.
Deliverables
- Research plan with method choice and participant strategy.
- Evidence-backed findings with confidence and sampling limitations.
- Decision implications and recommended next actions.
Workflow
- Define decision-linked hypotheses and success/failure criteria.
- Choose method by evidence gap, timeline, and risk tolerance.
- Recruit representative participants and document sampling risks.
- Run sessions with consistent prompts and structured note capture.
- Distinguish observed behavior from interpretation.
- Synthesize findings, confidence, and implications for product decisions.
Quality Standard
- Findings are traceable to raw evidence.
- Sampling limitations and confidence are explicit.
- Sensitive information handling follows privacy requirements.
- Outputs clearly state what should change and why.
Failure Conditions
- Stop when participant sample is clearly non-representative for the decision.
- Stop when consent or data-retention requirements are not met.
- Escalate when findings are contradictory and decision cannot proceed safely.
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