# speckit.tasks

speckit.tasks builds a tasks.md file for a feature from plan.md and spec.md, splitting work into phases by user story priority.

- command · `type=command` · Claude Code, Codex, GitHub Copilot, Gemini CLI · ★ 117 repo stars
- Author: Chat2AnyLLM
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/Chat2AnyLLM/awesome-claude-plugins/tree/HEAD/.claude/commands/speckit.tasks.md
- Updated: 2026-10-29
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/commands/speckittasks

## What it does

The `speckit.tasks` command starts by running `.specify/scripts/bash/check-prerequisites.sh --json` to locate the feature directory, then reads `plan.md` and `spec.md` as required inputs, pulling in `data-model.md`, `contracts/`, `research.md` or `quickstart.md` when they're present.

It turns those sources into a `tasks.md` built on `.specify/templates/tasks-template.md`: a setup phase, a foundational phase for blocking shared work, one phase per user story ordered by priority (P1, P2, P3...), and a final polish phase. Every line has to follow a fixed checklist pattern — checkbox, task ID like `T001`, an optional `[P]` tag for parallelizable work, a story tag like `[US1]`, and a file path — anything missing from that pattern counts as malformed.

Test tasks only show up if the feature spec calls for them or the user asks for a TDD workflow explicitly. The command finishes by reporting the output path, task counts per story, and which tasks can run in parallel.

## Install

### Claude Code (native platform)

**Manually: put the files in place**
- File: `.claude/commands/speckit.tasks.md` — Call it with /speckit.tasks. For all projects use ~/.claude/commands/

### Codex

**Manually: put the files in place**
- File: `~/.codex/prompts/speckit.tasks.md` — Call it with /prompts:speckit.tasks. Codex marks this format deprecated in favour of skills

### GitHub Copilot

**Manually: put the files in place**
- File: `.github/prompts/speckit.tasks.prompt.md`

### Gemini CLI

**Manually: put the files in place**
- File: `.gemini/commands/speckit.tasks.toml` — Gemini stores commands as TOML: the prompt text goes into the prompt field

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/Chat2AnyLLM/awesome-claude-plugins/tree/HEAD/.claude/commands/speckit.tasks.md

## When to use it
- split a feature into tasks grouped by user story
- get checklist-formatted tasks with IDs and file paths
- order work into setup, foundational, story, and polish phases
- scope an MVP around the first user story
- spot tasks that can run in parallel

## Example prompts
- Run /speckit.tasks for the current feature
- Generate tasks.md from plan.md and spec.md
- Break tasks down by user story using the contracts folder

## Similar
- [parallel-tasks-help](https://affpapa.org/en/nevibecode/commands/parallel-tasks-help.md) — command · ★ 1357 repo stars
- [speckit.analyze](https://affpapa.org/en/nevibecode/prompts/speckitanalyze.md) — prompt · ★ 110 repo stars
- [tasks-generation](https://affpapa.org/en/nevibecode/rules/tasks-generation.md) — rule · ★ 3774 repo stars
- [speckit-tasks](https://affpapa.org/en/nevibecode/skills/speckit-tasks.md) — skill · 2500 installs
- [add-task](https://affpapa.org/en/nevibecode/skills/add-task.md) — skill · 1300 installs
- [speckit.companion.after-tasks](https://affpapa.org/en/nevibecode/commands/speckitcompanionafter-tasks.md) — command · ★ 110 repo stars

From the same set: [chat2anyllm/awesome-claude-plugins](https://affpapa.org/en/nevibecode/by/chat2anyllm/awesome-claude-plugins.md) — 9 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
