task_plan_withdraw — Claude Code subagent: what it does, install
The task_plan_withdraw Claude Code subagent withdraws a plan that has not been started. It runs when a plan from the current conversation is no longer needed.
MIT ★ 395 updated 2026-11-16
.claude/agents/task_plan_withdraw.mdWhat task_plan_withdraw does
The subagent removes a task_plan card from the waiting-to-start state and takes it out of the pending-plan and briefing lists. It records the reason and tells the user in one line which card was withdrawn and why.
It needs the plan's plan_id and a one-sentence reason in the user's language. It refuses plans that have started, were already withdrawn, or belong to another conversation; those plans remain unchanged.
What it helps with
- withdraw a plan whose work was completed elsewhere
- cancel a plan the user decided not to carry out
- remove an unwanted card from pending-plan and briefing lists
Example prompts for the agent
- Withdraw
plan_123; the work was completed elsewhere. - Cancel
plan_123because the user decided not to do this plan.
How to install task_plan_withdraw
Manually: put the files in place
.claude/agents/task_plan_withdraw.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/task_plan_withdraw.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/task_plan_withdraw.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about task_plan_withdraw
How do I install task_plan_withdraw in Claude Code?
Add the agent file at .claude/agents/task_plan_withdraw.md.
What does task_plan_withdraw do?
It withdraws a not-yet-started plan from the current conversation, records the reason, and reports which card it removed.
Which plans can task_plan_withdraw withdraw?
Only a plan from the current conversation that is still waiting to start. It leaves started plans, already withdrawn plans, and plans from other conversations unchanged.
Source text
task_plan_withdraw.md · MIT
Take down a plan card this conversation put up (task_plan) while nothing of it has started: its work was done elsewhere, or the user decided not to do it. The card stops waiting for the user's 开始, as when they dismiss it themselves, and leaves the to-handle lists (the snapshot's plans waiting to start, the briefings). Only for a plan of this conversation that still waits for 开始; a started or dismissed plan, or another conversation's, is refused and nothing changes. Your reason is kept on record; tell the user in a line which card you took down and why.
```json
{
"type": "object",
"required": ["plan_id", "reason"],
"properties": {
"plan_id": {
"type": "string",
"description": "the plan's id (plan_…), as task_plan's answer or the snapshot's plans waiting to start give it"
},
"reason": {
"type": "string",
"description": "why it is no longer needed, in the user's language, one sentence"
}
}
}
```
© nwverse · MIT · nwverse/persona