ohos-req-review-gate

name	ohos-req-review-gate
description	Use when performing the Phase 0 Step 0.5 Review Ready Gate on a 04-feature.md, especially when the user says "evaluate gate", "review readiness", "feature ready?", "should we generate IR", or when the ohos-req-intake-orchestration main session needs a structured Ready / Conditional Ready / Not Ready judgment instead of doing the check inline. Reads 01-04, runs seven fixed checks plus a conditional-items check, and returns a machine-readable JSON summary plus a human-readable table that the main session can route on. Do NOT use for feature baseline generation (ohos-req-feature-baseline), value decision recording (ohos-req-value-decision), or IR generation (ohos-req-feature-to-ir).
metadata	{"author":"openharmony","scope":"common","stage":"requirements","capability":"review-gate","version":"0.3.0","status":"draft","tags":["sdd","requirements"]}

OHOS Review Ready Gate (结构化判定)

Announce at start: "我正在使用 ohos-req-review-gate skill 对 04-feature.md 执行 Review Ready Gate。"

定位

OHOS Review Ready Gate 是 Phase 0 唯一的独立 subagent 结构化判定——主 session 已持有 01-04 全文上下文，自行推算 Gate 会产生确认偏差，必须由隔离上下文的 subagent 执行判定。Gate JSON 输出的 observations 字段（PIR #152 P1）将性能/功耗/内存等需 Phase 5-7 实测的指标归类为观测项，不阻塞 Ready 判定，在 Phase 1-9 跟踪闭环。

适用边界

• ✅ 适用：Phase 0 Step 0.5（Feature 评审就绪）
• ❌ 不适用：决策 0（立项评审）、决策 1（方案确认）、决策 1.5（SIG 评审）、决策 2（Phase 4 评审）、决策 3（代码审查）、Phase 5 Step 5.2（设计待解决问题门禁）——这些由主 session / 后续 phase 流程承载
• 后续如果其他决策点也需要物化，可参考本 skill 的 JSON 输出契约复制推广

输入

• {docs_dir}/01-requirement.md
• {docs_dir}/02-feasibility.md
• {docs_dir}/03-arch-decision-record.md
• {docs_dir}/04-feature.md