skill_docs

Enforces metadata compliance and traceability across documentation artifacts including ADRs and invariants.

3|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/joshband/LocusQ --skill skill-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill_docs
Source: https://github.com/joshband/LocusQ/tree/main/.codex/skills/docs
Command: npx skills add https://github.com/joshband/LocusQ --skill skill-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documentation tends to drift, become inconsistent with specs and ADRs, and lose traceability. This skill enforces metadata hygiene and evidence logging to keep documentation lean, current, and auditable.

Core Features & Use Cases

  • Enforces canonical metadata presence (Title, Document Type, Author, Created Date, Last Modified Date) across markdown docs.
  • Maintains ADR hygiene by keeping ADRs as separate files named ADR-XXXX-... and linking them to related docs.
  • Ensures cross-references and traceability between specifications, invariants, and validation evidence.
  • Reduces duplication by promoting single-sourcing and clear governance policies.

Quick Start

Review and update documentation standards, ADRs, and validation evidence to ensure invariant traceability and metadata compliance.

Frequently Asked Questions about skill_docs

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

FAQPage Schema
How do I enforce required metadata fields across markdown documentation?

To enforce markdown documentation metadata compliance, validate the presence of Title, Document Type, Author, Created Date, and Last Modified Date fields across all artifacts to maintain consistency and auditability.

What is the best way to maintain ADR traceability and keep architecture decision records compliant?

Maintaining ADR traceability requires keeping architecture decision records as separate files named ADR-XXXX, then linking them to related specifications and validation evidence to ensure consistent governance and auditability.

How do I link validation evidence to specifications and invariants for governance audits?

Linking validation evidence to specifications requires enforcing cross-references between invariants and related artifacts, ensuring traceability across documentation to reduce duplication and maintain auditability.

Can I use documentation governance standards to reduce content duplication and drift?

Applying documentation governance standards reduces content duplication by promoting single-sourcing policies, enforcing metadata hygiene, and maintaining cross-references to prevent documentation drift and inconsistency.

When do I need to validate documentation artifacts for metadata compliance and traceability?

Validate documentation artifacts for metadata compliance and traceability whenever governance tasks involve ADRs, invariants, references, and validation evidence to maintain consistency and auditability across specs.

Why does documentation lose traceability and how do governance standards prevent it?

Documentation loses traceability when artifacts drift from specs and ADRs; governance standards prevent this by enforcing canonical metadata presence, maintaining separate ADR files, and validating cross-references.