requirement-review

To review requirement documents for a Go/No-Go decision, apply a structured checklist covering functionality, state flows, and data constraints to identify logic gaps. This generates a review report and checklist to ensure teams can make clear decisions.

Yes, you can use Feishu links for requirement review by providing a Feishu Story link or wiki/docx document. The system fetches the content to generate understanding files, checklists, and a concise report ready for the meeting.

A 12-dimension requirement checklist covers functionality, state flows, data constraints, security, UX, testing, and impact scope. It enforces comprehensive coverage to identify cross-team dependencies and missing constraints before the review.

To identify cross-team dependencies and logic gaps, run a systematic quality check with multi-agent parallel analysis. This cross-validation detects missing constraints and items requiring explicit confirmation across complex requirements.

Yes, the requirement review process supports optional Figma and code references. Providing these design links and code references helps perform deeper pre-review analysis and meeting preparation.

After a systematic requirement quality check, the artifacts generated are requirement_understanding.md, review_checklist.md, and report.md. These structured files support multi-stage review flows and can be exported to Feishu.