UX Research Pipeline
Designer Official v1.0.16Plan user interviews, collect responses, synthesize findings, generate personas, and create empathy maps
by skrptiq
Sign in to import this skrpt into your workspace.
Sign inWhat's included 11 nodes
UX Research Pipeline
Plan user interviews, collect responses, synthesize findings, generate personas, and create empathy maps
Empathy Mapping
Creates empathy maps for each persona covering what users think, feel, say, and do
Interview Collection
Human gate — pauses execution for the user to paste interview responses
Persona Generation
Creates evidence-based user personas from synthesized research findings
Research Planning
Plans interview questions and research methodology based on research goals and target users
Research Synthesis
Synthesises findings across multiple interview responses to identify patterns, themes, and insights
Collect Interview Responses
Gate prompt — pauses for user to paste interview responses or notes
Create Empathy Maps
Creates empathy maps from personas and research data
Generate Personas
Creates evidence-based user personas from synthesized research
Plan Research
Generates interview questions and research plan from goals and target users
Synthesize Research Findings
Synthesises patterns and insights across interview responses
Requirements 1 service, 1 data type
- LLM Service
- pii
Security Passed
Detected
- Services: llm-service
- Permissions:
- Data Handling: pii
Version history 14 releases
GH#844 — migrate the gate step from node-meta (`metadata.gate: true` in the skill) to the canonical execution-entry `gate: true` on the workflow step. Single source of truth; the engine + app read the execution entry. No behaviour change — `IsGate` is identical.
GH#745 — declare per-step `output: {name, type}` on every execution step (research_plan/text, responses/text, findings/text, personas/text, empathy_maps/text, polished_report/text, consistency_verdict/decision). Lights up the #744 rich flow-map. Content-only; no bindings or logic changes.
Fix-forward after Row 3b v1.0.13 publish failure. The v1.0.13 per-skrpt CI's "Register version with Hub API" step failed because the consumer's source `manifest.id` (d573d5ea…) did not match the D1 catalogue row's id (d389b5d8…) — a legacy drift from before Action 6 (`0bcc5ae0`) made publish-skrpt.mjs Step 2 INSERT use `manifest.id` for the D1 id column. v1.0.14 reconciles the source `manifest.id` to the catalogue authoritative value (Row-5-equivalent for consumers) and republishes. Per Adj-1: no re-tag of v1.0.13; the orphaned GitHub release artefact stays inert (no D1 versions row, no consumer pinned it).
Wave 2: re-signed with canonical engine signing pipeline.
Signature fix — RELEASE_NOTES.md now included in integrity checksum.
Initial catalogue release with full structural and content-quality validation. All scanner checks pass.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
More from Designer
View all →Design-to-Developer Handoff Pipeline
Review designs, generate component specs, define responsive requirements, audit accessibility, and produce handoff documentation
UX Strategy Pipeline
Define the problem space, analyze competitors, generate design principles, map experiences, and produce strategic recommendations
Usability Testing Pipeline
Plan usability tests, collect results via gate step, analyze findings, and produce prioritized recommendations