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-1/
Architecture Audit: OrderFlow Order Management Platform
Background
Your team has taken over maintenance of OrderFlow, a Python-based order management platform that has been running in production for two years. The engineering lead wants a comprehensive architecture review before the team begins adding new features — specifically a returns and refunds module and a B2B wholesale pricing tier. There are growing concerns that the current structure is making changes risky and slow.
The codebase is at inputs/. It uses FastAPI, SQLAlchemy, and several internal service clients.
What You Need to Produce
Perform a full architecture audit of the entire OrderFlow codebase. The team spans multiple functional areas (API layer, domain logic, infrastructure, utilities, testing), so your audit must cover all of them.
Produce a written architecture audit report as audit_report.md. The report should cover the main structural issues you find, explain which problems to tackle first and why, and identify any areas where you lacked enough evidence to draw firm conclusions.
The team will use this report to plan their next two quarters of technical work.