speckit-tasks

To generate a dependency-ordered task list, load your plan.md and spec.md files to extract features and user stories. The system outputs a structured tasks.md checklist with execution phases, inter-task dependencies, and MVP guidance.

Automating feature task planning involves reading design artifacts like plan.md and spec.md to build a template-driven tasks.md. It automatically structures phases, detects optional documents like data-model.md, and validates extension hooks.

You do not need a data-model.md file to generate a project task checklist. The generation process requires plan.md and spec.md, while optional documents like data-model.md, contracts/, and research.md are detected to enrich task coverage.

Task generation handles parallel execution by analyzing your design artifacts to map inter-task dependencies. It outputs a tasks.md file that organizes tasks into setup, foundational, and user-story phases, explicitly demonstrating parallel execution examples.

You can use automation hooks during tasks.md generation by leveraging built-in extension validation. The system checks for and reports extension hooks before and after task generation, enabling automation without disrupting the core workflow.

Generated project tasks may lack traceability if optional documents like research.md or contracts/ are missing. Including these files enriches task coverage, ensuring the output tasks.md explicitly contains file paths and story labels.