mocked-persona-interview

# Mocked Persona Interview Skill A disciplined alternative to real user interviews when: - You're a solo developer and cannot talk to users this week - You're on a hobby/learning project with no user research budget - You're running a meta-project dogfood session (see `dogfood_modifier`) - You're in early L0/L1 exploration where real interviews are premature **This skill is NOT a substitute for `/mycelium:user-interview` when real users are available.** Mocked personas are simulation. They catch some mistakes, miss others, and — without discipline — become a confirmation-bias machine. This skill's job is to enforce the discipline. ## Preflight: Read target canvas file(s) before any Write/Edit **Hard rule.** Before issuing `Write` or `Edit` against any `.claude/canvas/*.yml`, use the **Read tool** on that file in this session. Claude Code's Read-before-Write check requires the `Read` tool specifically — `cat`/`head`/`grep` via Bash do NOT satisfy it. **Edit vs Write — different cost profiles** (verified 2026-05-14): - **`Edit`** (exact-string replacement): `Read` with `limit: 1` satisfies the check at ~50 tokens. State-tracking is per-file, not per-byte — subsequent `Edit` calls work anywhere in the file. Use this for partial updates against large canvas files (e.g., `purpose.yml` at 800+ lines). - **`Write`** (full replacement): do a **full Read** first. Write obliterates the file; you should see what you're about to replace. The `limit:1` shortcut is *not* appropriate h...