bbl-senior-devops

Use this skill for THB-BBL delivery safety and operational readiness.

When to use

1. CI/CD correctness, resilience, speed, or failure isolation work.
2. Deployment safety, rollback readiness, and environment hardening.
3. Secrets/config handling and runtime observability changes.

When not to use

1. Pure feature development with no operations impact.
2. UI/backend implementation that does not touch delivery controls.
3. Architecture-only decisions without release or operations implications.

Preflight

1. Identify target environments and release constraints.
2. Identify current pipeline bottlenecks and frequent failure patterns.
3. Verify rollback path for app deploys and Prisma migrations.
4. Verify environment safety for DATABASE_URL, DIRECT_URL, and AI/API credentials.

Stop condition: if rollback path is unknown, stop and define rollback readiness first.

Execution checklist

1. Validate build/start health for Next.js (npm run build, npm run start expectations).
2. Strengthen deploy gates and rollback controls.
3. Verify Prisma migration sequencing and rollback guidance.
4. Validate local stack safety and reproducibility (npm run dev:stack).
5. Verify secret management and config safety.
6. Improve observability and failure diagnostics where needed.
7. Do not ship pipeline/deploy changes without documented rollback verification steps.
8. Run baseline checks: npm run lint, npm run typecheck, npm run test, and python3 -m pytest backend/tests when backend/** changes.

Fallbacks

1. If scope becomes architecture-heavy, coordinate with bbl-senior-architect.
2. If request is mostly app behavior changes, route to bbl-senior-backend or bbl-senior-frontend.
3. If safety checks are intentionally reduced, record explicit risk acceptance and impact.

Completion contract

Return:

1. scope_statement
2. pipeline_changes
3. deployment_gates
4. rollback_readiness
5. env_safety_checks
6. files_changed
7. validations_run
8. blocked_checks
9. residual_risks