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
procedural-rule-summaryGenerates structured, stage-organized summaries of procedural rules from federal, state, local, or administrative sources with deadlines, responsibilities, and non-compliance consequences. Extracts rules from uploaded texts, court orders, and standing orders. Use when summarizing FRCP, FRCrP, state civil/criminal procedure, local rules, administrative heari…
Independent GitHub snapshot · Automated classification · Original documentation governs
name: procedural-rule-summary language: en description: Generates structured, stage-organized summaries of procedural rules from federal, state, local, or administrative sources with deadlines, responsibilities, and non-compliance consequences. Extracts rules from uploaded texts, court orders, and standing orders. Use when summarizing FRCP, FRCrP, state civil/criminal procedure, local rules, administrative hearing procedures, or building procedural compliance checklists for case preparation and motion practice. tags:
Produces a structured, stage-organized summary of procedural rules for quick-reference compliance during litigation, administrative hearings, or regulatory proceedings.
If any prerequisite is missing, ask — do not assume jurisdiction or rule version.
[VERIFY]Use only stages relevant to the requested rules:
| Stage | Coverage |
|---|---|
| Initiation/Filing | Complaint requirements, filing fees, service of process |
| Responsive Pleadings | Answer deadlines, motions to dismiss, affirmative defenses |
| Discovery | Scope, initial disclosures, written discovery, depositions, ESI |
| Motions Practice | Filing requirements, briefing schedules, page limits, meet-and-confer |
| Pre-Trial | Conferences, exhibit/witness lists, motions in limine |
| Trial | Jury selection, presentation order, evidentiary objections |
| Post-Trial | JMOL, new trial motions, costs/fees |
| Appeal | Notice of appeal, record designation, briefing schedule, standards of review |
For each rule or procedural requirement:
### [Rule Number] — [Short Title]
**Action required:** [What must be done]
**Responsible party:** [Who must act]
**Deadline:** [Timeframe + calculation method]
**Method/Format:** [ECF, personal service, specific form, etc.]
**Mandatory vs. Discretionary:** [Whether court has discretion]
**Non-compliance consequence:** [Waiver, sanctions, dismissal, default]
**Extensions:** [Whether/how extendable + standard applied]
**Cross-references:** [Related rules, local rules, standing orders]
For every timing requirement, specify:
# Procedural Rule Summary: [Rule Set Name]
**Jurisdiction:** [Jurisdiction]
**Proceeding type:** [Type]
**Rules version:** [Date/version]
**Prepared:** [Date]
## Overview
[1-2 sentences identifying scope]
## [Stage Heading]
### [Rule X] — [Title]
[Per-rule elements from Step 3]
## Deadline Quick-Reference Table
| Action | Rule | Deadline | Calculated From | Days Type |
|--------|------|----------|-----------------|-----------|
## Common Pitfalls
- [Pitfall 1]
- [Pitfall 2]
## Cross-References
- [Related rule sets, standing orders, local rules]
Conflicting deadlines between general and local rules: Local rules typically modify general rules. Present both layers and flag the conflict explicitly.
Rule version uncertainty: If unable to confirm currency, insert [VERIFY: Confirm current version of [Rule] as of [date]] and note the version used.
Multi-layer jurisdictions: When state and local rules both modify general procedure, address each layer separately and show interplay.
[VERIFY]