architecture-maintainer

What problem does it solve?

Keeps system architecture documentation aligned with code and design changes so architecture drift, duplicated deep-dives, and missing update contexts are avoided for reviewers and future maintainers.

Core Features & Use Cases

• Index-plus-domain model: Uses a compact root architecture.md as an index and scoped domain docs for implementation detail.
• Change-to-doc mapping: Maps changed repository paths to the correct domain document(s) to limit updates to impacted areas.
• Delta and review hygiene: Requires concise delta blocks, link validation, and a scoped Definition of Done to make documentation updates small and reviewable.
• Use Case: When a database migration, background job, or auth boundary change is merged, use this skill to determine which domain docs require deltas and whether the root index needs a topology/invariants update.

Quick Start

Map changed files to their corresponding docs, append a short Delta: YYYY-MM-DD block to each impacted domain file, and update root architecture.md only if cross-cutting invariants or topology changed.