review-requirements

To review a PRD for ambiguity and feasibility, you need a structured evaluation across multiple dimensions. This Skill automates that by performing a formal ambiguity scan and a 12-dimension assessment to surface unclear phrases and risky elements early.

Yes, generating separate requirement review reports for developers and product stakeholders is possible. This Skill produces two tailored markdown files from your input, ensuring cross-team alignment by addressing the specific concerns of each audience.

Assessing user stories and feature requests for stakeholder alignment involves evaluating them against structured criteria. This Skill parses your specs to perform a multi-dimensional review, recording decisions in a reproducible format to support traceability.

Automating risk assessment for product specifications requires a systematic approach to identify potential failures. This Skill evaluates PRDs across 12 dimensions, highlighting ambiguous phrases and risky elements to ensure issues are surfaced before development.

Yes, you can review product requirements from a URL or inline text. This Skill parses input from files, URLs, or inline text to evaluate specs and user stories, automatically generating two markdown review files with clearly defined sections.

Yes, the PRD review process supports traceability for cross-team decisions. This Skill records identified issues and alignment decisions in a reproducible markdown format, ensuring that ambiguous elements and risk assessments are documented for future reference.