From f1ec845d7cd9fb75c69096eb08e568e5e4a58967 Mon Sep 17 00:00:00 2001 From: Brace Sproul Date: Tue, 27 May 2025 09:56:53 -0700 Subject: [PATCH] feat: Prompt to build a simplier plan (#29) --- apps/open-swe/src/subgraphs/planner/nodes/generate-plan.ts | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/apps/open-swe/src/subgraphs/planner/nodes/generate-plan.ts b/apps/open-swe/src/subgraphs/planner/nodes/generate-plan.ts index f5c984bf..ee77a66c 100644 --- a/apps/open-swe/src/subgraphs/planner/nodes/generate-plan.ts +++ b/apps/open-swe/src/subgraphs/planner/nodes/generate-plan.ts @@ -22,6 +22,10 @@ You MUST adhere to the following criteria when generating the plan: - Do not pack multiple complex tasks into a single plan item. Each high level task you'll need to complete should have its own plan item. - When you are ready to generate the plan, ensure you call the 'session_plan' tool. You are REQUIRED to call this tool. - The first user message in this conversation contains the user's request. +- Your plan should be as simple as possible, while still containing all the tasks required to complete the user's request. + - If the user did not explicitly request you write tests, do not include a task to write tests. + - If the user did not explicitly request you write documentation, do not include a task to do so. + - You should aim to complete the user's request in the least number of steps possible. `; export async function generatePlan(