---
name: AGTX Execute
slug: agtx-execute
category: Automation
description: AGTX Execute implements an approved implementation plan in the current working directory, runs tests to verify changes, and writes a summary to .agtx/execute.md before stopping for further instructions.
github: "https://github.com/fynnfluegge/agtx/tree/main/plugins/agtx-terse/skills/agtx-execute"
language: Rust
stars: 1245
forks: 111
install: "npx degit https://github.com/fynnfluegge/agtx/tree/main/plugins/agtx-terse/skills/agtx-execute ~/.claude/skills/agtx-execute"
installs_to: ~/.claude/skills/agtx-execute
source_path: plugins/agtx-terse/skills/agtx-execute/SKILL.md
collection_size: 7
category_size: 1523
collection_url: "https://dirskills.com/collections/fynnfluegge/agtx"
added: 2026-08-20T07:55:21.099Z
last_synced: 2026-08-20T07:55:21.099Z
canonical_url: "https://dirskills.com/skills/agtx-execute"
---

# AGTX Execute

AGTX Execute implements an approved implementation plan in the current working directory, runs tests to verify changes, and writes a summary to .agtx/execute.md before stopping for further instructions.

**Install:**

```bash
npx degit https://github.com/fynnfluegge/agtx/tree/main/plugins/agtx-terse/skills/agtx-execute ~/.claude/skills/agtx-execute
```

## README

# Execution Phase

You are in the **execution phase** of an agtx-managed task.

## Input

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>")
```

## Instructions

1. Read `.agtx/plan.md` if it exists (skip `get_task`), otherwise fetch via `get_task`
2. Implement the changes
3. Run relevant tests to verify your changes
4. Fix any issues found during testing

## Output

When implementation is complete, write a summary to `.agtx/execute.md` in the **current working directory** with these sections:

## Changes
What files were modified/created and what was changed in each.

## Testing
How you verified the changes — tests run, results, manual checks.

## CRITICAL: Stop After Writing

After writing `.agtx/execute.md` (in the current working directory):
- Do NOT start new work beyond the plan
- Say: "Implementation complete. Summary written to `.agtx/execute.md`."
- Wait for further instructions

## Output Style

Terse. No pleasantries. Fragments OK. Short synonyms. Code exact.
Status updates: one line. Pattern: [what] [why]. Done.