/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 files.
$ npx -y skills add fynnfluegge/agtx --skill agtx-research --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-research
Context preview
The summary Claude sees to decide when to auto-load this skill.
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.
SKILL.md
agtx-research.SKILL.mdname: agtx-research
description: 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.
Research Phase
You are in the **research phase** of an agtx-managed task. This is a read-only exploration.
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.
Instructions
1. Fetch the task description via `get_task` 2. Explore the codebase to find relevant files, patterns, and architecture 3. Identify dependencies, related code, and potential complexity 4. Assess feasibility and estimate scope
Output
Write your findings to `.agtx/research.md`. Include:
Relevant Files
Key files and their roles — what exists, what needs changing.
Architecture
How the relevant parts of the codebase fit together.
Complexity
Assessment of scope — simple change, moderate refactor, or major undertaking.
Open Questions
Things that need clarification before planning can begin.
CRITICAL: Do Not Modify Code
This is a **read-only** exploration:
- Do NOT modify any source files
- Do NOT create branches or worktrees
- Do NOT start planning or implementing
- Say: "Research complete. Findings written to .agtx/research.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-research description: 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.
Research Phase
You are in the **research phase** of an agtx-managed task. This is a read-only exploration.
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.
Instructions
1. Fetch the task description via `get_task` 2. Explore the codebase to find relevant files, patterns, and architecture 3. Identify dependencies, related code, and potential complexity 4. Assess feasibility and estimate scope
Output
Write your findings to `.agtx/research.md`. Include:
Relevant Files
Key files and their roles — what exists, what needs changing.
Architecture
How the relevant parts of the codebase fit together.
Complexity
Assessment of scope — simple change, moderate refactor, or major undertaking.
Open Questions
Things that need clarification before planning can begin.
CRITICAL: Do Not Modify Code
This is a **read-only** exploration:
- Do NOT modify any source files
- Do NOT create branches or worktrees
- Do NOT start planning or implementing
- Say: "Research complete. Findings written to .agtx/research.md."
- Wait for further instructions
Output Style
Terse. No pleasantries. Fragments OK. Short synonyms. Code exact. Status updates: one line. Pattern: [what] [why]. Done.
The blackboard for coding agents - Add tasks. Press one key. An orchestrator agent picks it up, plans, and delegates to multiple coding agents running in parallel. Come back to changes ready to merge.
Other skills on agtx.
- /benchmark
Run SWE-bench Lite benchmarks against agtx coding agent workflows. Guides setup, configuration, execution, evaluation, and reporting.
Open skill - /agtx-execute
Execute an approved implementation plan. Implement the changes, then write a summary to .agtx/execute.md and stop.
Open 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.
Open skill - /agtx-review
Self-review completed work. Check for correctness, edge cases, and code quality. Write review to .agtx/review.md and stop.
Open skill - /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 push outcomes to the board.
Open skill - /sweep
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.
Open skill