clear-discuss

Guide focused discussion with decision-tree questions and written records.

1|Updated May 7, 2026
One-click install
npx skills add https://github.com/liuzhengdongfortest/skills --skill clear-discuss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clear-discuss
Source: https://github.com/liuzhengdongfortest/skills/tree/main/clear-discuss
Command: npx skills add https://github.com/liuzhengdongfortest/skills --skill clear-discuss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When a topic is still fuzzy or not yet defined, this Skill helps you discuss it clearly without turning the conversation into a requirements interview or making irreversible changes to a project.

Core Features & Use Cases

  • Hard boundaries: only discussion and small experiments: clarifies understanding while explicitly avoiding real project changes (no code/config/roadmap/task edits).
  • Structured deepening via a decision tree: asks one key question at a time with recommended answer options to resolve major branches.
  • Conversation-to-record workflow: writes each discussion into a separate record file, keeping discussions non-overlapping and easy to revisit.

Quick Start

Tell the Skill what you want to discuss (e.g., product direction, architecture question, technical方案, or a writing/flow decision), and it will first restate your core understanding and then ask the next most important clarification question while staying within the “only discuss and small experiments” boundary.

Frequently Asked Questions about clear-discuss

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I clarify ambiguous product strategy and architecture decisions through discussion?

You can clarify fuzzy requirements by restating your core understanding and prompting the next most important clarification question, ensuring the conversation converges without turning into a formal requirements interview.

How does decision tree deepening work for resolving technical trade-offs?

Decision tree deepening resolves technical trade-offs by exploring one major branch per question, offering recommended answer options to make facts and trade-offs explicit, and concluding with recommended next questions for further exploration.

Can I use small experiments to verify architecture decisions without changing project code?

Yes, you can run small experiments to verify emerging ideas while enforcing strict non-action boundaries that prevent any actual code, configuration, or architecture changes to your project.

How do I keep discussion records for product direction and workflow decisions non-overlapping?

To keep discussion records non-overlapping, this Skill uses a conversation-to-record workflow that writes each specific product direction or workflow discussion into a separate written record file for easy revisiting.

What are the limitations of using a discussion Skill for requirements clarification?

The main limitation is the strict non-action boundary: it cannot modify code, requirements, architecture, or configurations, meaning it strictly facilitates discussion and small experiments rather than executing project changes.