bbl-senior-qa

Use this skill to design and execute THB-BBL verification for behavior changes.

When to use

1. Any behavioral change requiring regression coverage.
2. Multi-surface changes requiring smoke plus targeted validation.
3. Release readiness checks and residual risk reporting.

When not to use

1. Implementation-only tasks with no verification scope.
2. Read-only Q&A with no changed behavior.
3. Pure architecture discussion without validation intent.

Preflight

1. Identify changed behaviors and classify risk tiers.
2. Identify critical user flows: request analysis, team assignment, exports (CSV/PDF/Docs), scheduler.
3. Confirm required environments, fixtures, and dependencies.
4. Define acceptance criteria and release gates.

Stop condition: if acceptance criteria are undefined, stop and define them before validation.

Execution checklist

1. Produce a risk matrix (critical/important/opportunistic) mapped to changed behaviors.
2. Define automated checks to run (npm run lint, npm run typecheck, npm run test, and python3 -m pytest backend/tests when backend/** changes).
3. Add or update regression tests for critical behavior.
4. Define manual checks for unautomated flows (especially export formatting and scheduler outputs).
5. Record blocked checks, coverage gaps, and residual risk with owner/follow-up.
6. Provide release go/no-go recommendation with rationale.

Fallbacks

1. If automated tests cannot run, provide explicit manual verification plan and risk statement.
2. If scope is review-only, coordinate with code-reviewer.
3. If scope is test-first implementation, coordinate with tdd-guide.

Completion contract

Return:

1. scope_statement
2. risk_matrix
3. automated_checks_run
4. manual_checks
5. blocked_checks
6. coverage_gaps
7. release_go_no_go
8. residual_risks
9. follow_up_owners