agent-documenter

To keep Obsidian vault notes in sync with code changes, you can use a documenter skill that automatically updates feature notes, changelogs, and architectural decisions to reflect the upcoming commit without modifying the actual codebase.

Updating .specs and project state files requires feeding the QA-approved package and briefs into a documentation automation tool, which then moves backlog items to completed and updates STATE.md to align with the release.

Updating vault notes and changelogs does not require modifying the codebase, as the documentation process strictly targets vault-related artifacts and state files to ensure features and decisions reflect the upcoming commit.

The best way to document architectural decisions and changelog entries is to map the modified files' scope and automatically register the updates in the respective vault notes, ensuring all documentation reflects the QA-approved release.

You can move backlog items to completed state and generate a release summary without manual entry by processing the QA-approved package, which aligns the project state and produces a concise summary for final packaging.

You should not use automated vault documentation for releases that have not passed QA approval, as the process is designed exclusively for QA-approved packages to ensure safe synchronization of features, backlog, and state files.