// Cancel a task module — set status to cancelled, stop auto if running, optionally clean up worktree. Use when a task becomes infeasible, is deprioritized, or needs to be abandoned.
Process Plan panel annotations — triage, cross-impact assessment, and execution. Triggered automatically when annotations (Insert/Delete/Replace/Comment) are submitted from the Plan panel UI.
Autonomous execution loop — single Claude session orchestrates plan/check/exec cycle internally
Check plan feasibility at key checkpoints — post-plan, mid-execution, post-execution
Execute the implementation plan for a reviewed task module. Triggered after check PASS (from review status) or on NEEDS_FIX continuation (from executing status with fix guidance).
Initialize a new task module in AiTasks/ directory with system files, git branch, and optional worktree. Use when starting a new feature, bug fix, or refactoring task that needs structured lifecycle tracking.
Query task status and relationships — read-only, no file writes. Use to inspect task inventory, check progress, view dependency graphs, or audit status transition history.
| name | cancel |
| description | Cancel a task module — set status to cancelled, stop auto if running, optionally clean up worktree. Use when a task becomes infeasible, is deprioritized, or needs to be abandoned. |
| arguments | [{"name":"task_module","description":"Path to the task module directory (e.g., AiTasks/auth-refactor)","required":true},{"name":"reason","description":"Cancellation reason (recorded in .index.json)","required":false},{"name":"cleanup","description":"Also remove git worktree and delete the task branch (flag, no value)","required":false}] |
Cancel a task module, stopping any active auto loop and optionally cleaning up the git worktree.
/moonview:cancel <task_module_path> [--reason "..."] [--cleanup]
.index.json body.index.json — get current statusGET /api/task-auto/lookup?taskDir=<task_module_path> to find the session running this task's auto loopDELETE /api/sessions/<session_name>/task-auto.auto-signal file if exists.auto-stop file if exists.lock file if exists — first read lock content and verify the holder: (a) if holder pid is dead → delete lock (stale); (b) if holder session matches the auto session being cancelled → delete lock (same session); (c) if held by a different live session → REJECT with error identifying the holding session — user must stop that session first or use cancel from the holding session. Cancel does NOT force-override locks held by other live sessions to prevent concurrent write corruption-- ai-cli-task(<module>):cancel pre-cancel snapshot.index.json:
status to cancelledupdated timestamp.summary.md with condensed context: current status, cancellation reason, progress at time of cancellation (completed_steps), any known issues-- ai-cli-task(<module>):cancel user cancelled--cleanup:
git worktree remove .worktrees/task-<module>git branch -d task/<module> (safe delete — warns if unmerged). If -d fails because branch has unmerged work, report warning to user with the unmerged commit count. User can explicitly re-run with git branch -D if they want to force-deleteAny non-terminal status → cancelled. Terminal statuses (complete, cancelled) → REJECT.
complete (use a separate workflow to reopen) and cancelled (already terminal)--cleanup will warn before deleting--cleanup, the branch and worktree are preserved for referencereport for documentation purposes