mb-review

To audit a Memory Bank for gaps, you can run a fresh-context expert review that checks architecture, RTM, and documentation, producing a prioritized fix list. This validates readiness before autonomous execution by gating progress with a synthesized verdict.

The best way to perform a post-boot audit is to coordinate multi-stage expert reviews that surface governance and compliance gaps. This process synthesizes findings into a concrete fix plan, writing detailed reports to your tasks directory for traceability.

A fresh-context review verifies scope and security compliance by orchestrating dedicated reviewer stages. These expert stages independently evaluate the Memory Bank, automatically synthesizing their findings into a concise verdict to gate progress.

Yes, you can use a multi-stage expert review to bootstrap a new Memory Bank. The process coordinates fresh-context reviewers across architecture, scope, plan, and security to identify missing elements and generate a prioritized fix list.

A limitation of gating autonomous execution with this review is that it focuses strictly on architecture, RTM, and documentation compliance. Code quality checks are optional, so execution gating relies primarily on documentation and structural completeness rather than runtime validation.

You need existing Memory Bank documents to run a fresh-context MB review because the process evaluates current architecture and RTM artifacts. It references these MB docs to produce traceability and identify gaps for your prioritized fix list.