A command that creates a dependency-ordered task list for a software feature from available design documents. It uses documents such as the feature specification and implementation plan, plus optional data models, interface contracts, research, and test scenarios.

Use it to inspect a feature’s design artifacts and produce a tasks.md file for implementation. If no feature documents exist, it directs the user to create a specification first.

It turns design information into a practical work breakdown and exposes when the project lacks the documents needed to plan safely. It also keeps tasks connected to user stories and their priorities.

tasks — Command for Claude Code by akka

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.

Clone the repo

git clone --depth 1 https://github.com/akka/ai-marketplace

Made for: Claude Code.

Or install akka-specify, the plugin that ships this one along with the rest of its 13 commands.

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/akka/ai-marketplace/tasks.svg)](https://agentmods.dev/commands/akka/ai-marketplace/tasks)

Your own site

<a href="https://agentmods.dev/commands/akka/ai-marketplace/tasks"><img src="https://agentmods.dev/badge/commands/akka/ai-marketplace/tasks.svg" alt="Measured on agentmods" height="20"></a>

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

When invoked 1,484 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 86% copy Near-identical to another mod 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.00018	$0.01484
Opus 5	$0.00009	$0.00742
Sonnet 5	$0.00004	$0.00297
Haiku 4.5	$0.00002	$0.00148

Measured 8d ago against content hash 42a8685f1153, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

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 8d 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.

Origin

This is a copy

86% identical to speckit.tasks — 38 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

plugins/akka-specify/commands/tasks.md · 138 lines

How it starts

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

User Input

$ARGUMENTS

You MUST consider the user input before proceeding (if not empty).

Outline

Setup: Call the akka_sdd_list_specs MCP tool to find features and their available documents. From the response, identify the target feature's FEATURE_DIR and which artifacts exist (AVAILABLE_DOCS: spec.md, plan.md, tasks.md, etc.). If no features exist, instruct the user to run /akka-specify:specify first.
Load design documents: Read from FEATURE_DIR:
- Required: plan.md (tech stack, libraries, structure), spec.md (user stories with priorities)
- Optional: data-model.md (entities), contracts/ (interface contracts), research.md (decisions), quickstart.md (test scenarios)
- Note: Not all projects have all documents. Generate tasks based on what's available.
Execute task generation workflow:
- Load plan.md and extract tech stack, libraries, project structure
- Load spec.md and extract user stories with their priorities (P1, P2, P3, etc.)
- If data-model.md exists: Extract entities and map to user stories
- If contracts/ exists: Map interface contracts to user stories
- If research.md exists: Extract decisions for setup tasks
- Generate tasks organized by user story (see Task Generation Rules below)
- Generate dependency graph showing user story completion order
- Create parallel execution examples per user story
- Validate task completeness (each user story has all needed tasks, independently testable)
Generate tasks.md: Use akka_sdd_get_template as structure, fill with:
- Correct feature name from plan.md
- Phase 1: Setup tasks (project initialization)
- Phase 2: Foundational tasks (blocking prerequisites for all user stories)
- Phase 3+: One phase per user story (in priority order from spec.md)
- Each phase includes: story goal, independent test criteria, tests (if requested), implementation tasks
- Final Phase: Polish & cross-cutting concerns
- All tasks must follow the strict checklist format (see Task Generation Rules below)
- Clear file paths for each task
- Dependencies section showing story completion order
- Parallel execution examples per story
- Implementation strategy section (MVP first, incremental delivery)

Read the full file on GitHub · 138 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.

8d ago First seen · 138 lines · 18 tokens per session scan A 42a8685f1153

Subscribe to this mod's changes

tasks is a command published in the GitHub repository akka/ai-marketplace (6 stars, last pushed 8d ago), licensed Apache-2.0. It adds 18 tokens to every session and 1,484 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to speckit.tasks, differing in 38 lines, and is treated as a copy.

Claude Code Planning Project management ai akka gemini-ai spec-driven-development

speckit.companion.implement

Companion implement — execute tasks.md in dependency order, then mark complete.

alfredoperez/speckit-companion · 14 tokens

speckit.companion.tasks

Companion tasks — user-story phased task list.

alfredoperez/speckit-companion · 9 tokens

speckit.companion.doctor

Report on a spec's run health — unfinished steps, unjournaled tasks, step bleed, drift you can judge, a step that closed having verified nothing, a step that closed without the file it promised, and why completion did not land (read-only, retroactive, never halts).

alfredoperez/speckit-companion · 59 tokens

tasks