brooks-audit

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Chinese

Read
```
../_shared/common.md
```
for the Iron Law, Project Config, Report Template, and Health Score rules
Read
```
../_shared/source-coverage.md
```
for book-level coverage, exceptions, and tradeoffs
Read
```
../_shared/decay-risks.md
```
for symptom definitions and source attributions
Read
```
architecture-guide.md
```
in this directory for the audit framework

Onboarding mode: If the user asks for an onboarding report, codebase tour, or "explain this codebase to a new developer", read

onboarding-guide.md

from this directory and follow it instead of

architecture-guide.md

. This mode explains rather than diagnoses — no Health Score, no Iron Law findings.

If the user has not specified files or a directory to audit: apply Auto Scope Detection from

../_shared/common.md

to determine the audit scope before proceeding.

Gather codebase context and draw the module dependency graph as Mermaid (Steps 0–1 of the guide)
Scan for each decay risk in the order specified (Steps 2–4 of the guide)
Assign node colors in the Mermaid diagram based on findings (red/yellow/green) — after Step 4
Run the Testability Seam Assessment (Step 5 of the guide)
Run the Conway's Law check (Step 6 of the guide)
Output using the Report Template from common.md — Mermaid graph FIRST, then Findings

Mode line in report:

Architecture Audit

入职模式： 如果用户要求提供入职报告、代码库浏览或“向新开发者讲解这个代码库”，请阅读当前目录下的

onboarding-guide.md

并遵循其流程，而非

architecture-guide.md

。此模式侧重于讲解而非诊断——不包含健康评分，也不涉及铁律相关发现。

如果用户未指定要审计的文件或目录： 在开始之前，先使用

../_shared/common.md

中的自动范围检测功能确定审计范围。

报告中的模式行：

Architecture Audit