validate-features

Validate milestone features against implementation code, test coverage, and traceability matrices.

Updated May 7, 2026
One-click install
npx skills add https://github.com/tmalcolm-0607/mad-council-claw --skill validate-features-tmalcolm-0607
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validate-features
Source: https://github.com/tmalcolm-0607/mad-council-claw/tree/main/.claude/skills/validate-features
Command: npx skills add https://github.com/tmalcolm-0607/mad-council-claw --skill validate-features-tmalcolm-0607

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of inconsistent feature tracking in software projects, where implementation progress, test coverage, and documentation (feature traceability matrices and master feature maps) fall out of sync, leading to missed requirements, inaccurate project status, and untested features reaching production.

Core Features & Use Cases

  • Implementation & Test Validation: Confirms that every feature defined for a target milestone has corresponding implementation code and appropriate test coverage, flagging missing or incomplete work.
  • Status Accuracy Checks: Verifies that documented feature status (not-started, in-progress, complete, tested) matches the actual state of implementation and testing.
  • Feature Map Sync Validation: Ensures the feature traceability matrix and master feature map are fully aligned, catching missing entries, orphaned features, status mismatches, and broken spec links.
  • Use Case: For a team preparing to ship milestone M2 with 38 tracked features, this Skill quickly identifies 8 features lacking implementation, 3 status mismatches between documents, and 2 broken spec links, so gaps can be fixed before release.

Quick Start

Invoke the validate-features skill with your target milestone (for example, /validate-features M2) to run a full validation of feature implementation, test coverage, status accuracy, and feature map sync.

Frequently Asked Questions about validate-features

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

FAQPage Schema
How do I validate feature traceability and test coverage before a milestone release?

To validate feature traceability, you can run a validation check against your target milestone to confirm every defined feature has corresponding implementation code and test coverage. This process flags missing work, status mismatches, and broken documentation links.

Why does my feature traceability matrix fall out of sync with implementation code?

Feature traceability matrices fall out of sync when development teams update implementation code or test coverage without concurrently updating the master feature map. Validating milestone progress detects these discrepancies, catching orphaned features and status mismatches before release.

What is the best way to check feature map sync and status accuracy for a project milestone?

The best way to check feature map sync is to validate that documented feature status matches the actual state of implementation and testing. This ensures your traceability matrix and master feature map are fully aligned, catching missing entries and broken spec links.

How do I enforce software governance rules for milestone delivery?

To enforce software governance rules for milestone delivery, you validate feature tracking to ensure all milestone features have implementation and test coverage. This satisfies governance requirements by preventing untested features from reaching production and ensuring accurate project status reporting.

Can I detect untested features and status mismatches across multiple project tracking documents?

Yes, you can detect untested features and status mismatches by validating feature implementation against your project tracking documents. This identifies gaps in test coverage, flags incomplete work, and verifies that documented statuses align across the traceability matrix and feature map.