// 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.
Execute an approved implementation plan. Implement the changes, then write a summary to .agtx/execute.md and stop.
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.
| name | agtx-plan |
| description | 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. |
You are in the planning phase of an agtx-managed task.
The argument to this command is a task ID. Fetch the task description using the agtx MCP tool:
mcp__agtx__get_task(task_id: "<the id passed to this command>")
Use the description field as the task to work on. Also check for .agtx/research.md if a research phase was completed first.
get_task.agtx/research.md exists, read it for prior analysisWrite your plan to .agtx/plan.md in the current working directory (do NOT navigate up — write directly to .agtx/plan.md relative to where you are now) with these sections:
What you found in the codebase — relevant files, patterns, dependencies.
Step-by-step implementation plan — files to modify, approach, order of changes.
What could go wrong — edge cases, breaking changes, areas needing extra care.
After writing .agtx/plan.md (in the current working directory):
.agtx/plan.md. Waiting for approval."Terse. No pleasantries. Fragments OK. Short synonyms. Code exact. Status updates: one line. Pattern: [what] [why]. Done.