maintain-docs

Detect documentation drift against filesystem state and create new docs through structured interviews.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/nickgogan/improvement-loop --skill maintain-docs-nickgogan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: maintain-docs
Source: https://github.com/nickgogan/improvement-loop/tree/main/.claude/skills/maintain-docs
Command: npx skills add https://github.com/nickgogan/improvement-loop --skill maintain-docs-nickgogan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Documentation drifts out of sync with the actual system as agents, skills, and directories change, leaving stale counts, broken paths, and missing references that mislead collaborators. ## Core Features & Use Cases - Update Mode: Compares documented state (CLAUDE.md, agent definitions, skill contracts, governance docs) against actual filesystem state, produces a drift report, and applies factual fixes directly. - Create Mode: Interviews the user with focused questions to draft new documentation (system overviews, knowledge guides, operational references) and presents drafts for approval before writing. - Use Case: After adding three new skills to a system, run update mode to fix skill counts in CLAUDE.md, repair broken cross-references, and flag undocumented areas needing create mode. ## Quick Start Run the maintain-docs skill in update mode to check all documentation surfaces for drift and fix any factual inaccuracies found.

Frequently Asked Questions about maintain-docs

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

FAQPage Schema
How do I detect documentation drift in a project?▼

Run update mode, which reads each documentation surface and compares it against actual filesystem state using Glob and Grep. It produces a drift report listing mismatched counts, broken paths, and missing entries, then applies factual fixes directly.

How do I create new documentation for an undocumented system area?▼

Use create mode with a target, which interviews you with focused questions tailored to the document type (system overview, knowledge guide, or operational reference). It drafts the document and waits for your approval before writing.

When should I run a documentation update check?▼

Run it after structural changes like adding agents, skills, or directories, after a system audit flags drift, or periodically to verify docs match reality. Skill counts in CLAUDE.md are the most common drift source.

What documentation does this skill not handle?▼

It does not write research findings, create governance translations, propose structural changes, or modify workspace-root constitutional docs like CHARTER.md. Those belong to other skills or require human approval.

Does update mode rewrite documentation style or prose?▼

No. Update mode only fixes factual errors such as counts, lists, and broken paths. It preserves the original author's voice and does not reorganize sections unless factual accuracy requires it.