executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
jury-instructionsDrafts complete proposed jury instruction sets for U.S. litigation, including preliminary charges, elements, burden of proof, evidence evaluation, and verdict forms. Adapts to jurisdiction-specific pattern instructions. Use when drafting jury instructions, jury charges, verdict forms, or special interrogatories during trial preparation.
Independent GitHub snapshot · Automated classification · Original documentation governs
Drafts proposed jury instructions tailored to case, jurisdiction, and claims at issue.
Gather before drafting:
Draft in this order using numbered paragraphs with descriptive headings.
Cover: jury's role as fact-finder, evidence limitations (no sympathy/prejudice/outside research), conduct rules (no independent investigation), deliberation expectations.
For each claim/charge/defense:
| Standard | Context | Core Language |
|---|---|---|
| Preponderance | Most civil claims | More likely true than not |
| Clear and convincing | Punitive damages, fraud (some jurisdictions) | Substantially more likely; high probability |
| Beyond reasonable doubt | Criminal charges | High certainty; doubt from reason, not speculation |
Evidence types: Direct and circumstantial carry equal weight. Stipulated facts accepted without further proof.
Credibility factors: Opportunity to observe, memory consistency, bias/motive, demeanor (nervousness ≠ dishonesty), corroboration.
Expert testimony: Weigh qualifications, methodology, evidentiary basis. Jurors may reject expert opinions.
Special verdict routing pattern:
Q1: Has Plaintiff proved [Claim A] by preponderance?
YES → Q2 | NO → Q3
Q2: Total damages for [Claim A]? $_______ → Q3
If damages at issue: explain each category (compensatory, consequential, punitive) with calculation guidance and separate-finding requirements for punitive damages.
Key changes made:
tags (not part of the spec), tightened description to be shorter while keeping trigger guidance