Element-Based Complaint Drafter

Problem

Drafting court complaints from scattered dispute materials is often less about missing structure than about damaging the official template: tables get rearranged, fonts get replaced, and missing fields get deleted. This skill turns user materials into a .docx draft focused on the 67 element-based case types defined by the Supreme People's Court. It fills official templates for 54 case types, generates element-based applications for 13 state compensation or enforcement types, and falls back to a general complaint when no official element template is hit.

Workflow

• Case-type first: reads references/67类要素式案由清单.md, infers the legal relationship from contracts, chat logs, or complaint images, and matches the closest case type. If uncertain, it asks the user instead of guessing.
• Template fill, not rewrite: for the 54 complaint templates, it uses prebuilt marked references/marked/*.docx files and references/marked/*.fields.json, extracts field values into values.json, and runs generate_complaint_docx.py --fill to replace ⟦F{n}⟧ placeholders.
• Faithful formatting: official tables, column widths, fonts, labels, and prompt text are preserved; checkboxes are marked with √ / □; unknown fields are left blank and flagged for follow-up.
• Image-to-Word: it can process photos, scans, or screenshots, normalize the image, read text with Read, extract parties, claims, and facts, then rebuild the document as .docx.

Boundaries

The output is a document draft, not legal advice; it does not determine liability or whether a damages amount is reasonable. For major or complex cases, consult a licensed attorney, and follow the receiving court's current filing requirements.