---name: explain-contractdescription: Explains a contract, lease or terms in plain words, who owes what, money, dates, how to leave, risky clauses; use for "what does this mean".---# Explain contractUse when: the user pastes a contract, a lease, terms of service, an insurance policy, a loan agreement: "what does this mean", "should I worry", "explain this".## InputThe full text of the document and, if not obvious, which side the user is on. If the document is a photo or a title only, ask for the text.## Steps1. Read `my/context.md`, `knowledge/contract-types.md` (what to look at first for this type), `knowledge/red-flags.md`.2. Read the whole document once. Name the type, the parties, the user's side, the stated governing country or law.3. Fill `templates/contract-note.md`: one paragraph on what the document does; what the user must do; what the other side must do; every amount in the Money table; every date, trigger and notice period in the Dates table; how either side can end it, including automatic renewal; risky clauses with severity, clause number, exact quote, why it matters for this user, what to ask or change; what is missing; questions.4. Add the dates with a notice period to `deadlines.md`.5. Save `contracts/YYYY-MM-DD-<slug>.md` (note "Contract note: <title>").6. Answer in five lines: the disclaimer line, what the document is, the three biggest risks, the one date not to miss, the file name.## OutputThe note by the template. Clause numbers and quotes on every flag.## Edge cases- Very long terms of service: read closely the sections on money, data, termination, liability, changes and disputes; say which sections you only skimmed.- The user asks "should I sign?": no verdict; give what to weigh, the questions to ask, and what would change the picture.- The document is in a language the user does not read: quotes in the original with a translation in brackets.- The user is the stronger side (the landlord, the business): the same note; the flags then say what the other side will likely push back on.