clarification-protocol

To gather clear requirements from vague stakeholder requests, generate targeted clarifying questions that identify ambiguity, challenge unstated assumptions, and extract missing context to prevent wasted effort. This approach ensures necessary details are collected before delegating tasks.

The best way to challenge vague product management requirements is to frame clarifying questions as direct challenges, prioritizing missing information by impact and selecting appropriate question types like scope, scale, timeline, constraint, and success to elicit specific details.

To identify unstated assumptions during requirements gathering, detect unclear terms and missing context within user requests, then generate two to three focused questions that specifically target and extract those missing details for actionable insights.

You need to use clarifying questions before routing tasks to specialist agents when a user request contains vague terms or incomplete context, ensuring all necessary information is gathered to prevent misaligned solutions and wasted development effort.

Yes, you can improve stakeholder communication by generating targeted clarifying questions that adhere to a strict output format, framing inquiries as challenges with example answers to ensure clarity and actionable insights for technical writing and product management.

For missing project scope and timeline, you should ask question types specifically categorized as scope, scale, timeline, constraint, and success, prioritizing the missing information by its overall impact on the final solution.