Define: PRODUCT.md Synthesis

This skill takes the Define-phase documents — Product Offer, Customer Persona, Pricing Strategy, and Mini-Launch (plus the launch log and the optional Business Strategy Deep Dive, when they exist) — and synthesises them into a single readable PRODUCT.md that sits in docs/ at the project root. The output is what a co-founder, designer, advisor, or first hire could read in 4–6 minutes and walk away knowing exactly what the product is, who it's for, why it wins, how it makes money, and how we'll know if it's working.

The source documents are deliberately rigorous — they hold the founder to specifics, named entities, and concrete numbers. They also lean on acronyms — ICP, JTBD, MRR, ARR, GTM, RAG, BYOK, TAM/SAM/SOM — that work fine inside the founder's working documents but quietly shut out anyone reading PRODUCT.md without that vocabulary. This skill's job is to spell those acronyms out, not to strip wider framework language. Terms like wedge, anti-persona, north star, moat, freemium, willingness to pay are well-understood in startup and design conversation and read more clearly than their long-form alternatives — those stay. The skill keeps every substantive fact (real numbers, named competitors, customer-voice quotes, concrete prices) and trims only the abbreviations and over-qualification.

The output is intentionally succinct without being shallow. Each of the eight sections is a focused paragraph that contains everything substantive from the source documents, written in plain English a smart friend at a dinner party could follow.

Session length: Designed to be completable in 15–30 minutes of conversation. The skill reads the source documents, then drafts each of the eight sections one at a time — presenting the draft, asking for confirmation or amendments, folding the user's feedback in, and only then moving on to the next section. Once all eight are locked in, the assembled document gets one final look and then writes to file. No external research is required — all the input lives in the productos/define/ folder.

Inputs

Locate the source documents in productos/define/ (or define/ in a standalone ProductOS checkout). Look there before searching more widely, and never search node_modules/, build output, or vendored code:

1. The Product Offer — usually 1-Product-Offer.md. The single most important input. Provides Customer, Pain, Outcome, Mechanism, Guarantee, Proof, and the assembled one-sentence pitch.
2. The Customer Persona — usually 2-Customer-Persona.md. Provides the texture for the Customer and Problem sections — role, life context, the specific moment when the problem shows up, the customer's verbatim pain language, and the anti-persona for the "Not for: ..." closer.
3. The Pricing Strategy — usually 3-Pricing-Strategy.md. Provides the Business model section: who pays, the launch price, and the anchors it sits against.
4. The Mini-Launch — usually 4-Mini-Launch.md, plus the Launch Log at docs/LAUNCHES.md if it exists. Provides the Proof section's first-party evidence — real replies from potential customers, dated, warm/cold labelled, plus the believers list and the current rung on the signal ladder — and often the freshest customer-voice quotes in the folder. The Goal section's near-term bar is the ladder's next rung.
5. The Business Strategy Deep Dive — BONUS-Business-Strategy-Deep-Dive.md, if the user has done the optional deep dive. When filled, it upgrades the Business model section (revenue model, pricing ladder, cost & margin), the Why section (unfair advantage), and the Goal section (north star metric). When empty, skip it silently — the Pricing Strategy and launch log carry those sections.