Checklist status
Module · Stable
Read a record’s checklists: per-check state, gate blockers, and completion.
Read-only. Given a record_type + record_id, returns one row per check (check_id, label, kind, status, due_at, whether it’s blocking a gate), the list of gating checklists still blocking advancement, and is_complete (true when no check is pending). The standard first call before satisfy / waive / skip — discover check_ids and labels, then act on them by id.
When to use
Section titled “When to use”Use as the discovery step before acting on individual checks: feed a record_type + record_id from upstream (e.g. a claim or task id), read the returned checks list to find check_ids and statuses, then pass those ids into Satisfy check, Waive check, or Skip check (N/A).
When not to use
Section titled “When not to use”If you only need to act on a check whose id is already known, go straight to Satisfy check, Waive check, or Reopen check — skip this read step. To launch a new checklist bundle onto a record, use Launch checklist instead.
Inputs
Section titled “Inputs”Configured per use: record_type, record_id.
Outputs
Section titled “Outputs”Auto-generated from the skill registry (load_skills()). Do not edit by hand.