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
class-notice-planDrafts a Rule 23 class notice communication plan for U.S. federal class actions, covering notice content, delivery methods, timelines, budgets, and reporting to satisfy the "best notice practicable" standard. Use after class certification or when seeking settlement approval. Trigger when user mentions class notice, notice plan, communication plan, Rule 23(c…
Independent GitHub snapshot · Automated classification · Original documentation governs
Produces a court-ready plan for disseminating class notice under Fed. R. Civ. P. 23(c)(2)(B) and due process requirements.
Collect before drafting:
Generate each section below in order. Populate tables from user-supplied inputs. Mark unknowns with [TBD].
Table with: case name, court/case number, judge, procedural posture, certification order date, governing rules (default: Fed. R. Civ. P. 23(c)(2)(B); due process), key deadlines.
| Authority | Requirement |
|---|---|
| Fed. R. Civ. P. 23(c)(2)(B) | Best notice practicable; individual notice where feasible |
| Mullane v. Central Hanover Bank | Notice reasonably calculated to apprise interested parties |
| Eisen v. Carlisle & Jacquelin | Individual notice to identifiable class members |
| CAFA 28 U.S.C. § 1715 | Government notice for covered settlements (if applicable) |
Table with: class definition (verbatim), subclasses (verbatim), estimated class size, geographic/temporal limits, data sources, data gaps and remediation plan.
Every notice must include per Rule 23(c)(2)(B):
| Channel | When Used | Key Notes |
|---|---|---|
| Direct mail | Identifiable addresses | First-class; NCOA updates; re-mail undeliverables |
| Reliable email addresses | SPF/DKIM compliance; bounce tracking | |
| Publication | Non-identifiable members | Targeted print/digital; market-specific |
| Digital ads | Broad or niche reach | Geo/demo targeting aligned with class |
| Settlement website | All cases | Notice, claim form, FAQs, key dates |
| Toll-free line | All cases | Live + automated; multilingual if needed |
Milestones: court approval of plan → data extraction → website/hotline live → mail/email launch → publication run → opt-out deadline → objection deadline → fairness hearing/trial → due diligence declaration filed.
Default timing guidance (when not court-ordered):
Categories: claims administrator fees, data processing, printing/mail, publication, website/hosting, hotline, translation, contingency (10-20% reserve). Include basis and estimate for each.
| Metric | Source | Use |
|---|---|---|
| Mail sent/returned/re-mailed | Mail logs | Due diligence declaration |
| Email delivered/bounced | ESP reports | Effectiveness metrics |
| Publication insertions | Media affidavits | Compliance proof |
| Website traffic | Analytics | Reach assessment |
| Hotline volume | Call logs | Issue tracking |
| Opt-outs/objections | Administrator tracking | Court reporting |
List: (A) long-form notice, (B) postcard/short-form notice, (C) publication notice, (D) media plan and rate cards, (E) due diligence declaration template.
[VERIFY] to any uncertain citation or ruleKey changes from the original:
tags — not part of the Agent Skills spec (only name and description are valid frontmatter fields)- [ ] for actionable items (sections 4, 7, 10) to match workflow checklist patterns