Architecture Review
Purpose
Evaluate whether system structure supports the stated product and operational needs, using repository evidence rather than generic pattern scoring.
Workspace protocol
Read references/workspaces.md once per agent task before selecting or creating workflow artifacts; reuse it unless repository scope or task authority changes. This skill owns only the task-specific behavior below.
Inputs
- Goals, constraints, quality attributes, diagrams or proposals
- Current modules, dependencies, data flows, deployment topology, and ownership boundaries
- Known scale, failure modes, and change scenarios
Outputs
- Current-state model and material architectural findings
- Tradeoff analysis with prioritized recommendations
- Explicit assumptions, residual risks, and staged options when change is warranted
Rules
- Read
references/finding-rubric.md before emitting defects intended for remediation; keep tradeoff advice that does not cross the finding threshold in recommendations.
- Start from desired capabilities and likely changes, not fashionable architecture.
- Trace dependency direction, state ownership, contracts, failure propagation, and operational boundaries.
- Separate structural problems from local code-quality issues.
- Quantify scale or cost claims when evidence exists; label estimates otherwise.
- Prefer incremental, reversible improvements and describe migration cost.
- Remain read-only unless implementation is explicitly requested.
Decision-log updates
Record accepted boundaries, ownership, technology choices, quality-attribute priorities, and deliberately accepted coupling or debt. Capture alternatives and migration consequences.
When durable state is approved, append structural tradeoffs or accepted architecture risk to the selected work item's decisions.md and track actionable defects in findings.md; otherwise report them in the final response.
Escalate to the human
Escalate when priorities conflict, ownership is unclear, a recommendation commits the team to major platform or vendor cost, or missing product and operational constraints prevent a defensible recommendation.
1---2name: architecture-review3description: Use when architecture is the primary review objective for boundaries, coupling, ownership, scalability, resilience, maintainability, or long-term change cost; use review for a general defect review.4---56# Architecture Review78## Purpose910Evaluate whether system structure supports the stated product and operational needs, using repository evidence rather than generic pattern scoring.1112## Workspace protocol1314Read `references/workspaces.md` once per agent task before selecting or creating workflow artifacts; reuse it unless repository scope or task authority changes. This skill owns only the task-specific behavior below.1516## Inputs1718- Goals, constraints, quality attributes, diagrams or proposals19- Current modules, dependencies, data flows, deployment topology, and ownership boundaries20- Known scale, failure modes, and change scenarios2122## Outputs2324- Current-state model and material architectural findings25- Tradeoff analysis with prioritized recommendations26- Explicit assumptions, residual risks, and staged options when change is warranted2728## Rules2930- Read `references/finding-rubric.md` before emitting defects intended for remediation; keep tradeoff advice that does not cross the finding threshold in recommendations.31- Start from desired capabilities and likely changes, not fashionable architecture.32- Trace dependency direction, state ownership, contracts, failure propagation, and operational boundaries.33- Separate structural problems from local code-quality issues.34- Quantify scale or cost claims when evidence exists; label estimates otherwise.35- Prefer incremental, reversible improvements and describe migration cost.36- Remain read-only unless implementation is explicitly requested.3738## Decision-log updates3940Record accepted boundaries, ownership, technology choices, quality-attribute priorities, and deliberately accepted coupling or debt. Capture alternatives and migration consequences.41When durable state is approved, append structural tradeoffs or accepted architecture risk to the selected work item's decisions.md and track actionable defects in findings.md; otherwise report them in the final response.4243## Escalate to the human4445Escalate when priorities conflict, ownership is unclear, a recommendation commits the team to major platform or vendor cost, or missing product and operational constraints prevent a defensible recommendation.
nono911