customer-blueprint — the customer stone

Every business claims to know its customer; almost none can quote one. The usual persona deck — "Marketing Mary, 34, lives in a suburb, likes yoga" — is demographics cosplaying as understanding, and nothing downstream can use it. What messaging, pricing, and go-to-market actually need is psychology and language: what the customer is afraid of, what they're reaching for, what finally makes them buy, what makes them balk, and the exact words they use for all of it. This skill writes that down, interviews the founder against real evidence, refuses to launder guesses into quotes, and ships the result as a Business OS module: canonical CUSTOMER.md, machine contract, core tables, MCP server, standalone site.

This is stone 2 of 8. Read ../PROTOCOL.md before composing — the module contract, workspace layout, and definition of done live there and are not repeated here.

When to use it