ada-srs-review

Audits Software Requirements Specification documents through 12 structured review passes.

Updated Jul 23, 2026
One-click install
npx skills add https://github.com/wubing7755/Ada --skill ada-srs-review-wubing7755
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ada-srs-review
Source: https://github.com/wubing7755/Ada/tree/main/skills/software-development/ada-srs-review
Command: npx skills add https://github.com/wubing7755/Ada --skill ada-srs-review-wubing7755

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Large SRS documents accumulate dead requirements, stale cross-references, concept confusion, scope leaks, and silently rotted indexes after edits. This Skill provides a systematic audit methodology that finds these defects before the document drives design and implementation. ## Core Features & Use Cases - 12 Structured Audit Passes: Detect dead requirements, stale cross-references, terminology drift, implementation-detail leaks, scope violations, missing behaviors, and framework coverage gaps. - Post-Edit Consistency Sync (Pass J): After any add/delete/renumber, re-verify section indexes, statistics tables, numbering rules, deferred-requirements appendix, and change logs. - SRS-to-Code Coverage Analysis (Pass K): Compare requirements against actual source code across C#, TypeScript, and .razor layers, or audit an existing coverage report for accuracy. - Use Case: After bulk-renumbering requirements in a 4700-line SRS, run the post-edit consistency check to catch broken indexes, stale statistics, and hardcoded ID ranges before handoff. ## Quick Start Review docs/SRS.md for dead requirements, terminology confusion, scope leaks, missing acceptance criteria, and stale cross-references, reporting findings without editing the document.

Frequently Asked Questions about ada-srs-review

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

FAQPage Schema
How do I review an SRS document for quality issues?

Map the document structure first, then run targeted audit passes: dead requirements, stale cross-references, concept confusion, implementation-detail leaks, scope violations, and missing acceptance criteria. Report findings with location, risk, and recommended action without editing directly.

How to check SRS consistency after renumbering requirements?

Run a post-edit consistency sync covering section index counts, statistics tables, numbering rules, deferred-requirements appendix entries matched by title, change log rows, and hardcoded ID ranges inside requirement bodies. The included verify_srs_consistency.py script automates header counting and gap detection.

What is the difference between SRS gap analysis and SRS-to-code coverage?

Gap analysis compares the SRS against reference implementations like VS Code or Rider to find missing requirements. SRS-to-code coverage compares requirements against the actual source code, classifying each as Tested, Implemented, Partial, or Not Implemented.

Why does SRS-to-code coverage analysis miss implementations in Blazor projects?

C#-only scans miss 10-20% of implementations hidden in TypeScript interop files, .razor component lifecycle hooks like OnAfterRenderAsync, and Razor markup event handlers. Always grep the full repository across all source layers, not just .cs files.

When should I not use this SRS review workflow?

Do not use it for writing new requirements, deriving an SRS from a technical proposal, auditing source code quality, or executing approved large-scale edits. Those tasks route to SRS authoring, code quality analysis, or the SRS revision workflow respectively.