Policy Clarifier

Files (11)

• README.md
• SKILL.md
• openai.yaml · agents/
• template.md · assets/
• edge-cases.md · references/
• examples.md · references/
• rubric.md · references/
• skill.json
• edge-path.md · tests/
• failure-cases.md · tests/
• happy-path.md · tests/

SKILL.md (first lines)

# Policy Clarifier

## Summary

Clarify a policy or internal guideline into a more readable, operationally useful document.

## When To Use

- A policy document needs clearer language and action framing.
- You need a clarified policy document with definitions, practical guidance, and open question flags instead of unstructured notes.
- The workflow repeats often enough to justify a reusable asset.

## Avoid When

- The product behavior itself is still changing faster than the docs could stabilize.
- There is no source material to document or clarify yet.

## Inputs

- policy text
- audience
- common confusion points

## Output Contract

- clarified policy draft
- operational guidance
- FAQ candidates

## Workflow

1. Confirm the decision context, audience, and missing inputs.
2. Build a clarified policy document with definitions, practical guidance, and open question flags using the available evidence and constraints.
3. Separate facts from assumptions and make confidence explicit.
4. Finish with next actions, open questions, or escalation notes.

## Deliverable Shape

A clarified policy document with definitions, practical guidance, and open question flags

## Guardrails

- Do not invent facts that are not present in the supplied materials.
- Make uncertainty explicit when inputs are incomplete or contradictory.
- Keep the output structured enough that another operator can reuse it.

## Maturity Note

This Skill is part of the seeded breadth layer. It is intentionally lighter than the developed and flagship tiers.

From FDU-INS/Insurance-Skills, Apache-2.0.

More from FDU-INS/Insurance-Skills