Skill
benchmark
Run SWE-bench Lite benchmarks against agtx coding agent workflows. Guides setup, configuration, execution, evaluation, and reporting.
@fynnflueggeView SkillDevelopment
Skill
/agtx-plan
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.
Install
$ npx -y skills add fynnfluegge/agtx --skill agtx-plan --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/agtx-plan
Context preview
The summary Claude sees to decide when to auto-load this skill.
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.
SKILL.md
agtx-plan.SKILL.mdname: agtx-plan
description: 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.
Planning Phase
You are in the **planning phase** of an agtx-managed task.
Input
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.
Instructions
1. Fetch the task description via `get_task` 2. If `.agtx/research.md` exists, read it for prior analysis 3. Explore the codebase to understand relevant files, patterns, and architecture 4. Identify all files that need to be created or modified 5. Create a detailed implementation plan
Output
Write 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:
Analysis
What you found in the codebase — relevant files, patterns, dependencies.
Plan
Step-by-step implementation plan — files to modify, approach, order of changes.
Risks
What could go wrong — edge cases, breaking changes, areas needing extra care.
CRITICAL: Stop After Writing
After writing `.agtx/plan.md` (in the current working directory):
- Do NOT start implementing
- Do NOT modify any source files
- Say: "Plan written to `.agtx/plan.md`. Waiting for approval."
- Wait for explicit instructions to proceed
Output Style
Terse. No pleasantries. Fragments OK. Short synonyms. Code exact. Status updates: one line. Pattern: [what] [why]. Done.
Read more
name: agtx-plan description: 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.
Planning Phase
You are in the **planning phase** of an agtx-managed task.
Input
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.
Instructions
1. Fetch the task description via `get_task` 2. If `.agtx/research.md` exists, read it for prior analysis 3. Explore the codebase to understand relevant files, patterns, and architecture 4. Identify all files that need to be created or modified 5. Create a detailed implementation plan
Output
Write 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:
Analysis
What you found in the codebase — relevant files, patterns, dependencies.
Plan
Step-by-step implementation plan — files to modify, approach, order of changes.
Risks
What could go wrong — edge cases, breaking changes, areas needing extra care.
CRITICAL: Stop After Writing
After writing `.agtx/plan.md` (in the current working directory):
- Do NOT start implementing
- Do NOT modify any source files
- Say: "Plan written to `.agtx/plan.md`. Waiting for approval."
- Wait for explicit instructions to proceed
Output Style
Terse. No pleasantries. Fragments OK. Short synonyms. Code exact. Status updates: one line. Pattern: [what] [why]. Done.
Ships withagtx
The terminal-native agentic development environment for 10x productivity. A blackboard for coding agents - One shared board. A fleet of agents.
Get the whole plugin
In this plugin
See everything inside Other skills on agtx.
@fynnflueggeView SkillSkill
agtx-execute
Execute an approved implementation plan. Implement the changes, then write a summary to .agtx/execute.md and stop.
@fynnflueggeView SkillSkill
agtx-research
Explore the codebase to understand a task before planning. Write findings to .agtx/research.md and stop. This is a read-only exploration — do not modify any…
@fynnflueggeView SkillSkill
agtx-review
Self-review completed work. Check for correctness, edge cases, and code quality. Write review to .agtx/review.md and stop.
@fynnflueggeView SkillSkill
brainstorm
Enter brainstorm mode to explore a feature or enhancement idea. Stays in discussion mode only — no planning, no implementation. Use /agtx:sweep when ready to…
@fynnflueggeView SkillSkill
oneshot
One-shot a whole project on an agtx board: decompose the goal, run every task unattended, unblock the workers, and merge each one. Use when the user wants a…
@fynnflueggeView Skill