# Bep Best Engineering Practice

> Perform an explicitly requested comprehensive engineering-practice audit across relevant disciplines.

- Skill: `saltbo/bep-best-engineering-practice` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add saltbo/bep-best-engineering-practice`
- Raw SKILL.md: https://api.skillmd.com/api/skills/saltbo/bep-best-engineering-practice/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Security
- Author: saltbo (https://skillmd.com/u/saltbo)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/saltbo/bep-best-engineering-practice

---


# Comprehensive Engineering Audit

Use only for an explicitly requested cross-discipline audit. Preserve the existing
explicit-only invocation policy. A review-only request does not authorize repairs;
a request to audit and fix includes in-scope correction and local acceptance.

Read [audit scope](references/core.md), then inspect only the relevant disciplines:

- `$bep-backend-engineering`: backend ownership and dependencies.
- `$bep-frontend-engineering`: browser state and feature boundaries.
- `$bep-http-engineering`: request lifecycle semantics.
- `$bep-best-openapi-design`: resource and representation design.
- `$bep-software-testing`: test pyramid and behavioral proof.
- `$bep-verification-gates`: explicitly scoped formal verification governance.
- `$bep-software-debugging`: an actual fault investigation.
- `$bep-delivery-engineering`: migration or deployment work.
- `$bep-production-verification`: requested deployed-environment regression.
- `$bep-engineering-review`: a concrete change's outcome and risk.

Load separately installed specialists only when their actual workflow is needed.
Missing optional specialists are a limitation of that specialist review, not a
reason to abandon independent work. Report findings with evidence, separate defects
from preference differences, and identify unresolved verification.