product-writelisted

# product-write `PRODUCT.md` is the top of the altitude ladder - the thing specs, decisions and backlog items get judged against. This writes it by interview, not by template-filling. ## First: is it empty, stale, or contested? Three different jobs, and doing the wrong one wastes the session. - **Empty** - a full interview, below. - **Stale** - the product moved and the file did not. Do not rewrite from scratch: read it, read the specs and the accepted BDRs that came after it, and show the user the specific contradictions. Ask about those. A frame that survived contact deserves editing, not replacement. - **Contested** - the file is fine but people disagree with it. That is not a writing task; it is a decision, and `bdr-write` is the skill. Say so. ## The interview Ask few questions, in this order, and **stop after each** - the answers change what is worth asking next. Draft as you go and play it back in the user's own words. 1. **What is it, in one sentence a stranger would understand?** If the answer needs a second sentence, the product is not one product yet - and that is worth naming now rather than discovering it three capabilities in. 2. **Who is it for?** Names, roles, or segments. If `docs/personas.md` exists, read it first and ask whether it is still right; if it does not, this is where it starts, and `personas-write` takes over once names appear. 3. **What do they do today instead?** The status quo, including "nothing" and "a spreadshee