speckit-tasks

To convert a project plan into a structured task list, you translate your plan.md and spec.md files into a dependency-aware tasks.md checklist. This process organizes software development into phase-based user stories with specific file paths.

Generating dependency-aware tasks for software projects requires mapping data models, interfaces, and decisions into phase-based user stories. This creates a strict task-generation workflow covering setup, foundational tasks, and per-story phases.

Yes, you need plan.md and spec.md files to generate a task checklist. The workflow reads these specifications from your .specify directory to accurately map data models and contracts into structured phases.

You can use spec files to organize development by producing a Phase 1 setup, Phase 2 foundational tasks, and Phase 3 user story phases. This structure includes clear task labels, file paths, and optional tests.

To run pre-task and post-task actions during task generation, you integrate extension hooks using the .specify/extensions.yml configuration file. This allows the workflow to execute custom actions if configured.

A limitation when mapping data models to user stories is that the workflow strictly depends on the presence and accuracy of provided research inputs, contracts, and spec files to produce correct dependency-aware task sets.