discuss

Plugin discuss from marketplace juanmhidalgo-plugins in juanmhidalgo/claude-plugins. Commands read from the repo's manifest — 2 days ago.

Skills (4)

• adversarial-doc-review

  Use to adversarially review a technical document that already exists as a file — PRD, ADR, technical spec, design doc, RFC, or system/architecture documentation — to catch what would lead to a bad architecture, design, or implementation decision. Also use when asked to "review", "sanity check", "pok

• grill

  Use when the user wants to be interviewed until every decision in a plan, design, or idea is settled: "grill me", "interview me about this", "what do I still need to decide", "ask me everything before we start". Asks in rounds, each question with a recommended answer, and ends with a ledger of decis

• show-me

  Draw the flow, architecture, pipeline or sequence under discussion as a diagram page. Use when the user asks to graph, draw, diagram, sketch or visualize how something works ("graficame", "dibujame", "show me the flow"). Do NOT use for charts of data (numbers over time, distributions).

• wait-what

  Your last message did not land. Re-explain it simply, with the context I was missing.

Slash commands (4)

• /discuss:brainstorm

  Use when you need multiple alternative approaches before committing to a solution. Do NOT use when a clear solution exists (go straight to /feature-dev:spec) or for comparing known options (/discuss:tradeoffs). - brainstorm - alternatives - solution-exploration - ideation - "brainstorm solutions" -

• /discuss:challenge

  Use to stress-test a proposal by hearing the strongest counter-arguments. Do NOT use for neutral analysis (/discuss:feature) or comparing options (/discuss:tradeoffs). - devils-advocate - challenge - stress-test - counter-argument - "argue against" - "challenge this decision" - "why shouldn't I" - "

• /discuss:feature

  Use before writing a spec or plan to critically analyze a feature proposal for gaps, edge cases, and risks. Do NOT use for simple Q&A, implementation, or code review (/code-review:*). - feature-discussion - idea-review - critical-analysis - proposal-review - "discuss this feature" - "review my idea"

• /discuss:tradeoffs

  Use when you have 2-4 specific options and need a structured comparison. Do NOT use for open-ended exploration (/discuss:brainstorm) or single-option analysis (/discuss:feature). - tradeoffs - comparison - pros-cons - decision-matrix - "compare options" - "pros and cons" - "which should I choose" -

Subagents (1)

• doc-adversary

  Adversarial reviewer for technical documentation. Reports only what would cause a bad architecture, design, or implementation decision. Use on PRDs, ADRs, technical specs, design docs, RFCs, and system documentation before the work is implemented or relied upon. Spawned by the adversarial-doc-review

Similar plugins