Menu
Independent high-level architecture review gate for discovery.
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-architecture-review-gate |
| description | Independent high-level architecture review gate for discovery. |
| version | 1.0.0 |
| author | Hermes Profile |
| license | MIT |
| metadata | {"hermes":{"tags":["product","discovery","architecture","review","gate"],"related_skills":["woos-product-discovery","woos-architecture-overview"]}} |
Review the architecture overview in fresh context before discovery completes.
references/framework-architecture-validation.mddocs/product/<project>-architecture.mddocs/product/<project>-roadmap.mdIf any required file is not loaded, return BLOCKED.
docs/reviews/<project>-architecture-review-rN.md| # | Criterion | Fix Hint |
|---|---|---|
| A1 | Component boundaries | Split unclear or overloaded components |
| A2 | Communication consistency | Pick one dominant pattern and justify exceptions |
| A3 | Data decoupling | Add boundaries where raw sharing is too tight |
| A4 | Infrastructure proportional | Avoid premature infra for later versions |
| A5 | Dependencies manageable | Mark independent vs sequential buildability |
| A6 | Risks realistic | Add concrete mitigations |
| A7 | Version-aligned | Keep V2+ only elements out of V1 baseline |
Every row must have a finding and status.