speckit-tasks

To generate a dependency-ordered task plan from spec documents, you process design artifacts like plan.md and spec.md to produce an actionable tasks.md file. This organizes feature implementation work into phased checklists ordered by user stories and dependencies.

Generating a tasks plan requires a spec-kit structured project containing plan.md and spec.md files. Optional design artifacts including data-model.md, contracts/, and research.md can be included to enrich the generated checklist and organize work by user stories.

A tasks.md file for feature implementation is structured into Setup, Foundational, User Story, and Polish phases. It uses a strict checkbox-based checklist format to ensure reproducible task generation and track execution across user stories.

Yes, generated task plans support optional test inclusion within the strict checklist format. The output also produces a summary highlighting total tasks, MVP scope, and parallelization opportunities to streamline feature implementation.

Task generation supports extension hooks to ensure reproducible task generation within workflow automation. This allows customization of the dependency-ordered tasks.md output while maintaining the strict checkbox-based checklist format.