菜单
Independent high-level architecture review gate for discovery.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Produce the high-level architecture overview used by downstream product design and engineering.
Capture and structure raw ideas through guided interview or quick note. Produces a structured idea document ready for research or PRD pass. Focuses purely on product intent — no technical decisions.
Entry-point product workflow from raw idea to validated product design artifacts. Stops at reviewed PRD readiness and does not include engineering implementation.
Write the per-feature PRD from the ranked requirements contract using the mandatory PRD template.
Dedicated analyze gate for PRD and UI brief consistency. Runs script extraction first, then semantic review with evidence-backed findings.
Validate whether the captured problem is real, painful, frequent, and worth pursuing before broader discovery work begins.
| 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"]}} |
PASS, REQUEST_CHANGES, BLOCKED, NOT_RUNcritical, high, medium, low, warning[ASSUMPTION: ...], [NEEDS CLARIFICATION: ...], [NEEDS INPUT: ...]P0 … P11, P2a, Phase A, Phase Binternal-tool, single-operator, consumer-product, multi-stakeholder, CLIstrong, adequate, thin, broken## Background, ## Functional Requirements, ## Assumptions Index) — translations break downstream structural checks**Consequences (testable):**, **Out of Scope:**, **User value:**, Given … When … Then …)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.