ed/manual_slop
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fixes to mma skills

Browse Source
This commit is contained in:
Edward R. Gonzalez
2026-02-25 21:12:10 -05:00
parent 6152b63578
commit aea42e82ab
2 changed files with 7 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
.gemini/skills/mma-tier2-tech-lead/SKILL.md
View File

@@ -15,4 +15,5 @@ You are the Tier 2 Tech Lead. Your role is to ensure architectural integrity, al
## Limitations ## Limitations
- Do not write boilerplate or exhaustive feature code yourself. - Do not write boilerplate or exhaustive feature code yourself.
- Delegate implementation tasks to Tier 3 Workers. - Delegate implementation tasks to Tier 3 Workers using `uv python scripts/mma_exec.py --role tier3-worker "[PROMPT]"`.
- For error analysis of large logs, use `uv python scripts/mma_exec.py --role tier4-qa "[PROMPT]"`.

10
mma-orchestrator/SKILL.md
View File

@@ -11,21 +11,21 @@ To accomplish this, you MUST delegate token-heavy or stateless tasks to "Tier 3
**CRITICAL Prerequisite:** **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: 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\run_subagent.ps1 -Role <Role> -Prompt "..."` `uv python scripts/mma_exec.py --role <Role> "..."`
## 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): 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. 1. **DO NOT** attempt to write or use `replace`/`write_file` yourself. Your history will bloat.
2. **DO** construct a single, highly specific prompt. 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\run_subagent.ps1 -Role Worker -Prompt "Read [FILE_PATH] and modify it to implement [SPECIFIC_INSTRUCTION]. Only write the code, no pleasantries."` *Command:* `uv python scripts/mma_exec.py --role tier3-worker "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. 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) ## 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`): 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. 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. 2. **DO** immediately spawn a stateless Tier 4 agent to compress the error.
3. *Command:* `.\scripts\run_subagent.ps1 -Role QA -Prompt "Summarize this stack trace into a 20-word fix: [PASTE_SNIPPET_OF_STDERR_HERE]"` 3. *Command:* `uv python scripts/mma_exec.py --role tier4-qa "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. 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) ## 3. Context Amnesia (Phase Checkpoints)
@@ -40,7 +40,7 @@ When you complete a major Phase or Track within the `conductor` workflow:
**Agent (You):** **Agent (You):**
```json ```json
{ {
"command": ".\\scripts\\run_subagent.ps1 -Role QA -Prompt \"Summarize this stack trace into a 20-word fix: [snip first 30 lines...]\"", "command": "python scripts/mma_exec.py --role tier4-qa \"Summarize this stack trace into a 20-word fix: [snip first 30 lines...]\"",
"description": "Spawning Tier 4 QA to compress error trace statelessly." "description": "Spawning Tier 4 QA to compress error trace statelessly."
} }
``` ```
@@ -50,7 +50,7 @@ When you complete a major Phase or Track within the `conductor` workflow:
**Agent (You):** **Agent (You):**
```json ```json
{ {
"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.\"", "command": "python scripts/mma_exec.py --role tier3-worker \"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." "description": "Delegating implementation to a Tier 3 Worker."
} }
``` ```