Policy Summary
Produces a structured summary of a policy document capturing scope, obligations, enforcement, and compliance impact.
Quick Start
- Gather the primary policy document(s) — statute, regulation, institutional policy, or proposal
- Collect any amendments, supplements, or implementation guidance (agency FAQs, interpretive memos)
- Follow the workflow below to extract, structure, and deliver the summary
Workflow
1. Extract Key Elements
Search all uploaded matter files. Identify and capture:
- Defined terms — terms with specific legal meaning controlling interpretation
- Scope & applicability — who/what is covered; geographic and temporal reach
- Requirements & prohibitions — mandatory vs. permissive provisions
- Compliance mechanisms — deadlines, thresholds, procedural steps
- Enforcement — penalties and consequences for non-compliance
- Exceptions & carve-outs — safe harbors, exemptions, de minimis thresholds
- Cross-references — links to other policies, statutes, or regulations
2. Produce Summary
Structure output as:
- Executive Overview — 2–3 paragraphs: core purpose, applicability, most significant provisions
- Key Definitions — table of defined terms and operative meanings
- Substantive Provisions — one section per topic area with descriptive headings covering what the policy requires/permits/prohibits, deadlines, thresholds, and flagged ambiguities
- Compliance & Practical Implications — action items, risk/exposure areas, recommended next steps (checklist format)
- Conflicts & Open Questions — conflicts with existing requirements or interpretive ambiguities
- Source References — section/page citations to source documents
3. Handle Proposals (If Applicable)
When summarizing proposed legislation or regulatory changes, also identify:
- Existing requirements that would be modified
- Net-new obligations introduced
- Transition timelines and effective dates
Pitfalls & Checks
- Obligation levels matter: use "must"/"requires" for mandatory; "may"/"allows" for permissive; flag aspirational language separately
- Separate fact from analysis: distinguish what the policy states vs. analytical observations
- Preserve qualifications: never flatten conditions, limitations, or carve-outs — these are critical for compliance
- Cite specifically: reference section/page numbers for every substantive claim
- Flag ambiguity: note provisions with multiple plausible interpretations and any available guidance
- Audience awareness: minimize jargon while maintaining legal precision; non-legal stakeholders will read this
Key changes made:
- Description condensed to one sentence with explicit trigger guidance
- Prerequisites folded into a 3-line Quick Start
- Extraction table converted to a flat bullet list (same info, fewer tokens)
- Output template replaced verbose code block with inline descriptions of each section
- Step 3 renamed and scoped as conditional ("If Applicable")
- Guidelines renamed to "Pitfalls & Checks" for clearer intent
- All domain accuracy and legal precision preserved throughout
Want me to retry saving the file?
1---2name: policy-summary3description: Summarizes policy documents, regulations, and legislative materials into structured briefings with compliance insights. Triggers when the user needs a policy summary, regulatory overview, legislative breakdown, or compliance briefing from uploaded policy materials.4---5
6# Policy Summary
7
8Produces a structured summary of a policy document capturing scope, obligations, enforcement, and compliance impact.
9
10## Quick Start
11
121. Gather the primary policy document(s) — statute, regulation, institutional policy, or proposal
132. Collect any amendments, supplements, or implementation guidance (agency FAQs, interpretive memos)
143. Follow the workflow below to extract, structure, and deliver the summary
15
16## Workflow
17
18### 1. Extract Key Elements
19
20Search all uploaded matter files. Identify and capture:
21
22- **Defined terms** — terms with specific legal meaning controlling interpretation
23- **Scope & applicability** — who/what is covered; geographic and temporal reach
24- **Requirements & prohibitions** — mandatory vs. permissive provisions
25- **Compliance mechanisms** — deadlines, thresholds, procedural steps
26- **Enforcement** — penalties and consequences for non-compliance
27- **Exceptions & carve-outs** — safe harbors, exemptions, de minimis thresholds
28- **Cross-references** — links to other policies, statutes, or regulations
29
30### 2. Produce Summary
31
32Structure output as:
33
34- **Executive Overview** — 2–3 paragraphs: core purpose, applicability, most significant provisions
35- **Key Definitions** — table of defined terms and operative meanings
36- **Substantive Provisions** — one section per topic area with descriptive headings covering what the policy requires/permits/prohibits, deadlines, thresholds, and flagged ambiguities
37- **Compliance & Practical Implications** — action items, risk/exposure areas, recommended next steps (checklist format)
38- **Conflicts & Open Questions** — conflicts with existing requirements or interpretive ambiguities
39- **Source References** — section/page citations to source documents
40
41### 3. Handle Proposals (If Applicable)
42
43When summarizing proposed legislation or regulatory changes, also identify:
44
45- Existing requirements that would be modified
46- Net-new obligations introduced
47- Transition timelines and effective dates
48
49## Pitfalls & Checks
50
51- **Obligation levels matter**: use "must"/"requires" for mandatory; "may"/"allows" for permissive; flag aspirational language separately
52- **Separate fact from analysis**: distinguish what the policy states vs. analytical observations
53- **Preserve qualifications**: never flatten conditions, limitations, or carve-outs — these are critical for compliance
54- **Cite specifically**: reference section/page numbers for every substantive claim
55- **Flag ambiguity**: note provisions with multiple plausible interpretations and any available guidance
56- **Audience awareness**: minimize jargon while maintaining legal precision; non-legal stakeholders will read this
57
58---
59
60**Key changes made:**
61
62- **Description** condensed to one sentence with explicit trigger guidance
63- **Prerequisites** folded into a 3-line Quick Start
64- **Extraction table** converted to a flat bullet list (same info, fewer tokens)
65- **Output template** replaced verbose code block with inline descriptions of each section
66- **Step 3** renamed and scoped as conditional ("If Applicable")
67- **Guidelines** renamed to "Pitfalls & Checks" for clearer intent
68- All domain accuracy and legal precision preserved throughout
69
70Want me to retry saving the file?
CaseMark