What is orchestrate-tasks?

A procedure for coordinating implementation work from a specification's tasks.md file. It divides the listed task groups into an orchestration roadmap and assigns each group to a dedicated agent.

Preparing and running coordinated implementation of task groups from a project specification.

It gives a multi-step implementation effort a defined order and makes the work easier to track.

How johnreitano/spekka configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to johnreitano/spekka. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/johnreitano/spekka/main/.claude/commands/spekka/orchestrate-tasks.md

Clone the repo

git clone --depth 1 https://github.com/johnreitano/spekka

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/johnreitano/spekka/orchestrate-tasks/github.svg)](https://agentmods.dev/commands/johnreitano/spekka/orchestrate-tasks)

Your own site

<a href="https://agentmods.dev/commands/johnreitano/spekka/orchestrate-tasks"><img src="https://agentmods.dev/badge/commands/johnreitano/spekka/orchestrate-tasks/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/johnreitano/spekka/orchestrate-tasks"><img src="https://agentmods.dev/badge/commands/johnreitano/spekka/orchestrate-tasks.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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 785 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.1	$0.00000	$0.00785
Opus 5.5	$0.00000	$0.00314
Sonnet 5.5	$0.00000	$0.00157
Haiku 4.5	$0.00000	$0.00078

Measured 2mo ago against content hash 9fa55b5ca0a6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

orchestrate-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 2mo ago.

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.

.claude/commands/spekka/orchestrate-tasks.md · 89 lines

How it starts

The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Process for Orchestrating a Spec's Implementation

Now that we have a spec and tasks list ready for implementation, we will proceed with orchestrating implementation of each task group by a dedicated agent using the following MULTI-PHASE process.

Follow each of these phases and their individual workflows IN SEQUENCE:

Multi-Phase Process

FIRST: Get tasks.md for this spec

IF you already know which spec we're working on and IF that spec folder has a tasks.md file, then use that and skip to the NEXT phase.

IF you don't already know which spec we're working on and IF that spec folder doesn't yet have a tasks.md THEN output the following request to the user:

Please point me to a spec's `tasks.md` that you want to orchestrate implementation for.

If you don't have one yet, then run any of these commands first:
/spekka:shape-spec
/spekka:write-spec
/spekka:create-tasks

NEXT: Create orchestration.yml to serve as a roadmap for orchestration of task groups

In this spec's folder, create this file: spekka/specs/[this-spec]/orchestration.yml.

Populate this file with with the names of each task group found in this spec's tasks.md and use this EXACT structure for the content of orchestration.yml:

task_groups:
  - name: [task-group-name]
  - name: [task-group-name]
  - name: [task-group-name]
  # Repeat for each task group found in tasks.md

NEXT: Ask user to assign subagents to each task group

Next we must determine which subagents should be assigned to which task groups. Ask the user to provide this info using the following request to user and WAIT for user's response:

Please specify the name of each subagent to be assigned to each task group:

1. [task-group-name]
2. [task-group-name]
3. [task-group-name]
[repeat for each task-group you've added to orchestration.yml]

Simply respond with the subagent names and corresponding task group number and I'll update orchestration.yml accordingly.

Using the user's responses, update orchestration.yml to specify those subagent names. orchestration.yml should end up looking like this:

Read the full file on GitHub · 89 lines

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.

2mo ago First seen · 89 lines · 0 tokens per session scan A 9fa55b5ca0a6

Subscribe to this mod's changes

orchestrate-tasks is a command published in the GitHub repository johnreitano/spekka (5 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 785 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-31.

Planning Project management

orchestrate-tasks next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
orchestrate-tasksjohnreitano/spekka	Command	5	9mo ago	MIT	A	0	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code

spekka: Command for Claude Code