assurance-roadmap-check

Validate assurance roadmap item statuses against repository activity and documentation.

5|Updated Mar 4, 2026

Search Tags:#documentation #verification #roadmap #repository #status #drift

Ready to run

npx skills add https://github.com/nicholls-inc/claude-code-marketplace --skill assurance-roadmap-check

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: assurance-roadmap-check
Source: https://github.com/nicholls-inc/claude-code-marketplace/tree/main/crosscheck/skills/assurance-roadmap-check
Command: npx skills add https://github.com/nicholls-inc/claude-code-marketplace --skill assurance-roadmap-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps maintain accurate and truthful status tracking across assurance roadmap documents to prevent drift and miscommunication.

Core Features & Use Cases

Status Validation: Cross-checks declared statuses in docs/assurance/**/*.md against actual repository activity and artifacts.
Drift Detection: Identifies overclaims, underclaims, outdated progress, missing reasons, and malformed entries within roadmap documentation.
Use Case: When managing a project tailing multiple assurance items, this Skill automatically verifies each item's current reality versus declared status to ensure project consistency.

Quick Start

Use the assurance-roadmap-check skill to verify the current statuses of all roadmap items and identify any drift in the documentation.

Frequently Asked Questions about assurance-roadmap-check

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

FAQPage Schema

How do I verify the declared statuses in my project roadmap documentation?▼

To verify roadmap documentation statuses, you cross-check declared items against actual repository activity. This process analyzes documentation and artifacts to detect drift, overclaims, or underclaims, flagging any deviations for correction.

What is roadmap drift detection in project documentation?▼

Roadmap drift detection identifies overclaims, underclaims, outdated progress, missing reasons, and malformed entries within roadmap documentation. It ensures declared statuses match the actual project state, preventing misreporting and tracking errors.

How do I check if my assurance roadmap items match actual repository activity?▼

You check assurance roadmap items by analyzing documentation within the docs/assurance directory against current repository activity. This validation confirms status fields correctly reflect project reality and highlights inconsistencies for correction.

Can I automatically flag outdated progress in my project roadmap markdown files?▼

Yes, you can automatically flag outdated progress and malformed entries in markdown roadmap files. Validating status fields against actual project artifacts detects inconsistencies and flags deviations for correction.

Why do my declared project statuses show tracking errors and misreporting?▼

Declared project statuses show tracking errors when roadmap documentation drifts from actual repository activity. Status validation cross-checks declared items against real artifacts to identify overclaims and underclaims, preventing misreporting.

What is the best way to maintain accurate status tracking across multiple assurance roadmap items?▼

The best way to maintain accurate status tracking is to automatically verify each item's current reality versus its declared status. This prevents drift and miscommunication by validating status fields and flagging deviations for correction.