docguard-reviewlisted

<!-- docguard:version: 0.34.9 --> # DocGuard Review Skill ## User Input ```text $ARGUMENTS ``` You **MUST** consider the user input before proceeding (if not empty). ## Goal Perform a comprehensive, **read-only** analysis of the project's documentation health. Unlike `/docguard.guard` (which runs CLI validators), this skill performs **semantic analysis** — checking whether documentation actually matches the codebase, whether cross-references are consistent, and whether the documentation tells a coherent story. ## Operating Constraints **STRICTLY READ-ONLY**: Do **not** modify any files. Output a structured analysis report only. Offer remediation suggestions that the user must explicitly approve before any changes are made. ## Execution Flow ### Step 1: Gather Documentation Inventory 1. **List all canonical docs**: Read every file in `docs-canonical/` 2. **List support files**: Check for `CHANGELOG.md`, `DRIFT-LOG.md`, `AGENTS.md`, `README.md`, `ROADMAP.md` 3. **Check for spec-kit artifacts**: If `.specify/` exists, include `specs/*/spec.md`, `specs/*/plan.md`, `specs/*/tasks.md` 4. **Build a document map**: | Document | Exists | Last Modified | Size | Metadata Version | |----------|--------|---------------|------|-----------------| | ARCHITECTURE.md | ✅ | 2026-03-14 | 5.2KB | 0.5.0 | | SECURITY.md | ✅ | 2026-03-14 | 3.1KB | 0.5.0 | | ... | ... | ... | ... | ... | ### Step 2: Run Quantitative Analysis Execute DocGuard's diagnostic and scoring tools: ```bash npx