review-scenario-matrix

Route ambiguous review requests by mapping them to a primary scene and multiple engineering scenes. This dual-layer routing applies a 17-dimension matrix to architecture, code PRs, database, API design, agent, and security to generate a coverage plan.

A review scenario matrix is a 17-dimension coverage framework that ensures comprehensive project governance. You need it when ambiguous review requests require structured routing across architecture, API, database, and security scenes to guarantee traceable evidence.

Generate a playback-ready dossier by loading upstream truth sources and capturing evidence targets during review routing. The process outputs actionable next-step recommendations and an audit-ready plan covering architecture, code PRs, and security dimensions.

Yes, the review routing approach relies on a YAML dependency to manage configuration. It uses YAML to structure the 17-dimension matrix expansion and capture evidence targets across primary and secondary engineering scenes.

The best way to ensure comprehensive coverage is applying a matrix-driven approach across 17 dimensions. This routes review requests into specific scenes like code PR and release gate, loading relevant references on demand to produce traceable conclusions.

A limitation of matrix-driven routing is its dependency on upstream truth sources for accurate evidence capture. If primary and secondary scene mappings are ambiguous, generating a playback-ready dossier with actionable next steps may require manual clarification.