discuss

Facilitate structured multi-round discussions to decompose tasks into specification documents with checklists and iterations.

10|6|Updated Dec 2, 2025
One-click install
npx skills add https://github.com/WarLikeLaux/yii2-book-catalog --skill discuss-warlikelaux
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: discuss
Source: https://github.com/WarLikeLaux/yii2-book-catalog/tree/main/.claude/skills/discuss
Command: npx skills add https://github.com/WarLikeLaux/yii2-book-catalog --skill discuss-warlikelaux

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the task clarification process, ensuring all necessary details are gathered and understood before development begins, thereby preventing misunderstandings and rework.

Core Features & Use Cases

  • Structured Questioning: Engages in multi-round dialogues to uncover all requirements and constraints.
  • Task Decomposition: Helps break down complex tasks into manageable iterations.
  • Specification Generation: Creates comprehensive documentation including origin, decisions, iterations, and checklists.
  • Use Case: A product manager needs a new feature. Instead of immediately coding, they use this Skill to have a detailed discussion with the AI, resulting in a clear specification document that both parties agree on, before any code is written.

Quick Start

Use the discuss skill to clarify the requirements for adding a new user authentication method.

Frequently Asked Questions about discuss

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

FAQPage Schema
How do I clarify project requirements before coding to prevent rework?

Task clarification for new features involves engaging in multi-round dialogues to uncover constraints and requirements. This structured questioning generates a specification document outlining origin, decisions, iterations, and checklists before development begins.

How do I break down complex tasks into manageable iterations?

Task decomposition breaks down complex tasks into manageable iterations by facilitating structured discussions. This process identifies necessary details and edge cases, resulting in comprehensive documentation that aligns stakeholders with the development process before coding starts.

What is the best way to gather all necessary details for a task specification?

Gathering details for a task specification requires structured questioning through multi-round dialogues. This approach identifies constraints and edge cases, producing a comprehensive specification document that includes origin, decisions, iterations, and checklists for complete alignment.

Does structured requirements gathering work for product managers defining new features?

Structured requirements gathering works effectively for product managers defining new features. By engaging in detailed discussions to clarify tasks, it produces a clear specification document that both stakeholders and developers agree on before any code is written.

What should be included in a task specification document to ensure complete understanding?

A task specification document should include the task origin, decisions made, planned iterations, and checklists. This ensures complete understanding and alignment between stakeholders and the development process by capturing all gathered details and identified edge cases.