Use `analysis-agent` for module-boundary or dependency-direction analysis, or `review-agent` for independent assessment of a bounded architecture artifact. Skip isolated owner-internal edits with no structural impact.
Installs into .claude/skills of the current project.
Are you the author of Architecture Impact Reviewer?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/machenjie-architecture-impact-reviewer)
---
name: architecture-impact-reviewer
description: "Use `analysis-agent` for module-boundary or dependency-direction analysis, or `review-agent` for independent assessment of a bounded architecture artifact. Skip isolated owner-internal edits with no structural impact."
---
# architecture-impact-reviewer
## Role
- **Analysis mode (`analysis-agent`):** select a source-backed placement without claiming edits or approval.
- **Review mode (`review-agent`):** independently return `Approved`, `Returned`, or `Blocked`; never repair the artifact.
## When To Use
- module boundary change
- dependency direction risk
- owner-internal implementation structure reuse or deliberate separation remains unresolved
## Do Not Use
- isolated owner internal edit after placement is fixed
- no structural impact
## Required Inputs
- desired behavior
- module and dependency boundary
- **Analysis mode (`analysis-agent`):** candidate ownership, dependency, consumer, and reuse evidence.
- **Review mode (`review-agent`):** bounded architecture artifact, placement criteria and supporting evidence.
## Professional Decision Rules
- Preserve placement with its declared owner.
- Select named References for active consumer/data, dependency/enforcement, reversibility, or alternative risks.
- Record public/private surface and authority.
## High-Value Gotchas
- Directory proximity, framework layers, and team names do not prove semantic ownership.
- A local compile does not prove indirect-consumer, data-ownership, or dependency-direction safety.
- An abstraction that obscures authority or deletion cost is not a safer boundary.
## Execution Checklist
- **Analysis mode:** Map the current owner, public/private surface, consumers, data authority, dependencies, and smallest viable placement.
- **Review mode:** Verify placement, dependency direction, enforcement, reversibility, and unreviewed structural risk against current evidence.
- Reject a boundary whose owner, affected consumers, evolution path, or material alternative remains unsupported.
## Stop / Escalation Conditions
- Stop structural decisions missing applicable owner, surface, dependency, data, reversibility, or smaller-alternative evidence.
- Reuse authorization for ordinary read/search and respect Host permissions. For an inspected mutating or sensitive operation, require the applicable scope, recovery, and redaction evidence; these read-only roles do not perform the mutation.
- A blocked review names the missing evidence, unblock condition, repair owner, and handoff.
## Output Contract
- placement decision, architecture verdict, and structural risk
- **Analysis mode (`analysis-agent`):** placement decision, rejected alternatives, and dependency and consumer impact.
- **Review mode (`review-agent`):** architecture verdict, boundary findings, and unreviewed structural risk.
## Targeted References
| Path | Type | Load when | Do not load when | Required by | Required output |
|---|---|---|---|---|---|
| [placement and ownership](references/placement-and-ownership.md) | targeted | Structure responsibility ownership reuse or placement remains open | Owner public/private surface and smallest viable placement are fixed by current evidence | analysis-agent, review-agent | boundary-decision, selected-approach, residual-risk |
| [consumer and data impact](references/consumer-and-data-impact.md) | targeted | Public or indirect consumer or authoritative-data impact remains open | No consumer contract compatibility versioning migration or data-owner boundary changes | analysis-agent, review-agent | boundary-decision, validation-plan, residual-risk |
| [dependency topology and enforcement](references/dependency-topology-and-enforcement.md) | targeted | Dependency direction topology or durable enforcement remains open | Current source edges topology owner and enforcement evidence already fix the boundary | analysis-agent, review-agent | boundary-decision, gate-decision, validation-plan, residual-risk |
| [reversibility evolution and proof limits](references/reversibility-evolution-and-proof-limits.md) | targeted | Reversal coexistence migration evolution or architecture proof limits remain open | Current evidence fixes reversibility evolution residual risk and next owner | analysis-agent, review-agent | decision-record, validation-plan, proof-limit, residual-risk |
| [checklist](references/checklist.md) | decision-checklist | A bounded mode needs compact checks for its triggered placement, ownership, dependency, consumer, data, topology, or reversibility risk | The root contract is enough or targeted proof fields are required | analysis-agent, review-agent | checklist-result, residual-risk |
| [index](references/index.md) | index | competing architecture impact reviewer references require dependency, conflict, or output-fragment selection | the architecture impact reviewer root or a task-named reference already resolves selection | analysis-agent, review-agent | reference-selection |
| [solution optimality](references/solution-optimality.md) | targeted | An architecture boundary, ownership, dependency, topology, or operational-responsibility decision has a material alternative | The change is owner-internal with no structural impact or current evidence already fixes placement | analysis-agent, review-agent | selected-approach, residual-risk |