Install any skill in seconds. Free to start, no credit card required.
Get Started Free →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.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-14 | ✗→✓ | ▲ Improved | -71% | 0% |
| case-17 | ✗→✓ | ▲ Improved | -23% | 0% |
| case-10 | ✓→✗ | ▼ Worse | -75% | 0% |
| case-13 | ✓→✗ | ▼ Worse | -37% | 0% |
| case-15 | ✓→✗ | ▼ Worse | -44% | 0% |
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.
Other measured skills in the registry, with their headline benchmark lift.