speckit-tasks

To generate a dependency-ordered task list from design specs, you can use this skill to map data from plan.md and spec.md into a phased tasks.md file. It organizes trackable work items by user stories in priority order.

Yes, you can create a phased task plan aligned to user stories from a spec document. The skill converts spec.md and plan.md artifacts into an actionable checklist with clear file paths, dependencies, and parallelization hints.

You map design artifacts into an MVP-first delivery plan by focusing on the earliest user story in priority order. The skill produces a complete, independently testable plan and surfaces a summary with the total task count and MVP scope.

The best way to structure tasks.md for parallel development is to enforce a strict checklist format with explicit dependency mapping. This skill generates independently testable tasks with parallelization hints based on story relationships.

Yes, you need plan.md and spec.md to generate trackable work items. The skill maps data from these available design artifacts to produce a comprehensive task plan, while supporting gradual expansion as more optional documents are clarified.

Mapping story relationships helps with task generation by organizing tasks in priority order and enforcing a strict checklist format. This ensures the resulting tasks.md file contains complete, independently testable work items with accurate dependencies.