| name | packet-builder |
| title | packet-builder |
| description | Interactive complaint-packet assembly driven by packet-manifest.yaml — walks through authority, exhibit list, reference appendices, and runs scripts/packet/build.py. Triggers when the user says "build the packet" or when a complaint narrative and exhibit set are ready to compile. |
| author | EvanOchsner |
| author_url | https://github.com/EvanOchsner/personal-advocacy-toolkit/tree/main/.claude/skills/packet-builder |
| license | Apache-2.0 |
| version | 0.1.0 |
| execution_mode | open |
| jurisdiction | general |
| practice | litigation |
| language | en |
packet-builder
The builder is manifest-driven: everything authority-, case-, or
jurisdiction-specific lives in packet-manifest.yaml. This skill
shepherds that manifest to completeness and then runs the builder.
See templates/packet-manifests/schema.yaml for the authoritative
schema, and examples/maryland-mustang/complaint_packet/packet-manifest.yaml
for a filled-in synthetic reference.
When this skill fires
- User says "build the packet" or "compile the complaint."
- Complaint draft exists under
drafts/ and exhibit evidence is
in place under evidence/.
- After the
authorities-finder run has identified the forum.
Procedure
-
Locate or scaffold the manifest.
- If
packet-manifest.yaml exists in the packet directory, load
it and list which sections are filled.
- If not, copy
templates/packet-manifests/example-generic-dispute.yaml
into place and walk through the sections below.
-
Fill the manifest header with the user.
packet.name — a slug like maryland-mustang-mia.authority — name, short code, mailing address, intake URL.
Pulled from authorities-finder output; do not retype by
hand if the skill already found it.complainant — name, mailing address, email. For a public
derivative, use the scrubbed synthetic values.respondent — name, role, reference number (claim number,
case number, policy number).
-
Complaint narrative. complaint.source points at the
markdown or docx draft under drafts/. complaint.title shows
up in the cover page. Write lawyer-mode per tone-modes skill;
this is outbound.
-
Exhibit list. Each exhibit is {label, title, description, source(s), date?}. Labels are typically A, B, C, ... in the
order they'll be referenced in the complaint. Sources are paths
under evidence/ or drafts/. Multiple sources per exhibit are
fine — the builder concatenates in order.
-
Reference appendices. Optional. For policy / regulatory
compilations that aren't exhibits per se but that the
complainant wants attached for the reader's reference. Each has
.
