chore(conductor): Fix SKILL.md and documentation typos to correctly use the new Role-Based sub-agent protocol

MMA_Support/Architecture_Recommendation.md

@@ -15,13 +15,13 @@ The Multi-Model Architecture (MMA) utilizes a 4-Tier hierarchy to ensure token e
 - **Role:** Stateless code generator.
 - **Context:** Isolated. Sees only the target file and the specific ticket.
 - **Protocol:** Receives a "Worker" system prompt. Outputs clean code or diffs.
-- **Invocation:** `.\scripts
+- **Invocation:** `.\scripts\run_subagent.ps1 -Role Worker -Prompt "..."`
 
 ### Tier 4: The Utility (QA/Compressor)
 - **Role:** Stateless translator and summarizer.
 - **Context:** Minimal. Sees only the error trace or snippet.
 - **Protocol:** Receives a "QA" system prompt. Outputs compressed findings (max 50 tokens).
-- **Protocol:** Receives a "QA" system prompt. Outputs compressed findings (max 50 tokens).
+- **Invocation:** `.\scripts\run_subagent.ps1 -Role QA -Prompt "..."`
 
 ## 3. Invocation Protocol
 
@@ -33,7 +33,7 @@ Tier 2 detects a delegation trigger:
 ### Step 2: Spawning
 Tier 2 calls the delegation script:
 ```powershell
-Tier 2 calls the delegation script:
+.\scripts\run_subagent.ps1 -Role <Worker|QA> -Prompt "Specific instructions..."
 ```
 
 ### Step 3: Integration

mma-orchestrator/SKILL.md

@@ -11,21 +11,21 @@ To accomplish this, you MUST delegate token-heavy or stateless tasks to "Tier 3
 
 **CRITICAL Prerequisite:**
 To avoid hanging the CLI and ensure proper environment authentication, you MUST NOT call the `gemini` command directly. Instead, you MUST use the wrapper script:
-`.\scripts
+`.\scripts\run_subagent.ps1 -Role <Role> -Prompt "..."`
 
 ## 1. The Tier 3 Worker (Heads-Down Coding)
-## 1. The Tier 3 Worker (Heads-Down Coding)
+When you need to perform a significant code modification (e.g., refactoring a 50-line+ script, writing a massive class, or implementing a predefined spec):
 1. **DO NOT** attempt to write or use `replace`/`write_file` yourself. Your history will bloat.
 2. **DO** construct a single, highly specific prompt.
 3. **DO** spawn a sub-agent using `run_shell_command` pointing to the target file.
-3. **DO** spawn a sub-agent using `run_shell_command` pointing to the target file.
-   *Command:* `.\scripts
+   *Command:* `.\scripts\run_subagent.ps1 -Role Worker -Prompt "Read [FILE_PATH] and modify it to implement [SPECIFIC_INSTRUCTION]. Only write the code, no pleasantries."`
+4. The Tier 3 Worker is stateless and has no tool access. You must take the clean code it returns and apply it to the file system using your own `replace` or `write_file` tools.
 
 ## 2. The Tier 4 QA Agent (Error Translation)
-
+If you run a local test (e.g., `npm test`, `pytest`, `go run`) via `run_shell_command` and it fails with a massive traceback (e.g., 100+ lines of `stderr`):
 1. **DO NOT** analyze the raw `stderr` in your own context window.
 2. **DO** immediately spawn a stateless Tier 4 agent to compress the error.
-1. **DO NOT** analyze the raw `stderr` in your own context window.
+3. *Command:* `.\scripts\run_subagent.ps1 -Role QA -Prompt "Summarize this stack trace into a 20-word fix: [PASTE_SNIPPET_OF_STDERR_HERE]"`
 4. Use the 20-word fix returned by the Tier 4 agent to inform your next architectural decision or pass it to the Tier 3 worker.
 
 ## 3. Context Amnesia (Phase Checkpoints)
@@ -40,7 +40,7 @@ When you complete a major Phase or Track within the `conductor` workflow:
 **Agent (You):** 
 ```json
 {
-**Agent (You):** 
+  "command": ".\\scripts\\run_subagent.ps1 -Role QA -Prompt \"Summarize this stack trace into a 20-word fix: [snip first 30 lines...]\"",
   "description": "Spawning Tier 4 QA to compress error trace statelessly."
 }
 ```
@@ -50,15 +50,15 @@ When you complete a major Phase or Track within the `conductor` workflow:
 **Agent (You):**
 ```json
 {
-**User:** Please implement the `ASTParser` class in `file_cache.py` as defined in Track 1.
+  "command": ".\\scripts\\run_subagent.ps1 -Role Worker -Prompt \"Read file_cache.py and implement the ASTParser class using tree-sitter. Ensure you preserve docstrings but strip function bodies. Output the updated code.\"",
   "description": "Delegating implementation to a Tier 3 Worker."
 }
 ```
 </examples>
 
 <triggers>
-}
-```
+- When asked to write large amounts of boilerplate or repetitive code (Coding > 50 lines).
+- When encountering a large error trace from a shell execution (Errors > 100 lines).
 - When explicitly instructed to act as a "Tech Lead" or "Orchestrator".
 - When managing complex, multi-file Track implementations.
 </triggers>