asking-clarifying-questions

Resolve contradictions and clarify technical terms for design projects.

8|1|Updated Feb 25, 2022
One-click install
npx skills add https://github.com/ayubun/dotfiles --skill asking-clarifying-questions-ayubun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asking-clarifying-questions
Source: https://github.com/ayubun/dotfiles/tree/main/configs/opencode/skills/ed3d-plan-and-execute/asking-clarifying-questions
Command: npx skills add https://github.com/ayubun/dotfiles --skill asking-clarifying-questions-ayubun

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps in resolving contradictions, disambiguating terminology, clarifying scope boundaries, and verifying assumptions to prevent building the wrong solution.

Core Features & Use Cases

  • Contradiction Resolution: Identifies and resolves conflicting requirements before proceeding.
  • Technical Terminology Clarification: Ensures precise understanding of technical terms.
  • Scope Boundary Identification: Defines what is included and excluded in the project scope.
  • Assumption Verification: Validates underlying reasons and constraints behind requirements.
  • Version and API Specifics: Checks current state of external services or libraries.
  • Definition of Done: Establishes clear success criteria for the project.

Quick Start

Activate the asking-clarifying-questions skill to initiate the clarification process.

Frequently Asked Questions about asking-clarifying-questions

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

FAQPage Schema
How do I clarify project scope and verify assumptions before starting software design?

Project scope clarification defines what is included and excluded, resolves conflicting requirements, and validates underlying assumptions. This prevents building the wrong solution by establishing clear boundaries before design begins.

What is the best way to resolve contradictions in software requirements?

Resolving contradictions involves identifying conflicting requirements and disambiguating technical terms before proceeding with design. This ensures all stakeholders share a precise understanding of project constraints and terminology.

How do I establish a clear definition of done for a design project?

Establishing a definition of done sets clear success criteria for the project by verifying assumptions, checking external service versions, and defining scope boundaries. This creates measurable completion standards for design workflows.

Can I use assumption verification to check external API versions during design?

Assumption verification checks the current state of external services or libraries, including version and API specifics, to validate underlying constraints behind requirements. This ensures design decisions align with actual external dependencies.

When do I need requirement clarification in a design workflow?

Requirement clarification is needed when requirements contain contradictions, ambiguous technical terms, unclear scope boundaries, or unverified assumptions that could lead to building the wrong solution during design workflows.