blog-brand

# Blog Brand: Durable Editorial Context Generates two project-root files that the blog orchestrator auto-loads for supported writing and planning commands when present: - `BRAND.md`: who the audience is, what the brand stands for, what to never say - `VOICE.md`: how the brand sounds, structurally and lexically These are the editorial equivalent of impeccable's PRODUCT.md / DESIGN.md pattern: persistent context that survives across sessions and propagates to every command. ## Why this exists Today, persona JSON (from `blog-persona`) is loaded by some skills and not others. Topic-cluster context lives inside cluster vaults. Competitor positioning lives nowhere. Each blog command re-derives "what is the brand" from whatever context it has. `BRAND.md` and `VOICE.md` fix this: one canonical source, loaded by the `blog` orchestrator at the start of every command. When neither file exists, behavior is unchanged from v1.7.1. Backward compatible. ## Commands | Command | Purpose | |---|---| | `/blog brand init` | Interactive interview, writes BRAND.md and VOICE.md to project root | | `/blog brand show` | Display current contents (or report missing) | | `/blog brand update` | Re-run the interview with current values as defaults | ## Init Workflow Run the 5-step interactive interview. Ask each step, wait for response, then proceed. If `blog-persona` JSON already exists, pre-fill voice answers from it. ### Step 1: Audience Ask: - **Primary audience role** (e.g. "head of marke...