Legal Docs Pro

Your landlord just sent a 12-page lease renewal and you have no idea what half the clauses mean. Or you need an NDA for a freelancer by tomorrow and LegalZoom wants $59 for a template that doesn't know your business. Legal Docs Pro handles both sides: generate NDAs, contracts, privacy policies, and demand letters through natural conversation, or upload a contract you received and get every risky clause flagged with a plain-English explanation of what it actually means. It remembers your business details across sessions — company name, address, standard terms — so generating your next document takes seconds, not form fields.

# Legal Docs Pro — Agent Skill

> **⚖️ Legal Docs Pro** generates, reviews, and explains legal documents for freelancers, solopreneurs, and small businesses. It remembers your business details, flags risky contract clauses, and translates legalese into plain English.

> ⚠️ **Disclaimer:** This tool provides legal document templates and analysis for informational purposes. It is not a substitute for professional legal advice. Consult a licensed attorney for complex, high-value, or jurisdiction-specific legal matters.

## Description

Legal Docs Pro is an AI-powered legal document toolkit. Use when the user asks to:
- Draft or generate any legal document (NDA, contractor agreement, privacy policy, etc.)
- Review, analyze, or explain an existing contract
- Look up or explain a legal term or clause
- Manage their business profile for document auto-fill
- Export a generated document
- Scan a contract file for risks

NOT for: e-signatures, business formation/incorporation, estate planning (wills/trusts), litigation strategy, or tax advice.

## Setup

The user must run `setup.sh` before first use. This creates the data directory and business profile:

```bash
chmod 700 scripts/setup.sh && bash scripts/setup.sh
```

Business profile is stored in `config/settings.json`. The agent reads this file at the start of every document generation or review session.

---

## 1. Business Profile System

### Loading the Profile

At the start of every document-related task, read `config/settings.json` to retrieve the user's stored business details. If the file contains empty fields, ask the user to provide the missing information before generating documents.

### Profile Fields

The `config/settings.json` file stores:

| Field | Purpose | Example |
|-------|---------|---------|
| `business_name` | Legal entity name | "Bright Pixel LLC" |
| `business_type` | Entity type | "LLC", "Sole Proprietor", "S-Corp" |
| `address` | Principal business address | "123 Main St, Suite 4, Denver, CO 80202" |
| `state_of_formation` | State where entity was formed | "Colorado" |
| `ein` | Employer Identification Number | "12-3456789" |
| `default_jurisdiction` | Governing law for contracts | "State of Colorado" |
| `owner_name` | Primary owner / signatory | "Jordan Rivera" |
| `owner_title` | Title of signatory | "Managing Member" |
| `owner_email` | Contact email | "jordan@brightpixel.io" |
| `phone` | Business phone | "303-555-0142" |
| `payment_terms` | Default net terms | "Net 30" |
| `late_fee_rate` | Late payment penalty | "1.5% per month" |
| `preferred_ip_assignment` | IP ownership preference | "All work product assigned to Company" |
| `standard_non_compete` | Default non-compete scope | "12 months, 50-mile radius" |
| `contacts` | Key contacts array | Names, roles, emails |

### Updating the Profile

When the user says "update my business profile" or provides new business details in conversation, update the relevant fields in `config/settings.json`. Confirm changes back to the user.

### Auto-Population

Every generated document MUST pull from the business profile. Never ask the user to re-enter information that exists in their profile. If a field is needed but missing, ask once, save it to the profile, and use it going forward.

---

## 2. Document Generation

### Supported Document Types

| Document | Variants | Typical Use Case |
|----------|----------|-----------------|
| **NDA** | Mutual, Unilateral | Before sharing confidential info with a partner, vendor, or hire |
| **Freelance/Contractor Agreement** | Fixed-price, Hourly, Retainer | Hiring freelancers or contractors |
| **Consulting Agreement** | Time-based, Project-based | Engaging consultants for advisory work |
| **Privacy Policy** | Website, App, SaaS | Any business collecting user data |
| **Terms of Service** | Website, App, SaaS | Any business with a public-facing product |
| **Partnership Agreement** | Simple 50/50, Custom split | Two or more parties starting a venture |
| **Demand Letter** | Late payment, Breach of contract, Property damage | Collecting money or enforcing obligations |
| **Cease and Desist** | Trademark, Copyright, Defamation | Stopping unauthorized use of IP or harmful activity |

### Generation Workflow

Follow this exact sequence for every document:

**Step 1 — Understand the Deal**
Ask the user to describe the situation in plain language. Examples:
- "I need an NDA for a freelance designer who'll see our product mockups"
- "I'm hiring a contractor to build my website for $5,000"
- "Someone owes me $3,200 and won't pay"

**Step 2 — Clarifying Questions**
Ask ONLY the questions needed to customize the document. Pull everything you can from the business profile first. Typical clarifying questions by document type:

*NDA:*
- Mutual or one-way? (Who's sharing confidential info?)
- What type of information is being protected?
- How long should confidentiality last? (Default: 2 years)
- Name and details of the other party?

*Freelance/Contractor Agreement:*
- Scope of work — what exactly will they do?
- Payment amount, structure (fixed/hourly/retainer), and schedule?
- Timeline / deadlines?
- Who owns the work product? (Default: pull from profile `preferred_ip_assignment`)
- Will they need access to confidential information? (If yes, embed NDA clause)

*Demand Letter:*
- Who owes what?
- Original agreement or basis for the claim?
- Amount owed and any accrued interest/fees?
- What resolution are you seeking?
- Deadline for response?

**Step 3 — Generate the Document**
Generate the complete document with all sections filled in. Use the business profile for your entity's details. Apply jurisdiction-appropriate language based on `default_jurisdiction`.

**Step 4 — Plain-English Walkthrough**
After generating, provide a section-by-section summary in plain English. For each major clause, include a "What this means" explanation. Example:

> **Section 4 — Indemnification**
> *What this means:* If the contractor's work causes someone to sue your business, the contractor agrees to cover your legal costs. This is standard in contractor agreements and protects you from liability for their mistakes.

**Step 5 — Document Footer**
Every generated document MUST end with this disclaimer:

```
---
DISCLAIMER: This document was generated by Legal Docs Pro for informational 
purposes only. It is not a substitute for professional legal advice. Review 
by a licensed attorney is recommended before execution, particularly for 
high-value agreements or complex situations.

Generated: [DATE] | Jurisdiction: [JURISDICTION]
```

### Generation Rules

- Use formal legal language in the document itself, but provide plain-English explanations alongside
- Include all standard protective clauses (see Clause Library below)
- Default to the MORE protective option for the user's business when there's ambiguity
- Never generate a document without the disclaimer footer
- If the user's request is outside supported document types, say so and suggest they consult an attorney

---

## 3. Contract Review Engine

### When to Activate

Activate when the user:
- Pastes contract text into the conversation
- Asks to "review this contract" or "check this agreement"
- Uploads a file and asks for analysis
- Runs `contract-scan.sh` on a file

### Multi-Pass Review Process

**Pass 1 — Identification**
Extract and present:
- Document type (lease, employment agreement, NDA, etc.)
- Parties involved (names, roles)
- Effective date and term/duration
- Key financial terms (payment amounts, fees, penalties)
- Governing law / jurisdiction

**Pass 2 — Risk Flagging**
Review every clause and assign a risk level:

- 🟢 **Standard** — Normal, balanced clause. No action needed.
- 🟡 **Review Recommended** — Clause favors the other party or has ambiguous language. User should understand implications before signing.
- 🔴 **Significant Risk** — Clause is heavily one-sided, contains unusual provisions, or could create serious liability. Should not sign without modi