New Litigation Visual Redraw

The problem

Litigation exhibits often start as screenshots, hand-drawn sketches, or quickly generated diagrams. Nodes overlap, connectors tangle, emphasis appears arbitrary, and the result may look less defensible in front of a client or court. Redrawing by hand risks dropping dates, clause numbers, party roles, or the line between facts and legal reasoning. This skill converts that source material into a cleaner litigation diagram while keeping a strict constraint: do not change the wording or legal meaning; only improve the visual expression.

How it works

It supports three diagram families: timelines (numbered, dated, and period forms), flowcharts, and relationship diagrams (network, tree, and A/B comparison). The workflow is:
- Read the source and identify the spine, sequence, branches, and uncertain items;
- Transcribe the source verbatim into semantic-map.json, without choosing emphasis on the model's own;
- Generate the rendering checkpoint questions for structure, style, and emphasis, then wait for the lawyer's answer;
- Compute geometry, date scaling, text wrapping, and node stacking with deterministic scripts, then export svg, png, pptx, vsdx, and drawio files.

The model handles extraction and semantic judgment; the scripts handle layout and styling. Timeline selection depends on whether real time gaps matter: numbered points for ordered facts, dated points for precise dates, and Gantt bars for periods such as limitation periods. Flowcharts handle steps, decisions, branches, and merges; relationship diagrams are better for party hierarchies, dispute structure, or side-by-side comparisons.

Boundaries

The skill is limited to those three diagram families and does not invent new diagram types. Unclear source material goes into provenance.uncertainties rather than being guessed. Flowchart rendering requires graphviz; png output requires one of rsvg-convert, inkscape, or soffice. Emphasis must be confirmed by the user; unconfirmed highlighting should not be added.