Menu
Produce the per-feature requirements contract used as the input to priority ranking and PRD authoring.
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-requirement-contract |
| description | Produce the per-feature requirements contract used as the input to priority ranking and PRD authoring. |
| version | 1.0.0 |
| author | Hermes Profile |
| license | MIT |
| metadata | {"hermes":{"tags":["product","requirements","authoring","design-flow"],"related_skills":["woos-product-design-flow","woos-prd-authoring"]}} |
Turn one selected roadmap feature into a structured requirements file before any ranking or PRD work begins.
references/framework-prd.mdtemplates/requirements-template.mddocs/product/<project>-roadmap.mdideas/<slug>.md for Quick Note, or ideas/<slug>/00-idea-capture.md for Guided Interview) in place of the roadmapIf the required input file for the active mode is not loaded, return BLOCKED. In Lite mode the absence of docs/product/<project>-roadmap.md is expected and is not a BLOCK condition; the orchestrator MUST tell this skill which mode it is running in.
When the orchestrator identifies upstream dependencies (via Step 1.5), also load:
docs/prd/<version>/<upstream-feature-id>-interface.md for each declared upstream dependencyThese interface summaries define shared terminology, enums, data models, and API surfaces that this feature MUST align with. When writing requirements that reference shared concepts, use the exact names and definitions from the upstream interface summary.
docs/prd/<version>/<feature-id>-requirements.md## Problem Statement## Goals## User Stories## Non-Goals## Constraints## Risks & Unknowns## Priority Ranking[NEEDS CLARIFICATION: ...]P0 / P1 / P2 ranking and ship cut-line in ## Priority Ranking