work-slicinglisted

# Work Slicing Convert a confirmed requirement design into controller-intake candidates. This skill proposes slices; it does not write the controller TODO board, create state roots, or dispatch windows. ## Source Skills Used - `mattpocock/skills/engineering/to-issues`: tracer-bullet vertical slices, HITL/AFK marking, dependency order, user-story coverage, and granularity quiz. - `agile-product-owner`: INVEST checks and acceptance criteria quality. - Industry basis: INVEST user story quality and vertical-slice delivery. ## Wakeflow Role Design proposes task-package candidates. Controller decides whether they enter TODO, state roots, waves, or dispatch. Use this skill when a requirement design is confirmed enough to discuss implementation chunks. ## Interaction First Default to conversation. Use this skill to propose candidate slices, explain dependencies, and ask the user/controller to confirm granularity and HITL/AFK labels before writing any tracked Design artifact. Do not create or update slice notes, handoff drafts, TODO boards, task packages, or board rows 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. ## Inputs - Requirement design or PRD-like artifact. - Confirmed non-goals and completion definition. - Option-plan decis