speckit-tasks

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

Updated May 3, 2026
One-click install
npx skills add https://github.com/Mohsen3-5/Trader --skill speckit-tasks-mohsen3-5
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/Mohsen3-5/Trader/tree/main/Trader/.claude/skills/speckit-tasks
Command: npx skills add https://github.com/Mohsen3-5/Trader --skill speckit-tasks-mohsen3-5

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Speckit tasks can be hard to plan and sequence correctly when you have multiple design artifacts (plan.md, spec.md, optional model/contracts/docs) and need a single, immediately actionable checklist for implementation.

Core Features & Use Cases

  • Dependency-ordered task generation: Creates a tasks.md organized by user story priority with an explicit completion order.
  • Design-artifact driven coverage: Uses plan.md and spec.md, and conditionally incorporates data-model.md, contracts/, research.md, and quickstart.md when present.
  • Execution-ready output: Produces tasks that follow a strict checklist format with file paths and independent test criteria per story.
  • Extension hook awareness: Detects before_tasks and after_tasks hooks in .specify/extensions.yml and includes the required hook prompts/output format.

Quick Start

Run the speckit-tasks skill to generate a dependency-ordered tasks.md from your feature's available design artifacts in the spec-kit project structure.

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 by processing your spec-kit project's plan.md and spec.md files. The tool creates a tasks.md checklist organized by user-story priority, conditionally incorporating data-model.md, contracts/, research.md, and quickstart.md when present.

What is the best way to sequence user stories for incremental testing?

Sequence user stories by generating a tasks.md file with strict checklist formatting. It organizes tasks by user-story dependencies, applies sequential IDs, optional parallel markers, and ensures independent test criteria per story phase for incremental testing.

Can I use spec-kit artifacts like data-model.md and contracts to build an implementation plan?

Yes, you can use spec-kit artifacts to build an implementation plan. The tool automatically detects and incorporates optional files like data-model.md, contracts/, research.md, and quickstart.md alongside required plan.md and spec.md to ensure complete coverage.

How does the tasks.md checklist handle before_tasks and after_tasks extension hooks?

The tasks.md checklist handles extension hooks by detecting before_tasks and after_tasks in .specify/extensions.yml. It includes the required hook prompts and output format directly in the dependency-ordered task sequence.

Does the generated tasks.md checklist support parallel task execution?

Yes, the generated tasks.md checklist supports parallel task execution. It enforces strict checklist formatting with sequential IDs and optional parallel markers, allowing independent tasks within the same user-story phase to run concurrently.

Why do my spec-kit implementation tasks lack clear testing criteria?

Implementation tasks lack clear testing criteria when not properly sequenced from design artifacts. Generating a tasks.md enforces independent test criteria per story, sequential IDs, and story-based phases to ensure every task is incrementally testable.