UX Strategize

UX Strategize

Generate structured UX artifacts from business analysis. Dual output: markdown (human) + YAML (machine, for /ux-wireframe).

Artifact Types

Workflow

1. Parse $ARGUMENTS → {artifact-type} {subject}.

   • If subject missing → AskUserQuestion.
   • If artifact-type missing → Glob ux/*.md, recommend next artifact per build order:

   What exists in ux/	Recommend	Why
   Nothing	empathy-map	Foundation — understand the user first
   empathy-map	jtbd	Structure the jobs from empathy data
   empathy-map + jtbd	forces	Understand switching behavior
   + forces	journey-map	Map end-to-end experience
   + journey-map	vpc	Align value prop to known jobs/pains
   + vpc	persona	Synthesize into coherent archetype

   Present recommendation + confirm with user before generating.

2. Load template — Read references/{artifact-type}.md + references/common.md.

3. Discover context — Glob + Read (priority order):

   • analysis/*{subject}* and analysis/*.md
   • PRD-*-llm.md, NOTES-*-learnings.md
   • ux/*.md (prior artifacts for cross-referencing)

4. If no relevant input found → AskUserQuestion for target customer + pain context.

5. Generate artifact using loaded template (markdown + YAML schema + frontmatter).

6. Write to ux/{artifact}-{subject}.md.

Output Contract

Every file must include both elements from the artifact reference:

1. YAML frontmatter (artifact, subject, persona, date, source_docs, engagement_layer)
2. Structured YAML block at end of file (§ Structured Data for /ux-wireframe)

Key Rules

• Ground ALL content in source data — no fictional personas or invented verbatims
• Use original language from sources (preserve FR quotes when input is French)
• Cross-reference prior ux/*.md artifacts when available
• Tag engagement layer mapping per artifact
• See references/common.md for domain adaptations, kill criteria, and engagement layer mapping