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.
git clone --depth 1 https://github.com/fynnfluegge/agtx /tmp/agtx-plan && cp -r /tmp/agtx-plan/plugins/agtx-terse/skills/agtx-plan ~/.claude/skills/agtx-planSKILL.md
# 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.
Integrate a spec-driven/skill framework as a bundled agtx plugin. Pass a GitHub repo URL to auto-generate the plugin.toml, or run without arguments to write one from scratch.
Run SWE-bench Lite benchmarks against agtx coding agent workflows. Guides setup, configuration, execution, evaluation, and reporting.
Execute an approved implementation plan. Implement the changes, then write a summary to .agtx/execute.md and stop.
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 files.
Self-review completed work. Check for correctness, edge cases, and code quality. Write review to .agtx/review.md and stop.
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 push outcomes to the board.
Sweep this conversation into agtx tasks and push them to the kanban board. Use when the user wants to capture, decompose, or hand off conversation results to the agtx board.