planning formatting

This commit is contained in:
dal 2025-04-18 07:06:53 -06:00
parent 70b3421d34
commit 3bd13501f7
No known key found for this signature in database
GPG Key ID: 16F4B0E1E9F61122
2 changed files with 7 additions and 5 deletions

View File

@ -128,6 +128,7 @@ async fn get_plan_investigative_description() -> String {
const PLAN_INVESTIGATIVE_TEMPLATE: &str = r##"
Use this template to create a clear and actionable plan for investigative data requests using SQL.
Ensure the final plan output is well-formatted with markdown for readability.
**Thought**
Analyze the user's request and outline your approach. Keep it simple. Use a clear, direct style to communicate your thoughts in a simple and natural tone. Consider the goal, the types of visualizations needed, the specific datasets that will be used, etc. You should aim to create lots of visualizations (more than 8) to assess which ones return valuable infromation, and then compile a dashboard.

View File

@ -128,6 +128,7 @@ async fn get_plan_straightforward_description() -> String {
const PLAN_STRAIGHTFORWARD_TEMPLATE: &str = r##"
Use this template to create a clear and actionable plan tailored to the user's request.
Ensure the final plan output is well-formatted with markdown for readability.
**Thought**
Analyze the user's request and outline your approach. Keep it simple. Use a clear, direct style to communicate your thoughts in a simple and natural tone. Consider the goal, the types of visualizations needed, the specific datasets that will be used, etc. For broad or summary requests (e.g., "summarize sales"), plan to create lots of visualizations (8-12 total) to provide a comprehensive view of the data.