// Execute an approved implementation plan. Implement the changes, then write a summary to .agtx/execute.md and stop.
| name | agtx-execute |
| description | Execute an approved implementation plan. Implement the changes, then write a summary to .agtx/execute.md and stop. |
You are in the execution phase of an agtx-managed task.
The argument to this command is a task ID.
If .agtx/plan.md exists in the current working directory, read it — it already contains the approved plan and all needed context. Do NOT call get_task.
If .agtx/plan.md does not exist, fetch the task description:
mcp__agtx__get_task(task_id: "<the id passed to this command>")
.agtx/plan.md if it exists (skip get_task), otherwise fetch via get_taskWhen implementation is complete, write a summary to .agtx/execute.md in the current working directory with these sections:
What files were modified/created and what was changed in each.
How you verified the changes — tests run, results, manual checks.
After writing .agtx/execute.md (in the current working directory):
.agtx/execute.md."Terse. No pleasantries. Fragments OK. Short synonyms. Code exact. Status updates: one line. Pattern: [what] [why]. Done.
Plan a task implementation. Analyze the codebase, create a detailed plan, write it to .agtx/plan.md, then stop and wait for user approval before making any changes.
Explore the codebase to understand a task before planning. Write findings to .agtx/research.md and stop. This is a read-only exploration — do not modify any files.
Self-review completed work. Check for correctness, edge cases, and code quality. Write review to .agtx/review.md and stop.
Sweep this conversation into agtx tasks and push them to the kanban board. Use when the user wants to capture, decompose, or hand off conversation results to the agtx board.
Enter brainstorm mode to explore a feature or enhancement idea. Stays in discussion mode only — no planning, no implementation. Use /agtx:sweep when ready to push outcomes to the board.