Fix: clarification bugs - max rounds, locale passing, and over-clarification (#647)

Fixes: Max rounds bug, locale passing bug, over-clarification issue

* reslove Copilot spelling comments

---------

Co-authored-by: Willem Jiang <willem.jiang@gmail.com>
This commit is contained in:
jimmyuconn1982
2025-10-24 16:43:39 +08:00
committed by GitHub
parent 5eada04f50
commit 2001a7c223
6 changed files with 119 additions and 40 deletions

View File

@@ -64,18 +64,32 @@ Your primary responsibilities are:
Goal: Get 2+ dimensions before handing off to planner.
## Three Key Dimensions
## Smart Clarification Rules
A specific research question needs at least 2 of these 3 dimensions:
**DO NOT clarify if the topic already contains:**
- Complete research plan/title (e.g., "Research Plan for Improving Efficiency of AI e-commerce Video Synthesis Technology Based on Transformer Model")
- Specific technology + application + goal (e.g., "Using deep learning to optimize recommendation algorithms")
- Clear research scope (e.g., "Blockchain applications in financial services research")
**ONLY clarify if the topic is genuinely vague:**
- Too broad: "AI", "cloud computing", "market analysis"
- Missing key elements: "research technology" (what technology?), "analyze market" (which market?)
- Ambiguous: "development trends" (trends of what?)
## Three Key Dimensions (Only for vague topics)
A vague research question needs at least 2 of these 3 dimensions:
1. Specific Tech/App: "Kubernetes", "GPT model" vs "cloud computing", "AI"
2. Clear Focus: "architecture design", "performance optimization" vs "technology aspect"
2. Clear Focus: "architecture design", "performance optimization" vs "technology aspect"
3. Scope: "2024 China e-commerce", "financial sector"
## When to Continue vs. Handoff
- 0-1 dimensions: Ask for missing ones with 3-5 concrete examples
- 2+ dimensions: Call handoff_to_planner() or handoff_after_clarification()
**If the topic is already specific enough, hand off directly to planner.**
- Max rounds reached: Must call handoff_after_clarification() regardless
## Response Guidelines