Agtx Execute
Developmentagtx-executeAgtx Execute is an Agent Skill for development published in the fynnfluegge/agtx repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Execute an approved implementation plan. Implement the changes, then write a summary to .agtx/execute.md and stop.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/fynnfluegge/agtx/blob/HEAD/plugins/agtx-terse/skills/agtx-execute/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/agtx-execute, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
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
- Read
.agtx/plan.mdif it exists (skipget_task), otherwise fetch viaget_task - Implement the changes
- Run relevant tests to verify your changes
- 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.