recipe-personalisted

**Context**: Create or update persona files with demographics, context, JTBD, pains/gains, and behavioral patterns. Integrates existing codebase analysis when available. ## Orchestrator Definition **Execution Protocol**: 1. **Delegate code analysis** to codebase-analyzer (via Agent tool, subagent_type: "discover:codebase-analyzer") when existing code reveals user behavior 2. **Follow the persona flow** defined below 3. **Stop at every `[STOP — BLOCKING]` marker** — present findings and CANNOT proceed until user explicitly confirms ## Workflow Overview ``` Input (new persona request / persona update / discovery trigger) ↓ 1. Context Assessment → New vs. Update, existing code? ↓ 2. Research Gathering → User data, interviews, analytics, code analysis ↓ 3. Persona Drafting → Using persona-template.md [Stop: User confirms persona] ↓ Output: docs/product/personas/persona-[name].md ``` ## Execution Decision Flow ### 1. Context Assessment Input: $ARGUMENTS | Situation | Action | |-----------|--------| | No personas exist | Create from scratch — gather user research or assumptions | | Personas exist, new data available | Update existing personas with new evidence | | Existing codebase | Invoke codebase-analyzer for real user behavior insights | | Post-interview / post-survey | Update with new primary research | ### 2. Research Gathering #### From Existing Code (if applicable) **Invoke codebase-analyzer** using Agent tool (subagent_type: "discover:codebase-ana