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.
79%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./jiuwenclaw/jiuwenswarm/agents/harness/code/rails/sdd/design_rail/skills/aet-req-review/SKILL.mdTriage: orchestrate the gate pipeline — enforce gate cycles, manage user-interactive revision cycles, and route state transitions based on gate outcomes.
fully passed → skip next gate iteration; conditionally passed → skip next gate iteration; failed → mandatory next gate iteration.Exists: flag — trust it and hand that absolute path to the Subagent. Do NOT shell out to test -f / [[ -f ]] to check it: those are not portable to Windows PowerShell, and the failing probe aborts the gate.Exists: no, stop and ask the user for the correct path — do not start the gate against a missing deliverable.subagent_spawn with a subagent_type from the system's "Available subagent types" list, then subagent_wait in the same turn. Use the synchronous task_tool only when the system prompt says the registered subagent tool is task_tool — task_tool accepts only the synchronous subagent types, and explore_agent is not one of them, so calling task_tool with it is rejected before the gate starts. (Reference the prompt template in ).task_tool with an available subagent type), providing:
write_file (in-place overwrite), and return a brief revision summary.CRITICAL: Before calling ask_user, you MUST output the complete review results as visible content (not just in reasoning). The output MUST include:
After outputting the review results as content, call ask_user with a structured question — the confirmation must be a choice, never a free-text box. A free-text confirmation lets the user "confirm" with an empty input, which the transport cannot carry, and the gate then re-asks the same question forever.
{
"query": "文档审查完成,是否需要修改?",
"questions": [{
"question": "是否需要修改?如有其他意见请说明,无需修改请直接确认。",
"header": "审查结论确认",
"options": [
{"label": "无需修改,进入下一阶段"},
{"label": "需要修改(请补充具体意见)"},
{"label": "Other"}
]
}]
}The Other option is the frontend's free-text slot (rendered as 「其他(自定义输入)」): picking it opens an input box for the concrete modification request. Keep the literal label Other.
NEVER merge the review summary into the question text: the summary is visible content, the question carries only the confirmation. Keep the option labels free of the words 返工 / 拒绝 / rework — the rail treats them as a rework request.
If the user requests modifications:
If the user approves (no modifications needed):
These three user actions all mean "no modification requested". Treat them identically and go straight to [R4]:
| User action | Answer text you receive | Action |
|---|---|---|
| Selects "无需修改,进入下一阶段" | the option label | Proceed to [R4] |
| Selects "Other" and types the modification request | the typed text | Apply the revision, then follow the User Gate below |
| Clicks 「跳过」 (skip) | 用户已跳过此题,未选择任何选项。 | Proceed to [R4] |
| Clicks 「取消」 (cancel) | 用户已取消本次问答,未作答。 | Proceed to [R4] |
ask_user again after an empty submission, a skip or a cancel: re-asking after an empty submission stalls the flow — the user has already signalled "no modifications"."文档审查完成。审查结果:[grade],发现问题 [X] 个,已修复 [Y] 个。现在进入下一阶段:[下一阶段名称]。"
sdd_advance tool to proceed to the next stage. Do NOT guess or skip.sdd_advance.You are an authoritative Quality Assurance Reviewer. Your objective is to rigorously evaluate the deliverable against the specified gates.
## Input
- Review Materials: <path_to_review_materials>
- Deliverable: <path_to_deliverable>
## Task
1. Strictly adhere to the criteria, methodology, and checklists defined in the **Review Materials**.
2. Scrutinize the **Deliverable** to identify all logical flaws, missing requirements, inconsistencies, and non-conformities.
3. Output a definitive gate grade. It MUST be exactly one of the following: [fully passed, conditionally passed, failed].
4. If a SubAgent returns any grade outside [fully passed, conditionally passed, failed] or returns malformed output, treat the result as 'failed' and request a SubAgent rerun; if the SubAgent is unresponsive after one retry, escalate to user intervention with error details.
5. Provide a structured, exhaustive list of all identified issues, accompanied by specific and actionable remediation recommendations.ask_user tool for all user interactions.Deliverable Path to be Reviewed
Review Materials Path
reviewer role and checklist (may be unified into a single document).fully OR conditionally) THEN execute R2 revisions -> proceed directly to R3.XiaoLuoLYG/GOD
d114340
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.