review-requirements

Parse product requirements from files, URLs, or text into two markdown review reports.

Updated Apr 8, 2026

Search Tags:#documentation #ambiguity #PRD #feasibility #risk-assessment #stakeholder-alignment #requirements-review

Ready to run

npx skills add https://github.com/taotao7/jingle-workflow-marketplace --skill review-requirements-taotao7

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review-requirements
Source: https://github.com/taotao7/jingle-workflow-marketplace/tree/main/plugins/jingle-workflow/skills/review-requirements
Command: npx skills add https://github.com/taotao7/jingle-workflow-marketplace --skill review-requirements-taotao7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams systematically evaluate requirements by generating two tailored reports—one for developers and one for product stakeholders—so ambiguous and risky elements are surfaced early.

Core Features & Use Cases

Generates two separate reports (dev and product) based on a provided PRD, spec, user story, or feature request.
Performs a structured ambiguity scan across 12 evaluation dimensions and highlights unclear phrases for clarification.
Records issues and decisions in a reproducible format to support traceability and cross-team alignment.

Quick Start

Review the provided requirement and trigger automatic generation of the two reports.

Frequently Asked Questions about review-requirements

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

FAQPage Schema

How do I review a PRD for ambiguity and feasibility risks?▼

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.

Can I generate separate requirement review reports for developers and product stakeholders?▼

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.

How do I assess user stories and feature requests for stakeholder alignment?▼

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.

What is the best way to automate risk assessment for product specifications?▼

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.

Can I review product requirements directly from a URL or inline text?▼

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.

Does the PRD review process support traceability for cross-team decisions?▼

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.