persona-writelisted

# Persona Write ## Purpose Scaffold a structured user-persona document for the project to consume internally. The output is for the team — designers, PMs, researchers, agents — to anchor decisions against. It does NOT ship to end users. The skill enforces a consistent shape so personas across the project's research corpus are comparable and easy to dispatch tasks against (e.g., "review this flow as persona:gabi"). ## Scope In: - A markdown file at `docs/personas/<id>.md` (or operator-specified path) with the required fields. - A frontmatter block with `id`, `created`, `last-reviewed`, `source` (research interview / synthesized / placeholder). - A standard template covering: name, demographic context, goals, frustrations, behaviors, JTBD, primary devices, accessibility considerations. Out: - Real user research. The skill scaffolds the shape; filling it with truth is the researcher's job (interview transcripts, diary studies, analytics). - Marketing personas / ICPs. Different artifact, different shape. This is a UX persona — anchored on goals and frustrations, not segmentation for sales. - Anti-personas / negative personas. Different template; out of scope for v1. ## When to use - At project kickoff, to lock in 3-5 primary personas. - After a research round (interviews, diary study), to consolidate findings into a comparable artifact. - When a flow review uncovers "we don't actually know who this is for" — pause and write the persona first. - Before