Agent skill · writing content · erichowens

checklist-discipline

Design and implement systematic checklists that reduce errors by 30-50% in complex, high-stakes domains (medicine, aviation, construction, finance). NOT for simple tasks or when comprehensive

Why this skill is useful

Provides structured methodologies for creating effective checklists in high-stakes environments, which the AI wouldn't reliably generate on its own.

What it needs

About 8k tokens when loaded. Last updated 2026-07-14. 180 stars on the source repository.

What this skill does

Checklist Discipline Transform individual expertise into systematic excellence by catching inevitable cognitive failures and enabling team coordination in extreme complexity. When to Use ✅ Use for: Complex processes with 100+ steps where memory/attention failures are inevitable High-stakes domains (surgery, aviation, construction, finance) where 1% error rates compound catastrophically Coordinating specialists across disciplines who must integrate decisions Converting strangers into functioning teams under time pressure Combating ineptitude (knowledge exists but isn't applied) vs. ignorance ❌ NOT for: Simple tasks with <10 steps that professionals reliably complete Teaching comprehensive procedures to complete novices (use training instead) Replacing professional judgment or handling true unpredictability Situations requiring detailed instruction manuals Avoiding responsibility through bureaucratic compliance theater Core Process Checklist Design Decision Tree Construction Coordination Decision Tree Surgical Checklist Example (WHO Model) Anti-Patterns Master Builder Syndrome Novice approach: "I'm the expert—I can hold all the knowledge and coordinate everything myself. Systematic coordination constrains my professional judgment." Expert approach: "Modern complexity exceeds individual cognitive capacity. I need systematic tools to coordinate specialists and catch my inevitable memory lapses. Checklists buttress expertise, not replace it." Timeline to expertise: 0-2 years: Resist checklists as threats to developing autonomy 3-5 years: Begin noticing personal memory failures, reluctantly try checklists 5-10 years: Experience prevented error through checklist, embrace as cognitive net 10+ years: Advocate for systematic approaches, design checklists for others Recognition shibboleth: "Checklists handle the dumb stuff so I can focus cognitive capacity on the hard stuff" vs. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills erichowens/checklist-discipline

View the source on GitHub

Browse the @skills marketplace