uc-audit-cross-check

Audits all Use Cases against SRS requirements, SQL schema, and JIRA tasks to detect gaps.

Updated Mar 3, 2026
One-click install
npx skills add https://github.com/manhthien2005/PM_REVIEW --skill uc-audit-cross-check-manhthien2005
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: uc-audit-cross-check
Source: https://github.com/manhthien2005/PM_REVIEW/tree/main/tooling/.windsurf-template/shared/skills/UC_AUDIT
Command: npx skills add https://github.com/manhthien2005/PM_REVIEW --skill uc-audit-cross-check-manhthien2005

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Keeping Use Cases, SRS requirements, database schema, and JIRA tasks synchronized is error-prone in large projects. This Skill batch-audits the entire UC corpus to uncover missing tasks, orphan database columns, broken UC relationships, and documentation desync before they cause delivery issues. ## Core Features & Use Cases - UC Inventory & Quality Check: Reads all 26 Use Cases module by module, validating required sections, actor definitions, flow structure, and business rules against a detailed checklist. - SRS Relevance Scoring: Maps every UC to HG-FUNC functional requirements and classifies each as CORE, SUPPORTING, MANAGEMENT, or LOW, flagging uncovered requirements and orphan UCs. - Triad Cross-Check (UC ↔ SQL ↔ JIRA): Detects gaps such as UC_NO_TASK, MISSING_COLUMN, ORPHAN_COLUMN, BROKEN_INCLUDE, and STATS_DESYNC, then outputs a prioritized Vietnamese report at PM_REVIEW/UC_AUDIT_report.md. - Use Case: After updating the SRS or adding new SQL migrations, run a full audit to confirm every requirement still has a covering UC, every UC has a JIRA Story, and no database column is left unreferenced. ## Quick Start Ask the AI to run a full UC audit cross-checking all Use Cases against the SRS, SQL schema, and JIRA tasks, then generate the UC_AUDIT report.

Frequently Asked Questions about uc-audit-cross-check

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

FAQPage Schema
How do I audit Use Cases against SRS requirements?▼

Run the UC audit workflow, which reads the SRS_INDEX functional requirements (HG-FUNC) and maps each Use Case to them. Every UC is scored as CORE, SUPPORTING, MANAGEMENT, or LOW, and uncovered requirements are flagged as UNCOVERED_REQUIREMENT.

How to cross-check Use Cases with JIRA tasks and SQL schema?▼

The audit uses the JIRA Index UC-to-Epic lookup to verify every UC has at least one Story, and maps UC data fields to SQL table columns layer by layer. Gaps are flagged with codes like UC_NO_TASK, MISSING_COLUMN, and ORPHAN_COLUMN.

What gaps can a Use Case audit detect?▼

It detects missing JIRA tasks, orphan SQL columns, broken include/extend relationships between UCs, count mismatches between index files, platform mapping desync, and zombie files for deleted UCs. Each gap has a severity level and recommended action.

Does the UC audit read the full SRS document?▼

No. The audit explicitly forbids reading the full SRS and instead uses SRS_INDEX for requirement context. It follows a strict four-tier loading protocol to keep context usage minimal and process UCs module by module.

Where is the UC audit report saved and in what language?▼

The report is written to PM_REVIEW/UC_AUDIT_report.md with Vietnamese section headers, following a mandatory template. Re-running the audit overwrites the previous report and adds a comparison section showing fixed, remaining, and new issues.