speckit-tasks

Convert plan.md and spec.md into a dependency-aware tasks.md checklist.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/raccioly/coach-gravity --skill speckit-tasks-raccioly
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-tasks
Source: https://github.com/raccioly/coach-gravity/tree/main/.agent/skills/speckit-tasks
Command: npx skills add https://github.com/raccioly/coach-gravity --skill speckit-tasks-raccioly

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill converts high-level planning outputs (plan.md and spec.md) into a concrete, dependency-aware tasks.md, enabling teams to implement features from a shared blueprint without misalignment.

Core Features & Use Cases

  • Generates a single tasks.md from plan.md and spec.md, organizing tasks by phase (Setup, Foundational, User Story phases) and mapping user stories to concrete tasks with clear file paths.
  • Creates a dependency graph and parallel-execution hints so teams can plan rollout and identify independent tasks.
  • Enforces a strict checklist format for every task, ensuring precise task IDs, file paths, and story labels, and supports optional extension hooks for pre/post task steps.

Quick Start

Run the speckit-tasks skill after you have plan.md and spec.md to generate a ready-to-run tasks.md.

Frequently Asked Questions about speckit-tasks

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

FAQPage Schema
How do I generate a dependency-aware task list from a project plan and spec?

Generate a tasks.md file from plan.md and spec.md to map user stories into concrete, dependency-aware tasks. It organizes project phases, creates a dependency graph, and outputs a strict checklist format with clear file paths and parallel execution cues.

What is the best way to map user stories to concrete development tasks?

Map user stories to tasks by converting spec.md definitions into a strict checklist format within tasks.md. This assigns precise task IDs, file paths, and story labels across setup, foundational, and feature-driven phases.

Do I need a feature-driven spec to organize my project phases?

Yes, a feature-driven spec is required to organize project phases. The skill maps user stories from spec.md across setup, foundational, and story work phases, generating a dependency graph and parallel execution cues.

Can I add pre-task and post-task automation hooks to my task generation process?

Yes, you can add pre-task and post-task automation hooks. The skill supports optional extension hooks for pre- and post-task steps within the generated tasks.md checklist format.

How do I identify parallel execution opportunities in a software development task plan?

Generate a dependency graph from plan.md and spec.md to identify parallel execution opportunities. This creates parallel execution cues that highlight independent tasks ready for simultaneous rollout.

Why are my task IDs and file paths misaligned with my user stories?

Task IDs and file paths misalign without a strict checklist format. Converting plan.md and spec.md into tasks.md enforces precise alignment between task IDs, file paths, and story labels.