verify-doc-status

Audit ArenaQuest RFC, milestone, and task statuses against implementation.

1|1|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/RaphaelSilva/ArenaQuest --skill verify-doc-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-doc-status
Source: https://github.com/RaphaelSilva/ArenaQuest/tree/main/.claude/skills/verify-doc-status
Command: npx skills add https://github.com/RaphaelSilva/ArenaQuest --skill verify-doc-status

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that ArenaQuest product documentation is up-to-date, consistent, and aligned with the current implementation.

Core Features & Use Cases

  • Audit Documentation Status: Checks the status of RFCs, milestones, and tasks against implementation.
  • Status Normalization: Ensures that all statuses adhere to a single canonical vocabulary.
  • Cross-Reference Verification: Cross-checks status signals against each other and against the implementation.
  • Report-Only: Never edits files or modifies code, always points to files for editing.

Quick Start

Run the 'verify-doc-status' skill to audit the status of all product documentation.

Frequently Asked Questions about verify-doc-status

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

FAQPage Schema
How do I audit product documentation status against current code implementation?

You can normalize documentation status to a single canonical vocabulary by running the verify-doc-status script, which checks RFCs, milestones, and tasks to ensure all statuses adhere to standardized usage.

What is the best way to cross-check RFC and milestone status signals for inconsistencies?

No, documentation audit tools like this operate in report-only mode and never edit files or modify code, always pointing to files requiring manual editing instead.

Do I need Node.js to run scripts that check documentation and code alignment?

Yes, you need Node.js installed to run this documentation audit script, as it requires Node.js and specific command-line arguments to define different scopes and outputs for the verification process.

Why does my product documentation audit show non-canonical status usage errors?

Your product documentation audit shows non-canonical status usage errors because the script detected statuses in RFCs, milestones, or tasks that deviate from the single canonical vocabulary expected by the implementation.