From 51f9b86f057f90bc1f1d324af0d1314529b0f123 Mon Sep 17 00:00:00 2001
From: Eyal Toledano <eyal@microangel.so>
Date: Wed, 9 Apr 2025 20:03:32 -0400
Subject: [PATCH] chore: Adjust next_step information to mention: 'Before
 creating the PRD for the user, make sure you understand the idea fully and
 ask questions to eliminate ambiguity'

---
 mcp-server/src/tools/initialize-project.js |  2 +-
 tests/fixture/test-tasks.json              | 26 +++++++++++-----------
 2 files changed, 14 insertions(+), 14 deletions(-)

diff --git a/mcp-server/src/tools/initialize-project.js b/mcp-server/src/tools/initialize-project.js
index 5f1c653c..3f47c615 100644
--- a/mcp-server/src/tools/initialize-project.js
+++ b/mcp-server/src/tools/initialize-project.js
@@ -83,7 +83,7 @@ export function registerInitializeProjectTool(server) {
 				return createContentResponse({
 					message: 'Taskmaster successfully initialized for this project.',
 					next_step:
-						'Now that the project is initialized, the next step is to create the tasks by parsing a PRD. This will create the tasks folder and the initial task files. The parse-prd tool will required a prd.txt file as input in scripts/prd.txt. You can create a prd.txt file by asking the user about their idea, and then using the scripts/example_prd.txt file as a template to genrate a prd.txt file in scripts/. You can then use the parse-prd tool to create the tasks. So: step 1 after initialization is to create a prd.txt file in scripts/prd.txt. Step 2 is to use the parse-prd tool to create the tasks. Do not bother looking for tasks after initialization, just use the parse-prd tool to create the tasks after creating a prd.txt from which to parse the tasks.'
+						'Now that the project is initialized, the next step is to create the tasks by parsing a PRD. This will create the tasks folder and the initial task files. The parse-prd tool will required a prd.txt file as input in scripts/prd.txt. You can create a prd.txt file by asking the user about their idea, and then using the scripts/example_prd.txt file as a template to genrate a prd.txt file in scripts/. Before creating the PRD for the user, make sure you understand the idea fully and ask questions to eliminate ambiguity. You can then use the parse-prd tool to create the tasks. So: step 1 after initialization is to create a prd.txt file in scripts/prd.txt. Step 2 is to use the parse-prd tool to create the tasks. Do not bother looking for tasks after initialization, just use the parse-prd tool to create the tasks after creating a prd.txt from which to parse the tasks. '
 				});
 			} catch (error) {
 				// Catch errors from execSync or timeouts
diff --git a/tests/fixture/test-tasks.json b/tests/fixture/test-tasks.json
index a1ef13d7..6b99c177 100644
--- a/tests/fixture/test-tasks.json
+++ b/tests/fixture/test-tasks.json
@@ -1,14 +1,14 @@
 {
-	"tasks": [
-		{
-			"id": 1,
-			"dependencies": [],
-			"subtasks": [
-				{
-					"id": 1,
-					"dependencies": []
-				}
-			]
-		}
-	]
-}
+  "tasks": [
+    {
+      "id": 1,
+      "dependencies": [],
+      "subtasks": [
+        {
+          "id": 1,
+          "dependencies": []
+        }
+      ]
+    }
+  ]
+}
\ No newline at end of file