---
name: architecture
description: "Understand module boundaries, dependencies, data flow, public interfaces, and risks before making structural changes."
---

# Architecture Skill

Understand existing boundaries and dependencies before proposing structural changes; useful for large repositories.

## Subagents
When you need to delegate sub‑tasks, use the `pi-subagents` skill.

**Example:** For a large codebase, you might spawn a **scout** to map module boundaries in the `auth` package, another **scout** to trace data flow in the `payment` pipeline, and a **reviewer** to verify that the proposed interface changes don't break downstream consumers—all running in parallel.

*You may adapt the delegation pattern to fit the exact requirements of the codebase.*

## Analysis

### 1. Module Boundaries
- Identify public vs private APIs
- Find circular dependencies
- Map ownership areas

### 2. Dependencies
- External vs internal deps
- Dependency direction
- Coupling strength

### 3. Data Flow
- Trace key data paths
- Identify transformation points
- Find single sources of truth

### 4. Public Interfaces
- Document stable contracts
- Identify breaking change risks
- Plan migration strategies

### 5. Risks
- Migration complexity
- Testing implications
- Rollback feasibility