verify-claimslisted

<!-- Adapted from pedrohcgs/claude-code-my-workflow (MIT), https://github.com/pedrohcgs/claude-code-my-workflow --> # /verify-claims — Chain-of-Verification on a Draft Fact-check a draft using the **Post-Flight Verification protocol**. This skill is where that protocol lives; [`.claude/rules/post-flight-verification.md`](../../rules/post-flight-verification.md) is the trigger rule that points here. **Input:** `$ARGUMENTS` — path to a file containing the draft (markdown, .qmd, .tex, .md) or a shorthand pointer. Optional flags: - `--source <path-or-url>` — one or more source-material pointers (repeat for multiple). If omitted, the skill infers from context (e.g., papers referenced, cited arXiv URLs). - `--no-fail-closed` — downgrade FAIL outcomes to warnings without regeneration. Use sparingly. ## When to pick this skill - **`/verify-claims`** (this skill) — ad-hoc fact-checking on any draft or text block the user hands you. One-shot, user-invoked. - **Other skills that auto-run Post-Flight internally** (`/lit-review`, `/research-ideation`, `/respond-to-referees`, `/review-paper --peer`) — no need to call this separately; they already run it. - **`/proofread`** — grammar, typos, overflow. Different lens. - **`/review-paper`** (default mode) — full manuscript review, not just claim verification. ## How it works Implements the 4-step CoVe loop from Dhuliawala et al. 2023 ([arXiv:2309.11495](https://arxiv.org/abs/2309.11495)), with architectural enforcement of the fresh-c