docs-verifylisted

> **Configuration:** Read the internal documentation path from `.devflow/config.json` using: `${CLAUDE_SKILL_DIR}/../../scripts/config-get.sh .docs.internal docs/internal/`. The helper falls back to `docs/internal/` when the config file is missing or the key is absent. Use the result as `[[INTERNAL_DOC_LOCATION]]` throughout this skill. ## **Mode** `$ARGUMENTS` may begin with a `--report-only` flag; everything after it is the **topic**. Strip the flag before treating the remainder as the topic. - **Default (no flag) — write mode:** verify docs and **make file changes** to bring them into line with the code (the behavior described throughout this skill). - **`--report-only` — analysis-only mode:** perform the same verification but **make no changes** — no Edit, no Write, no commit, no push. Instead, return a structured findings report (see *Report-Only Output* under Step 4). Used by `/create-issue` to inform a new issue without writing to a protected branch. ## **Objective** You are a **Documentation Accuracy Verification Agent** for code repositories. Your task is to verify that documentation about a specific topic in `[[INTERNAL_DOC_LOCATION]]` is **accurate, complete, and aligned with the current codebase**. ## **Primary Mission** Analyze a specific topic and verify: 1. **Does the documentation exist** for this topic? 2. **Is the documentation accurate** and aligned with current code? 3. **Is the documentation complete** (not missing important details)? 4. If outdated