aet-req-review

Enforces automated quality gates and user validation for requirement deliverables before handover.

7.1k|1.1k|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/openJiuwen-ai/jiuwenswarm --skill aet-req-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aet-req-review
Source: https://github.com/openJiuwen-ai/jiuwenswarm/tree/main/jiuwenswarm/agents/harness/code/rails/sdd/design_rail/skills/aet-req-review
Command: npx skills add https://github.com/openJiuwen-ai/jiuwenswarm --skill aet-req-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Requirement documents like PRDs, specs, and SDDs often ship with logical flaws, missing requirements, and inconsistencies that surface late in development. This Skill enforces a structured review-then-revision gate pipeline so deliverables pass automated quality checks and explicit user confirmation before moving to the next stage.

Core Features & Use Cases

  • SubAgent Gate Evaluation: Delegates deliverable review to subagents against reviewer checklists, returning a definitive grade of fully passed, conditionally passed, or failed.
  • Iterative Fix-and-Reassess Loop: Automatically routes failed deliverables through revision cycles (up to 2 iterations) with worst-case routing for multiple deliverables, then escalates to the user.
  • User-in-the-Loop Validation: Outputs complete review results and asks for confirmation via ask_user, supporting optional re-review before advancing the SDD stage with sdd_advance.
  • Use Case: During a spec-driven development workflow, run this gate on a generated PRD so a reviewer subagent flags requirement gaps, a revision subagent fixes them in place, and you confirm the result before design begins.

Quick Start

Review the requirement document at the given deliverable path against the review materials, fix any issues found, and confirm the result with me before advancing to the next stage.

Frequently Asked Questions about aet-req-review

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

FAQPage Schema
How do I review a PRD or requirement document with automated quality gates?

Provide the deliverable path and review materials path to the gate pipeline. A reviewer subagent evaluates the document against the checklist and returns a grade of fully passed, conditionally passed, or failed, followed by automated revision and your confirmation.

How does the review-then-revision loop work for requirement documents?

Failed deliverables are delegated to a revision subagent that fixes each issue in place, then re-gated. The loop stops after 2 iterations, at which point you choose to ignore and proceed or continue gating.

What happens when reviewing multiple deliverables at once?

Each deliverable is delegated to an independent subagent in parallel. Final routing follows the worst-case result principle, so a single failed deliverable forces the revision loop for the whole batch.

What happens if the review materials path is missing?

The pipeline prompts you with three options: provide the review materials, proceed with limited checks where all checks are treated as failed, or abort the review entirely.

What are the limitations of this requirement review gate?

The gate depends on the quality of the supplied reviewer checklist and cannot proceed without a valid deliverable path. Gate loops are capped at 2 iterations, and malformed subagent grades are treated as failed.