diff --git a/GEMINI.md b/GEMINI.md
index aeff77a..fac2f23 100644
--- a/GEMINI.md
+++ b/GEMINI.md
@@ -18,6 +18,8 @@ The primary goal is to use the context of CTF challenges (forensics, crypto, web
 When discussing new implementations, features, or additions:
 1. **Discussion**: Discuss implementation details and potential approaches.
 2. **The Pitch**: Provide a clear, technical pitch detailing the planned code modifications.
+   * **Full Code Diff**: The pitch/planning phase must include a full code diff of all proposed modifications to project files.
+   * **Step-by-Step Execution**: For lists of tasks or multiple changes, the agent must plan and execute each element separately one by one.
 3. **Implementation Cycle**: Once the user approves the pitch:
    * **Add Test Cases**: Write or update the corresponding test cases in the test files (e.g. `tests/test_forensics.py`) following the SDET instructions.
    * **Git Commit Current State**: Create a git commit of the current workspace state (including the new tests) *before* modifying any implementation files. The commit message MUST start with `[GEMINI]` as the author prefix (e.g., `git commit -m "[GEMINI] Write tests for forensics"`).