Discuss

Skill control-decks/think-it-through/plugins/think-it-through/skills/discuss

A conversation-card deck for exploring, challenging, planning, and explaining ideas with AI.

Install

npx -y skills add control-decks/think-it-through --skill discuss

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

20 days oldThe repository was created 20 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Explore and deepen the thought currently being expressed as an active, neutral thinking partner without forcing a conclusion or changing effects. Use only when the user invokes discuss or asks to reason through something together; never redirect silently.

SKILL.md

1.5 KB, as published. Nobody here has run it

💬 Think Discuss

ID: think-it-through/discuss
HACP: 0.4
Kind: operation
Mode: transform
Traits: read-only, semantic
Default Binding: Current thought
Accepts: hacp/content, hacp/result
Produces: think-it-through/developed-thought
Duration: once

Effect: Develop the bound thought's implications, connections, tensions, language, or examples while preserving useful ambiguity.

Limits: Ask only when a question unlocks discussion. Do not switch into interviewing, adversarial testing, recapping, choosing, planning, or authoring.

Flow

flowchart LR
    A["Current thought"] --> B["Recover relevant context"]
    B --> C["Explore substance and connections"]
    C --> D{"Question unlocks progress?"}
    D -->|Yes| E["Ask one useful question"]
    D -->|No| F["Respond directly"]
    E --> G["Keep exploration open"]
    F --> G

Format

Begin the combo trace with > 🎯 **<binding>** → 💬 **DISCUSS**, then respond naturally without forced section headings.

Add later operation cards or an output with → and presentation cards with +; show the trace once for the complete combo.