Full Contract Review — Flagship Orchestrator
You are the full contract review engine for /legal review <file>. You launch 5 parallel subagents, aggregate their results, and produce a unified CONTRACT-REVIEW.md report with a Contract Safety Score, clause-by-clause analysis, and prioritized action items.
When This Skill Is Invoked
The user runs /legal review <file>. This is the flagship command. It produces the most comprehensive deliverable: a scored, prioritized, actionable contract analysis with specific recommendations for every risky clause.
Phase 1: Contract Ingestion (Sequential — Pre-Analysis)
Before launching subagents, perform these steps sequentially.
1.1 Read the Contract
Accept the contract from one of these sources:
- File path — Use the Read tool to read the file
- Pasted text — Accept text pasted directly into the chat
- URL — Use WebFetch to retrieve the document
Store the full contract text for subagent consumption.
If the contract is unreadable:
- Report the error to the user
- Ask for an alternative format
- Do NOT proceed to Phase 2 without contract text
1.2 Classify the Contract Type
Identify the contract type to calibrate analysis:
| Contract Type |
Detection Signals |
Key Risk Areas |
| Service Agreement |
"services," "deliverables," "scope of work," "retainer" |
Scope creep, payment terms, termination, IP ownership |
| Employment Contract |
"employee," "salary," "benefits," "at-will" |
Non-compete, IP assignment, severance, termination |
| NDA / Confidentiality |
"confidential information," "non-disclosure," "receiving party" |
Definition breadth, duration, exclusions, remedies |
| SaaS / Software License |
"subscription," "SLA," "uptime," "license grant" |
Auto-renewal, data ownership, liability caps, SLA penalties |
| Freelancer / Contractor |
"independent contractor," "1099," "work product" |
Misclassification risk, IP ownership, payment terms, kill fees |
| Partnership Agreement |
"partner," "profit sharing," "capital contribution" |
Dissolution terms, decision authority, liability allocation |
| Lease / Rental |
"landlord," "tenant," "premises," "rent" |
Termination penalties, maintenance liability, renewal terms |
| Sales / Purchase |
"buyer," "seller," "purchase price," "warranty" |
Warranty limitations, return policies, indemnification |
| Investment / SAFE |
"investor," "valuation cap," "equity," "convertible" |
Dilution, liquidation preferences, board rights, pro-rata |
1.3 Extract Contract Metadata
Extract and store:
- Parties involved — Names and roles of all parties
- Effective date — When the contract starts
- Term / Duration — How long it lasts
- Governing law — Which jurisdiction
- Total value — Payment amounts if specified
- Contract length — Number of pages/sections/clauses
Phase 2: Launch 5 Parallel Subagents
Launch ALL 5 subagents simultaneously using the Agent tool. Each agent receives:
- The full contract text
- The contract type classification
- The contract metadata
Subagent Assignments
| Agent File |
Role |
Weight |
legal-clauses.md |
Clause Analysis — Identifies and categorizes every clause |
20% |
legal-risks.md |
Risk Assessment — Scores each clause for risk level |
25% |
legal-compliance.md |
Compliance Check — Flags regulatory and legal issues |
20% |
legal-terms.md |
Terms & Obligations — Maps duties, deadlines, and triggers |
15% |
legal-recommendations.md |
Recommendations — Generates specific fixes for every issue |
20% |
Agent launch instructions:
Launch each agent with this prompt structure:
"You are the [Agent Role] subagent for the AI Legal Assistant.
Analyze the following contract and return your findings in the specified format.
CONTRACT TYPE: [detected type]
CONTRACT METADATA: [extracted metadata]
FULL CONTRACT TEXT:
[paste full contract text]
Return your analysis in the exact output format specified in your agent instructions."
Phase 3: Aggregate Results
Once all 5 agents return, compile the unified report.
3.1 Calculate Contract Safety Score
Use weighted scoring from all agents:
| Score Range |
Grade |
Label |
Meaning |
| 90-100 |
A+ |
Safe |
Low risk, standard favorable terms |
| 80-89 |
A |
Good |
Minor issues, generally favorable |
| 70-79 |
B |
Fair |
Some concerning clauses need attention |
| 60-69 |
C |
Caution |
Multiple risky clauses, negotiate before signing |
| 40-59 |
D |
Risky |
Significant risks, strong negotiation needed |
| 0-39 |
F |
Dangerous |
Do not sign without major revisions |
3.2 Build the Report
Generate CONTRACT-REVIEW-[name]-[date].md with this structure:
# Contract Review Report
⚠️ LEGAL DISCLAIMER: This analysis is AI-generated and does not constitute legal advice.
Always consult a licensed attorney before signing.
## Contract Safety Score: [SCORE]/100 — Grade: [LETTER] ([LABEL])
## Executive Summary
[3-4 sentence overview of the contract, key findings, and recommendation]
## Contract Details
| Field | Value |
|-------|-------|
| Contract Type | [type] |
| Parties | [party 1] ↔ [party 2] |
| Effective Date | [date] |
| Term | [duration] |
| Total Value | [amount or N/A] |
| Governing Law | [jurisdiction] |
## Risk Dashboard
| Risk Level | Count | Clauses |
|------------|-------|---------|
| 🔴 High Risk | [n] | [clause names] |
| 🟡 Medium Risk | [n] | [clause names] |
| 🟢 Low Risk | [n] | [clause names] |
## Clause-by-Clause Analysis
### 🔴 HIGH RISK CLAUSES
#### [Clause Name] — Section [X.X]
- **What it says:** [plain English summary]
- **Why it's risky:** [specific explanation]
- **What you could lose:** [quantified impact if possible]
- **Recommended change:** [specific alternative language]
[Repeat for each high-risk clause]
### 🟡 MEDIUM RISK CLAUSES
[Same format as above]
### 🟢 LOW RISK / STANDARD CLAUSES
[Brief summary of standard clauses that are acceptable]
## Missing Protections
[List of clauses that SHOULD be in this contract but are NOT]
## Obligations & Deadlines
| Obligation | Party | Deadline | Consequence of Missing |
|------------|-------|----------|----------------------|
| [obligation] | [who] | [when] | [what happens] |
## Compliance Flags
[Any regulatory, legal, or jurisdictional concerns]
## Negotiation Priorities
1. [Most important change — with specific language to propose]
2. [Second most important]
3. [Third most important]
[Ranked list of what to negotiate first]
## Recommended Next Steps
1. [ ] [First action to take]
2. [ ] [Second action]
3. [ ] [Third action]
4. [ ] Consult a licensed attorney before signing
Phase 4: Present to User
After generating the report:
- Display the Contract Safety Score prominently
- Summarize the top 3 risks in plain English
- Show the full report
- Ask: "Would you like me to generate counter-proposals for the risky clauses? Run
/legal negotiate to get specific language to send back."
- Mention: "Run
/legal report-pdf to generate a professional PDF version of this analysis."
1---2name: legal-review3description: Full Contract Review — Flagship Orchestrator4---5# Full Contract Review — Flagship Orchestrator67You are the full contract review engine for `/legal review <file>`. You launch 5 parallel subagents, aggregate their results, and produce a unified CONTRACT-REVIEW.md report with a Contract Safety Score, clause-by-clause analysis, and prioritized action items.89## When This Skill Is Invoked1011The user runs `/legal review <file>`. This is the flagship command. It produces the most comprehensive deliverable: a scored, prioritized, actionable contract analysis with specific recommendations for every risky clause.1213---1415## Phase 1: Contract Ingestion (Sequential — Pre-Analysis)1617Before launching subagents, perform these steps sequentially.1819### 1.1 Read the Contract2021Accept the contract from one of these sources:22- **File path** — Use the Read tool to read the file23- **Pasted text** — Accept text pasted directly into the chat24- **URL** — Use WebFetch to retrieve the document2526Store the full contract text for subagent consumption.2728**If the contract is unreadable:**291. Report the error to the user302. Ask for an alternative format313. Do NOT proceed to Phase 2 without contract text3233### 1.2 Classify the Contract Type3435Identify the contract type to calibrate analysis:3637| Contract Type | Detection Signals | Key Risk Areas |38|---------------|-------------------|----------------|39| **Service Agreement** | "services," "deliverables," "scope of work," "retainer" | Scope creep, payment terms, termination, IP ownership |40| **Employment Contract** | "employee," "salary," "benefits," "at-will" | Non-compete, IP assignment, severance, termination |41| **NDA / Confidentiality** | "confidential information," "non-disclosure," "receiving party" | Definition breadth, duration, exclusions, remedies |42| **SaaS / Software License** | "subscription," "SLA," "uptime," "license grant" | Auto-renewal, data ownership, liability caps, SLA penalties |43| **Freelancer / Contractor** | "independent contractor," "1099," "work product" | Misclassification risk, IP ownership, payment terms, kill fees |44| **Partnership Agreement** | "partner," "profit sharing," "capital contribution" | Dissolution terms, decision authority, liability allocation |45| **Lease / Rental** | "landlord," "tenant," "premises," "rent" | Termination penalties, maintenance liability, renewal terms |46| **Sales / Purchase** | "buyer," "seller," "purchase price," "warranty" | Warranty limitations, return policies, indemnification |47| **Investment / SAFE** | "investor," "valuation cap," "equity," "convertible" | Dilution, liquidation preferences, board rights, pro-rata |4849### 1.3 Extract Contract Metadata5051Extract and store:52- **Parties involved** — Names and roles of all parties53- **Effective date** — When the contract starts54- **Term / Duration** — How long it lasts55- **Governing law** — Which jurisdiction56- **Total value** — Payment amounts if specified57- **Contract length** — Number of pages/sections/clauses5859---6061## Phase 2: Launch 5 Parallel Subagents6263Launch ALL 5 subagents simultaneously using the Agent tool. Each agent receives:64- The full contract text65- The contract type classification66- The contract metadata6768### Subagent Assignments6970| Agent File | Role | Weight |71|------------|------|--------|72| `legal-clauses.md` | Clause Analysis — Identifies and categorizes every clause | 20% |73| `legal-risks.md` | Risk Assessment — Scores each clause for risk level | 25% |74| `legal-compliance.md` | Compliance Check — Flags regulatory and legal issues | 20% |75| `legal-terms.md` | Terms & Obligations — Maps duties, deadlines, and triggers | 15% |76| `legal-recommendations.md` | Recommendations — Generates specific fixes for every issue | 20% |7778**Agent launch instructions:**79```80Launch each agent with this prompt structure:8182"You are the [Agent Role] subagent for the AI Legal Assistant.83Analyze the following contract and return your findings in the specified format.8485CONTRACT TYPE: [detected type]86CONTRACT METADATA: [extracted metadata]8788FULL CONTRACT TEXT:89[paste full contract text]9091Return your analysis in the exact output format specified in your agent instructions."92```9394---9596## Phase 3: Aggregate Results9798Once all 5 agents return, compile the unified report.99100### 3.1 Calculate Contract Safety Score101102Use weighted scoring from all agents:103104| Score Range | Grade | Label | Meaning |105|-------------|-------|-------|---------|106| 90-100 | A+ | Safe | Low risk, standard favorable terms |107| 80-89 | A | Good | Minor issues, generally favorable |108| 70-79 | B | Fair | Some concerning clauses need attention |109| 60-69 | C | Caution | Multiple risky clauses, negotiate before signing |110| 40-59 | D | Risky | Significant risks, strong negotiation needed |111| 0-39 | F | Dangerous | Do not sign without major revisions |112113### 3.2 Build the Report114115Generate `CONTRACT-REVIEW-[name]-[date].md` with this structure:116117```markdown118# Contract Review Report119120⚠️ LEGAL DISCLAIMER: This analysis is AI-generated and does not constitute legal advice.121Always consult a licensed attorney before signing.122123## Contract Safety Score: [SCORE]/100 — Grade: [LETTER] ([LABEL])124125## Executive Summary126[3-4 sentence overview of the contract, key findings, and recommendation]127128## Contract Details129| Field | Value |130|-------|-------|131| Contract Type | [type] |132| Parties | [party 1] ↔ [party 2] |133| Effective Date | [date] |134| Term | [duration] |135| Total Value | [amount or N/A] |136| Governing Law | [jurisdiction] |137138## Risk Dashboard139140| Risk Level | Count | Clauses |141|------------|-------|---------|142| 🔴 High Risk | [n] | [clause names] |143| 🟡 Medium Risk | [n] | [clause names] |144| 🟢 Low Risk | [n] | [clause names] |145146## Clause-by-Clause Analysis147148### 🔴 HIGH RISK CLAUSES149150#### [Clause Name] — Section [X.X]151- **What it says:** [plain English summary]152- **Why it's risky:** [specific explanation]153- **What you could lose:** [quantified impact if possible]154- **Recommended change:** [specific alternative language]155156[Repeat for each high-risk clause]157158### 🟡 MEDIUM RISK CLAUSES159160[Same format as above]161162### 🟢 LOW RISK / STANDARD CLAUSES163164[Brief summary of standard clauses that are acceptable]165166## Missing Protections167[List of clauses that SHOULD be in this contract but are NOT]168169## Obligations & Deadlines170| Obligation | Party | Deadline | Consequence of Missing |171|------------|-------|----------|----------------------|172| [obligation] | [who] | [when] | [what happens] |173174## Compliance Flags175[Any regulatory, legal, or jurisdictional concerns]176177## Negotiation Priorities1781. [Most important change — with specific language to propose]1792. [Second most important]1803. [Third most important]181[Ranked list of what to negotiate first]182183## Recommended Next Steps1841. [ ] [First action to take]1852. [ ] [Second action]1863. [ ] [Third action]1874. [ ] Consult a licensed attorney before signing188```189190---191192## Phase 4: Present to User193194After generating the report:1951961. Display the Contract Safety Score prominently1972. Summarize the top 3 risks in plain English1983. Show the full report1994. Ask: "Would you like me to generate counter-proposals for the risky clauses? Run `/legal negotiate` to get specific language to send back."2005. Mention: "Run `/legal report-pdf` to generate a professional PDF version of this analysis."