ng:audit-product-feature

Compare PRD/SRS, AI-generated documents, and codebase to surface gaps and risks.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/huunghiaish/ng-skills --skill ng-audit-product-feature
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ng:audit-product-feature
Source: https://github.com/huunghiaish/ng-skills/tree/main/ng-audit-product-feature
Command: npx skills add https://github.com/huunghiaish/ng-skills --skill ng-audit-product-feature

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps product teams and engineering organizations verify that implemented software aligns with original requirements by performing a 3-way comparison between Original Requirements (PRD/SRS), AI-generated documentation, and the actual codebase. It identifies gaps, drift in requirements, hallucinated features, and potential business-logic risks.

Core Features & Use Cases

  • 3-way gap analysis: Original → AI Docs, Original → Code, AI Docs → Code.
  • Structured outputs: OVERVIEW.md, AUDIT.md, and REPORT.md for stakeholder communication and traceability.
  • Reference-driven workflow: uses PRD/SRS, audit checklist, and risk matrix; if docs are missing, infers requirements from the code.
  • Multilingual support via language mode for English and Vietnamese outputs.

Quick Start

Pack the target project context and trigger Claude Code with the project directory to begin the audit.

Frequently Asked Questions about ng:audit-product-feature

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

FAQPage Schema
How do I audit requirements against my codebase to find implementation gaps?

A requirements audit compares original PRD/SRS documents, AI-generated documentation, and the actual codebase to surface implementation gaps, requirement drift, and business-logic risks.

What is a 3-way gap analysis between requirements, documentation, and code?

A 3-way gap analysis compares Original Requirements to AI Docs, Original Requirements to Code, and AI Docs to Code to identify hallucinated features, missing implementations, and requirement drift across artifacts.

How do I generate an audit report and risk matrix for stakeholder review?

Generate an audit report and risk matrix by comparing implemented code against original requirements, producing structured outputs like OVERVIEW.md, AUDIT.md, and REPORT.md to communicate traceability and guide remediation planning.

Can I audit my codebase if the original PRD or SRS requirements documents are missing?

Yes, if original requirements documents are missing, the audit process can infer requirements directly from the existing codebase to perform the gap analysis and generate the audit checklist and risk matrix.

Does the requirements gap analysis support outputting audit reports in multiple languages?

Yes, the requirements gap analysis supports multilingual output, specifically providing language modes for generating audit reports and stakeholder documentation in both English and Vietnamese.

What are the limitations of using automated requirement verification for drift detection?

Automated requirement verification relies on documented artifacts; if the original PRD or AI-generated documentation lacks detail, the 3-way comparison may yield incomplete gap detection and require manual inference from the codebase.