What is implement-tasks?

A task implementation command that carries out the tasks in a project plan. For code, it can use TDD, a process of writing a failing test before the code that makes it pass; documents and configuration are implemented directly.

Use it to implement planned code changes, tests, documentation, and configuration updates.

It turns a task list into working changes while applying the project's specified development approach.

implement-tasks — Command by Zts0hg

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/zts0hg/codexspec/implement-tasks

Clone the repo

git clone --depth 1 https://github.com/Zts0hg/codexspec

Made for: Claude Code.

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

When invoked 4,405 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.00023	$0.04405
Opus 5	$0.00012	$0.02202
Sonnet 5	$0.00005	$0.00881
Haiku 4.5	$0.00002	$0.00441

Measured 3d ago against content hash 815c528fa467, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 3d 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/codexspec/implement-tasks.md · 405 lines

How it starts

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

Task Implementer

Language Preference

Read .codexspec/config.yml. Two independent language controls apply (each falls back to language.output, then English):

Interaction language (language.interaction): language for all conversation with the user — questions, explanations, status messages, and codexspec CLI terminal output.
Document language (language.document): language for generated artifact files (requirements/spec/plan/tasks).

Converse in the interaction language and author artifacts in the document language. Apply the project's translation standard to both: translate by meaning (not word-for-word), keep English for terms with no good native equivalent, and write as if originally in that language.

Feature Resolution

Resolve the feature in this order:

Use an explicit path from $ARGUMENTS when it identifies a tasks.md file or feature directory.
Otherwise match the current branch, which must use the timestamp format, to .codexspec/specs/<branch>/.
If no unique feature can be resolved, ask the user to select one. Never silently select the latest workspace.

Derive all artifact paths from the selected feature directory. All implementation-side output belongs to that workspace.

Input Documents and Authority

Read:

requirements.md
spec.md
design.md
plan.md
tasks.md
.codexspec/memory/constitution.md when present

Authority order:

Confirmed entries in requirements.md
spec.md
Constitution and verified repository facts
design.md
Approved plan.md
tasks.md

A legacy feature may have no design.md; when it is absent, proceed with plan.md as the design-and-plan authority.

When requirements.md is absent, use legacy spec-only mode. Treat spec.md as the temporary highest feature authority and state that fidelity to the original discussion cannot be verified.

Role

You are an autonomous implementation agent. Your responsibility is to execute all tasks in the task list systematically until completion.

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

3d ago First seen · 405 lines · 23 tokens per session scan A 815c528fa467

Subscribe to this mod's changes

implement-tasks is a command published in the GitHub repository Zts0hg/codexspec (5 stars, last pushed 4d ago), licensed MIT. It adds 23 tokens to every session and 4,405 once invoked, about $0.0001 per session on Opus 5. 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 TDD Testing ai-assisted-development claude-code cli-tool i18n sdd

implement-tasks