adjustments

.gemini/skills/mma-orchestrator/SKILL.md

@@ -44,6 +44,7 @@ When creating tracks (`activate_skill mma-tier1-orchestrator`), follow this prot
 6. **MAP DEPENDENCIES**: State execution order and blockers between tracks.
 
 ## 1. The Tier 3 Worker (Execution)
+
 When performing code modifications or implementing specific requirements:
 1. **Pre-Delegation Checkpoint:** For dangerous or non-trivial changes, ALWAYS stage your changes (`git add .`) or commit before delegating to a Tier 3 Worker. If the worker fails or runs `git restore`, you will lose all prior AI iterations for that file if it wasn't staged/committed.
 2. **Code Style Enforcement:** You MUST explicitly remind the worker to "use exactly 1-space indentation for Python code" in your prompt to prevent them from breaking the established codebase style.
@@ -55,6 +56,7 @@ When performing code modifications or implementing specific requirements:
 7. The Tier 3 Worker is stateless and has tool access for file I/O.
 
 ## 2. The Tier 4 QA Agent (Diagnostics)
+
 If you run a test or command that fails with a significant error or large traceback:
 1. **DO NOT** analyze the raw logs in your own context window.
 2. **DO** spawn a stateless Tier 4 agent to diagnose the failure.
@@ -62,9 +64,11 @@ If you run a test or command that fails with a significant error or large traceb
 4. **Mandatory Research-First Protocol:** Avoid direct `read_file` calls for any file over 50 lines. Use `get_file_summary`, `py_get_skeleton`, or `py_get_code_outline` first to identify relevant sections. Use `git diff` to understand changes.
 
 ## 3. Persistent Tech Lead Memory (Tier 2)
+
 Unlike the stateless sub-agents (Tiers 3 & 4), the **Tier 2 Tech Lead** maintains persistent context throughout the implementation of a track. Do NOT apply "Context Amnesia" to your own session during track implementation. You are responsible for the continuity of the technical strategy.
 
 ## 4. AST Skeleton & Outline Views
+
 To minimize context bloat for Tier 2 & 3:
 1. Use `py_get_code_outline` or `get_tree` to map out the structure of a file or project.
 2. Use `py_get_skeleton` and `py_get_imports` to understand the interface, docstrings, and dependencies of modules.
@@ -75,6 +79,7 @@ To minimize context bloat for Tier 2 & 3:
 7. Tier 3 workers MUST NOT read the full content of unrelated files.
 
 ## 5. Cross-Skill Activation
+
 When your current role requires capabilities from another tier, use `activate_skill`:
 - **Track creation/refinement**: `activate_skill mma-tier1-orchestrator` — applies the Surgical Spec Protocol
 - **Track execution**: `activate_skill mma-tier2-tech-lead` — applies persistent context and TDD workflow
@@ -93,6 +98,7 @@ When your current role requires capabilities from another tier, use `activate_sk
 ```
 
 ### Example 2: Spawning a Tier 3 Worker with Surgical Prompt
+
 **User:** Please implement the cost tracking column in the token usage table.
 **Agent (You):**
 ```json
@@ -103,6 +109,7 @@ When your current role requires capabilities from another tier, use `activate_sk
 ```
 
 ### Example 3: Creating a Track with Audit
+
 **User:** Create a track for adding dark mode support.
 **Agent (You):**
 1. First, audit the codebase: `py_get_code_outline gui_2.py` → find `_render_theme_panel` (lines 2993-3030).