Policy Manual Summary
Distills complex legal policies, procedures, and regulatory compliance guidelines into a structured, plain-language policy manual for organizational use.
Prerequisites
- Source materials — policies, regulatory frameworks, industry standards, organizational guidelines
- Organizational context — industry, jurisdiction(s), departmental structure
- Audience — employee level (all-hands, management, department-specific)
- Scope — which functional areas or regulatory domains to cover
Quick Start
- Gather source materials and confirm organizational context
- Identify applicable functional areas and compliance themes
- Draft each policy section using the per-policy template below
- Assemble into the document framework with cover, TOC, glossary, and appendices
- Flag uncertain citations with
[VERIFY] and multi-step processes with [FLOWCHART: description]
Document Framework
| Section |
Contents |
| Cover & Revision History |
Title, effective date, version, last review, next review |
| Table of Contents |
Auto-generated navigation |
| Executive Summary |
Critical policies in 1–2 pages; highest-priority obligations |
| Policy Sections |
Organized by functional area (template below) |
| Glossary |
Terms defined at first use, consolidated here |
| Appendices |
Forms, flowcharts, contact directories |
Per-Policy Section Template
## [Policy Area]: [Policy Name]
**Effective Date:** [Date] | **Applies To:** [Roles/Depts] | **Owner:** [Dept]
### Purpose & Scope
[1–2 sentences: why this policy exists, who it covers]
### Key Requirements
- [ ] Requirement 1
- [ ] Requirement 2
### Procedures
1. Step-by-step procedural guidance
2. Decision points noted with criteria
### Legal Authority
- [Statute/regulation citation] — [brief description]
### Non-Compliance Consequences
- [Disciplinary, civil, criminal, or regulatory consequences]
### Examples & Scenarios
- **Scenario:** [Situation] → **Required Action:** [What to do]
### Questions & Escalation
- Contact: [Role/department] at [contact info]
Cross-Cutting Compliance Themes
Address each if present in source materials:
| Theme |
Key Elements |
| Data privacy & security |
Collection limits, retention, breach notification, access controls |
| Anti-discrimination & harassment |
Protected classes, reporting channels, investigation process |
| Ethics & conflicts of interest |
Disclosure obligations, gift policies, outside activities |
| Health & safety |
OSHA/jurisdiction-specific requirements, reporting, PPE |
| Financial controls & reporting |
Authorization levels, segregation of duties, audit trails |
Pitfalls & Checks
- Plain language, not imprecise language — write for non-lawyers but maintain accuracy of legal obligations
- Jurisdiction flags — clearly mark where requirements vary by state, locality, or jurisdiction; use a federal/national baseline with local callouts
- Citation currency — verify all regulatory citations are current; mark uncertain ones with
[VERIFY]
- Privilege protection — never reproduce attorney work product or privileged analysis; summarize the compliance obligation only
- Review cadence — recommend annual review minimum; quarterly for rapidly evolving areas
- Version control — maintain a revision history table with date, author, and change description
Key changes made:
- Removed
tags from frontmatter (not part of the Agent Skills spec)
- Tightened description — shorter while keeping trigger guidance and discovery keywords
- Added Quick Start section for immediate actionable steps
- Flattened structure — removed the nested
### Output Structure > ### Document Framework nesting; promoted sections to top level
- Renamed "Guidelines" to "Pitfalls & Checks" — aligns with best-practice section naming
- Trimmed redundancy — removed the "visual aids" and "multi-jurisdiction" bullets that duplicated guidance already in the template or other bullets
- Reduced line count from 89 to 72 lines, well under the 500-line limit
1---2name: policy-manual3description: Generates structured policy manual summaries that distill complex legal policies and compliance guidelines into employee-facing reference documents organized by functional area. Use when creating compliance manuals, employee policy guides, regulatory summaries, onboarding compliance materials, or organizational procedure handbooks.4license: Apache-2.05---67# Policy Manual Summary89Distills complex legal policies, procedures, and regulatory compliance guidelines into a structured, plain-language policy manual for organizational use.1011## Prerequisites12131. **Source materials** — policies, regulatory frameworks, industry standards, organizational guidelines142. **Organizational context** — industry, jurisdiction(s), departmental structure153. **Audience** — employee level (all-hands, management, department-specific)164. **Scope** — which functional areas or regulatory domains to cover1718## Quick Start19201. Gather source materials and confirm organizational context212. Identify applicable functional areas and compliance themes223. Draft each policy section using the per-policy template below234. Assemble into the document framework with cover, TOC, glossary, and appendices245. Flag uncertain citations with `[VERIFY]` and multi-step processes with `[FLOWCHART: description]`2526## Document Framework2728| Section | Contents |29|---|---|30| Cover & Revision History | Title, effective date, version, last review, next review |31| Table of Contents | Auto-generated navigation |32| Executive Summary | Critical policies in 1–2 pages; highest-priority obligations |33| Policy Sections | Organized by functional area (template below) |34| Glossary | Terms defined at first use, consolidated here |35| Appendices | Forms, flowcharts, contact directories |3637## Per-Policy Section Template3839```40## [Policy Area]: [Policy Name]4142**Effective Date:** [Date] | **Applies To:** [Roles/Depts] | **Owner:** [Dept]4344### Purpose & Scope45[1–2 sentences: why this policy exists, who it covers]4647### Key Requirements48- [ ] Requirement 149- [ ] Requirement 25051### Procedures521. Step-by-step procedural guidance532. Decision points noted with criteria5455### Legal Authority56- [Statute/regulation citation] — [brief description]5758### Non-Compliance Consequences59- [Disciplinary, civil, criminal, or regulatory consequences]6061### Examples & Scenarios62- **Scenario:** [Situation] → **Required Action:** [What to do]6364### Questions & Escalation65- Contact: [Role/department] at [contact info]66```6768## Cross-Cutting Compliance Themes6970Address each if present in source materials:7172| Theme | Key Elements |73|---|---|74| Data privacy & security | Collection limits, retention, breach notification, access controls |75| Anti-discrimination & harassment | Protected classes, reporting channels, investigation process |76| Ethics & conflicts of interest | Disclosure obligations, gift policies, outside activities |77| Health & safety | OSHA/jurisdiction-specific requirements, reporting, PPE |78| Financial controls & reporting | Authorization levels, segregation of duties, audit trails |7980## Pitfalls & Checks8182- **Plain language, not imprecise language** — write for non-lawyers but maintain accuracy of legal obligations83- **Jurisdiction flags** — clearly mark where requirements vary by state, locality, or jurisdiction; use a federal/national baseline with local callouts84- **Citation currency** — verify all regulatory citations are current; mark uncertain ones with `[VERIFY]`85- **Privilege protection** — never reproduce attorney work product or privileged analysis; summarize the compliance obligation only86- **Review cadence** — recommend annual review minimum; quarterly for rapidly evolving areas87- **Version control** — maintain a revision history table with date, author, and change description8889---9091**Key changes made:**9293- **Removed `tags`** from frontmatter (not part of the Agent Skills spec)94- **Tightened description** — shorter while keeping trigger guidance and discovery keywords95- **Added Quick Start** section for immediate actionable steps96- **Flattened structure** — removed the nested `### Output Structure` > `### Document Framework` nesting; promoted sections to top level97- **Renamed "Guidelines" to "Pitfalls & Checks"** — aligns with best-practice section naming98- **Trimmed redundancy** — removed the "visual aids" and "multi-jurisdiction" bullets that duplicated guidance already in the template or other bullets99- **Reduced line count** from 89 to 72 lines, well under the 500-line limit
ThomasMoreAI