Audit a software change or system across engineering disciplines. This is the explicit umbrella workflow, not the default entry point for ordinary coding.
Read references/core.md, then load only the independently installed skills relevant to the requested audit:
$bep-backend-engineeringfor backend ownership and dependency direction;$bep-frontend-engineeringfor browser architecture and UI runtime behavior;$bep-http-engineeringfor HTTP lifecycle and protocol semantics;$bep-software-testingfor proof-layer and test-design decisions;$bep-verification-gatesfor coverage governance and blocking CI policy;$bep-production-verificationfor deployed-environment verification;$bep-software-debuggingfor a fault or regression investigation;$bep-delivery-engineeringfor compatibility, migration, release, or rollback;$bep-engineering-reviewfor risk classification and review disposition;$bep-best-openapi-designfor REST/OpenAPI resource and contract design.
Preserve the requested task mode. An audit, plan, diagnosis, or review remains read-only unless the user separately authorizes implementation.
Do not load every skill mechanically. State which disciplines apply, inspect only those areas, and report the observable outcome, blocking findings, unresolved risk, and evidence used.