A command that turns a software specification into an executable task DAG, or directed acyclic graph: a set of tasks with their required order and dependencies.

Finding a target project and specification, running planning agents, and producing a task graph for the /execute command.

It organizes a specification into work that can be executed in sequence or in parallel. The workflow also checks the plan before it is ready for execution.

plan — Command by Dowwie

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/dowwie/tasker/plan

Clone the repo

git clone --depth 1 https://github.com/Dowwie/tasker

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 100 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.00100
Opus 5	$0.00000	$0.00050
Sonnet 5	$0.00000	$0.00020
Haiku 4.5	$0.00000	$0.00010

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

Security

Grade A, and why

plan 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.

commands/plan.md · 12 lines

What it actually says

Plan

Decompose a specification into an executable task DAG.

IMPORTANT: Follow the instructions in the tasker:plan skill directly. Do NOT invoke any other skill.

The plan workflow guides you through:

Asking for the target project directory
Detecting specs from /specify workflow
Running planning agents (physical-architect, task-author, task-plan-verifier, plan-auditor)
Producing a task DAG ready for /execute

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 · 12 lines · 0 tokens per session scan A 00ca5d011b05

Subscribe to this mod's changes

plan is a command published in the GitHub repository Dowwie/tasker (19 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 100 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 agentic-development claude-code

plan

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

Plan

What this file has done since we first saw it

Other commands, from other repositories

spec-intake

ask-local

brainstorm

govern-audit

retro

review