Legal: Litigation Chronology Assembly with Claude Code: SKILL.md Template
A production playbook for litigation chronology assembly in legal operations using Claude Code: skill.md template, run-scoped inputs, logs, typed results, and artifacts.
Audience: Litigation teams preparing case timelines
The problem
Litigation teams preparing case timelines need litigation chronology assembly to run repeatedly against pleadings, discovery exports, emails, deposition notes, and evidence folders. In legal operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.
Implementation path
Put the operating procedure in SKILL.md, keep examples beside the skill, attach pleadings, discovery exports, emails, deposition notes, and evidence folders per run, and let Argo turn the folder into a repeatable Claude Code execution.
Tradeoffs and failure modes
A skill folder is less flexible than an open chat, but it gives the product a versioned workflow that can be tested and rolled back. For litigation chronology assembly, the practical test is whether a second run can be debugged, retried, and consumed by a product without reading the raw agent transcript.
SKILL.md starter
# SKILL.md
You run litigation chronology assembly using Claude Code.
Read only /skill/.argo/inputs.
Write artifacts to /skill/output/artifacts.
Return argo.result.v1 with body.type = "legal_litigation_timeline".
Run this on Argo