What is implement-tasks?

A command that implements a planned software feature from its specification and task list.

It is for selecting task groups, delegating their implementation, and producing a final verification report after all selected work is done.

It organizes implementation into defined phases and adds a separate check that the completed work matches the plan.

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/implement-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/implement-tasks/github.svg)](https://agentmods.dev/commands/johnreitano/spekka/implement-tasks)

Your own site

<a href="https://agentmods.dev/commands/johnreitano/spekka/implement-tasks"><img src="https://agentmods.dev/badge/commands/johnreitano/spekka/implement-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/implement-tasks"><img src="https://agentmods.dev/badge/commands/johnreitano/spekka/implement-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 784 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.00784
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 b3fc5fcd26b8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

implement-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/implement-tasks.md · 59 lines

How it starts

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

Spec Implementation Process

Now that we have a spec and tasks list ready for implementation, we will proceed with implementation of this spec by following this multi-phase process:

PHASE 1: Determine which task group(s) from tasks.md should be implemented PHASE 2: Delegate implementation to the implementer subagent PHASE 3: After ALL task groups have been implemented, delegate to implementation-verifier to produce the final verification report.

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

Multi-Phase Process

PHASE 1: Determine which task group(s) to implement

First, check if the user has already provided instructions about which task group(s) to implement.

If the user HAS provided instructions: Proceed to PHASE 2 to delegate implementation of those specified task group(s) to the implementer subagent.

If the user has NOT provided instructions:

Read spekka/specs/[this-spec]/tasks.md to review the available task groups, then output the following message to the user and WAIT for their response:

Should we proceed with implementation of all task groups in tasks.md?

If not, then please specify which task(s) to implement.

PHASE 2: Delegate implementation to the implementer subagent

Delegate to the implementer subagent to implement the specified task group(s):

Provide to the subagent:

The specific task group(s) from spekka/specs/[this-spec]/tasks.md including the parent task, all sub-tasks, and any sub-bullet points
The path to this spec's documentation: spekka/specs/[this-spec]/spec.md
The path to this spec's requirements: spekka/specs/[this-spec]/planning/requirements.md
The path to this spec's visuals (if any): spekka/specs/[this-spec]/planning/visuals

Instruct the subagent to:

Analyze the provided spec.md, requirements.md, and visuals (if any)
Analyze patterns in the codebase according to its built-in workflow
IF your task involves user-facing UI, and IF any of the views and UI elements that you will be modifying already exist, and IF you have access to a browser testing tool (such as the Playwright MCP server), THEN

Using this browser testing tool, use all of these pre-existing views and/or UI elements as if you are a user to capture their visual appearance BEFORE your change.
Take before-change screenshots of these views and UI elements you will be modifying and store those in spekka/specs/[this-spec]/verification/screenshots/before-change/. Do not store before-change screenshots anywhere in the codebase other than this location.

Implement the assigned task group according to requirements
Update spekka/specs/[this-spec]/tasks.md to update the tasks you've implemented to mark that as done by updating their checkbox to checked state: - [x]

Read the full file on GitHub · 59 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 · 59 lines · 0 tokens per session scan A b3fc5fcd26b8

Subscribe to this mod's changes

implement-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 784 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

implement-tasks next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
implement-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