speckit-tasks

To generate a dependency-ordered task list from spec-kit design documents, the skill parses your `.specify/` artifacts like `plan.md` and `spec.md`, mapping user stories into an actionable `tasks.md` checklist with IDs and dependencies.

Automated task generation maps user stories to development tasks by parsing spec-kit design files, extracting requirements, and building a dependency graph that sequences tasks correctly across user stories in a structured output file.

Yes, you need a project using the spec-kit structure with `.specify/` design documents such as `plan.md` and `spec.md` present, as the tool parses these artifacts to map user stories into dependency-ordered tasks.

Yes, you can run custom scripts during the task generation process because the skill detects and runs pre- and post-generation hooks defined in your `.specify/extensions.yml` file.

The best way to translate design artifacts into a development checklist is to automate the process by parsing `plan.md` and `spec.md` files, which eliminates manual translation errors and outputs a ready-to-use `tasks.md`.

Incorrect dependency ordering across user stories occurs when the dependency graph is built from incomplete or misaligned design artifacts, so ensure your `.specify/` `plan.md` and `spec.md` files accurately define user story relationships.