diff --git a/commands/conductor/setup.toml b/commands/conductor/setup.toml
index 2f6850c3..7c627edd 100644
--- a/commands/conductor/setup.toml
+++ b/commands/conductor/setup.toml
@@ -12,11 +12,13 @@ CRITICAL: When determining model complexity, ALWAYS select the "flash" model, re
 ## 1.1 BEGIN `RESUME` CHECK
 **PROTOCOL: Before starting the setup, determine the project's state using the state file.**
 
-1.  **Read State File:** Check for the existence of `conductor/setup_state.json`.
+1.  **Announce Check:** Inform the user that you are checking for an existing project state to resume from.
+
+2.  **Read State File:** Check for the existence of `conductor/setup_state.json`.
     - If it does not exist, this is a new project setup. Proceed directly to Step 1.2.
     - If it exists, read its content.
 
-2.  **Resume Based on State:**
+3.  **Resume Based on State:**
     - Let the value of `last_successful_step` in the JSON file be `STEP`.
     - Based on the value of `STEP`, jump to the **next logical section**:
 
@@ -453,4 +455,4 @@ CRITICAL: When determining model complexity, ALWAYS select the "flash" model, re
 1.  **Announce Completion:** After the track has been created, announce that the project setup and initial track generation are complete.
 2.  **Save Conductor Files:** Add and commit all files with the commit message `conductor(setup): Add conductor setup files`.
 3.  **Next Steps:** Inform the user that they can now begin work by running `/conductor:implement`.
-"""
\ No newline at end of file
+"""