PRD Requirement Reality Auditor

The problem

Engineering teams often inherit PRDs that look polished but still contain hidden assumptions, vague requirements, unresolved dependencies, and unmeasurable goals. These gaps can lead to mid-sprint scope creep, rework, blocked implementation, and features that ship without clear success criteria.

What it does

• Flags vague terminology like "intuitive," "fast," or "scalable" until it is translated into observable requirements.
• Maps dependencies across APIs, databases, permissions, vendors, analytics, infrastructure, and external teams.
• Pressure-tests meaningful edge cases including partial success, timeouts, retries, permission failures, concurrent actions, and recovery.
• Classifies evidence behind user problems as Observed, Reported, Inferred, Assumed, or Not Provided.
• Audits acceptance criteria so important requirements are observable and testable.
• Identifies missing product decisions, hidden operational burden, proxy-metric risks, and unclear ownership.

Why this beats prompting it yourself

Generic PRD reviews often smooth over missing details by inventing plausible answers or returning broad feedback like "add more clarity." This skill follows a structured 17-step audit sequence that keeps missing decisions visible instead of silently filling them in.

Use cases

• Reviewing a feature spec before engineering grooming or sprint planning.
• Finding requirements engineering would otherwise have to guess.
• Identifying hidden operational burden for QA, support, security, or operations.
• Checking success metrics for missing baselines, weak proxies, and unclear decision thresholds.
• Determining whether a PRD is Ready to Build, needs revision, or is blocked by missing decisions or evidence.

Known limitations

This skill does not perform technical feasibility studies, security or compliance certification, engineering estimation, or user research. It works best when provided with an existing PRD, feature brief, user story, acceptance criteria, or related product documentation.