architecture-audit

To conduct a system design review, provide architecture Markdown files and trigger an explicit audit request. The analysis reads design docs and diagram references to evaluate structural flaws, outputting a brutal audit report with file and component scores.

The best way to generate an improvements roadmap is by running a two-phase architecture audit. After the rigorous audit phase identifies structural flaws, the improvements phase translates those findings into a prioritized roadmap of actionable solutions.

Yes, you can audit architecture Markdown files that reference external diagrams. The analysis processes design docs and diagram references within the Markdown input to evaluate structural quality and produce the audit report.

To trigger an architecture audit and get component scores, provide your architecture Markdown files and use an explicit request such as 'audit architecture'. This generates both the audit report and the prioritized improvements roadmap in a single run.

An architecture audit on design docs requires explicit triggers and Markdown inputs to operate. It does not process non-Markdown files directly and relies entirely on the provided documentation to surface structural flaws and generate the improvements roadmap.