design-handofflisted

# Design Handoff Prepare a concise, evidence-backed handoff from Design to the Wakeflow controller. A handoff is an intake artifact, not an execution plan and not a final product decision. ## Source Skills Used - `mattpocock/skills/productivity/handoff`: compact summary, suggested skills, avoid duplicating existing artifacts, and redact sensitive data. - `planning-with-files`: keep notes and deliverables separate; reference source artifacts instead of copying them. - Wakeflow governance: Design signals become executable only after controller intake. ## Wakeflow Role Use this skill when: - Design has clarified a requirement enough for controller review; - a requirement design is ready for intake; - an option comparison needs a controller/user decision; - open questions or risks should be preserved without becoming TODOs. ## Interaction First Default to conversation. Use this skill to summarize handoff readiness, separate facts from recommendations, name missing upstream Design work, and recommend the next skill or controller action before writing any tracked handoff artifact. Do not create or update handoff documents, handoff board rows, or workspace intake records as the first action. Write files only when the user/controller explicitly asks for a tracked artifact, confirms that the proposed content should be recorded, or a controller state root assigns a write deliverable. If a write is justified, state what will be written and why before editing. ## Workflow