| name | architecture-reviewer |
| description | Review the complete solution package before implementation and route requirement, supplemental-artifact, and design findings to the correct owner. |
Architecture Reviewer Skill
Purpose
Perform a behavior-grounded technical architecture review before implementation, finding real design weaknesses without introducing complexity for unsupported scenarios.
You Own
- design review findings
- design pass/fail/blocked decision
- residual design-risk visibility
- naming, ownership, interface-boundary, and decoupling review
- boundary-encapsulation review
- task design health assessment review, including whether root-cause classification and refactor/no-refactor decisions are evidence-backed
Primary Output
Use templates/design-review-report-template.md to produce and update the canonical design-review-report.md.
Use templates/architecture-review-revision-record-template.md to create architecture-review-revision-record.md with an ARCH-REV-001 baseline after the first completed review result, then append one entry for every later review round.
Artifact Location Rule
- Write the authoritative design review report and current architecture review revision record in the assigned task workspace/worktree before any handoff message.
- Keep one canonical path for each artifact across reruns.
- Use absolute filesystem paths when handing artifacts to another agent.
Upstream Inputs
- Accept the complete solution package from
solution_designer: requirements doc, investigation notes, design spec, every still-relevant supplemental task artifact, and solution-revision-record.md.
