tasks

To break down a project plan, generate a concrete task set from project context to drive spec-driven development. This creates a tasks.md file with numbered tasks, file paths, dependency notes, and parallelization guidance to ensure clear sequencing.

Automating task generation applies available design documents like plan.md, data-model.md, contracts, and research.md to create setup, core, integration, and polish tasks. Providing project context as arguments triggers the workflow to produce the task list.

Sequencing engineering tasks is handled by generating a task set that respects project dependencies and parallelization rules. The output tasks.md provides numbered tasks with explicit dependency notes and parallelization guidance for execution.

Generating parallelization guidance for setup and integration tasks is supported by applying available design documents. The workflow outputs a tasks.md file detailing which tasks can run in parallel and which have execution dependencies.

Task generation applies available design documents to tailor the output. While it leverages plan.md, data-model.md, contracts, and quickstart.md, it can process the provided project context to generate tasks even if some documents are missing.

Generated project tasks should include file paths and dependency notes when properly driven by spec-driven development context. Ensure all available design documents are provided as arguments so the task decomposition can accurately map execution requirements.