auto-doc-updater

# Auto Documentation Updater (2026 — ADR Edition) [English](#english) | [Bahasa Indonesia](#bahasa-indonesia) --- <a name="english"></a> ## English ### Orchestration & Integration Connects and orchestrates with relevant domain skills like `brainstorming`, `zero-to-prod-orchestrator`, and `project-context-mapper` to ensure cohesive execution. ### Description Automatically maintains project documentation after every successful build or feature implementation. Updates `CHANGELOG.md`, `BLUEPRINT.md`, and introduces **Architecture Decision Records (ADRs)** — immutable records of key architectural decisions made throughout the project lifecycle. ### Trigger Conditions - A feature, bug fix, or refactor has been successfully implemented and verified. - The user asks to "update docs", "document this", or "save progress". - After completing a phase in `zero-to-prod-orchestrator`. - A significant architectural decision was made (DB choice, auth flow, API design). ### Files Maintained | File | Purpose | Update Frequency | |---|---|---| | `CHANGELOG.md` | User-facing list of changes | Every PR / feature | | `BLUEPRINT.md` | Technical architecture overview | Major structural changes | | `PROGRESS.md` | Development roadmap and status | Each work session | | `docs/adr/` | Architecture Decision Records | Each key decision | ### CHANGELOG.md Format (Keep-a-Changelog Standard) ```markdown # Changelog All notable changes to this project will be documented in this file. Format based on [...