woos-deviation-control-gate
Block unresolved implementation drift against PRD, product context, and engineering design artifacts.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Block unresolved implementation drift against PRD, product context, and engineering design artifacts.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Transform product requirements into a focused UI/UX design brief with screens, flows, visual direction, and optional image-generation concepts. Bridge between product thinking and implementation.
Stage 3 of idea-to-delivery: gated engineering workflow that receives PRD, roadmap, and architecture inputs, decomposes into stories, and executes with TDD, traceability, and review gates.
Planning and decomposition review skill adapted from ECC planner agent. Covers story-set review (Gate 2) and planning consults for upstream skills. PRD-quality review is NOT in scope — that is owned by `woos-product-prd-review-gate`.
Produce a lean story plan (table) for the Gate 3 execution loop — execution order plus diff scope per story. PRD AC is the spec; tests are the verification. No per-story prose documents.
Resolve multi-agent review conflicts with explicit authority matrix, evidence weighting, and escalation criteria.
Architecture review and design skill adapted from ECC architect agent. Use for design validation, trade-off analysis, and system-level decisions.
| name | woos-deviation-control-gate |
| description | Block unresolved implementation drift against PRD, product context, and engineering design artifacts. |
| version | 1.1.0 |
| author | Hermes Profile |
| license | MIT |
Stop silent drift between planned intent and final implementation.
woos-code-reviewer (or an equivalent whitelisted reviewer) in fresh context with a deviation-control focus. In-context self-review where the implementer's session re-labels itself as reviewer is NOT a valid invocation.woos-review-context before and after reviewer execution.NOT_RUN and stop.BLOCKED and stop.invocation_evidence MUST include dispatch_mode: "fresh_context". Any other value MUST return BLOCKED.noneintentional_documentedintentional_undocumentedunintentionalintentional_undocumented or unintentional => REQUEST_CHANGES.intentional_documented only passes when all affected artifacts are updated.BLOCKED.engineering-design in Lite is expected and MUST NOT be classified as drift or BLOCKED.status: PASS | REQUEST_CHANGES | NOT_RUN | BLOCKEDexecution_mode: Lite | Standardengineering_design_present: true|falsedeviation_findingsdeviation_typeartifact_update_requiredartifact_update_status{
"enforcement": {
"required_invocations": ["woos-code-reviewer", "woos-review-context"],
"actually_invoked": ["woos-code-reviewer", "woos-review-context"],
"missing_invocations": [],
"invocation_evidence": [
{
"skill": "woos-code-reviewer",
"dispatch_mode": "fresh_context",
"invoked_at": "2026-06-12T00:00:00Z",
"artifact_ref": "git diff HEAD + docs/engineering/<version>/<feature-id>-design.md",
"output_digest": "sha256:..."
}
],
"execution_mode": "Standard",
"engineering_design_present": true,
"deviation_type": "none",
"artifact_update_required": false,
"artifact_update_status": "n/a"
}
}
Missing invocation_evidence MUST return BLOCKED. A status: PASS without a populated enforcement block is INVALID and MUST be rejected by the orchestrator.