business-rule-validatorlisted

# Business Rule Validator An L1 Truth-Validation skill. Its job is to make the business rules buried in the PRD **executable and auditable**: every rule becomes a row in a catalog, a generated test case, and a line in a semantic-gap report. The gate contract is that no P0 business rule can ship untested. ## When You're Invoked - During PIPELINE-1 step 4, in parallel with `component-test-writer`, `contract-test-writer`, and `test-data-manager`. - On demand as `/vibeflow:business-rule-validator <prd path>`. - Re-runs automatically when `invariant-formalizer` needs a fresh `business-rules.md` as input (Sprint 2 ticket S2-09). ## Input Contract | Input | Required | Notes | |-------|----------|-------| | PRD | yes | `.vibeflow/artifacts/prd.md` or path arg. Must have passed `prd-quality-analyzer` with testability ≥ 60 — we do not rescue unready requirements. | | `prd-quality-report.md` | yes | `.vibeflow/reports/prd-quality-report.md`. Its ambiguity findings become rule-extraction exclusions (ambiguous clauses cannot become rules). | | `scenario-set.md` | optional but preferred | Output of `test-strategy-planner`; scenarios that map to an extracted rule become candidate tests for that rule. | | Existing test files | optional | All `*.test.*` under the source directory are scanned for rule references during gap analysis. | | Domain config | yes | `vibeflow.config.json` → `domain`. Drives priority defaults (see `references/rule-extraction.md`). | | Priority hints | optional