docs-vault-maintainer

Append concise iteration summaries to docs/operations/progress.md and update changelogs.

7|1|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/sparkeh9/DoclingDotNet --skill docs-vault-maintainer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-vault-maintainer
Source: https://github.com/sparkeh9/DoclingDotNet/tree/main/.agent/skills/docs-vault-maintainer
Command: npx skills add https://github.com/sparkeh9/DoclingDotNet --skill docs-vault-maintainer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps documentation lean by guiding concise iteration summaries and milestone-focused changes, avoiding high-churn doc overhead.

Core Features & Use Cases

  • Append concise progress entries to docs/operations/progress.md after each iteration.
  • Update docs/CHANGELOG.md only for milestone or contract/workflow changes.
  • Update docs pages selectively for public API/contract changes, CI/gating/workflow updates, or upstream upgrades.
  • If policies change, update AGENTS.md accordingly.

Quick Start

Document each iteration by appending a concise progress entry to docs/operations/progress.md.

Frequently Asked Questions about docs-vault-maintainer

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

FAQPage Schema
How do I keep documentation lean during iterative development?

To keep documentation lean during iterative development, append concise progress entries to docs/operations/progress.md after each iteration and update docs/CHANGELOG.md only for milestone or contract changes.

When should I update CHANGELOG.md versus progress.md for milestone releases?

Update docs/CHANGELOG.md for milestone or contract/workflow changes, while docs/operations/progress.md receives concise iteration summaries after every development cycle.

How do I manage documentation governance for CI workflow and upstream upgrade events?

Manage documentation governance for CI workflows and upstream upgrades by selectively updating docs pages for public API changes, CI gating updates, or upstream upgrades, and adjusting AGENTS.md when policies change.

What is the best way to track iteration progress without high-churn doc overhead?

Track iteration progress without high-churn doc overhead by enforcing concise iteration summaries and milestone-focused changes, appending brief entries to progress.md rather than rewriting full documentation pages.