checklist

InventoryStackStructure

Items with state markers — done, partial, failed, unknown, to do, skipped.

Use for completion reports, readiness audits, or pre-flight checks. State markers [x]/[-]/[!]/[?]/[ ]/[/] produce status-colored circles carrying a distinct mark — check / dash / cross / question / ring / slash — so the shape reads independently of color (color-blind-safe).

statusstoplightprocessrequirements

When to use

Completion reports. Use when the audience needs to see what's done, what's in progress, and what's outstanding. The state marks are the load-bearing signal.
Readiness audits. Pre-launch, pre-release, pre-flight. A short list where the mix of green / amber / red tells the room whether to proceed.
Five to eight items. Short enough that the audience can take in the state mix at a glance. Past eight, split into two checklists by phase or owner.

When not to use

All-done lists. If every item is [x] the state markers are decoration. Use list (or its takeaway variant) for celebratory recaps; checklist earns its weight when the mix matters.
Long per-item prose. Each item is one short line. If a row needs a sentence of explanation, the right home is cards-stack or list-tabular.
Custom state markers. Only the six markers — [x] [-] [!] [?] [ ] [/] — map to the mark palette. Anything else in brackets ([X], [~], [>]) renders as literal text and breaks the visual contract. [X] is the trap: GitHub-flavored markdown reads it as a checked box, and it does not draw a mark here.

Common mistakes

Writing the status pill as plain trailing text instead of {status} in inline code. The optional trailing status tag must be a pill in inline code (e.g. ` {blocked} `) to render as a floated pill — plain trailing text just becomes part of the line's prose.
Confusing [/] (out-of-scope, struck through) with [-] (partial / in-progress). [-] marks partial progress (amber dash); [/] marks an item explicitly descoped (muted, struck through) — using [/] for 'in progress' mis-signals the row as cut rather than underway.

Authoring

<!-- _class: checklist -->

## Pre-launch readiness.

- [x] First item that is fully done.
- [x] Second item that is fully done.
- [-] Third item that is partially complete with a caveat.
- [!] Fourth item that was checked and failed.
- [?] Fifth item nobody can settle yet.
- [ ] Sixth item that is not yet started.

Slots

Slot	Selector	Required	Description
`title`	`h2`	yes	Slide heading.
`items`	`ul > li`	yes	Each item prefixed with a state marker — [x] done, [-] partial, [!] failed, [?] unknown, [ ] to do, or [/] skipped (struck through). Plain text follows the marker; an optional trailing pill, written `{status}` in inline code, floats right as a status tag.

Anatomy

┌─────────────────────────────────────────┐
│  header                                 │
│  Checklist heading.                     │
│                                         │
│  [x] Completed item — green tint        │
│  [-] Partial item — amber tint          │
│  [ ] Open item — red tint               │
│  [x] Another completed item             │
│                                         │
│  footer                           1/19  │
└─────────────────────────────────────────┘

Guides

The six answerswhat each state marker means
Marks in layoutsthis layout’s words for each mark, and renaming them with a label set

listitems have no state — just bullets
list-tabularrows need a label-plus-description structure, not state
cards-stackeach item needs two sentences of body