Execute planned work from existing `prd`, `tdd`, and `tasks-plan` artifacts. Supports standard task mode, `--one-shot`, and `--preserve-review-artifacts`.
Implement task work from the required planning artifact set:
tasks/prd-<plan-key>.mdtasks/tdd-<plan-key>.mdtasks/tasks-plan-<plan-key>.mdInvoke explicitly with $execute-task.
Required request context:
<task-id> plus <plan-key> when it cannot be inferred--one-shot plus <plan-key> when it cannot be inferredSupported modifiers:
--one-shot--preserve-review-artifactsActivation examples:
$execute-task task-id=<task-id> plan-key=<plan-key>$execute-task task-id=<task-id>$execute-task --one-shot plan-key=<plan-key>$execute-task --one-shotLoad these files before running:
skills/shared/references/execution/task-file-contract.mdskills/shared/references/execution/task-management.mdskills/shared/references/review/review-protocol.mdtask-file-contract.md.review-protocol.md Step 1 rules, carrying and committing the required planning artifacts on the new branch when they are the only uncommitted kickoff files.tasks/tmp/plan-task-<task-id>.md with the sub-task contract before coding, then keep it current as implementation and review findings refine the slicesub-task review round automatically using the active prompt profile from review-protocol.md, in a fresh review subagent when subagents are available; in one-shot mode, defer Prompt G to the final full-branch reviewtasks/tmp/ when --preserve-review-artifacts is enabled; otherwise clean them up per protocoltasks/tasks-plan-<plan-key>.mdtasks/tasks-plan-<plan-key>.md after the commit, identify the next unchecked sub-task in file order, and continue directly when one existsfull-branch review round automatically using the active prompt profile from review-protocol.md in one fresh review subagent before finalization. This is the review round that must satisfy Prompt G for frontend-facing work.review-protocol.md Step 9 rules only after all unchecked sub-tasks in the task plan are complete, and do not treat one-shot execution as finished until the feature branch is pushed and the PR has been created.tasks/tasks-plan-<plan-key>.md and confirm there are no remaining unchecked sub-tasks anywhere in the file. If any remain, continue execution instead of handing off unless a real blocker prevents further progress.tasks/tmp/plan-task-<task-id>.md before implementation starts.Task execution includes automatic review rounds. Manual review runs through explicit $review-chain activation, optionally scoped to a specific <task-id>.