asking-clarifying-questions

Resolve contradictions, disambiguate terminology, and verify assumptions in early design.

Updated May 7, 2026
One-click install
npx skills add https://github.com/TK-Evans01/tk-harness --skill asking-clarifying-questions-tk-evans01
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asking-clarifying-questions
Source: https://github.com/TK-Evans01/tk-harness/tree/main/plugins/tk-rpie/skills/asking-clarifying-questions
Command: npx skills add https://github.com/TK-Evans01/tk-harness --skill asking-clarifying-questions-tk-evans01

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps resolve contradictions, disambiguate terminology, clarify scope boundaries, and verify assumptions to ensure that the right solution is being built.

Core Features & Use Cases

  • Resolve Contradictions: Identify and resolve conflicting requirements early in the design process.
  • Disambiguate Terminology: Clarify technical terms to ensure a common understanding.
  • Define Scope Boundaries: Establish clear boundaries for what is included and excluded in the project.
  • Verify Assumptions: Confirm underlying reasons and constraints to avoid assumptions leading to incorrect solutions.
  • Use Case: Before starting a design for a new feature, this Skill is used to ensure that the requirements are well-understood and there are no misunderstandings or assumptions that could lead to a failed project.

Quick Start

Use the asking-clarifying-questions skill to ensure that the requirements for the new feature are clear and unambiguous.

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 design?

To clarify project scope and verify assumptions before design, you need to resolve contradictions, disambiguate technical terms, and establish clear boundaries for what is included and excluded in the project.

What is requirement clarification and why is it needed in software engineering?

Requirement clarification is the process of disambiguating terminology and verifying constraints to prevent building the wrong solution. It is needed in early design stages to ensure a common understanding of project goals and avoid failed outcomes.

How do I resolve conflicting requirements early in the design process?

To resolve conflicting requirements early in the design process, identify contradictions and verify underlying reasons and constraints to ensure that the right solution is being built without misunderstandings.

Can I use assumption verification to define scope boundaries for a new feature?

Yes, you can use assumption verification to define scope boundaries for a new feature by confirming underlying constraints and establishing clear boundaries for what is included and excluded in the project.

What is the best way to disambiguate technical terms during project planning?

The best way to disambiguate technical terms during project planning is to clarify terminology to ensure a common understanding, resolving any contradictions that could lead to incorrect solutions.