Architecture Audit

Clean-architecture audit for an existing codebase or module — dependency direction, layer/port/adapter boundaries, domain modeling, bounded-context seams, and cross-cutting concerns. Provenance lives in skill.json; this file is runtime routing only.

Produces: an audit-report.md (or audit-report-multi.md for all) plus a findings-ledger + workflow-state file when tracked.

Core principle

The dependency rule is the load-bearing invariant. Source-code dependencies point inward, toward more abstract code. If an outer concern (framework, ORM, HTTP, message broker) has reached into the domain or application core, that is a finding worth its severity — verify it against the structural graph, do not guess from names.

Activation