idea-to-deliverylisted

# Idea to Delivery Use this skill when an idea has been refined enough to become executable project work. ## Hierarchy - Tiny isolated change: one implementation task. - Medium feature: one Epic/initiative plus roughly 2–5 independently deliverable tasks. - Large/cross-cutting feature: discovery/design first, then an Epic plus delivery slices and human gates. Default rule: **one independently mergeable PR = one implementation task**. Do not split by technical layer when the slices cannot be meaningfully delivered or tested independently. ## Epic contract An Epic describes the outcome and coordination boundary. Include goal, context, chosen architecture/design reference, scope, non-goals, success criteria, child slices, human gates, dependency graph, parallel lanes, rollout/preview strategy, and completion rule. ## Implementation task contract Each agent-ready task should include: 1. Goal 2. Context 3. Scope 4. Testable acceptance criteria 5. Technical direction / relevant repository paths when known 6. Out of scope 7. Dependencies by ticket title 8. Preview/seed scenarios for user-facing work or reproducible bugs 9. Automated test expectations 10. Human test expectations 11. Parent Epic/initiative reference Do not make a task agent-ready while material product/architecture questions remain unresolved. ## Classification Keep workflow queues separate from architecture/domain classification. Prefer structured fields when the project supports them. Use each project's