Menu
Enforce executable done criteria by mapping requirements to concrete automated checks.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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-executable-acceptance-gate |
| description | Enforce executable done criteria by mapping requirements to concrete automated checks. |
| version | 1.0.0 |
| author | Hermes Profile |
| license | MIT |
Ensure "done" is proven by executable checks, not manual confidence.
For each requirement or acceptance criterion, provide:
requirement_idcheck_type (unit/integration/e2e/lint/type/security/perf/schema)check_command or test identifierexpected_resultstatus (pass/fail/not_run)REQUEST_CHANGES.REQUEST_CHANGES.BLOCKED.status: PASS | REQUEST_CHANGES | BLOCKEDacceptance_trace: requirement -> check -> resultmissing_executable_checksfailed_checks