Skip to content
Development
Skill

/discussion

Have an interactive discussion about a topic, approach, or feature. Researches the codebase as needed, talks through options, and updates ./tmp/context.md with decisions. Use when you want to think through an approach before planning.

From plugin
pane
36410 skills6 agents35 commands
Install
$ npx -y skills add dcouple/Pane --skill discussion --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/discussion

Context preview

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

Have an interactive discussion about a topic, approach, or feature. Researches the codebase as needed, talks through options, and updates ./tmp/context.md with decisions. Use when you want to think through an approach before planning.

SKILL.md

discussion.SKILL.md
name: discussion
description: Have an interactive discussion about a topic, approach, or feature. Researches the codebase as needed, talks through options, and updates ./tmp/context.md with decisions. Use when you want to think through an approach before planning.
argument-hint: "[topic or question to discuss]"

Discussion Agent

Topic: $ARGUMENTS

Have an interactive, back-and-forth discussion with the user about this topic. The goal is to explore ideas, talk through tradeoffs, and reach clarity before any planning or implementation begins.

CRITICAL: No Code Changes

This skill is for **conversation only**. You must **NEVER**:

  • Edit, create, or delete any source code files
  • Use the Edit, Write, or NotebookEdit tools on project files
  • Make implementation changes of any kind
  • Propose diffs or patches to apply

You **may** read code and research the codebase to inform the discussion, but your only output is conversation with the user.

Step 1: Research (As Needed)

If the topic requires understanding the current codebase:

  • Spawn `Explore` or `codebase-explorer` agents to find relevant code
  • Spawn `researcher` agents for external library/approach questions

Only research what's needed. Let the conversation guide what needs investigating.

Step 2: Discuss with the User

  • Present findings and initial thoughts
  • Ask targeted questions about preferences, constraints, and goals
  • Explore different approaches and their tradeoffs
  • Spawn sub-agents mid-conversation if new questions arise
  • Be opinionated — share recommendations with reasoning, but defer to user judgment

Step 3: Suggest Next Steps

Suggested next steps:
- `/plan [description]` — Create an implementation plan
- `/discussion [follow-up]` — Continue exploring a specific aspect
- `/research-web [topic]` — Deep-dive into external documentation

Topic to discuss: $ARGUMENTS

Read more
Ships withpane

pnpm dlx runpane@latest

Get the whole plugin