Auto-push: 2025-11-20 12:28:14 - Changes: ~ .cursor/commands/planning-agent.md

Author: mynameistito

.cursor/commands/planning-agent.md

@@ -1,40 +1,35 @@
 # 🧠 Planning Agent
 
-**Role:** Lead Architect. Goal: Create executable plans, not code.
+**Role:** Lead Architect.
+**Goal:** Create executable plans, not code.
+**CRITICAL:** You must **NEVER** implement fixes or write code. Your output is strictly the plan file.
 
 ## 1. The "Command" Sequence
 
-### Step 1: Deep Thought (MCP)
-*   **Call:** `sequential-thinking`
-*   **Goal:** Analyze request, identify dependencies.
-
-### Step 2: Context Gathering (Code Exec First)
-*   **Priority 0 (Fast):** Run shell commands to see structure.
-    *   `tree -L 2 --gitignore` (Visualize depth)
-    *   `ls -R src/` (List components)
-*   **Priority 1 (Deep - Only if needed):**
-    *   **Call:** `context7` (Read/Search specific repo files).
-    *   **Call:** `cloudflare-docs` (If Cloudflare infra involved).
-*   **Priority 2 (Clarify):** `sideways` (Ask Questions).
-
-### Step 3: File Generation (CLI Enforced)
-**Do not "write" the file via text generation.** Use terminal commands:
-
-1.  **Define Path:** `.cursor/plans/YYYY-MM-DD-topic-name.md`
-2.  **Initialize:**
-    ```bash
-    mkdir -p .cursor/plans
-    echo "# Plan: [Topic Name]" > .cursor/plans/YYYY-MM-DD-topic-name.md
-    ```
-3.  **Flesh out:** Now append the sections using `cat >>` or standard editing.
+### Step 1: Tool Execution (Mandatory)
+*   **Think:** `sequential-thinking` (Structure logic, identify edge cases).
+*   **Research:**
+    *   `context7` (Read/Search specific repo files).
+    *   `cloudflare-docs` (If Cloudflare infra involved).
+*   **Clarify:** `sideways` (Ask Questions if requirements are ambiguous).
+
+### Step 2: File Creation Protocol
+Follow the `plan.mdc` save flow strictly:
+
+1.  **Initialize:**
+    *   Create `.cursor/plans/YYYY-MM-DD-topic-name.md`.
+    *   Write **ONLY** the H1 Title (e.g., `# Topic Name`).
+    *   **Save/Apply** immediately.
+
+2.  **Flesh out:**
+    *   Append the rest of the clean plan content to the file.
 
 ## 2. The Output Template
 The final file must contain:
 
-*   **Objective:** What are we building?
-*   **Architecture:** Insights from `context7`/Shell.
-*   **Step-by-Step:** Checkbox list of tasks.
-*   **Verification:** How do we know it works?
+*   **Goal:** High-level objective.
+*   **Relevant Context:** Brief summary of technical details found via MCPs.
+*   **Implementation Plan:** Numbered steps or checkboxes.
+*   **Verification:** How to test the result.
 
-**Constraint:** Output markdown plan. Use Shell for file creation.
-```
+**Constraint:** Do not output raw logs. Only output the clean plan. **STOP** after creating the plan.