Compliance training refresh
Updates compliance training modules against revised policies, identifies changed learner obligations, and creates source-linked lesson text, scenario questions, and an answer key. Use for annual compliance refreshes, policy changes, code-of-conduct training, and controlled learning-content updates.
Publicado 21 de ago de 2026 · Actualizado 26 de ago de 2026
Requisitos
Add current policy, prior module, change log, glossary, and reporting procedure. Define audience roles, learning objectives, reading level, and question count.
Documento de la habilidad
El SKILL.md completo que tu agente lee y sigue.
Compliance training refresh
Purpose
Refresh a learner-facing compliance module when a policy, control, role duty, or escalation path changes. The result preserves required rules, explains what changed, and tests comprehension with answer-supported scenarios.
Scope
Cover policy requirements, definitions, prohibited conduct, reporting channels, role-specific duties, exceptions, effective dates, lesson objectives, knowledge checks, and answer rationales. Excluded: legal interpretation beyond the supplied policy, publishing the course, tracking attendance, or certifying a learner.
Data basis
- Current policy and prior training module, including section headings and version dates.
- Change log, control matrix, code of conduct, reporting procedure, and approved glossary.
- Audience role list and learning objectives.
- Existing quiz items and answer key when present.
Result
A change register, refreshed lesson document, and question sheet with correct answers, distractor rationale, source citation, and objective mapping.
Quality criteria
- Every changed obligation cites current policy section and effective date.
- No retired requirement remains presented as current.
- Each question has one defensible answer and a rationale grounded in policy.
- Examples do not add thresholds, penalties, or reporting channels absent from the sources.
- Required concepts from the prior module are either retained, updated, or explicitly removed.
Instructions
Treat the latest approved policy version as authoritative only when its approval and effective date are visible. Preserve mandatory verbs such as must, may, and must not. Write plain learner language but retain defined terms exactly. Mark a policy conflict as unresolved instead of choosing the more restrictive wording. Build scenarios from supplied roles and facts; label hypothetical details as examples. The answer key must explain why each distractor fails.
Adapt before use
- Add current policy, prior module, change log, glossary, and reporting procedure.
- Define audience roles, learning objectives, reading level, and question count.
- Set approval, effective-date, version-control, and translation requirements.
Habilidades relacionadas
- Claim chronology builder
Builds a dated chronology from claim notices, correspondence, contracts, invoices, incident records, and evidence logs, preserving source citations and disputed dates. Use for insurance claims, commercial disputes, incident files, demand packages, litigation chronologies, and internal fact reviews.
- Contract obligation register
Extracts dated and recurring duties from signed contracts into an obligation register with parties, triggers, notice windows, service levels, payment terms, evidence, and owners. Use for contract lifecycle management, renewal tracking, vendor obligations, or inherited agreement cleanup.
- Contract playbook review
Reviews a commercial contract against a company playbook, records missing or non-standard clauses with exact citations, and proposes fallback positions. Use for procurement, sales, SaaS, services, and contract redline preparation.
- Contract renewal watchlist
Builds a contract renewal watchlist by calculating expiry and notice dates, checking auto-renewal clauses, reconciling spend and usage, and identifying negotiation priorities. Use for vendor renewals, customer agreements, termination windows, contract calendars, and renewal planning.