tasks — Claude Code prompt: what it does, how to install
Generates dependency-ordered tasks with estimates from a feature spec. Outputs a structured tasks.md file.
MIT ★ 110 updated 2026-10-19
.claude/commands/tasks.mdWhat tasks does
The prompt turns a feature specification into an ordered task breakdown. It analyzes design artifacts provided in Markdown and arranges all action items by their dependencies.
The result is formatted as a tasks.md document containing TODO items, estimates, and dependency links. You need a prepared Markdown spec beforehand. Without an initial spec file, the prompt has no source material to process.
What it helps with
- Break down a Markdown feature specification into ordered tasks
- Generate a tasks.md file with TODO items and estimates
- Determine task execution order based on dependencies
Example prompts for the agent
- Generate tasks with dependencies from
spec.md - /tasks create
tasks.mdfrom the feature specification - Break down this markdown spec into estimated tasks
How to install tasks
Manually: put the files in place
.claude/commands/tasks.mdHow to use
Paste the text at the start of a chat or into project instructions
Questions about tasks
How to install tasks in Claude Code?
Save the prompt file to .claude/commands/tasks.md. Once saved, the command is available directly in your Claude Code workflow.
What does the tasks prompt do?
It parses a feature spec in Markdown and writes a tasks.md file containing actionable TODOs, estimates, and task dependencies.
What input does the prompt require?
It requires a feature specification in Markdown format. The prompt uses those design artifacts to structure the tasks.
Source text
tasks.md · MIT
# tasks Generate actionable, dependency-ordered tasks for a feature based on design artifacts. Inputs: - spec: The feature spec in markdown Output: - tasks.md content with TODOs, estimates, and dependencies.
© alfredoperez · MIT · alfredoperez/speckit-companion