Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Execute an approved implementation plan. Implement the changes, then write a summary to .agtx/execute.md and stop.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-04 | ✗→✓ | ▲ Improved | -6% | 0% |
| case-05 | ✗→✓ | ▲ Improved | -55% | 0% |
| case-12 | ✗→✓ | ▲ Improved | -48% | 0% |
| case-13 | ✗→✓ | ▲ Improved | -45% | 0% |
| case-15 | ✗→✓ | ▲ Improved | -71% | 0% |
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.
Other measured skills in the registry, with their headline benchmark lift.