docs-steward

Audit repository documentation drift and enforce placement rules.

1|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/flatrick/mdt --skill docs-steward
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-steward
Source: https://github.com/flatrick/mdt/tree/main/skills/docs-steward
Command: npx skills add https://github.com/flatrick/mdt --skill docs-steward

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of maintaining accurate, up-to-date, and well-organized documentation within a repository, preventing information drift and ensuring clarity for both human readers and AI systems.

Core Features & Use Cases

  • Documentation Auditing: Identifies and helps correct inconsistencies between different documentation surfaces (e.g., root READMEs, docs/ directory, runtime prompts).
  • Doc Placement Guidance: Provides rules for where specific types of documentation should reside (e.g., current truth in docs/, fast-find entrypoints at the root).
  • Stale Doc Management: Assists in removing or de-authorizing outdated documentation that may conflict with current information.
  • Verification Claim Management: Ensures that claims about tool capabilities or verification statuses are accurate and stamped with precise versions.

Quick Start

Use the docs-steward skill to audit documentation drift across the repository.

Frequently Asked Questions about docs-steward

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

FAQPage Schema
How do I audit documentation drift across multiple repository surfaces?

Documentation drift auditing identifies inconsistencies between root READMEs, dedicated docs directories, and runtime assets. This process classifies documentation types using a core taxonomy to maintain accuracy and prevent conflicting information across evolving project surfaces.

What is the best way to manage stale documentation in a repository?

Stale documentation management removes or de-authorizes outdated content that conflicts with current information. It enforces defined update workflows and placement rules to ensure readers only encounter accurate, actively maintained repository documentation.

Where should specific types of technical writing files reside in a project?

Technical writing placement rules dictate that current truth resides in dedicated docs directories, while fast-find entrypoints stay at the root. Enforcing this organization prevents information drift and clarifies repository structure for both humans and AI systems.

How do I ensure verification claims about tool capabilities are accurate?

Verification claim management ensures capability and status claims are accurate and stamped with precise versions. It audits runtime prompts and documentation surfaces to guarantee technical writing reflects the exact tool specifications currently deployed.

Can I use a content management steward for projects with evolving documentation needs?

A content management steward applies to projects with evolving documentation needs across multiple surfaces. It requires adherence to a core taxonomy for classifying documentation types and a defined workflow for managing ongoing updates.

Why does documentation accuracy degrade in repositories with multiple surfaces?

Documentation accuracy degrades due to drift between root files, dedicated docs directories, and runtime assets. Without stewardship enforcing placement rules and update workflows, evolving project information naturally diverges across these disparate surfaces.