13-DOCS-verify

Verify documentation completeness and accuracy against an outline and code changes.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/medtrics/medtrics-acumen --skill 13-docs-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 13-DOCS-verify
Source: https://github.com/medtrics/medtrics-acumen/tree/main/templates/shared/skills/13-DOCS-verify
Command: npx skills add https://github.com/medtrics/medtrics-acumen --skill 13-docs-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that all necessary documentation has been written and is accurate by cross-referencing it against a predefined outline, preventing gaps and outdated information.

Core Features & Use Cases

  • Completeness Verification: Compares written documentation against docs-outline.md to identify missing items.
  • Staleness Check: Detects documentation that contradicts recent code changes.
  • Cross-feature Validation: Ensures documentation covers interdependencies between features.
  • Use Case: After writing documentation for a new feature, use this Skill to confirm that every aspect outlined in the discovery phase has been documented and that existing documentation remains accurate.

Quick Start

Verify the completeness of all documentation against the outline.

Frequently Asked Questions about 13-DOCS-verify

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

FAQPage Schema
How do I verify documentation completeness against an outline?

To verify documentation completeness, compare written files against a predefined outline to identify missing items. This process cross-references existing documentation to ensure all specified items are present and accurately reflect recent code changes.

What is documentation staleness detection and how does it work?

Documentation staleness detection identifies written content that contradicts recent code changes. It works by cross-referencing existing documentation files against code modifications to pinpoint outdated information that requires updating.

How do I check technical writing for cross-feature consistency?

Checking technical writing for cross-feature consistency involves validating that documentation covers interdependencies between features. This ensures written content accurately reflects how different features interact within the broader system.

Do I need a docs-outline.md file to review content for missing items?

Yes, you need a docs-outline.md file to review content for missing items. The outline serves as the baseline reference required to cross-check existing documentation files and verify that all specified features are documented.

When should I run a documentation quality assurance check?

Run a documentation quality assurance check after writing documentation for a new feature. This confirms that every aspect outlined in the discovery phase has been documented and that existing documentation remains accurate against code changes.