document

Trace documentation claims to code, specs, or upstream documents.

8|Updated Feb 2, 2026

Search Tags:#versioning #documentation #verification #drift #code #documentation-quality #source-of-truth

Ready to run

npx skills add https://github.com/usurobor/cnos --skill document-usurobor

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: document
Source: https://github.com/usurobor/cnos/tree/main/src/packages/cnos.eng/skills/eng/document
Command: npx skills add https://github.com/usurobor/cnos --skill document-usurobor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documentation often drifts from reality when claims are not anchored to verifiable sources. This Skill enforces coherence by ensuring every assertion traces to code, specs, or upstream documents and becomes a single source of truth for the project.

Core Features & Use Cases

Trace every claim to a source of truth (code, spec, upstream doc) before writing.
Verify claims before writing and after editing to maintain consistency across READMEs, architecture docs, and specs.
Remove stale claims and ensure versioned, testable documentation that matches the current implementation.

Quick Start

Identify a claim in a doc, verify it against the source of truth, and update the documentation accordingly.

Frequently Asked Questions about document

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

FAQPage Schema

How do I prevent documentation drift from code changes?▼

Prevent documentation drift by tracing every claim to a source of truth like code or specs, verifying assertions before writing and after editing to maintain consistency across READMEs and architecture docs.

What is a source of truth in technical documentation?▼

A source of truth in documentation is the verifiable origin of a claim, such as source code, specifications, or upstream documents, ensuring every written assertion accurately reflects the current implementation reality.

How do I verify README claims against source code?▼

Verify README claims by identifying specific assertions, tracing them directly to the source code or upstream specs, and updating the documentation to match the verified implementation before and after edits.

How do I remove stale content from architecture docs?▼

Remove stale content from architecture docs by verifying each claim against the current codebase or specs, deleting unverified assertions, and maintaining only versioned, executable examples that match the implementation.

Does documentation versioning work without executable examples?▼

Documentation versioning without executable examples risks drifting from reality. Maintaining versioned, testable examples ensures the documentation remains a verifiable source of truth that matches the current implementation.