Analyze a software repository at the system and framework level, then write actionable architecture recommendations under `doc/software-architecture-recommendations.md`. Use when Codex needs to assess the project's main architecture, layering, module boundaries, framework choices, runtime topology, dependency direction, integration style, or evolution path without focusing on feature-level implementation details.
Inspect a repository from the architecture boundary inward, then produce a practical recommendation document under doc/.
Focus on structural design, framework fit, module relationships, and evolution strategy rather than business feature details.
README*, docs/, doc/, package manifests, build files, entrypoints, framework config, deployment config, and top-level source directories.doc/ if it does not exist.doc/software-architecture-recommendations.md.src/app, server/, packages/core, or cmd/api.Read these references before drafting:
事实, 判断, and 建议 when ambiguity matters.P0, P1, P2 only when they are justified by repository impact.待确认 instead of filling gaps with generic architecture language.doc/software-architecture-recommendations.md exists.