speckit-tasks

Generate dependency-ordered tasks.md files from design artifacts for spec-kit projects.

Updated May 20, 2026
One-click install
npx skills add https://github.com/igmo71/Myrmex --skill speckit-tasks-igmo71
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/igmo71/Myrmex/tree/main/.agents/skills/speckit-tasks
Command: npx skills add https://github.com/igmo71/Myrmex --skill speckit-tasks-igmo71

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate an actionable, dependency-ordered tasks.md for a feature from available design artifacts.

Core Features & Use Cases

  • Task generation organized by user stories (US1, US2) and phases (Setup, Foundational, US phases, Polish)
  • Dependency graph and parallel execution hints to plan work efficiently
  • Built to integrate with spec-kit workflows and the .specify directory to ensure repeatable task production

Quick Start

Run speckit-tasks in the project root to generate a ready-to-run tasks.md from design artifacts.

Frequently Asked Questions about speckit-tasks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate dependency-ordered tasks from spec-kit design artifacts?

Generate dependency-ordered tasks from spec-kit design artifacts by running the task generation workflow in your project root to map plan and spec data into a structured tasks.md file. The process organizes actionable items by user stories and phases.

What is a dependency-ordered tasks.md file in spec-kit workflows?

A dependency-ordered tasks.md file in spec-kit workflows is an actionable checklist mapping design artifacts into sequential development phases. It provides dependency graphs and parallel execution hints to plan implementation work efficiently across user stories.

Can I generate task lists from specs without a .specify directory?

Generating task lists from specs requires a .specify directory in your project root. The spec-kit pattern relies on this directory structure to read available design artifacts and map plan data into ordered phases for the tasks.md output.

Does spec-kit task generation organize work by user stories and phases?

Spec-kit task generation organizes work by user stories such as US1 and US2, alongside phases including Setup, Foundational, US phases, and Polish. This structure ensures dependencies are respected and parallel execution hints are provided for efficient workflows.

What's the best way to structure project management tasks for spec-kit features?

The best way to structure project management tasks for spec-kit features is using a strict checklist-based tasks.md generation workflow. It maps design artifacts into dependency-ordered phases with optional tests, ensuring repeatable task production across project workflows.

Why does task generation from specs include parallel execution hints?

Task generation from specs includes parallel execution hints to help plan work efficiently within dependency-ordered phases. These hints identify tasks without mutual dependencies, allowing concurrent development across user stories while maintaining structural integrity.