speckit-tasks

This Skill generates a dependency-ordered tasks.md by consuming spec-kit documents like plan.md and spec.md to produce checklist-formatted tasks organized by user story and priority.

The best way to organize parallelizable tasks is by building a dependency graph from your design artifacts that explicitly marks which tasks can run concurrently, enabling safe parallel execution across user stories.

Extension hook detection works by reading .specify/extensions.yml to identify pre and post hooks without evaluating their conditions, presenting them in the generated tasks.md as optional or mandatory execution steps.

Yes, a .specify directory structure is required. The Skill reads templates, scripts output, and spec-kit documents from this folder to generate the per-user-story task phases and dependency graphs.

Yes, you can use optional data-model.md and contracts to create sprint planning checklists. These artifacts are parsed alongside plan.md to produce immediately executable tasks with file paths and parallel execution guidance.

Generated tasks might appear unordered if the dependency graph cannot resolve from the provided plan.md or spec.md artifacts. Ensure your spec-kit documents clearly define user stories and priorities for accurate dependency ordering.