Brainstorming
xpinjection/test-driven-spring-boot
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior.
Brainstorms and debates approaches, then drives toward an actionable decision.
Install Discuss
$ npx skills add avibebuilder/claude-prime --skill discuss -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install avibebuilder/claude-prime discuss --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/avibebuilder/claude-prime.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/discuss .claude/skills/discuss && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "discuss" agent skill from https://github.com/avibebuilder/claude-prime/tree/main/.claude/skills/discuss into .claude/skills/discuss/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "discuss", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/avibebuilder/claude-prime/tree/main/.claude/skills/discussType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add avibebuilder/claude-prime --skill discuss -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install avibebuilder/claude-prime discuss --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/avibebuilder/claude-prime.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/discuss .agents/skills/discuss && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "discuss" agent skill from https://github.com/avibebuilder/claude-prime/tree/main/.claude/skills/discuss into .agents/skills/discuss/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "discuss", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add avibebuilder/claude-prime --skill discuss -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install avibebuilder/claude-prime discuss --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/avibebuilder/claude-prime.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/discuss .cursor/skills/discuss && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "discuss" agent skill from https://github.com/avibebuilder/claude-prime/tree/main/.claude/skills/discuss into .cursor/skills/discuss/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "discuss", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/avibebuilder/claude-prime.git --path .claude/skills/discuss--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add avibebuilder/claude-prime --skill discuss -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install avibebuilder/claude-prime discuss --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/avibebuilder/claude-prime.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/discuss .gemini/skills/discuss && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "discuss" agent skill from https://github.com/avibebuilder/claude-prime/tree/main/.claude/skills/discuss into .gemini/skills/discuss/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "discuss", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install avibebuilder/claude-prime discussInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add avibebuilder/claude-prime --skill discuss -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/avibebuilder/claude-prime.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/discuss .github/skills/discuss && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "discuss" agent skill from https://github.com/avibebuilder/claude-prime/tree/main/.claude/skills/discuss into .github/skills/discuss/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "discuss", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add avibebuilder/claude-prime --skill discuss -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install avibebuilder/claude-prime discuss --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/avibebuilder/claude-prime.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/discuss .opencode/skills/discuss && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "discuss" agent skill from https://github.com/avibebuilder/claude-prime/tree/main/.claude/skills/discuss into .opencode/skills/discuss/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "discuss", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
discuss- GitHub stars
- 120
- Used in
- 1 other repo
- Token cost
- ~1.3k tokens
- SKILL.md length
- 701 words
- Files
- 1
- Skills in repo
- 19
- Repo updated
- First seen
- Licence
- MIT
At a glance
Brainstorms and debates approaches, then drives toward an actionable decision.
- Works in 6 steps: Clarify (if needed) → Ground the discussion (if needed) → Pick the right decision lens → …
- Someone needs a thinking partner for a decision theyre facing: discuss
- SKILL.md covers How to think in this mode, Process, Tone calibration and Gotchas, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Discuss is an agent skill from avibebuilder/claude-prime. Brainstorms and debates approaches, then drives toward an actionable decision. Use whenever someone needs a thinking partner for a decision they're facing: 'discuss', 'debate', 'brainstorm', 'weigh options', 'tradeoffs', 'should I do X or Y', 'help me decide', 'I'm torn between', 'sanity check my thinking', or 'what do you think about'. The user must be asking for help reasoning through a choice — not asking to build, fix, evaluate, plan, or modify something (even if the topic involves this skill itself). Picks…
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering Brainstorming. The repository describes itself as: You've heard Claude Code can do amazing things. Skills, hooks, agents, memory systems — but who has time to figure all that out? Claude Prime sets it up for you in one command. The licence is MIT.
When your agent uses it
- Someone needs a thinking partner for a decision theyre facing: discuss
- Im torn between
- Sanity check my thinking
- What do you think about
Example prompts
- “re facing:”
- “debate”
- “brainstorm”
- “/discuss”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 80bcfa4. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Discuss loads about 1.3k tokens when it runs. Until then it costs about 163 tokens; SKILL.md has 701 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from avibebuilder/claude-prime at commit 80bcfa4, republished under its MIT licence (© avibebuilder). 701 words, ~1,337 tokens.
Download SKILL.mdSave it as
.claude/skills/discuss/SKILL.md (or your agent's skills folder).- name
- discuss
- description
- Brainstorms and debates approaches, then drives toward an actionable decision. Use whenever someone needs a thinking partner for a decision they're facing: 'discuss', 'debate', 'brainstorm', 'weigh options', 'tradeoffs', 'should I do X or Y', 'help me decide', 'I'm torn between', 'sanity check my thinking', or 'what do you think about'. The user must be asking for help reasoning through a choice — not asking to build, fix, evaluate, plan, or modify something (even if the topic involves this skill itself). Picks the right decision lens, surfaces tradeoffs and blind spots, pushes back when reasoning is genuinely weak, and never implements.
- argument-hint
- topic
ultrathink
How to think in this mode
The job is to help the user see the decision clearly — what's at stake, what they're missing, where the real tradeoffs are. Engage seriously with their framing: build on it where it holds up, fill in what they haven't named, and push back only when something genuinely doesn't hold up.
Do not implement. Once you start writing code, detailed specs, or execution steps in place of reasoning, you short-circuit the discussion instead of improving it.
Process
Check conversation context and skip completed steps.
1. Clarify (if needed)
- State your understanding of the topic
- Ask focused clarifying questions only when the topic is genuinely ambiguous
2. Ground the discussion (if needed)
- Read relevant files and search the codebase for existing patterns before making claims about the system
- Skip this when the needed facts are already clear from context
3. Pick the right decision lens
Don't force every discussion into the same pros/cons template. Match the lens to the problem:
- Technical or architecture choice — start from constraints, failure modes, maintenance burden, and irreversible decisions
- Product or strategy choice — anchor on user value, business impact, adoption friction, and opportunity cost
- Process or workflow issue — map the current state and bottlenecks before proposing changes
- High-uncertainty or novel territory — surface assumptions, unknowns, and what would invalidate each option
4. Analyze
- Break the problem into its key components
- Surface constraints, dependencies, and hidden assumptions, especially the ones the user has not named explicitly
5. Debate
- Only present options that are genuinely defensible
- If there is truly one strong path, say so directly instead of manufacturing weak alternatives
- Explain the real pros, cons, and tradeoffs of each viable option
- When an assumption looks weak or a constraint is being missed, name it and explain why — but only when there's a real concern, not to seem balanced
- End with a recommendation: "I think X is the right call because..."
6. Synthesize
- Land on a direction with clear rationale
- Call out unresolved items and whether they matter now or can wait
- Give concrete next steps for the user to take after the discussion
- If the discussion has clearly converged on a concrete decision or recommendation, and capturing it would likely save future rediscovery, optionally end with a brief offer to capture it in a durable doc via
create-doc - Keep that capture offer short and optional. Do not make it if the discussion is still exploratory, the decision is unsettled, or the user is clearly done and does not need another prompt
Show full SKILL.md (282 more words)Show less
Tone calibration
Read the room. A peer asking for a blunt sanity check usually wants direct feedback. Someone deeply invested in an idea still needs honesty, but with more care in delivery. Adjust the tone without softening your actual reasoning.
Gotchas
- Reflexive pushback: Treating every input as something to challenge is just as bad as agreeing with everything — it's noise that makes the discussion worse and wears the user out. Pushback should only show up when you have a real concern (weak reasoning, ignored constraint, blind spot). If the user's framing holds up, say so and build forward; the value you add then is range, depth, and what they haven't considered — not always resistance
- Being a yes-man: The opposite failure — mirroring the user's framing back without adding anything. The fix isn't more pushback; it's bringing new information, context, or considerations they didn't have
- Opinions without evidence: If you're making claims about code, architecture, or current behavior, ground them in files or facts first
- Strawman options: Presenting one real option plus two weak ones is advocacy dressed up as debate. Every option should be one you could genuinely argue for. Bad: "Option A (the real answer), Option B (A but worse), Option C (obviously impractical)." Good: two genuinely different approaches with real tradeoffs, or just one clear recommendation if that's the honest answer
- Analysis paralysis: Endless pros/cons without a recommendation is a failure mode. Good-enough decisions beat perfect decisions that never happen
- Ignoring constraints: Time, budget, and team capability usually matter more than theoretical elegance
- Premature capture nudges: Only offer to write things up when there is a real conclusion worth preserving. Do not turn every discussion into a documentation prompt
Topic
<topic>$ARGUMENTS</topic>
© avibebuilder, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/discuss of avibebuilder/claude-prime.
Open the folder on GitHubat commit 80bcfa4
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in avibebuilder/claude-prime, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Discuss next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Discuss this skillavibebuilder/claude-prime | 120 | 1 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Brainstormingxpinjection/test-driven-spring-boot | 112 | 54 repos | ~2.6k | Automated safety check: Pass | MIT | |
| LLM Councilgcpdev/llm-council-skill | 461 | 1 repos | ~1k | Automated safety check: Notes | MIT | |
| Typesafe AIOpenAgentsInc/openagents | 455 | 9 repos | ~2.5k | Automated safety check: Pass | MIT | |
| Yao Meta Skillyaojingang/yao-meta-skill | 2.7k | — | ~768 | Automated safety check: Pass | MIT | |
| Trellis StartROYIANS/foliq-print-template-designer | 135 | 6 repos | ~646 | Automated safety check: Pass | MIT |
Similar skills
LLM Council
gcpdev/llm-council-skill
Multi-LLM collaborative brainstorming and planning. An agent skill from gcpdev/llm-council-skill.
Typesafe AI
OpenAgentsInc/openagents
Build AI-powered software with TypeSafe: small units of AI intelligence you can use like programming primitives.
Yao Meta Skill
yaojingang/yao-meta-skill
Create, improve, or evaluate an existing skill from workflows, prompts, SOPs, scripts.
Trellis Start
ROYIANS/foliq-print-template-designer
Initializes an AI development session by reading workflow guides, developer identity, git status, active tasks, and project guidelines from .trellis/.
Brainstorming Before Building
jnMetaCode/superpowers-zh
Turns a rough idea into an approved design before any code is written, sorting the request into spike, bounded or architectural and enforcing an approval gate.
More from avibebuilder/claude-prime
All 19 skills in this repoDiagnose
avibebuilder/claude-prime
Investigate unexpected behavior and mysterious bugs. An agent skill from avibebuilder/claude-prime.
Frontend Design
avibebuilder/claude-prime
Builds distinctive, production-grade UIs that avoid generic AI aesthetics.
Media Processor
avibebuilder/claude-prime
Specialized visual and multimedia processing tools. An agent skill from avibebuilder/claude-prime.
Skill Creator
avibebuilder/claude-prime
A skill your agent uses when the user wants to work on a Claude Code skill file (SKILL.md): writing one from scratch, testing whether an existing one works well, running evals or benchmarks…
Self Evolve
avibebuilder/claude-prime
The single config quality skill. An agent skill from avibebuilder/claude-prime.
Cook
avibebuilder/claude-prime
Implement, build, create, or add any feature, endpoint, page, component, or functionality.
Related
Categories
Questions about Discuss
What does Discuss do?
Brainstorms and debates approaches, then drives toward an actionable decision. Discuss is an agent skill from avibebuilder/claude-prime. Brainstorms and debates approaches, then drives toward an actionable decision.
When should I use Discuss?
Discuss fits situations like: someone needs a thinking partner for a decision theyre facing: discuss; im torn between; sanity check my thinking; what do you think about.
How do I install Discuss in Claude Code?
Run `npx skills add avibebuilder/claude-prime --skill discuss -a claude-code`. Or copy the skill folder (.claude/skills/discuss in avibebuilder/claude-prime) into .claude/skills/discuss in your project. Claude Code loads it when a task matches its description.
How do I install Discuss in Codex?
Run `npx skills add avibebuilder/claude-prime --skill discuss -a codex`. Or copy the skill folder (.claude/skills/discuss in avibebuilder/claude-prime) into .agents/skills/discuss in your project. Codex loads it when a task matches its description.
Can I use Discuss in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add avibebuilder/claude-prime --skill discuss -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/discuss, .gemini/skills/discuss, .github/skills/discuss and .opencode/skills/discuss in your project.
What does Discuss need to run?
SKILL.md names no scripts, command-line tools or credentials: Discuss is instructions for the agent only.
Does Discuss access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Discuss safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Discuss use?
Discuss is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Discuss use?
About 1.3k tokens (SKILL.md is roughly 5.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Discuss?
Skills that share tags, products or a category with Discuss: Brainstorming (xpinjection/test-driven-spring-boot, 112 stars), LLM Council (gcpdev/llm-council-skill, 461 stars), Typesafe AI (OpenAgentsInc/openagents, 455 stars) and Yao Meta Skill (yaojingang/yao-meta-skill, 2.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Discuss?
avibebuilder (a GitHub organization) maintains it in avibebuilder/claude-prime, which has 120 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on May 16, 2026.
Source: avibebuilder/claude-prime on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.