util-usanalyzer

Analyzes PRD.md files for quality issues and injects inline [TODO] annotations.

3|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/rashidee/co2-skills --skill util-usanalyzer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: util-usanalyzer
Source: https://github.com/rashidee/co2-skills/tree/main/skills/util-usanalyzer
Command: npx skills add https://github.com/rashidee/co2-skills --skill util-usanalyzer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PRD.md quality assurance is time-consuming and error-prone; this Skill analyzes PRD.md files for issues like incomplete sentences, missing or broken references, cross-module inconsistencies, contradictory requirements, and misaligned architectural guidance, and automatically injects actionable [TODO] annotations to guide remediation.

Core Features & Use Cases

  • Detects incomplete user stories and missing acceptance criteria, broken references, and cross-module inconsistencies in PRD.md.
  • Validates alignment between User Stories, Non-Functional Requirements, and Constraints, and flags contradictions.
  • Inserts inline [TODO] annotations directly into PRD.md to guide editors and maintainers.
  • Supports multi-module PRDs with cross-reference and design-system/architecture principle checks and generates a remediation plan.

Quick Start

Run the util-usanalyzer on the target application (e.g., /util-usanalyzer mainapp) to scan PRD.md files and inject inline [TODO] annotations.

Frequently Asked Questions about util-usanalyzer

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

FAQPage Schema
How do I audit PRD.md quality and find cross-module inconsistencies?

To audit PRD.md quality, you need to validate user stories, NFRs, and cross-module references against architecture principles. This process surfaces incomplete requirements and broken references, returning line-accurate inline [TODO] annotations to guide remediation.

What's the best way to inject actionable TODOs into a PRD with missing acceptance criteria?

The best way to inject actionable TODOs is to run an automated analysis that identifies incomplete user stories and missing acceptance criteria. It inserts line-accurate inline [TODO] annotations directly into the PRD.md file to guide editors.

Can I check architecture principles and design-system rules in a multi-module PRD?

Yes, you can check architecture principles and design-system rules in a multi-module PRD. The analysis validates alignment between user stories, NFRs, and constraints while scanning cross-module references to surface architectural gaps.

How does PRD analysis handle contradictory requirements and non-functional requirements?

PRD analysis handles contradictory requirements by validating alignment between user stories, non-functional requirements, and constraints. It flags contradictions and cross-module inconsistencies, returning inline [TODO] annotations for precise remediation.

What limitations exist when scanning PRD.md files for broken references?

Limitations when scanning PRD.md files for broken references include dependencies on the file's structural clarity for accurate line-accurate annotations. Multi-module cross-reference checks require complete architecture principle documentation to effectively surface gaps without missing constraints.