Report Pdf

Use the Glob tool to find matching files. If multiple matches exist, use the most recently modified file.

If no analysis file is found:

• Tell the user: "No contract review data found in the current directory. Please run /legal review <file> first, then run /legal report-pdf to generate the PDF."
• Do NOT proceed.

1.2 Parse the Analysis Data

Read the analysis file and extract:

Phase 2: Locate or Generate the PDF Script

2.1 Look for Existing Script

Search for the PDF generation Python script in these locations (in order):

1. [working directory]/scripts/generate_pdf_report.py
2. [working directory]/scripts/generate_pdf_report.py
3. ../scripts/generate_pdf_report.py (one level up from working directory)

Use the Glob tool to search for **/generate_pdf_report.py within the project.

2.2 If Script Found

Run the script, passing it the path to the analysis markdown file:

python3 [script_path] --input [analysis_file_path] --output CONTRACT-REVIEW-REPORT.pdf

2.3 If Script Not Found — Generate Inline

If no script is found, generate the PDF directly using inline Python with ReportLab. Write and execute a Python script that produces the PDF.

First, check that ReportLab is installed:

pip3 install reportlab 2>/dev/null || pip install reportlab 2>/dev/null

Then generate and execute the following Python script. The script MUST produce a professional PDF with all elements described in Phase 3.

Phase 3: PDF Content and Layout Specification

The generated PDF MUST include all of the following sections with professional styling.

3.1 Page Setup

3.2 Cover Page

The cover page MUST include:

[Top: Thin colored bar across full width in primary color]

INFORME DE REVISIÓN CONTRACTUAL
CONTRACT REVIEW REPORT
[Large, bold, primary color, centered]

[Subtitle: Contract type or "Análisis Jurídico Integral / Comprehensive Legal Analysis"]

[Large circular score gauge graphic — see 3.3]

Puntuación de Seguridad Contractual / Contract Safety Score: [SCORE]/100
Calificación / Grade: [LETTER] — [LABEL]
[Color-coded based on score: red for F/D, amber for C, green for B/A]

Preparado para / Prepared for: [Party name or "Contract Review"]
Fecha / Date: [DD/MM/YYYY — use Spanish date format]

[Bottom of page:]
⚠️ AVISO LEGAL / LEGAL DISCLAIMER: Este análisis ha sido generado por IA y
no constituye asesoramiento jurídico. Consulte siempre a un abogado colegiado.
This analysis is AI-generated and does not constitute legal advice.
Always consult a licensed attorney.

[Thin colored bar at bottom]

3.3 Score Gauge Graphic

Draw a semi-circular gauge (speedometer style) using ReportLab drawing primitives:

• Semi-circle arc from 0 to 180 degrees
• Color gradient: red (left) to yellow (center) to green (right)
• Needle pointing to the score position
• Score number displayed large and centered below the gauge
• Grade letter displayed below the score

Implementation approach using ReportLab:

from reportlab.graphics.shapes import Drawing, Wedge, String, Line
from reportlab.graphics import renderPDF
from reportlab.lib.colors import Color
import math

# Create a drawing for the gauge
# Use Wedge shapes for the colored arc segments
# Use Line for the needle
# Use String for the score text

If the gauge is too complex to render reliably, fall back to a large color-coded score box:

+----------------------------------+
|     CONTRACT SAFETY SCORE        |
|                                  |
|           72 / 100               |
|          Grade: B                |
|           (Fair)                 |
+----------------------------------+

Color the box border and score text based on the grade.

3.4 Executive Summary Page

EXECUTIVE SUMMARY
[Section header with colored underline]

[3-4 sentence overview from the analysis]

CONTRACT DETAILS
[Table with alternating row colors:]
| Field           | Value              |
| Contract Type   | [type]             |
| Parties         | [party 1] ↔ [party 2] |
| Effective Date  | [date]             |
| Term            | [duration]         |
| Total Value     | [amount]           |
| Governing Law   | [jurisdiction]     |

3.5 Risk Dashboard Page

RISK DASHBOARD
[Section header with colored underline]

[Color-coded risk summary boxes in a row:]
+----------+  +----------+  +----------+
| 🔴 HIGH  |  | 🟡 MED   |  | 🟢 LOW   |
|    [n]   |  |    [n]   |  |    [n]   |
+----------+  +----------+  +----------+

[Risk matrix table:]
| Risk Level | Count | Clauses Affected           |
|------------|-------|----------------------------|
| High       | [n]   | [clause1], [clause2], ...  |
| Medium     | [n]   | [clause1], [clause2], ...  |
| Low        | [n]   | [clause1], [clause2], ...  |

Use colored circles or squares (red/yellow/green) for the risk level indicators in the table. ReportLab can draw these with canvas.circle() or by using colored table cell backgrounds.

3.6 Clause-by-Clause Analysis Pages

For EACH clause analyzed, create a structured entry:

[Risk level color bar on left margin]

CLAUSE: [Clause Name] — Section [X.X]
Risk Level: [🔴 HIGH / 🟡 MEDIUM / 🟢 LOW]

What it says:
[plain English summary]

Why it matters:
[risk explanation]

What you could lose:
[quantified impact]

Recommended change:
[specific alternative language]

[Separator line]

Group clauses by risk level: all High Risk first, then Medium, then Low.

3.7 Missing Protections Checklist

MISSING PROTECTIONS
[Section header]

[Checklist table:]
| # | Protection              | Status |
|---|-------------------------|--------|
| 1 | [protection name]       | ❌ Missing |
| 2 | [protection name]       | ✅ Present |
| 3 | [protection name]       | ❌ Missing |
...

Use red background for missing items, green for present items.

3.8 Obligations Timeline

OBLIGATIONS & DEADLINES
[Section header]

[Table:]
| Obligation | Responsible Party | Deadline | Consequence |
|------------|-------------------|----------|-------------|
| [obligation] | [who]          | [when]   | [what happens] |

3.9 Compliance Flags

COMPLIANCE FLAGS
[Section header]

[List of any regulatory or jurisdictional concerns identified]

3.10 Negotiation Priorities

NEGOTIATION PRIORITIES
[Section header]

1. [HIGHEST PRIORITY]
   Current: [what the clause says now]
   Proposed: [specific language to propose]
   Why: [one-sentence justification]

2. [SECOND PRIORITY]
   ...

3. [THIRD PRIORITY]
   ...

Number and rank all priorities. Use bold for the priority title.

3.11 Recommended Next Steps

RECOMMENDED NEXT STEPS
[Section header]

☐ [First action]
☐ [Second action]
☐ [Third action]
☐ Consult a licensed attorney before signing

3.12 Legal Disclaimer (Final Page)

AVISO LEGAL / LEGAL DISCLAIMER

⚠️ Este documento ha sido generado por una herramienta de análisis jurídico
basada en IA. NO constituye asesoramiento jurídico y no debe utilizarse como
tal. El análisis se basa en interpretación automatizada de texto y puede no
capturar todos los matices del contrato ni del derecho aplicable.

This document was generated by an AI-powered legal analysis tool.
It does NOT constitute legal advice. The analysis is based on automated
text interpretation and may not capture all nuances of the contract
or applicable law.

CONSULTE SIEMPRE a un abogado colegiado antes de:
ALWAYS consult a licensed attorney before:
• Firmar cualquier contrato / Signing any contract
• Tomar decisiones jurídicas basadas en este análisis /
  Making legal decisions based on this analysis
• Negociar términos contractuales / Negotiating contract terms
• Cualquier actuación con consecuencias legales /
  Taking any action that could have legal consequences

Este informe se facilita únicamente a efectos informativos.
This report is provided for informational purposes only.

Generado / Generated: [DD/MM/YYYY HH:MM]
Herramienta / Tool: AI Legal Assistant — España — Claude Code

3.13 Page Footer (All Pages Except Cover)

Every page after the cover should have:

[Left: "AI Legal Assistant España — Informe de Revisión Contractual"]
[Center: "CONFIDENCIAL / CONFIDENTIAL"]
[Right: "Página X de Y / Page X of Y"]

Use a thin line above the footer to separate it from content.

Date format throughout the PDF: Use DD/MM/YYYY (Spanish standard). Example: 10/04/2026 not April 10, 2026.

Phase 4: Generate the PDF

4.1 Write the Python Script

Write a complete Python script that:

1. Reads the analysis markdown file
2. Parses the sections using string matching / regex
3. Builds the PDF page by page using ReportLab
4. Includes all sections from Phase 3
5. Uses professional styling throughout
6. Handles missing sections gracefully (skip if data not found)

4.2 Execute the Script

Run the script using Bash:

cd [working directory] && python3 /tmp/generate_legal_pdf.py --input "[analysis_file]" --output "CONTRACT-REVIEW-REPORT.pdf"

4.3 Verify Output

After execution:

1. Check that the PDF was created successfully
2. Verify the file size is reasonable (should be >10KB for a real report)
3. Report any errors to the user

Phase 5: Present to User

After generating the PDF:

1. Confirm the PDF was generated: "PDF report generated: CONTRACT-REVIEW-REPORT.pdf"
2. State the file location (absolute path)
3. Summarize what's in the report (sections included, page count if known)
4. Note: "Open the PDF to review the full formatted report with the score gauge, risk dashboard, and clause-by-clause analysis."
5. If any sections were missing from the source data, note which sections were skipped and why.

Error Handling