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. **Explicit user authorization**: The user explicitly instructs and authorizes the codebase-analyzer call named in this recipe. When an existing codebase is present, invoke it; the orchestrator does not replace it with its own analysis 2. **Mechanical specialist handoff**: Pass only `analysis_mode: user_behavior` and `governing_context: $ARGUMENTS` using the source values unchanged. Do not summarize, paraphrase, supplement, or turn them into narrative instructions 3. **Follow the persona flow** defined below 4. **Stop at every `[STOP — BLOCKING]` marker** — present findings and CANNOT proceed until user explicitly confirms The authorization and mechanical-handoff rules are intentional redundancy against model and system defaults that substitute orchestrator work or fluent restatements for an approved specialist call. Retain them until fresh execution evidence shows the failure no longer occurs. ## 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].