1---2name: policy-story-explainer3description: >-4 Rewrites long policy, compliance, HR, legal, or governance documents into5 accurate story-led explanations. Use this skill when the user wants a policy6 made relatable and scenario-based without watering down obligations. Do not7 use when/for HTML page packaging (use policy-html-explainer) or inventing8 policy that is not in the source.9version: 1.2.010---1112# Policy Story Explainer1314## Critical rules1516- Preserve meaning, obligations, thresholds, exceptions, definitions, and consequences.17- Do not invent rules; do not soften `must`/`shall`; do not widen exceptions.18- Keep numbers, dates, approval levels, defined terms, and template placeholders verbatim.19- Separate policy quote, explanation, and scenario visually/structurally.20- Flag ambiguity: "The policy is not explicit on this point."21- 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).2223## Workflow24251. Read the three reference files above (mandatory).262. Read the policy; extract rules, duties, permissions, exceptions, risks, consequences.273. Group into themes; for each write scenario, plain-English meaning, verbatim rule, what to do, why it exists, what goes wrong if ignored.284. Preserve source references (section/clause/page) where available.295. For long/high-stakes policies, lead with an executive summary then the full story-led version (examples §6 shape).306. Flag legal/safeguarding/medical/financial/regulatory items for human review.317. Run Validation.3233## Resources3435- [references/output-format.md](references/output-format.md) — templates and section structure. Read before writing output.36- [references/writing-style.md](references/writing-style.md) — tone, audience tuning, anti-slop. Read before drafting prose.37- [references/examples.md](references/examples.md) — WRONG vs CORRECT fidelity traps and full miniature. Read before/during drafting.3839## Validation4041- [ ] Mandatory language intact (`must`/`shall` not softened)42- [ ] Thresholds, placeholders, source refs unchanged43- [ ] Exceptions present and not widened44- [ ] Ambiguity flagged; no invented advice45- [ ] Long docs: executive summary drops no obligation46- [ ] Genuinely easier to read than the source4748## Constraints4950- Ask if audience, tone, or "make it friendlier" could change meaning.51- Sibling for HTML packaging: `policy-html-explainer`.
jagreehal