benchmark
Run SWE-bench Lite benchmarks against agtx coding agent workflows. Guides setup, configuration, execution, evaluation, and…
@fynnflueggeInstall SkillDevelopment
Skill
/agtx-execute
Execute an approved implementation plan. Implement the changes, then write a summary to .agtx/execute.md and stop.
Claude Code
$ npx -y skills add fynnfluegge/agtx --skill agtx-execute --agent claude-code
Codex
$ npx skills add fynnfluegge/agtx --skill agtx-execute -a codex -y
Cursor
$ npx skills add fynnfluegge/agtx --skill agtx-execute -a cursor -y
Gemini CLI
$ npx skills add fynnfluegge/agtx --skill agtx-execute -a gemini-cli -y
GitHub Copilot
$ npx skills add fynnfluegge/agtx --skill agtx-execute -a github-copilot -y
OpenCode
$ npx skills add fynnfluegge/agtx --skill agtx-execute -a opencode -y
Windsurf
$ npx skills add fynnfluegge/agtx --skill agtx-execute -a windsurf -y
SKILL.md
agtx-execute.SKILL.mdname: agtx-execute
description: Execute an approved implementation plan. Implement the changes, then write a summary to .agtx/execute.md and stop.
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 5. Commit. `git add -A`, commit with a short imperative message, verify `git status --short` clean. Your worktree is deleted at task completion — uncommitted work is destroyed and the merge is blocked. agtx's own files are already git-excluded, so `add -A` takes only your work.
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.
Read more
name: agtx-execute description: Execute an approved implementation plan. Implement the changes, then write a summary to .agtx/execute.md and stop.
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 5. Commit. `git add -A`, commit with a short imperative message, verify `git status --short` clean. Your worktree is deleted at task completion — uncommitted work is destroyed and the merge is blocked. agtx's own files are already git-excluded, so `add -A` takes only your work.
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.
In this plugin
See everything inside Ships withagtx
The terminal-native agentic development environment for 10x productivity. A blackboard for coding agents - One shared board. A fleet of agents.
1.7k8 skills1 MCP
Stars on GitHub
Momentum
- stars in total
- 1.7k
Other skills on agtx.
@fynnflueggeInstall Skillagtx-plan
Plan a task implementation. Analyze the codebase, create a detailed plan, write it to .agtx/plan.md, then stop and wait for user…
@fynnflueggeInstall Skillagtx-research
Explore the codebase to understand a task before planning. Write findings to .agtx/research.md and stop. This is a read-only…
@fynnflueggeInstall Skillagtx-review
Self-review completed work. Check for correctness, edge cases, and code quality. Write review to .agtx/review.md and stop.
@fynnflueggeInstall Skillbrainstorm
Enter brainstorm mode to explore a feature or enhancement idea. Stays in discussion mode only — no planning, no implementation.…
@fynnflueggeInstall Skilloneshot
One-shot a whole project on an agtx board: decompose the goal, run every task unattended, unblock the workers, and merge each…
@fynnflueggeInstall SkillMore skills from other plugins.
Auto-invoked
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
@obraInstall Skillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
@mattpocockInstall SkillAuto-invoked
Questions about agtx-execute.
- Which coding agents can use agtx-execute?
- agtx-execute installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.