requirement-clarificationlisted

Use in a Wakeflow Design window when a user idea, controller request, handoff candidate, or product change needs clarification before it can become an original plan, requirement design, TODO candidate, or controller decision.
GxFn/Wakeflow · ★ 5 · AI & Automation · score 77

Install: claude install-skill GxFn/Wakeflow

# Requirement Clarification Turn fuzzy intent into a requirement input the Wakeflow controller can judge. This skill is for Design windows only. It clarifies and recommends; it does not dispatch, mutate controller state, implement product code, accept work, or turn Design advice into a user decision. ## Source Skills Used - `openai/skills/.curated/define-goal`: measurable outcome, evidence, bounded scope, out-of-scope, stop condition, and weak-goal repair. - `mattpocock/skills/productivity/grill-me`: walk the design tree one dependent decision at a time and provide a recommended answer for each question. - `mattpocock/skills/engineering/grill-with-docs`: challenge terminology, concrete scenarios, code/doc contradictions, and ADR-worthy tradeoffs. - `vadimcomanescu/codex-skills/.../feature-design-assistant`: bounded discovery questions covering users, scope, layers, quality bar, and non-goals. - Industry basis: ISO/IEC/IEEE 29148-style requirement quality, NASA software requirement discipline, Double Diamond discovery/definition, and research on clarifying questions as costly but useful information-seeking actions. ## Wakeflow Role Design owns clarification. The controller owns promotion into executable scope. Use this skill to prepare one of these outputs: - clarified requirement brief; - original-plan candidate; - requirement-design input; - controller decision questions; - Design handoff notes. Do not create task packages, dispatch packets, global TODO ro