What is speckit.tasks?

A task-generation command that reads a feature's planning documents and creates implementation tasks, using separate coding assistants for independent work.

Use it to load specifications, plans, data models, interface agreements, and test scenarios, then create tasks for each user story.

It turns a written plan into an actionable development checklist while reducing waiting for unrelated analysis.

speckit.tasks — Command by github

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add commands/github/spec-kit-copilot/speckit.tasks

Clone the repo

git clone --depth 1 https://github.com/github/spec-kit-copilot

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 401 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00000	$0.00401
Opus 5	$0.00000	$0.00200
Sonnet 5	$0.00000	$0.00080
Haiku 4.5	$0.00000	$0.00040

Measured yesterday against content hash 3b85ab3edaf7, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

speckit.tasks scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

spec-kit-presets/copilot-sub-agents/commands/speckit.tasks.md · 28 lines

What it actually says

Sub-Agent Delegation

When executing this command, delegate independent work to parallel sub-agents to reduce total execution time.

How to dispatch sub-agents in Copilot:

VS Code: Use the runSubagent tool to spawn each sub-agent in an isolated context.
CLI: Delegate to a sub-agent process — Copilot CLI automatically manages subsidiary sub-agent execution. You can also target custom agents defined in .github/agents/ or ~/.copilot/agents/.

Document Loading in Parallel

When loading design documents (step 2), dispatch parallel reads for all available documents:

Sub-agent: Core docs — "Read plan.md and spec.md. Extract tech stack, libraries, project structure, user stories with priorities (P1, P2, P3). Return structured summaries of both."
Sub-agent: Supporting docs — "Read data-model.md, contracts/, research.md, and quickstart.md (whichever exist under {FEATURE_DIR}). Extract entities, interface contracts, technical decisions, and test scenarios. Return a consolidated summary."

Per-User-Story Task Generation

After loading all documents, generate tasks for independent user stories in parallel:

For each user story (P1, P2, P3, ...) from spec.md: → Sub-agent: "Generate implementation tasks for User Story {N}: '{story title}'. Tech stack: {from plan.md}. Related entities: {from data-model.md if applicable}. Related contracts: {from contracts/ if applicable}. Follow the strict checklist format: - [ ] [TaskID] [P?] [USN] Description with file path. Return: ordered task list with dependency notes and parallel markers."

Collect all sub-agent results, then:

Assign sequential Task IDs (T001, T002, ...) across all phases
Resolve cross-story dependencies
Assemble into the final tasks.md using the template structure

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

yesterday First seen · 28 lines · 0 tokens per session scan A 3b85ab3edaf7

Subscribe to this mod's changes

speckit.tasks is a command published in the GitHub repository github/spec-kit-copilot (11 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 401 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Planning Testing ai copilot copilot-cli github-copilot plugin spec-driven-development

speckit.tasks

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

Sub-Agent Delegation

Document Loading in Parallel

Per-User-Story Task Generation

What this file has done since we first saw it

Other commands, from other repositories

spec-kitty.analyze

sdd-plan

sdd-setup

sdd-clarify

plan

epic-plan