Your contract, marked up against your rules.

You're helping me write a contract review playbook for a skill that marks up contracts in Word. The playbook is the set of rules the skill checks every contract against. The positions are mine to decide. Don't invent any, and don't present your suggestions as legal advice.

Interview me one question at a time and wait for my answer before moving on.

First, ask which country we're in, whether we're usually the customer or the supplier, and what kind of contracts we review. Use my answers to tailor your suggestions and your spelling.

Then work through these topics, in order:
1. Payment terms
2. Fee increases
3. Renewal
4. Termination for convenience
5. Limitation of liability
6. Intellectual property
7. Data, privacy and security
8. Insurance
9. Subcontracting
10. Governing law

For each topic:
- Say in one sentence what it covers.
- Suggest a common starting position I can accept, change or skip. If I skip it, leave it out.
- Ask for my standard (what we ask for), my fallback (what we'll accept without a fight) and my red flags (what we always change).
- Ask whether a contract with no clause on this topic at all should be reported as high risk.

After the ten topics, ask if there's anything else we always check, such as publicity, non-solicitation or service levels, and add a rule for each one I give you. Then read me a one-line summary of each rule and let me confirm or correct it.

When I confirm, create a downloadable Markdown file called playbook.md. If you can't create a file, put the whole thing in one code block. Use exactly this format, numbering the rules R1, R2, R3 in the order we covered them, and writing suggested wording for every rule in plain contract language using "the Customer" and "the Supplier":

# Contract review playbook

[One line: the kind of contracts this covers and which side we're on.]

Not legal advice. These positions are our own, and a person reviews and signs off every change the skill suggests.

Each rule has a standard position (what we ask for), a fallback (what we accept without a fight) and red flags (what we always change). If a clause already meets the standard or the fallback, leave it alone. Clauses no rule covers are left alone too. A rule marked "If missing: high risk" is reported as high risk when the contract has no clause for it at all.

## R1 [Topic]

- Standard: [our position]
- Fallback: [what we'll accept, or "none. This rule is not negotiable."]
- Red flags: [what we always change]
- Suggested wording: "[clause text the reviewer can drop in]"
- If missing: high risk.

Only include the "If missing: high risk." line on rules where I said yes.