nw-roadmap-review-checks

Execute six mandatory roadmap checks for implementation readiness in architecture reviews.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/StudentCristian/nWave-github --skill nw-roadmap-review-checks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nw-roadmap-review-checks
Source: https://github.com/StudentCristian/nWave-github/tree/main/.github/skills/nw-roadmap-review-checks
Command: npx skills add https://github.com/StudentCristian/nWave-github --skill nw-roadmap-review-checks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Roadmap reviews often miss critical quality gates; this Skill provides a standardized set of six validations to ensure architecture reviews yield actionable, implementable findings.

Core Features & Use Cases

  • External Validity: ensure steps produce an invocable feature with proper integration points and driving tests where applicable.
  • AC Implementation Coupling: detect when acceptance criteria expose internal structure or make code assumptions that hamper flexibility.
  • Step Decomposition Ratio: compare implementation steps to unique production files to avoid overly granular or under-defined steps.
  • Implementation Code in Roadmap: prevent embedding executable code or direct implementation details in roadmap descriptions.
  • Roadmap Concision and Precision: enforce concise, precise criteria with limited optional text, focusing on testable outcomes.
  • Unit Test Boundary Validation: ensure tests and driving ports are respected, avoiding private or internal API tests.

Quick Start

Run the six roadmap checks during reviews to generate actionable findings for implementation readiness.

Frequently Asked Questions about nw-roadmap-review-checks

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

FAQPage Schema
How do I validate roadmap readiness for architecture reviews?

You validate roadmap readiness by executing six mandatory checks covering external validity, implementation coupling, step decomposition, code-free roadmaps, concision, and unit-test boundary validation to ensure actionable architecture findings.

What are the mandatory checks for a roadmap review?

The six mandatory roadmap review checks are external validity, acceptance criteria implementation coupling, step decomposition ratio, implementation code in roadmap, roadmap concision and precision, and unit test boundary validation.

How do I prevent acceptance criteria from exposing internal code structure?

Acceptance criteria implementation coupling checks detect when criteria expose internal structure or make code assumptions that hamper flexibility, ensuring architecture reviews yield actionable and implementable findings.

How do I validate unit test boundaries in a roadmap?

Unit test boundary validation ensures tests and driving ports are respected during roadmap reviews, avoiding private or internal API tests to maintain proper architecture integration boundaries.

Can I check if my roadmap steps are too granular for the production files?

Step decomposition ratio compares implementation steps to unique production files during roadmap validation, detecting overly granular or under-defined steps to ensure proper architecture readiness.

Why should executable implementation code be kept out of roadmap descriptions?

Implementation code in roadmap checks prevent embedding executable code or direct implementation details in roadmap descriptions, enforcing concise criteria with limited optional text focusing on testable outcomes.