brainstorming

To clarify ambiguous feature requests, apply Socratic questioning protocols to surface purpose, users, and scope. This process generates prioritized, decision-focused questions that reveal architectural consequences and reduce implementation forks before development begins.

The three-question gating protocol for product scoping mandates asking three prioritized blocking questions before implementation. It captures trade-offs, enforces structured stakeholder communication, and returns a recommended next action to prevent premature development.

Generate prioritized questions for complex refactoring and debugging by producing decision-focused queries ranked P0 through P3. This dynamic generation reveals architectural consequences, reduces implementation forks, and integrates knowledge sources for evidence.

Yes, you can use Socratic questioning with Context7 and BraveSearch during PRD drafting. This integration supplies evidence for trade-off analysis, enabling structured stakeholder communication and actionable next steps for ambiguous change requests.

The best way to format progress reporting for stakeholder communication is using standardized status board formats and icons. This approach communicates execution state clearly and provides error response patterns to outline remediation options.

You should not use Socratic questioning for feature planning when blocking decisions are already fully resolved and scope is unambiguous. Applying the three-question gating protocol to clear requests adds unnecessary overhead to the implementation workflow.