feature-validate

Verify documented feature capabilities against codebase implementations and test coverage.

Updated Feb 12, 2026

Search Tags:#documentation #codebase #audit #alignment #verify #tests

Ready to run

npx skills add https://github.com/edgeandnode/ampup --skill feature-validate-edgeandnode

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: feature-validate
Source: https://github.com/edgeandnode/ampup/tree/main/.agents/skills/feature-validate
Command: npx skills add https://github.com/edgeandnode/ampup --skill feature-validate-edgeandnode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verify that documented feature capabilities have a real implementation in the codebase and that test coverage exists, preventing drift between docs and release.

Core Features & Use Cases

Verifies that documented capabilities map to production code.
Checks test coverage and flags untested or misaligned features.
Generates a structured verification report highlighting gaps and mismatches.

Quick Start

Run a feature verification workflow on a specified feature document to ensure code matches documentation and that test coverage exists.

Frequently Asked Questions about feature-validate

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

FAQPage Schema

How do I verify that documented features match my codebase implementation?▼

To verify documented features match your codebase, run a feature validation workflow that reads implementation files and architecture references to check component existence and behavior, surfacing alignments, gaps, and misalignments.

What causes documentation drift between feature docs and production code?▼

Documentation drift happens when feature docs are updated without corresponding codebase changes or test coverage. Auditing alignment verifies that documented capabilities map to real implementation files to prevent mismatches before release.

How can I check if test coverage exists for specific feature capabilities?▼

Check test coverage for feature capabilities by running a verification process across project feature docs that reads implementation files and flags untested or misaligned features in a structured report.

How do I generate a report of gaps and misalignments between docs and code?▼

Generate a verification report by applying an audit process across project feature docs that reads architecture references and implementation files to output a structured document highlighting mismatches and gaps.

Can I audit multiple feature documents to verify implementation alignment?▼

Yes, you can audit multiple feature documents by applying the verification process across project feature docs to validate component existence and behavior, generating a comprehensive verification report.

What limitations exist when verifying architecture references against a codebase?▼

Limitations include relying on readable implementation files and accurate architecture references; the audit cannot validate undocumented code or external dependencies outside the specified feature docs and codebase scope.