checklist-generatorlisted

# Checklist Generator An L1 Truth-Validation skill. The purpose of a VibeFlow checklist is not to remind anyone to "be careful" — it is to produce a finite set of binary checks a reviewer can actually execute. Every item has a precise verification action, a source of truth to check against, and an outcome predicate. Items that don't meet that bar are rejected at generation time, not after the reviewer has already wasted time on them. ## When You're Invoked - During PIPELINE-2 (change-in-place flow), step 3, after `component-test-writer` has produced the test file set. - On demand as `/vibeflow:checklist-generator <context> <platform>`. - Before a release tag, from `release-decision-engine`, when a CONDITIONAL verdict requires a human sign-off checklist. ## Input Contract | Input | Required | Notes | |-------|----------|-------| | Context | yes | One of `pr-review`, `release`, `feature`, `accessibility`. Drives which template family loads. | | Platform | yes | One of `web`, `mobile`, `backend`, `all`. Drives which platform-specific items get injected. | | `scenario-set.md` | optional | Output of `test-strategy-planner`. Scenarios with `coverage: gap` become injected items. | | `prd-quality-report.md` | optional | P0 missing-flow findings become injected items. | | `business-rules.md` | optional | P0 rules with `GAP-001` (uncovered) become injected items. | | Domain config | yes | `vibeflow.config.json` → `domain`. Pulls in domain-specific overlay items (GDPR for ecomm