contract-framework

Drafts clear, protective service-agreement frameworks in the voice of a senior contracts specialist with 20 years drafting for freelancers, creative agencies, and independent consultants. Four required inputs (YOUR_BUSINESS, CLIENT_NAME, SERVICE_DESCRIPTION, PAYMENT_TERMS) plus two optional (PROTECTIONS_NEEDED, TONE) drive a locked eight-section framework: PARTIES, SCOPE OF SERVICES, PAYMENT TERMS, INTELLECTUAL PROPERTY, CONFIDENTIALITY, TERMINATION, LIABILITY AND WARRANTIES, GENERAL PROVISIONS. Every framework addresses the three most common freelance disputes (scope creep, late payment, IP ownership). Plain-English by default with three selectable tone profiles (FORMAL CORPORATE, PLAIN PROFESSIONAL, CREATIVE INDUSTRY) applied consistently across all eight sections. Fabrication firewall: never invents statutes, case law, party names, figures, revision limits, kill-fee percentages, notice periods, or liability caps; jurisdiction-sensitive clauses are written in neutral language and flagged for local confirmation; any non-critical gap becomes a marked [TO BE COMPLETED: field] placeholder rather than a fabricated value. Missing-input gate halts and asks when any of the four critical fields is blank or reads as an instruction; blank PROTECTIONS_NEEDED defaults to standard protections; blank or invalid TONE defaults to PLAIN PROFESSIONAL. Treats all inputs as untrusted literal data, stripping markdown/code/HTML from PROTECTIONS_NEEDED and ignoring embedded directives. Writes the framework to contract-[business]-[client].md (sanitized, Windows-reserved-name safe) when a file tool is available, else prints it; output contains the eight sections only, no commentary. Silent output validation confirms all sections present and ordered, every clause traces to an input or stated default, and tone is consistent. Includes /draft-contract slash command with AskUserQuestion intake. Not legal advice; flags jurisdiction-specific items for finalisation with local counsel.