discussion-create

Automate structured discussion document creation with Clarify and validate outputs.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/oogDZ/2 --skill discussion-create
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: discussion-create
Source: https://github.com/oogDZ/2/tree/main/.claude/skills/discussion-create
Command: npx skills add https://github.com/oogDZ/2 --skill discussion-create

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of a formal discussion document (SDD) with Clarify, auto-generating sections and validating content to ensure alignment between problem, requirements, and success criteria.

Core Features & Use Cases

  • SSOT-driven drafting and validation of discussion artifacts
  • Automatic generation of sections for problem, requirements, design, and success criteria
  • Guidance and references to established discussion standards to accelerate onboarding and stakeholder alignment

Quick Start

Invoke /discussion-create with a topic to start a new discussion and generate the required sections.

Frequently Asked Questions about discussion-create

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

FAQPage Schema
How do I automatically generate a structured discussion document for stakeholder alignment?

To generate a structured discussion document automatically, invoke the creation command with a topic to auto-draft sections for problems, requirements, design, and success criteria, ensuring stakeholder alignment.

What is an SSOT-driven workflow for validating requirements and problem statements?

An SSOT-driven workflow validates requirements by enforcing a single source of truth, automatically checking drafted discussion artifacts to ensure alignment between the problem statement, requirements, and success criteria.

Can I use Clarify to draft and validate new initiative specifications?

Yes, you can use Clarify to draft and validate new initiative specifications by automating the creation of formal discussion documents that structure conversations around problems and success criteria.

What is the best way to structure requirements and design discussions for a new project?

The best way to structure requirements and design discussions is using an automated SSOT-driven approach that generates standardized sections for problems, requirements, design, and success criteria to produce reusable documentation artifacts.

How do I ensure alignment between success criteria and requirements during clarification?

You ensure alignment between success criteria and requirements during clarification by using automated validation on the generated discussion document to verify that all drafted sections adhere to SSOT-driven standards.

Does generating discussion artifacts require prior knowledge of specification standards?

No, generating discussion artifacts does not require prior knowledge of specification standards because the process provides built-in guidance and references to established discussion standards to accelerate onboarding.