← ClaudeAtlas

aet-req-reviewlisted

Gate pipeline for requirement deliverables — enforces automated quality gates and interactive user validation before handover. Trigger when: (1) structured PRD/spec/SDD reviews are required, (2) executing a Stage demanding review-then-revision cycles, (3) workflows necessitate HCritic automated checks coupled with user-in-the-loop revision.
SOYL-AI/soyl-skills-hub · ★ 0 · AI & Automation · score 75
Install: claude install-skill SOYL-AI/soyl-skills-hub
<role> **Triage**: orchestrate the gate pipeline — enforce gate cycles, manage user-interactive revision cycles, and route state transitions based on gate outcomes. </role> <guideline> - The pipeline comprises: a SubAgent gate loop → a user-interactive revision step → a conditional re-gate loop. - **Triage**: halt any gate loop exceeding 2 iterations → request user intervention (options: ignore and proceed OR continue gate loop). - Gate Routing: `fully passed` → skip next gate iteration; `conditionally passed` → skip next gate iteration; `failed` → mandatory next gate iteration. - Post-revision: Systematically verify that chain impacts (terminology, cross-references) are consistently updated across the entire document. </guideline> <instruct> ### [R1] SubAgent Gate - Validate input completeness by confirming path existence ONLY — DO NOT read the content. - Delegate the deliverable and Review Materials to a Subagent for gate evaluation. Use `task_tool` with an available subagent type from the system's "Available subagent types" list. (Reference the prompt template in <example>). - If multiple deliverables exist, parallelize delegation to independent subagents. Final routing decisions MUST follow the worst-case result principle. ### [R2] Deliverable Revision (via Subagent) - CRITICAL: Do NOT read the deliverable content yourself — delegate the revision to a Subagent to avoid context explosion from large file reads. - Delegate to a Subagent (u