docs-manager

Audit, organize, and validate repository documentation governance and source-of-truth ownership.

3|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/ceasarXuu/AstartesSkills --skill docs-manager-ceasarxuu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-manager
Source: https://github.com/ceasarXuu/AstartesSkills/tree/main/skills/docs-manager
Command: npx skills add https://github.com/ceasarXuu/AstartesSkills --skill docs-manager-ceasarxuu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Repositories accumulate inconsistent documentation paths, duplicate sources of truth, stale links, and drifted indexes over time. This Skill audits and governs documentation structure without forcing a rigid layout or overriding specialized artifact-owner workflows like PRD or engineering-plan contracts. ## Core Features & Use Cases - Documentation Auditing: Builds a responsibility map identifying each document's purpose, owner workflow, source-of-truth status, and lifecycle stage. - Safe Migration & Archival: Moves or reorganizes docs while updating inbound references, release manifests, indexes, and CI, archiving superseded files instead of deleting them. - Drift Validation: Ships a Python validator that detects broken local Markdown links, missing release-manifest paths, and current-release references pointing into archives. - Use Case: After a repository restructure, run this Skill to find stale links, resolve two files both claiming to be the canonical PRD, and archive outdated release docs while preserving the existing planning workflow's contracts. ## Quick Start Use docs-manager to audit this repository's documentation, fix broken links and duplicate source-of-truth declarations, and archive superseded docs without changing the existing PRD or engineering-plan structure.

Frequently Asked Questions about docs-manager

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

FAQPage Schema
How do I audit and organize repository documentation?

Use docs-manager to inspect existing docs roots, build a responsibility map of each document's owner and source-of-truth status, then apply the minimum necessary change: fix stale links first, clarify ownership, archive superseded files, and only restructure when there is a concrete benefit.

How do I validate broken Markdown links in a repository?

Run the bundled validator with python3 scripts/validate_docs_manager.py --repo-root . It scans all Markdown files for broken local links, checks that release-manifest paths exist, and fails if current-release documents point into the archive.

Does docs-manager force a specific docs folder structure?

No. It preserves the repository's existing documentation contract and artifact-owner workflows by default. The version-trio layout (docs/v<version>/ with prd.md, technical-design.md, engineering-plan.md) is an opt-in profile only used when explicitly selected.

Can docs-manager migrate docs without breaking existing references?

Yes. During migration it updates inbound references, release manifests, indexes, CI, and scripts, avoids parallel copies of canonical artifacts, and archives rather than deletes superseded documentation unless deletion is explicitly requested.

When should I not use docs-manager?

Do not use it to author PRDs, engineering plans, implementation reports, or repository summaries when a specialized workflow owns those artifacts. It governs documentation structure and validation, not the semantic content of owned documents.