菜单
Review an AxonFlow product task before coding, validate evidence, value, scope, safety, and testability, then approve it, refine it, request product rework, or stop. Use as a Supervisor quality gate between product analysis and implementation and after implementation or testing results.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Run automated AxonFlow acceptance tests, operate the local UI in a real headless browser, capture visible evidence, and record every requirement as passed or failed. Use after coding changes, for workflow UI regression checks, and whenever HTTP-only checks cannot verify rendered or interactive behavior.
Inspect the current AxonFlow repository and runtime, identify evidence-backed product gaps, and turn the highest-value gap into one bounded implementation task. Use for product health reviews, self-optimization runs, backlog proposals, and deciding the next improvement before coding.
| name | requirement-gate |
| description | Review an AxonFlow product task before coding, validate evidence, value, scope, safety, and testability, then approve it, refine it, request product rework, or stop. Use as a Supervisor quality gate between product analysis and implementation and after implementation or testing results. |
Read references/review-policy.md. Treat static workflow routes as suggestions, not proof that the task should proceed.
For a product proposal, require current evidence, one bounded outcome, explicit acceptance criteria, and no hidden deployment or destructive action. Preserve the proposal's structured fields when assigning Codex.
For Codex output, require changed-file evidence and proportionate automated tests before sending to acceptance testing. For test output, finish only when every requirement has a recorded pass; route failures back to Codex with exact evidence.
Supervisor decisions must be a plain JSON object matching the schema requested by the Supervisor prompt. Do not wrap JSON in Markdown fences. Never mark the workflow done merely because a node returned transport-level status=success; inspect the business verdict and evidence.
