Where does it store project plans?

It uses a structured approach: current active plans live in docs/plans/active.md, detailed plans in docs/plans/details/, and completed or rejected plans are moved to docs/plans/archive/.

How does this skill handle README files?

It follows a 'thin root' philosophy, treating the root README as a fast-find entrypoint while delegating the exhaustive technical truth to the docs/ directory.

What is documentation drift?

Documentation drift occurs when the codebase changes but the documentation remains the same, leading to stale claims, broken links, or incorrect instructions that confuse developers and LLMs.

Can it verify if my code actually supports a feature?

Yes, the Documentation Steward includes rules to audit tool capability claims against local CLI behavior and evidence rather than just trusting adapter or configuration files.

Documentation Steward

Name: Documentation Steward
Author: flatrick

byflatrick

0•

学习与文档

Maintains repository documentation integrity by preventing drift, organizing file taxonomies, and auditing technical claims for accuracy.

The Documentation Steward skill transforms Claude into a proactive technical librarian for your codebase, ensuring that documentation remains a reliable single source of truth. It implements a rigorous framework for auditing Markdown drift, pruning stale information, and organizing content into a structured hierarchy that separates active plans from archived history and core documentation. By enforcing specific destination rules and verification workflows, it ensures that your repository remains navigable and accurate for both human contributors and AI agents, specifically optimizing how documentation is consumed during the development lifecycle.

主要功能

01Automates the propagation of technical truth from core docs to public-facing READMEs

020 GitHub stars

03Audits and resolves Markdown drift across root files, subdirectories, and runtime assets

04Validates tool capability claims against real-world CLI behavior and audited evidence

05Enforces a strict documentation taxonomy for entrypoints, truth, and planning

06Prunes obsolete or contradictory documentation to prevent developer confusion

使用场景

01Restructuring a messy repository to follow professional documentation standards

02Auditing technical claims before a commit to ensure docs match actual software versions

03Managing the transition of project plans from active development to historical archives

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add flatrick/mdt documentation-steward

For use in Claude.ai and ChatGPT