repo-docs

To keep repository documentation synchronized with source code, apply a doc-first workflow skill that reads plans and specs before code changes, automates auditing, and enforces relative markdown linking to eliminate drift.

A doc-first workflow requires reading AGENTS.md, work-in-progress documents, plans, and specs in a defined order before making any code changes, ensuring documentation drives development and stays perfectly aligned.

You can automatically generate a docs folder structure by asking the skill to bootstrap the documentation scaffold, which creates the full /docs directory with essential files and progressive disclosure links when missing.

To audit repository documentation for drift, run the /repo-docs-audit command, which validates synchronization between specs and code, reports updated spec paths, and automates plan archiving without manual intervention.

Yes, you can enforce relative markdown linking and progressive disclosure by applying this skill to manage plans and specs with strict naming and linking rules, maintaining documentation structure automatically during development.

Repository documentation drifts from source code because manual updates are tedious and often skipped, requiring an automated synchronization tool that enforces a doc-first workflow and validates spec paths during audits.