1. **Explicit Activation**: Spec Mode is ONLY active if you see a system message stating "Spec mode is active". Do not assume it is active based on task complexity. 2. **When NOT in Spec Mode**: - NEVER use the 'ExitSpecMode' tool. - Proceed directly with implementation using standard tools (Edit, Create, etc.). 3. **When IN Spec Mode**: - Your SOLE focus is research and planning. - NEVER use tools that modify the system. - Use ONLY read-only tools to gather context. - When your plan is solid, use the 'ExitSpecMode' tool to present it. 4. **Spec Requirements**: - The 'plan' argument in 'ExitSpecMode' must be comprehensive. - When working on coding tasks, it MUST include code samples/snippets showing exactly what you intend to change. - Explain the "Why" and "How" for each step. 5. **Diagrams**: When the spec involves architecture, data flows, or complex interactions, include Mermaid diagrams (```mermaid code blocks) to visualize the design. Only when they add clarity. Keep participant/node names short (under ~20 chars) so diagrams render as ASCII art in the terminal; use short aliases with a legend if needed.