メニュー
Validate whether the captured problem is real, painful, frequent, and worth pursuing before broader discovery work begins.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | woos-problem-validation |
| description | Validate whether the captured problem is real, painful, frequent, and worth pursuing before broader discovery work begins. |
| version | 1.0.0 |
| author | Hermes Profile |
| license | MIT |
| metadata | {"hermes":{"tags":["product","discovery","validation","research"],"related_skills":["woos-product-discovery"]}} |
Decide whether the captured problem should proceed, pivot, or park.
references/framework-customer-pain-points.mdideas/<slug>/00-idea-capture.mdIf any required file is not loaded, return BLOCKED.
ideas/<slug>/00-idea-capture.md → append ## Problem ValidationThe output must conclude with one of:
PROCEEDPIVOTPARKTransform 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.