doc-versioning-discipline
Keep living documents trustworthy over time — the status header (draft/active/superseded) that tells readers what they're holding, the change-log-for-decisions inside the doc, the supersession chain that kills zombie versions, and the review-date heartbeat. Use when asked which version of this doc is current, our wiki is full of stale pages, set up doc lifecycle rules, or people keep following the old process doc. Produces the status-header standard, the in-doc change log, the supersession protocol, and the staleness heartbeat.
npx skills add mohitagw15856/pm-claude-skills --skill doc-versioning-discipline --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Doc Versioning Discipline Skill Documents don't announce their own death — the old process doc reads exactly as confidently as the new one, and readers follow whichever they found first. Trust in a doc system is a *metadata* problem: every living doc carries a status header (what am I holding — draft? active? superseded-by-X?), meaningful changes get logged inside the doc (decisions, not typo-fixes), superseded versions get killed properly (pointer left behind, per the [version-chaos-untangler](../version-chaos-untangler/SKILL.md) rule), and a review date gives every doc a heartbeat — because "current as of when?" is the question every reader silently asks. ## What This Skill Produces - **The status-header standard** — the four-line block every living doc carries: status, owner, last-reviewed, supersedes/superseded-by - **The in-doc change log** — decision-grade changes only, newest first, with the why - **The supersession protocol** — how a doc dies: pointer installed, links redirected, search de-weighted where possible - **The heartbeat** — review dates by doc class, and the stale-flag that fires when they lapse ## Required Inputs Ask for these if not provided: - **The doc popu
- What This Skill Produces
- Required Inputs
- Framework: The Trust Rules
- Output Format
- The Status Header (standard)
- The Change Log Rule
- Supersession Protocol
- The Heartbeat
- Quality Checks
- Anti-Patterns
What does the doc-versioning-discipline skill do?
Keep living documents trustworthy over time — the status header (draft/active/superseded) that tells readers what they're holding, the change-log-for-decisions inside the doc, the supersession chain that kills zombie versions, and the review-date heartbeat. Use when asked which version of this doc is current, our wiki is full of stale pages, set up doc lifecycle rules, or people keep following the old process doc. Produces the status-header standard, the in-doc change log, the supersession protocol, and the staleness heartbeat.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill doc-versioning-discipline --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.