extend-task

A workflow for adding new missions to a software task that is already partly or fully completed. It updates the existing task plan after requirements change or new work appears.

In plain words
What is it for?
Gathering and checking new requirements, appending missions to the progress tracker, reopening completed tasks, and updating roadmap status when needed.
Why use it?
It keeps added requirements connected to the original task instead of creating a separate, disconnected plan. It also surfaces unresolved questions before planning the new work.

Command for Claude Code

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/ayoubben18/ab-method/extend-task
Clone the repo
git clone --depth 1 https://github.com/ayoubben18/ab-method

Made for: Claude Code.

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

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00498
Opus 5 $0.00000 $0.00249
Sonnet 5 $0.00000 $0.00100
Haiku 4.5 $0.00000 $0.00050

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

Security

Grade A, and why

extend-task 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 2d 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/extend-task.md · 47 lines

How it starts

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

Extend Task

Description

Add new missions to an existing task after initial missions have been completed. Useful when requirements change or new features need to be added to an ongoing task.

Usage

/extend-task

Behavior

Loads and executes the extend-task workflow from .ab-method/core/extend-task.md

This workflow will:

  1. Select a task to extend
  2. Review current mission progress 2b. Surface any open unresolved questions (⚠️ UQ-n) — this is where a parked question gets answered: the workflow grills the answer, swaps the TODO(UQ-n) placeholder (or plans real missions if it's more than a seam swap), and marks the entry RESOLVED
  3. Gather requirements for new missions (grills if vague)
  4. Append the new missions as one-line entries in progress-tracker.md (no mission docs)
  5. Run critique-plan on the new missions — the pre-implementation domain critic pushes back only on genuine conflicts before you confirm
  6. Reopen the task if it was Completed — and, if it belongs to a roadmap, reopen its roadmap.md entry too (status: done → pending) so a /start-roadmap re-run picks up the new work in dependency order

Workflow Details

The extend-task workflow provides:

  • Task Selection - Choose which task to extend
  • Progress Review - See what missions are already completed
  • Mission Planning - Define new missions to add
  • Context Preservation - Maintain technical context from existing missions
  • Progress Tracking - Update progress-tracker.md with new missions (one-line entries, no separate mission docs)
  • Roadmap-aware - If the task is part of a roadmap, reopening it updates roadmap.md so /start-roadmap re-runs the extended work in dependency order
  • Optional Parallel Groups - Independent new missions can be tagged [pp-x] (or join a pending group) for concurrent subagent execution — only with the user's explicit yes

Examples

/extend-task
# Selects a task and adds new missions
# Creates detailed mission documents
# Updates progress tracker with additional missions

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

  1. 2d ago First seen · 47 lines · 0 tokens per session scan A 8e63f3ef4eab

Subscribe to this mod's changes

extend-task is a command published in the GitHub repository ayoubben18/ab-method (187 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 498 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.