checklist-enforcer

Status: v0.1 — minimum viable. Full skill (per-project checklist registry) lands in Phase 1.

When to invoke

Trigger files: any *CHECKLIST*.md, preflight.md, release_checklist.md. Trigger words: "go through the checklist", "before we ship", "run the checks", "preflight".

The Rule

For EVERY item in the checklist: 1. State the item verbatim. 2. State PASS or FAIL. 3. If PASS: paste the evidence (command output, file path, screenshot, computed value). 4. If FAIL: state what failed and the remediation. 5. If SKIP: state explicit reason ("not applicable because X") and get user acknowledgment.

NO "everything looks good". NO summary-only walkthrough. NO batching multiple items under one pass.

Minimum viable checklist (v0.1)

1. Locate the checklist file. If multiple candidates, ask the user which one.
2. Parse items (numbered, bulleted, or - [ ] markdown checkbox style).
3. For each item, do the work, capture evidence, write it inline. Do not move to the next item until evidence is captured.
4. At the end, print a summary table: item | status | evidence link.
5. If ANY item is FAIL or SKIP, surface them at the top before the summary.

Anti-patterns

• "All 12 items passed ✓" without item-by-item evidence. ← blocked
• Marking items as PASS based on memory of a prior session.
• Skipping items because "we did this last time" — last time is not now.
• Reading the checklist but not actually running the commands.

Cross-references

• Each item's evidence step IS a superpowers:verification-before-completion invocation in miniature.
• For balance/strategy checklist items, defer to bg-superpowers:balance-report-critic for the actual statistical gate.

TODO (Phase 1 full implementation)

• Per-project checklist registry (bg-superpowers.config.json maps project root → list of canonical checklists).
• Auto-fill markdown checkbox - [ ] → - [x] only after evidence is captured.
• Block git commit if any checklist item is unresolved (optional pre-commit hook).