Skip to content
Development
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.

From plugin
agtx
1.2k7 skills1 command1 MCP
Install
$ npx -y skills add fynnfluegge/agtx --skill brainstorm --agent claude-code

How 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/brainstorm

Context preview

The summary Claude sees to decide when to auto-load this skill.

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.

SKILL.md

brainstorm.SKILL.md
name: agtx-brainstorm
description: "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."
disable-model-invocation: true

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.

Read more
Ships withagtx

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.

Get the whole plugin
Stats
1,228
Stars
108
Forks
Active
Maintenance
Rust
Language
Apache-2.0
License
21h ago
Last commit
6mo ago
Created

Repo: fynnfluegge/agtx