sdd-task

To decompose a spec or plan into tasks for AI coding agents, provide your plan.md or spec.md file, and the skill breaks requirements into independent, ordered task files with goals, context, and verification scenarios.

Breaking down workflow requirements into independent, testable tasks is best handled by enforcing task independence and traceability, yielding structured task files with concrete completion criteria and test scenarios for reliable automation.

Yes, you can generate task files without an existing document by selecting independent input mode, which allows you to define discrete, self-contained tasks with explicit inputs and verification scenarios directly.

Task decomposition does enforce testability and traceability by requiring each generated task file to include concrete goals, context, and verification scenarios, ensuring coding agents can implement and verify them independently.

AI agents struggle to execute tasks directly from a large plan or spec file because high-level requirements lack discrete, self-contained context, making it difficult to verify completion without referring back to the original document.

You should not use automated task decomposition if your project requirements are too vague to define concrete goals or test scenarios, as the process relies on explicit context and verification criteria to generate executable task files.