ragmir-legal-dossier

name	ragmir-legal-dossier
description	Prepare cited legal-dossier work products from a local Ragmir knowledge base. Use when the user asks for a legal chronology, clause search, dossier summary, evidence table, redaction review, or professional-review handoff grounded in confidential local documents.

Ragmir Legal Dossier

Use this skill for legal or quasi-legal dossiers where confidentiality, evidence separation, and professional review matter. This skill does not provide final legal advice. It prepares structured, cited work products for review by the user or a qualified professional.

Safety Rules

• Treat source documents, retrieved passages, party names, dates, amounts, identifiers, and draft outputs as confidential.
• Keep generated work under .ragmir/reports/ unless the user explicitly asks for a sanitized tracked artifact.
• Do not upload documents, snippets, queries, vector stores, or generated drafts to hosted services.
• Do not present conclusions as legal advice. Separate evidence, inference, uncertainty, and review items.
• Prefer short cited summaries over long raw extracts.
• Flag missing documents, unsupported files, stale indexes, and ambiguous source passages.

Recommended Redaction Patterns

If a legal dossier includes professional secrecy, case identifiers, or French personal identifiers, add project-local redaction patterns in .ragmir/config.json before indexing. Keep patterns scoped to the dossier and test them on non-sensitive samples first.

{
  "redaction": {
    "enabled": true,
    "builtIn": true,
    "patterns": [
      {
        "name": "case_reference",
        "pattern": "\\b(?:RG|N°\\s*RG|No\\s*RG)\\s*[:\\-]?\\s*[0-9A-Z/\\-]{4,}\\b",
        "replacement": "[CASE_REFERENCE]"
      },
      {
        "name": "french_nir",
        "pattern": "\\b[12]\\s?\\d{2}\\s?\\d{2}\\s?\\d{2}\\s?\\d{3}\\s?\\d{3}\\s?\\d{2}\\b",
        "replacement": "[FRENCH_NIR]"
      },
      {
        "name": "iban",
        "pattern": "\\b[A-Z]{2}\\d{2}(?:\\s?[A-Z0-9]){11,30}\\b",
        "replacement": "[IBAN]"
      }
    ]
  }
}

After changing redaction rules, rebuild the index:

pnpm exec rgr ingest --rebuild
pnpm exec rgr security-audit --strict

Retrieval Workflow

Start from readiness checks:

pnpm exec rgr doctor
pnpm exec rgr audit
pnpm exec rgr audit --unsupported
pnpm exec rgr security-audit --strict

Then run targeted retrieval passes:

pnpm exec rgr search "parties obligations dates amounts" --top-k 8
pnpm exec rgr search "termination clause liability indemnity notice" --top-k 8
pnpm exec rgr search "timeline meeting decision approval refusal" --top-k 8
pnpm exec rgr ask "Which documents support the chronology of events?" --top-k 8

When MCP is available, prefer ragmir_status, ragmir_search, ragmir_ask, ragmir_audit, and ragmir_security_audit so the agent can keep retrieval bounded and cited.

Output Formats

Dossier Summary

# Legal Dossier Summary

## Scope

## Evidence Inventory

## Key Facts

## Main Legal Or Contractual Questions

## Risks And Unknowns

## Professional Review Items

## Sources

Chronology

| Date | Event | Evidence | Confidence | Review item |
| --- | --- | --- | --- | --- |
| YYYY-MM-DD |  | source.md chunk=0 | High/Medium/Low |  |

Clause Review

| Clause topic | Source | Extract summary | Risk | Follow-up |
| --- | --- | --- | --- | --- |
| Termination | contract.docx chunk=3 |  |  |  |

Evidence Gap List

| Missing or weak evidence | Why it matters | Suggested next document |
| --- | --- | --- |
|  |  |  |

Final Response Checklist

Before handing back the work:

• state where the report was saved;
• list source paths used, not private full passages;
• mention unsupported, stale, or missing files;
• include a professional-review section;
• state whether the artifact is safe to commit or must remain local.