speckit-tasks

You can generate dependency-ordered tasks by loading design artifacts like plan.md and spec.md to automatically produce a structured tasks.md. This process maps tasks to user stories and builds a dependency graph for clear execution ordering.

Organizing feature tasks by user story phases is best handled by enforcing a strict Phase structure including Setup, Foundational, User Story phases, and Polish. This approach maps tasks directly to user stories and outputs a ready-to-run tasks.md document.

Yes, you need a .specify directory containing project artifacts like plan.md and spec.md to generate a structured tasks document. The task generation process relies on these spec-kit style structures to create phase-based task lists for multiple user stories.

Yes, you can automate workflow planning for multiple user stories in spec-kit by using design artifacts to generate a tasks.md file. This automation enforces a strict checklist format and provides parallel execution hints alongside an MVP scope.

Task generation handles dependencies by building a dependency graph from your feature design artifacts. It then outputs a tasks.md document that includes parallel execution hints and an MVP scope to guide efficient implementation.

A limitation when creating a tasks.md from plan and spec artifacts is that the generation requires a strict spec-kit project structure with a .specify directory. Without these specific design artifacts, the dependency-ordered task generation cannot be performed.