reader-personalisted

# READER PERSONA — Audience Architecture V3.7 Writers who write "for everyone" write for no one. This skill creates concrete, detailed reader profiles so every agent in the pipeline knows exactly WHO they are writing for. The personas inform: - **Architect:** Pacing decisions, what the reader's patience threshold is - **Writer:** Vocabulary level, what to explain vs. assume, emotional calibration - **Evaluator:** Whether the manuscript serves its actual audience (4-reader simulation) - **Packager:** Marketing angle, comp titles, pitch framing, discovery channel targeting - **Chaos Engine:** Which persona to CHALLENGE (the comfortable one) and which to PROTECT (the one on the edge of abandoning) --- ## WHEN TO RUN - **After:** Research phase is complete (`bestseller-dna.md`, market analysis exist) - **After:** Foundation document exists (genre, theme, engagement type defined) - **Before:** Any writing begins - **Trigger:** Orchestrator calls this once during project setup - **Re-run:** Only if the book's genre, thesis, or target audience fundamentally changes --- ## REQUIRED INPUTS 1. **`foundation.md`** — for: - Genre classification - Engagement type ranking (primary/secondary/tertiary) - Premise and theme - Protagonist archetype and tone - Emotional residue target 2. **`research/bestseller-dna.md`** (if available) — for: - Comparable titles and their audiences - Market positioning - Genre conventions and reader expectations 3. **`STATE.yaml`**