architecture-review
Installation
SKILL.md
Architecture review
Find the choices that would make a design wrong, unsafe, or impossible to prove, while they are still cheap to change. Judge the decisions, not the document's length or format.
Reviewer
Someone who did not write the proposal: a fresh subagent, or another agent CLI run read-only (codex exec "<prompt>" or claude -p "<prompt>"). If neither is available, say review is blocked. The reviewer changes nothing.
Steps
- Read the proposal,
REQUIREMENTS.md,ARCHITECTURE.md, and the code, schemas, and config it touches. Check every claim about the current system against them. - Write down the problem, who it affects, the intended outcome, and the main tradeoff. Flag any the proposal leaves unclear.
- Walk one real request from input to what the user sees, including what happens when a step fails, is retried, or runs twice at once.
- Check data ownership, interfaces, migrations, rollback, security (auth, untrusted input, secrets), and the scale the proposal claims.
- Look for a simpler design that gets the same result with less state or fewer moving parts.
- Check that each important rule and failure has an acceptance check.