Architecture Docs Updater
This skill enforces that architecture docs are always authoritative and current.
Required Sources
Read these first:
- •
docs/architecture/architecture-baseline.md - •
docs/architecture/architecture-evolution.md - •
docs/architecture/README.md
Trigger Conditions
Use this skill when changes touch any of:
- •
lib/domain/*task/session contracts - •
lib/session/*orchestration and adaptation logic - •
lib/skills/*registry and skill definition shape - •
lib/generators/*generator pipeline and constraints - •
components/tasks/*rendering boundaries - •
lib/persistence/*storage boundaries or interfaces - •Any new discipline/skill framework
Workflow
- •Inspect changed files and determine architecture impact.
- •If architecture impact exists, update the docs in
docs/architecture/. - •Keep Mermaid diagrams aligned with as-is implementation.
- •Explicitly document:
- •stable contracts
- •extension seams
- •current gaps
- •migration implications (if any)
- •If no architecture impact exists, state that no doc update is required.
Output Contract
Provide:
- •What changed in architecture terms.
- •Which architecture docs were updated.
- •Why those updates preserve source-of-truth status.
Non-Negotiable Rule
If architecture changed and docs were not updated, work is incomplete.