requirement-designlisted

# Requirement Design Write a requirement design that the Wakeflow controller can review, schedule, and dispatch. This skill turns known context into a structured design; it does not interview endlessly, publish issues, mutate controller state, or implement product code. ## Source Skills Used - `mattpocock/skills/engineering/to-prd`: synthesize conversation and codebase understanding into problem, solution, user stories, implementation decisions, testing decisions, out-of-scope, and notes. - `vadimcomanescu/codex-skills/.../agile-product-owner`: INVEST-style stories and acceptance criteria. - `planning-with-files`: separate notes from deliverables and keep references explicit. - Industry basis: ISO/IEC/IEEE 29148-style requirement quality and INVEST slicing criteria. ## Preconditions Use this skill only when at least one of these is true: - the user has confirmed the clarified requirement; - the controller asked Design for a requirement design; - a Design handoff has enough evidence to draft a candidate and clearly mark open decisions. If the goal, scope, or completion evidence is unclear, run `requirement-clarification` first. If the implementation route is unclear, run `option-planning` first. ## Interaction First Default to conversation. Use this skill to draft or review requirement-design sections with the user, call out gaps, and recommend the next Design or controller decision before writing any tracked Design artifact. Do not create or update requi