checklist-and-runbook
Create practical checklists and runbooks that help people execute processes reliably under real conditions. Use for operational procedures, incident response, release steps, onboarding, or any repeatable process that benefits from standardization.
- License 许可
- MIT
- 最近更新
- 2026-07-22
- Stars
- ★ 7
- Forks
- 1
01 前言 Front Matter
- name
- checklist-and-runbook
- description
- Create practical checklists and runbooks that help people execute processes reliably under real conditions. Use for operational procedures, incident response, release steps, onboarding, or any repeatable process that benefits from standardization.
03 SKILL.md 正文
Checklist and Runbook
Overview
Checklists and runbooks reduce errors and cognitive load. They should be written for the person doing the work, especially under time pressure or stress.
When to Use
- Operational procedures
- Incident response and on-call guides
- Release / deployment steps
- Onboarding and recurring operational tasks
- Safety or compliance-critical processes
Design Principles
- Write for the doer, not the auditor
- Use clear, actionable steps (verb-first)
- Include preconditions, expected results, and failure signals
- Keep the happy path prominent; branch for exceptions
- Make ownership and escalation paths obvious
- Version and date the document
Checklist vs Runbook
- Checklist — Short, ordered verification or action items
- Runbook — More detailed procedure with context, decision points, and recovery steps
Verification
- [ ] Someone unfamiliar with the process can follow it
- [ ] Critical steps cannot be easily skipped or misread
- [ ] Failure and escalation paths are defined
04 同仓库更多 Skills
compliance-monitoring
Design compliance monitoring and testing programs that verify controls work in practice and surface issues before regulators do. Use when building monitoring plans, compliance testing, or continuous control monitoring.
complaints-handling
Operate complaints-handling processes that meet regulatory standards — logging, timely resolution, root-cause analysis, and fair outcomes. Use when designing or improving regulated complaints frameworks or analyzing complaint themes for conduct risk.
aml-kyc-basics
Apply AML/KYC fundamentals — customer due diligence, monitoring, suspicious activity escalation, and recordkeeping — for financial crime compliance. Use when designing onboarding controls, transaction monitoring concepts, or AML program components in financial services.
ai-model-compliance
Apply compliance controls to AI and automated decision systems — transparency, fairness, human oversight, documentation, and regulatory alignment. Use when deploying AI in regulated processes (credit, fraud, customer decisions) or responding to AI governance expectations.
data-quality-management
Manage data quality end-to-end — dimensions, rules, remediation, and prevention — beyond one-off cleaning scripts. Use when building sustained data quality programs or fixing systemic accuracy, completeness, or consistency problems.
data-lineage
Capture and use data lineage — where data comes from, how it transforms, and what depends on it — for impact analysis, debugging, and trust. Use when tracing metric origins, assessing change impact, or diagnosing broken pipelines.