util-usanalyzerlisted

Analyze PRD.md files for quality issues: incomplete sentences, non-existent references, cross-module inconsistencies, contradictory requirements, duplicate roles, design system validation, architecture principle violations, and process flow coverage gaps. Validates bi-directional coverage between User Stories/NFRs and High Level Process Flows — detects modules not covered by any process flow and process flow steps not covered by any User Story or NFR. Adds inline [TODO] annotations directly into the PRD.md file for each issue found. Trigger on keywords: "analyze user story", "analyze user stories", "check user story quality", "validate user stories", "find user story issues", "audit user stories", "review user stories", "check requirements quality", "find inconsistencies", "find contradictions". Accepts an application name as input (e.g., `/util-usanalyzer mainapp`, `/util-usanalyzer "Main App"`).
rashidee/co2-skills · ★ 3 · AI & Automation · score 77

Install: claude install-skill rashidee/co2-skills

# Util US Analyzer Analyze PRD.md files for quality issues and add `[TODO]` annotations for each issue found. ## Input Resolution This skill requires one mandatory argument: `<application>`. | Argument | Required | Description | |----------|----------|-------------| | `<application>` | Yes | Application name — matched against root-level application folders | | `<module>` | No | Optional module name to limit analysis to a single module | ### Application Folder Resolution 1. List root-level application folders that may have a numeric prefix (e.g., `1_hub_middleware`, `2_hc_adapter`) or no prefix (e.g., `mainapp`) 2. Strip the leading `<number>_` prefix from each folder name if present (e.g., `1_hub_middleware` -> `hub_middleware`) 3. Match the provided application name **case-insensitively** against the stripped folder names 4. Accept `snake_case`, `kebab-case`, or title-case input (e.g., `hub_middleware`, `hub-middleware`, `Hub Middleware` all match `1_hub_middleware`) 5. If no match is found, list all available application names and **stop** ### Auto-Resolved Paths | File | Resolved Path | |------|---------------| | PRD.md | `<app_folder>/context/PRD.md` | Example invocations: - `/util-usanalyzer mainapp` - `/util-usanalyzer "Main App"` - `/util-usanalyzer mainapp module:Home` ## Workflow ### 1. Read and Parse PRD.md Read the entire PRD.md file and parse its structure: - Identify all module sections (delimited by `## <Module Name>` headers under `# System Module`