Client Advisory Summary
Produces distribution-ready U.S. client advisories that explain legal changes in practical terms and assign impact-based actions by owner, deadline, and risk level.
Quick Start
- Confirm jurisdiction (US federal/state/agency) and client industry.
- Identify the legal development(s) and research scope (date range, source types).
- Choose audience and format (client memo, board brief, partner update).
- Run the workflow below; output the draft using the template in step 5.
Workflow
1. Intake Validation
Verify before drafting:
2. Development Synthesis
For each legal development, capture:
| Development |
Source Type |
Why Material |
Status |
Practical Effect |
| (description) |
Fed reg / case / statute / agency guidance |
(impact rationale) |
Final / Proposed / Enjoined / Appealed |
(compliance duty or strategic change) |
3. Impact Analysis
| Topic |
Immediate |
Short-Term |
Long-Term |
Category |
| (area) |
(effect) |
(effect) |
(effect) |
Compliance / Opportunity / Risk |
4. Action Plan
| Action |
Owner |
Deadline |
Dependency |
Evidence Needed |
| (task) |
(role) |
(date) |
(blocker) |
(supporting docs) |
5. Draft Template
Use this section order exactly:
Date:
Client:
Matter/Engagement:
Prepared by:
Executive Summary (2–3 short paragraphs)
Key Developments (table + plain-language explanation)
Impact Analysis
- Immediate | Short-term | Long-term
- Compliance obligations
- Operational/strategic effects
- Competitive or reputational implications
Action Plan
- Priority actions with owner and due date
- Recommended follow-up review points
Assumptions / Information Gaps
Authorities (Bluebook style, verified primary sources)
Conclusion + optional next-step call
Pitfalls and Checks
- Every legal claim needs a citation. Tag unverified or non-primary sources with
[VERIFY].
- Never imply legal advice beyond provided facts. Mark assumptions and data gaps explicitly.
- Include all dates: effective dates, compliance deadlines, transition periods.
- US-only scope. Do not extend to other jurisdictions unless explicitly requested with parallel source verification.
- Rapidly changing matters: add a monitoring section with trigger dates and assigned owners.
- Style: plain language in body, legal precision in citations. Use headings, short bullets, and tables. Avoid narrative blocks longer than 3 paragraphs.
Key changes from the original:
- Removed
tags from frontmatter — not part of the Agent Skills spec (only name and description are supported).
- Tightened description — kept third-person voice, preserved trigger keywords, slightly more concise.
- Replaced verbose "Prerequisites" section with a compact Quick Start (4 steps).
- Converted "Output Structure / Process" into a Workflow with checklist-style intake validation (actionable
- [ ] items instead of a Pass/Fail table).
- Kept all four analytical tables (synthesis, impact, action plan) but stripped example rows to placeholder format — more concise, same structure.
- Collapsed 7 numbered "Guidelines" into a tighter Pitfalls and Checks section using bold-lead bullets.
- Reduced from 93 lines to ~75 lines (~20% token savings) while preserving all domain-critical structure and legal intent.
1---2name: advisory-summary3description: Drafts U.S. regulatory client advisory summaries translating legal developments into actionable risk and compliance guidance. Use when a client needs a proactive memo, client alert, or legal-update brief for a new law, case, rulemaking, agency guidance, or pending reform. Trigger on requests for "client advisory," "regulatory update," "legal alert," "compliance briefing," "new law summary," or "quarterly advisory."4license: Apache-2.05---67# Client Advisory Summary89Produces distribution-ready U.S. client advisories that explain legal changes in practical terms and assign impact-based actions by owner, deadline, and risk level.1011## Quick Start12131. Confirm jurisdiction (US federal/state/agency) and client industry.142. Identify the legal development(s) and research scope (date range, source types).153. Choose audience and format (client memo, board brief, partner update).164. Run the workflow below; output the draft using the template in step 5.1718## Workflow1920### 1. Intake Validation2122Verify before drafting:2324- [ ] Jurisdiction confirmed (US federal, state, or agency)25- [ ] Topic scope and affected business functions defined26- [ ] Primary sources located (statute text, regulations, opinions, dockets)27- [ ] Effective dates, filing deadlines, and implementation dates captured28- [ ] Unverified commentary excluded or tagged `[VERIFY]`29- [ ] Confidentiality or non-public info restrictions flagged3031### 2. Development Synthesis3233For each legal development, capture:3435| Development | Source Type | Why Material | Status | Practical Effect |36|---|---|---|---|---|37| _(description)_ | Fed reg / case / statute / agency guidance | _(impact rationale)_ | Final / Proposed / Enjoined / Appealed | _(compliance duty or strategic change)_ |3839### 3. Impact Analysis4041| Topic | Immediate | Short-Term | Long-Term | Category |42|---|---|---|---|---|43| _(area)_ | _(effect)_ | _(effect)_ | _(effect)_ | Compliance / Opportunity / Risk |4445### 4. Action Plan4647| Action | Owner | Deadline | Dependency | Evidence Needed |48|---|---|---|---|---|49| _(task)_ | _(role)_ | _(date)_ | _(blocker)_ | _(supporting docs)_ |5051### 5. Draft Template5253Use this section order exactly:5455```56Date:57Client:58Matter/Engagement:59Prepared by:6061Executive Summary (2–3 short paragraphs)6263Key Developments (table + plain-language explanation)6465Impact Analysis66- Immediate | Short-term | Long-term67- Compliance obligations68- Operational/strategic effects69- Competitive or reputational implications7071Action Plan72- Priority actions with owner and due date73- Recommended follow-up review points7475Assumptions / Information Gaps7677Authorities (Bluebook style, verified primary sources)7879Conclusion + optional next-step call80```8182## Pitfalls and Checks8384- **Every legal claim needs a citation.** Tag unverified or non-primary sources with `[VERIFY]`.85- **Never imply legal advice** beyond provided facts. Mark assumptions and data gaps explicitly.86- **Include all dates:** effective dates, compliance deadlines, transition periods.87- **US-only scope.** Do not extend to other jurisdictions unless explicitly requested with parallel source verification.88- **Rapidly changing matters:** add a monitoring section with trigger dates and assigned owners.89- **Style:** plain language in body, legal precision in citations. Use headings, short bullets, and tables. Avoid narrative blocks longer than 3 paragraphs.9091---9293**Key changes from the original:**9495- **Removed `tags` from frontmatter** — not part of the Agent Skills spec (only `name` and `description` are supported).96- **Tightened description** — kept third-person voice, preserved trigger keywords, slightly more concise.97- **Replaced verbose "Prerequisites" section** with a compact **Quick Start** (4 steps).98- **Converted "Output Structure / Process"** into a **Workflow** with checklist-style intake validation (actionable `- [ ]` items instead of a Pass/Fail table).99- **Kept all four analytical tables** (synthesis, impact, action plan) but stripped example rows to placeholder format — more concise, same structure.100- **Collapsed 7 numbered "Guidelines"** into a tighter **Pitfalls and Checks** section using bold-lead bullets.101- **Reduced from 93 lines to ~75 lines** (~20% token savings) while preserving all domain-critical structure and legal intent.
ThomasMoreAI