speckit-tasks

To generate a dependency-ordered task plan from design artifacts, run the generator from your repository root. It sources your plan.md and spec.md to produce a ready-to-run tasks.md organized by user stories.

Generating user story tasks requires a project with a .specify/ directory containing your plan.md and spec.md. The generator reads these design artifacts to map dependencies and build the phased task documentation.

Yes, you can automatically organize project tasks by user stories and execution phases. The generator structures tasks into Phase 1 Setup, Phase 2 Foundational, Phase 3+ User Story phases, and a final Polish phase for cross-cutting concerns.

Task dependencies and parallelizable work are mapped by linking generated tasks to user stories like US1 and US2. This creates a task graph from your plan.md that visualizes execution order and identifies parallel work streams.

Yes, this task generation approach works without external project management dependencies. It operates autonomously within your repository, enforcing required task-format rules to output a standalone tasks.md and a succinct project summary.

You should not use automated task generation from spec documents if your project lacks a .specify/ directory or a defined plan of user stories. The generator strictly sources existing plan.md and spec.md files to map dependencies.