documentation-management

Detect documentation drift and update project docs and README.

1|Updated Dec 14, 2025
One-click install
npx skills add https://github.com/mgkyawzayya/claude-code-usage-flow --skill documentation-management-mgkyawzayya
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: documentation-management
Source: https://github.com/mgkyawzayya/claude-code-usage-flow/tree/main/.claude/skills/documentation-management
Command: npx skills add https://github.com/mgkyawzayya/claude-code-usage-flow --skill documentation-management-mgkyawzayya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeping project documentation aligned with evolving code and features can be error-prone. This Skill ensures docs stay current, reducing confusion and misalignment across teams.

Core Features & Use Cases

  • Change detection: Identify documentation gaps whenever features or models change.
  • Targeted updates: Update docs/project-overview-pdr.md, docs/codebase-summary.md, code-standards, system-architecture as needed.
  • Documentation hygiene: Verify README length constraints and link integrity.

Quick Start

Run the documentation-management skill after a feature update to refresh the relevant docs:

  • Update project-overview-pdr.md with a concise feature summary.
  • Validate README length to stay under 300 lines.

Frequently Asked Questions about documentation-management

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

FAQPage Schema
How do I keep documentation in sync when code changes?

Documentation drift occurs when code evolves but docs lag behind. This Skill detects changes in features, models, and architecture, then updates project-overview-pdr.md, codebase-summary.md, code-standards, and system-architecture files automatically to reflect current behavior.

What files does documentation management update?

The Skill targets the docs/ directory and root README, specifically project-overview-pdr.md, codebase-summary.md, code-standards.md, and system-architecture.md. It verifies links, enforces README line limits under 300 lines, and applies concise edits.

Can I automate README validation and link checking?

Yes. The Skill validates README length constraints, verifies internal and external links, and ensures paths are current. It runs after feature or architecture updates to catch broken references and enforce documentation hygiene standards.

When should I run documentation updates after code changes?

Run the Skill after implementing new features, adding models or controllers, changing patterns, updating architecture, or modifying setup. It identifies gaps between code behavior and existing documentation, then applies targeted updates to keep docs current.

Does this work with markdown and version-controlled repositories?

Yes. The Skill operates on markdown files in version-controlled docs/ directories and README files. It uses Read, Edit, Write, and Grep tools to detect changes and make concise, targeted edits across your repository.

What's the difference between updating docs manually vs. automated detection?

Manual updates are error-prone and miss edge cases. Automated change detection identifies documentation gaps systematically whenever features or architecture shift, ensuring consistency across project-overview, codebase summary, standards, and architecture docs.