Requirement Clarifier

Problem

Requirement docs often hide three kinds of risk: vague business goals, implicit technical assumptions, and missing test boundaries. A single review pass can miss cross-role contradictions or mix blockers with optional polish.

How It Works

requirement-clarifier runs multi-round reviews in order: product manager, tech lead, senior test engineer. Each round asks one critical question at a time, prioritizing red critical defects, yellow important gaps, and green optimization suggestions; user answers are recorded, then the same role re-reviews the updated context. PM checks business goals, user stories, acceptance criteria, scope, and market context; tech lead checks feasibility, data models/APIs, performance/security, architecture impact, and solution trade-offs; test engineer checks testability, edge cases, verifiable acceptance, data consistency, and logic consistency.

It then outputs {requirement}_review_report_{YYYY-MM-DD}.md and {requirement}_requirement_doc_refined_{YYYY-MM-DD}.md, preserving original wording, marking TBD items and pending decisions instead of rewriting or inventing requirements.

Notes

Best for PRDs, requirement notes, and feature specs; .docx input should be converted to Markdown first. If a role exceeds three rounds with unresolved critical issues, the workflow suggests pausing for more information. Green suggestions are listed rather than interrogated, making them suitable for selective adoption.