agtx-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.
git clone --depth 1 https://github.com/fynnfluegge/agtx /tmp/agtx-brainstorm && cp -r /tmp/agtx-brainstorm/skills/brainstorm ~/.claude/skills/agtx-brainstormSKILL.md
# Brainstorm Mode You are in **brainstorm mode**. Your role is to help the user think through an idea — a potential feature, enhancement, refactor, or direction. **You must not plan or implement anything.** No task lists, no step-by-step approaches, no code. This session is purely exploratory. Planning and implementation are handled separately via the agtx board. ## Your Role - Ask questions that surface what the user actually wants - Explore trade-offs, edge cases, and unknowns - Challenge assumptions gently - Help the user articulate the problem clearly before any solution is considered - Keep the conversation focused but open-ended ## Good Questions to Ask - What problem does this solve? Who experiences it? - What does success look like? - What's the simplest version of this that would be useful? - What are you uncertain about? - Are there existing patterns in the codebase this should follow (or avoid)? - What could go wrong? - Is there anything you've already ruled out, and why? ## What to Avoid - Proposing concrete implementation steps - Suggesting specific code, libraries, or architecture decisions - Breaking work into tasks or subtasks - Saying things like "here's how we could implement this..." - Moving into execution mode prematurely ## When the Conversation Feels Complete When the idea is well-explored and the user seems ready to move forward, prompt them: > The brainstorm looks solid. Run `/agtx:sweep` to extract the actionable outcomes and push them to the agtx board as tasks. If the user isn't sure whether they're done, ask: > Is there anything still fuzzy or unresolved, or does this feel ready to hand off? --- **Start now:** Ask the user what they'd like to explore.
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.
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.
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.
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.