architecture-maintainer

Update architecture documentation with delta blocks and link validation.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/alexwox/genesis-template --skill architecture-maintainer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-maintainer
Source: https://github.com/alexwox/genesis-template/tree/main/.cursor/skills/architecture-maintainer
Command: npx skills add https://github.com/alexwox/genesis-template --skill architecture-maintainer

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about architecture-maintainer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep architecture documentation updated when database schema or background job changes are merged?

To update architecture documentation after schema or background job merges, map changed repository paths to the correct domain document and append a concise delta block. Update the root architecture.md only if cross-cutting invariants or system topology changed.

What is the best way to structure architecture docs to prevent documentation drift?

The best way to prevent architecture drift is using an index-plus-domain model. Maintain a compact root architecture.md as an index, and store detailed implementation context in scoped domain-specific documents.

When do I need to update the root architecture.md file versus scoped domain docs?

Update scoped domain docs for localized changes like agent tools or frontend flows by adding delta blocks. Update the root architecture.md only when cross-cutting invariants, topology, or high-level entry points change.

How do I map code changes to the correct architecture documentation files?

Map code changes to architecture files by tracing changed repository paths to their corresponding domain documents. This limits documentation updates to only impacted areas, ensuring small and reviewable delta blocks.

Does maintaining architecture documentation require validating links and entry points?

Yes, maintaining architecture documentation requires validating links and entry points. This ensures documentation updates follow review hygiene and maintain a scoped Definition of Done for maintainers.