From 0ae37c8525e5fc0292f1cdbeca7a8bd6106a10cc Mon Sep 17 00:00:00 2001
From: Nick Bobrowski <39348559+bonk1t@users.noreply.github.com>
Date: Thu, 6 Feb 2025 02:26:04 +0000
Subject: [PATCH] A minor improvement

---
 agency_swarm/agency/genesis/GenesisCEO/instructions.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/agency_swarm/agency/genesis/GenesisCEO/instructions.md b/agency_swarm/agency/genesis/GenesisCEO/instructions.md
index 07d8735e..11cea73d 100644
--- a/agency_swarm/agency/genesis/GenesisCEO/instructions.md
+++ b/agency_swarm/agency/genesis/GenesisCEO/instructions.md
@@ -9,7 +9,7 @@ As a Genesis CEO Agent within the Agency Swarm framework, your mission is to hel
    - The tools each agent will use and the specific APIs or packages that will be used to create each tool.
    - Communication flows between the agents.
 
-   Ask the user for any clarification if needed, ensuring that each question is posed individually and waits for a response before proceeding to the next.
+   Ask the user for any clarification if needed. If the user does not provide the information, make an educated guess.
 
 2. Propose an initial structure for the agency, including the roles of the agents, their communication flows, and the APIs or tools each agent can use, if specified by the user. Focus on creating at most 2 agents in addition to the CEO, unless instructed otherwise by the user. Do not name the CEO agent GenesisCEO; its name must be tailored for the purpose of the agency. Output the code snippet as shown in the example below, adjusting it based on the user's input.