synthesize-personas

Synthesize JTBD personas and capability-to-persona maps from epics and scope inputs.

3|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/kapilvirenahuja/garura --skill synthesize-personas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: synthesize-personas
Source: https://github.com/kapilvirenahuja/garura/tree/main/core/components/skills/synthesize-personas
Command: npx skills add https://github.com/kapilvirenahuja/garura --skill synthesize-personas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It transforms intent epics and scope signals into validated JTBD personas with a capability-to-persona map so designers can plan journeys and screens without guessing user roles.

Core Features & Use Cases

  • JTBD Persona Extraction: Pulls candidate user types from expectation success and failure scenarios and related recovery notes.
  • Demographic-Free Persona Synthesis: Converts functional roles into strict JTBD job stories using the When/I want/so I can format while rejecting demographic personas.
  • Capability Mapping for Design: Maps each in-scope capability to one or more persona roles derived from the epics and selected capability list.
  • Decision Manifest Emission: Writes a decision-manifest.yaml that records tiered decisions and grounding for auditability.
  • Defensive Output Contract: Produces structured failure output when required inputs (notably the MVP recommendation file) are missing or empty.

Quick Start

Run synthesize-personas during the design Stage 1 to read epics from the scope area, generate experience/personas.md, and emit the decision-manifest.yaml alongside it.

Frequently Asked Questions about synthesize-personas

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate personas from epics using the JTBD framework?

Generating JTBD personas from epics involves extracting candidate user types from expectation success and failure scenarios, then synthesizing them into strict When/I want/so I can job stories. This process rejects demographic personas and outputs a capability-to-persona map.

What is a capability-to-persona map in UX discovery?

A capability-to-persona map links each in-scope capability to one or more persona roles derived from intent epics. It allows designers to plan user journeys and screens without guessing user roles during the design Stage 1 workflow.

How do I map capabilities to personas for design planning?

Mapping capabilities to personas requires loading epics_dir YAML files and scope.yaml to identify selected capabilities. The system reads the Primary Focus section from the MVP recommendation file to narrow which personas get created and emits personas.md alongside a decision-manifest.yaml.

Can I use demographic personas for UX discovery in this workflow?

Demographic personas are explicitly rejected in this UX discovery workflow. The system strictly converts functional roles extracted from intent epics into JTBD job stories using the When/I want/so I can format to ensure design planning remains grounded in user intent.

What happens if the MVP recommendation file is missing during persona synthesis?

If the MVP recommendation file is missing or empty, the system executes a defensive output contract. It produces a structured failure output instead of attempting persona synthesis, ensuring required scope inputs are present before generating personas.md.

Why does persona synthesis require a decision-manifest.yaml file?

A decision-manifest.yaml file is required to record tiered decisions and grounding during persona synthesis. It ensures auditability by documenting how intent epics and scope inputs were transformed into validated JTBD personas and the capability-to-persona map.