architecture-doc-sync

To keep architecture documentation aligned with code, this skill consumes design notes and implementation summaries to update module boundaries, ADR statuses, and dependency graphs, preventing architectural drift.

Architectural drift occurs when design notes, ADRs, and implementation details become misaligned with the codebase. You prevent it by synchronizing architecture documents using evidence-based updates from upstream artifacts.

You can update ADRs and module boundaries by running a synchronization workflow that consumes implementation summaries to verify consistency and apply necessary changes to architecture documentation.

Yes, you can generate an architecture-sync-report that captures touched documents, consumed artifacts, and consistency checks to maintain full traceability of architecture updates.

The best way to verify consistency is to consume both design-note and implementation-summary artifacts, derive necessary updates, and cross-check documentation against actual codebase changes.

Yes, you need upstream artifacts like design-note.md and implementation-summary.md to drive evidence-based updates and ensure architecture documentation accurately reflects the current implementation.