Repository Architecture Review: Ownership & Boundaries

When one feature change touches unrelated modules, it is hard to know where the real problem lives. Get an evidence-backed architecture review showing unclear ownership, conflicting rules, and targeted improvements instead of a broad rewrite.

What it does

• Maps responsibilities: Explains what major modules own and where important rules belong.
• Finds structural risks: Identifies duplicated concepts, scattered policies, unclear boundaries, and departures from documented decisions.
• Explains change impact: Shows why a single concept change may require edits across several modules.
• Prioritizes improvements: Delivers findings with concrete locations and a phased refactor plan.
• Accounts for context: Distinguishes new problems from documented compromises and flags uncertainty when evidence is incomplete.

How it works

1. Point the assistant at a local repository and describe the architecture question.
2. Ask for a repository-wide review or focus on a specific concept or boundary.
3. Receive an architecture map, prioritized findings, and recommended next steps.
4. Decide which changes to approve. Review alone does not modify code.

Works with

Local code repositories, architecture documents, configuration files, and decision records. The review is general-purpose rather than tied to a particular language or framework.

Why use this skill

It helps developers and technical leads choose smaller refactors with clearer ownership. Location-based findings make recommendations easier to discuss and turn into scoped work.

Use cases

• Assess ownership before adding a new workflow.
• Investigate business rules duplicated across services.
• Compare implementation with architecture decisions.
• Plan incremental cleanup of tangled module boundaries.

Known limitations

Requires repository access for evidence-backed findings. It does not replace bug-focused code review, testing review, or performance analysis.