Docs Vault Maintainer
Purpose
Preserve useful documentation without high-churn doc overhead.
When to use
- •Every implementation iteration (for concise progress entry).
- •Milestone-level behavior/process/contract changes.
- •CI/workflow or upgrade-process changes.
Required actions
- •Always append one concise entry to
docs/05_Operations/Progress/progress.md:- •
Changed - •
Validation - •
Next
- •
- •Update
docs/CHANGELOG.mdonly for milestone/significant changes. - •Update
docs/pages only when one of these changes:- •public API/contract behavior
- •CI/gating/workflow behavior
- •upstream-upgrade process
- •If process policy changes, update
AGENTS.mdand this skill.
Default behavior
- •Prefer no broad docs sweep per small slice.
- •Avoid touching multiple docs files for routine internal implementation increments.
- •Keep iteration-level detail in
docs/05_Operations/Progress/progress.mdonly.
Completion gate
- •Iteration is documented when concise
docs/05_Operations/Progress/progress.mdentry exists. - •Milestone/contract/workflow changes also require:
- •
docs/CHANGELOG.mdupdate - •targeted doc page update(s) only where needed.
- •