1---2name: policy-story-explainer3description: Rewrites long policy, compliance, HR, legal, or governance documents into accurate story-led explanations. Use this skill when the user wants a policy made relatable and scenario-based without watering down obligations. Do not use when/for HTML page packaging (use policy-html-explainer) or inventing policy that is not in the source.4---56# Policy Story Explainer78## Critical rules910- Preserve meaning, obligations, thresholds, exceptions, definitions, and consequences.11- Do not invent rules; do not soften `must`/`shall`; do not widen exceptions.12- Keep numbers, dates, approval levels, defined terms, and template placeholders verbatim.13- Separate policy quote, explanation, and scenario visually/structurally.14- Flag ambiguity: "The policy is not explicit on this point."15- Before rewriting, read [references/output-format.md](references/output-format.md), [references/writing-style.md](references/writing-style.md), and [references/examples.md](references/examples.md).1617## Workflow18191. Read the three reference files above (mandatory).202. Read the policy; extract rules, duties, permissions, exceptions, risks, consequences.213. Group into themes; for each write scenario, plain-English meaning, verbatim rule, what to do, why it exists, what goes wrong if ignored.224. Preserve source references (section/clause/page) where available.235. For long/high-stakes policies, lead with an executive summary then the full story-led version (examples §6 shape).246. Flag legal/safeguarding/medical/financial/regulatory items for human review.257. Run Validation.2627## Resources2829- [references/output-format.md](references/output-format.md) — templates and section structure. Read before writing output.30- [references/writing-style.md](references/writing-style.md) — tone, audience tuning, anti-slop. Read before drafting prose.31- [references/examples.md](references/examples.md) — WRONG vs CORRECT fidelity traps and full miniature. Read before/during drafting.3233## Validation3435- [ ] Mandatory language intact (`must`/`shall` not softened)36- [ ] Thresholds, placeholders, source refs unchanged37- [ ] Exceptions present and not widened38- [ ] Ambiguity flagged; no invented advice39- [ ] Long docs: executive summary drops no obligation40- [ ] Genuinely easier to read than the source4142## Constraints4344- Ask if audience, tone, or "make it friendlier" could change meaning.45- Sibling for HTML packaging: `policy-html-explainer`.
jagreehal