discuss
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 reaso
npx skills add majiayu000/claude-skill-registry --skill discuss --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
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**
- How to think in this mode
- Process
- 1. Clarify (if needed)
- 2. Ground the discussion (if needed)
- 3. Pick the right decision lens
- 4. Analyze
- 5. Debate
- 6. Synthesize
- Tone calibration
- Gotchas
- Topic
What does the discuss skill do?
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 reaso
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill discuss --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.