fr-acceptancelisted

Drive the acceptance matrix: backfill an existing repo's business-level acceptance tests into docs/acceptance/matrix.yaml, flip row statuses as evidence lands, and keep the CI gate honest. Use when: "backfill the acceptance matrix", "acceptance debt", "add acceptance rows", a session starts with an acceptance-debt nag, or `fr acceptance check` fails.
derio-net/super-fr · ★ 1 · AI & Automation · score 67

Install: claude install-skill derio-net/super-fr

# fr-acceptance The matrix (`docs/acceptance/matrix.yaml`) is the registry of business-level acceptance tests × verification levels (unit/api/int/ui) × automation status. This skill drives the agent-side work; the mechanics live in the CLI. **Announce at start:** "I'm using fr-acceptance to work the acceptance matrix." ## Statuses — the honesty scale `ci` / `scheduled` = automated, cannot drift · `skipped` = verification exists but not in CI (warning, backfill owed) · `not-implemented` = nothing yet (warning) · `failing` = known red, `fr acceptance check` exits 2 and CI fails. Statuses move **explicitly, never silently** — with `fr acceptance set-status`, never a hand-edit. The drift channel is precisely the hand-tracked claims — when in doubt between ci and skipped, **choose skipped**. Do not inflate coverage; the operator audits statuses at review. ## Backfill an existing repo 1. `fr acceptance init` (idempotent) if the repo has no matrix — scaffolds matrix + CI workflow + backfill rule + gitignore entry. 2. `fr acceptance backfill` — emits the inventory (Test Plan specs not yet cited, plans without linked rows, test-tree hints) + this protocol. 3. DRAFT rows — **one row per business acceptance, not per test** — via `fr acceptance add --id <kebab> --capability <group> --acceptance "<operator can X>" --origin <repo>:<path> --level unit=<repo>:<path> --status <honest> --notes "<evidence / backfill owed>"`. Never hand-edit YAML shapes; `add` validates a