sharaf/software-architecture-audit
Run an evidence-grounded software architecture audit workflow that builds a repo brief, selects single-auditor or specialist-panel mode, inspects boundary, layering, dependency, composition, cohesion, and testability risks, writes required finding blocks, and sequences incremental refactors. Use when asked for an architecture audit, architecture review, repo-structure review, software architecture report, audit_report.md, structural issue findings, or specialist-panel synthesis across multi-module systems.
100
100%
Does it follow best practices?
Impact
100%
1.85xAverage score across 3 eval scenarios
Passed
No known issues
task.mdevals/scenario-3/
Architecture Review: Nexus CMS
Background
Nexus CMS is a Node.js content management system used by a network of publisher websites. The engineering team is growing from two engineers to six, and the CTO has asked for a comprehensive architecture review before bringing on the new hires. The team needs to know where the structural problems are so that multiple squads can work on different parts of the system without constantly stepping on each other.
The system spans several distinct functional areas: content management, media handling, user authentication, and publishing workflows. The source is in inputs/.
What You Need to Produce
Produce a written architecture audit report as audit_report.md.
The report should cover all functional areas of the codebase. For each structural problem you identify, include the supporting evidence you found in the files. Make sure problems that share a common underlying cause are grouped under that root cause rather than listed as unrelated issues. Finish with a sequenced list of recommended improvements — starting with whichever change will most safely unblock the others.