菜单
Write the per-feature PRD from the ranked requirements contract using the mandatory PRD template.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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-prd-authoring |
| description | Write the per-feature PRD from the ranked requirements contract using the mandatory PRD template. |
| version | 1.0.0 |
| author | Hermes Profile |
| license | MIT |
| metadata | {"hermes":{"tags":["product","prd","authoring","design-flow"],"related_skills":["woos-product-design-flow","woos-requirement-contract","woos-product-prd-review-gate"]}} |
Convert the ranked requirements contract into a full PRD for one feature.
references/framework-prd.md — authoring framework / reference readingtemplates/prd-template.md — the authoring template; the output PRD MUST match this template's section structure (Background / User Personas / Functional Requirements / Non-Functional Requirements / User Flows / Edge Cases / Non-Goals / Success Metrics). This template is the source of truth for Step 4's section checks.docs/prd/<version>/<feature-id>-requirements.mdreferences/template-prd-template.md — a richer per-feature PRD reference (Vision / JTBD / UJ-N etc.) kept for context; do not use it as the section structure for the output PRD. When it conflicts with templates/prd-template.md, the template wins.If any mandatory file is not loaded, return BLOCKED.
When the orchestrator provides upstream interface summaries, also load:
docs/prd/<version>/<upstream-feature-id>-interface.md for each declared upstream dependencyWhen referencing shared concepts (status enums, data models, event types, API endpoints), use the exact definitions from upstream interface summaries. Do NOT invent alternate names for concepts already defined upstream.
docs/prd/<version>/<feature-id>.md## Background## User Personas## Functional Requirements## Non-Functional Requirements## User Flows## Edge Cases## Non-Goals## Success MetricsP0 scope; keep P2 brief[NEEDS CLARIFICATION: ...]