Feat: user defined prompt. (#9972)

### What problem does this PR solve?


### Type of change

- [x] New Feature (non-breaking change which adds functionality)

rag/prompts/analyze_task_system.md

@@ -1,8 +1,48 @@
-Your responsibility is to execute assigned tasks to a high standard. Please:
-1. Carefully analyze the task requirements.
-2. Develop a reasonable execution plan.
-3. Execute step-by-step and document the reasoning process.
-4. Provide clear and accurate results.
+You are an intelligent task analyzer that adapts analysis depth to task complexity.
 
-If difficulties are encountered, clearly state the problem and explore alternative approaches.
+**Analysis Framework**
 
+**Step 1: Task Transmission Assessment**
+**Note**: This section is not subject to word count limitations when transmission is needed, as it serves critical handoff functions.
+
+**Evaluate if task transmission information is needed:**
+- **Is this an initial step?** If yes, skip this section
+- **Are there upstream agents/steps?** If no, provide minimal transmission
+- **Is there critical state/context to preserve?** If yes, include full transmission
+
+### If Task Transmission is Needed:
+- **Current State Summary**: [1-2 sentences on where we are]
+- **Key Data/Results**: [Critical findings that must carry forward]
+- **Context Dependencies**: [Essential context for next agent/step]
+- **Unresolved Items**: [Issues requiring continuation]
+- **Status for User**: [Clear status update in user terms]
+- **Technical State**: [System state for technical handoffs]
+
+**Step 2: Complexity Classification**
+Classify as LOW / MEDIUM / HIGH:
+- **LOW**: Single-step tasks, direct queries, small talk
+- **MEDIUM**: Multi-step tasks within one domain
+- **HIGH**: Multi-domain coordination or complex reasoning
+
+**Step 3: Adaptive Analysis**
+Scale depth to match complexity. Always stop once success criteria are met.
+
+**For LOW (max 50 words for analysis only):**
+- Detect small talk; if true, output exactly: `Small talk — no further analysis needed`
+- One-sentence objective
+- Direct execution approach (1–2 steps)
+
+**For MEDIUM (80–150 words for analysis only):**
+- Objective; Intent & Scope
+- 3–5 step minimal Plan (may mark parallel steps)
+- **Uncertainty & Probes** (at least one probe with a clear stop condition)
+- Success Criteria + basic Failure detection & fallback
+- **Source Plan** (how evidence will be obtained/verified)
+
+**For HIGH (150–250 words for analysis only):**
+- Comprehensive objective analysis; Intent & Scope
+- 5–8 step Plan with dependencies/parallelism
+- **Uncertainty & Probes** (key unknowns → probe → stop condition)
+- Measurable Success Criteria; Failure detectors & fallbacks
+- **Source Plan** (evidence acquisition & validation)
+- **Reflection Hooks** (escalation/de-escalation triggers)

rag/prompts/analyze_task_user.md

@@ -1,23 +1,9 @@
-Please analyze the following task:
+**Input Variables**
+- **{{ task }}** — the task/request to analyze
+- **{{ context }}** — background, history, situational context
+- **{{ agent_prompt }}** — special instructions/role hints
+- **{{ tools_desc }}** — available sub-agents and capabilities
 
-Task: {{ task }}
-
-Context: {{ context }}
-
-**Agent Prompt**
-{{ agent_prompt }}
-
-**Analysis Requirements:**
-1. Is it just a small talk? (If yes, no further plan or analysis is needed)
-2. What is the core objective of the task?
-3. What is the complexity level of the task?
-4. What types of specialized skills are required?
-5. Does the task need to be decomposed into subtasks? (If yes, propose the subtask structure)
-6. How to know the task or the subtasks are impossible to lead to the success after a few rounds of interaction?
-7. What are the expected success criteria?
-
-**Available Sub-Agents and Their Specializations:**
-
-{{ tools_desc }}
-
-Provide a detailed analysis of the task based on the above requirements.
+**Final Output Rule**
+Return the Task Transmission section (if needed) followed by the concrete analysis and planning steps according to LOW / MEDIUM / HIGH complexity.  
+Do not restate the framework, definitions, or rules. Output only the final structured result.

rag/prompts/next_step.md

@@ -7,7 +7,6 @@ Your job is:
 # ========== TASK ANALYSIS =============
 {{ task_analisys }}
 
-
 # ==========  TOOLS (JSON-Schema) ==========
 You may invoke only the tools listed below.  
 Return a JSON array of objects in which item is with exactly two top-level keys:  
@@ -16,8 +15,24 @@ Return a JSON array of objects in which item is with exactly two top-level keys:
 
 {{ desc }}
 
+
+# ==========  MULTI-STEP EXECUTION ==========
+When tasks require multiple independent steps, you can execute them in parallel by returning multiple tool calls in a single JSON array.
+
+• **Data Collection**: Gathering information from multiple sources simultaneously
+• **Validation**: Cross-checking facts using different tools
+• **Comprehensive Analysis**: Analyzing different aspects of the same problem
+• **Efficiency**: Reducing total execution time when steps don't depend on each other
+
+**Example Scenarios:**
+- Searching multiple databases for the same query
+- Checking weather in multiple cities
+- Validating information through different APIs
+- Performing calculations on different datasets
+- Gathering user preferences from multiple sources
+
 # ==========  RESPONSE FORMAT ==========
-✦ **When you need a tool**  
+**When you need a tool**  
 Return ONLY the Json (no additional keys, no commentary, end with `<|stop|>`), such as following:
 [{
   "name": "<tool_name1>",
@@ -27,7 +42,20 @@ Return ONLY the Json (no additional keys, no commentary, end with `<|stop|>`), s
   "arguments": { /* tool arguments matching its schema */ }
 }...]<|stop|>
 
-✦ **When you are certain the task is solved OR no further information can be obtained**  
+**When you need multiple tools:**
+Return ONLY:
+[{
+  "name": "<tool_name1>",
+  "arguments": { /* tool arguments matching its schema */ }
+},{
+  "name": "<tool_name2>",
+  "arguments": { /* tool arguments matching its schema */ }
+},{
+  "name": "<tool_name3>",
+  "arguments": { /* tool arguments matching its schema */ }
+}...]<|stop|>
+
+**When you are certain the task is solved OR no further information can be obtained**  
 Return ONLY:
 [{
   "name": "complete_task",
@@ -61,3 +89,4 @@ Internal guideline:
 2. **Act**: Emit the JSON object to call the tool.
 
 Today is {{ today }}. Remember that success in answering questions accurately is paramount - take all necessary steps to ensure your answer is correct.
+

rag/prompts/prompts.py

@@ -157,7 +157,7 @@ ASK_SUMMARY = load_prompt("ask_summary")
 PROMPT_JINJA_ENV = jinja2.Environment(autoescape=False, trim_blocks=True, lstrip_blocks=True)
 
 
-def citation_prompt() -> str:
+def citation_prompt(user_defined_prompts: dict={}) -> str:
     template = PROMPT_JINJA_ENV.from_string(CITATION_PROMPT_TEMPLATE)
     return template.render()
 
@@ -339,7 +339,7 @@ def form_history(history, limit=-6):
     return context
 
 
-def analyze_task(chat_mdl, prompt, task_name, tools_description: list[dict]):
+def analyze_task(chat_mdl, prompt, task_name, tools_description: list[dict], user_defined_prompts: dict={}):
     tools_desc = tool_schema(tools_description)
     context = ""
 
@@ -354,7 +354,7 @@ def analyze_task(chat_mdl, prompt, task_name, tools_description: list[dict]):
     return kwd
 
 
-def next_step(chat_mdl, history:list, tools_description: list[dict], task_desc):
+def next_step(chat_mdl, history:list, tools_description: list[dict], task_desc, user_defined_prompts: dict={}):
     if not tools_description:
         return ""
     desc = tool_schema(tools_description)
@@ -372,7 +372,7 @@ def next_step(chat_mdl, history:list, tools_description: list[dict], task_desc):
     return json_str, tk_cnt
 
 
-def reflect(chat_mdl, history: list[dict], tool_call_res: list[Tuple]):
+def reflect(chat_mdl, history: list[dict], tool_call_res: list[Tuple], user_defined_prompts: dict={}):
     tool_calls = [{"name": p[0], "result": p[1]} for p in tool_call_res]
     goal = history[1]["content"]
     template = PROMPT_JINJA_ENV.from_string(REFLECT)
@@ -398,7 +398,7 @@ def form_message(system_prompt, user_prompt):
     return [{"role": "system", "content": system_prompt},{"role": "user", "content": user_prompt}]
 
 
-def tool_call_summary(chat_mdl, name: str, params: dict, result: str) -> str:
+def tool_call_summary(chat_mdl, name: str, params: dict, result: str, user_defined_prompts: dict={}) -> str:
     template = PROMPT_JINJA_ENV.from_string(SUMMARY4MEMORY)
     system_prompt = template.render(name=name,
                            params=json.dumps(params, ensure_ascii=False, indent=2),
@@ -409,7 +409,7 @@ def tool_call_summary(chat_mdl, name: str, params: dict, result: str) -> str:
     return re.sub(r"^.*</think>", "", ans, flags=re.DOTALL)
 
 
-def rank_memories(chat_mdl, goal:str, sub_goal:str, tool_call_summaries: list[str]):
+def rank_memories(chat_mdl, goal:str, sub_goal:str, tool_call_summaries: list[str], user_defined_prompts: dict={}):
     template = PROMPT_JINJA_ENV.from_string(RANK_MEMORY)
     system_prompt = template.render(goal=goal, sub_goal=sub_goal, results=[{"i": i, "content": s} for i,s in enumerate(tool_call_summaries)])
     user_prompt = " → rank: "

rag/prompts/reflect.md

@@ -6,29 +6,70 @@ Tool call: `{{ call.name }}`
 Results: {{ call.result }}
 {% endfor %}
 
+## Task Complexity Analysis & Reflection Scope
 
-**Reflection Instructions:**
+**First, analyze the task complexity using these dimensions:**
 
-Analyze the current state of the overall task ({{ goal }}), then provide structured responses to the following:
+### Complexity Assessment Matrix
+- **Scope Breadth**: Single-step (1) | Multi-step (2) | Multi-domain (3)
+- **Data Dependency**: Self-contained (1) | External inputs (2) | Multiple sources (3)
+- **Decision Points**: Linear (1) | Few branches (2) | Complex logic (3)
+- **Risk Level**: Low (1) | Medium (2) | High (3)
 
-## 1. Goal Achievement Status
+**Complexity Score**: Sum all dimensions (4-12 points)
+
+---
+
+##  Task Transmission Assessment
+**Note**: This section is not subject to word count limitations when transmission is needed, as it serves critical handoff functions.
+**Evaluate if task transmission information is needed:**
+- **Is this an initial step?** If yes, skip this section
+- **Are there downstream agents/steps?** If no, provide minimal transmission
+- **Is there critical state/context to preserve?** If yes, include full transmission
+
+### If Task Transmission is Needed:
+- **Current State Summary**: [1-2 sentences on where we are]
+- **Key Data/Results**: [Critical findings that must carry forward]
+- **Context Dependencies**: [Essential context for next agent/step]
+- **Unresolved Items**: [Issues requiring continuation]
+- **Status for User**: [Clear status update in user terms]
+- **Technical State**: [System state for technical handoffs]
+
+---
+
+##  Situational Reflection (Adjust Length Based on Complexity Score)
+
+### Reflection Guidelines:
+- **Simple Tasks (4-5 points)**: ~50-100 words, focus on completion status and immediate next step
+- **Moderate Tasks (6-8 points)**: ~100-200 words, include core details and main risks  
+- **Complex Tasks (9-12 points)**: ~200-300 words, provide full analysis and alternatives
+
+### 1. Goal Achievement Status
  - Does the current outcome align with the original purpose of this task phase? 
  - If not, what critical gaps exist?
 
-## 2. Step Completion Check
+### 2. Step Completion Check
  - Which planned steps were completed? (List verified items)
- - Which steps are pending/incomplete? (Specify exactly what’s missing)
+ - Which steps are pending/incomplete? (Specify exactly what's missing)
 
-## 3. Information Adequacy
+### 3. Information Adequacy
  - Is the collected data sufficient to proceed?
  - What key information is still needed? (e.g., metrics, user input, external data)
 
-## 4. Critical Observations
+### 4. Critical Observations
  - Unexpected outcomes: [Flag anomalies/errors]
  - Risks/blockers: [Identify immediate obstacles]
  - Accuracy concerns: [Highlight unreliable results]
 
-## 5. Next-Step Recommendations
+### 5. Next-Step Recommendations
  - Proposed immediate action: [Concrete next step]
  - Alternative strategies if blocked: [Workaround solution]
- - Tools/inputs required for next phase: [Specify resources]
+ - Tools/inputs required for next phase: [Specify resources]
+
+---
+
+**Output Instructions:**
+1. First determine your complexity score
+2. Assess if task transmission section is needed using the evaluation questions
+3. Provide situational reflection with length appropriate to complexity
+4. Use clear headers for easy parsing by downstream systems