From 63fd391dff7de01e5f4957f505a3cd4a3701d924 Mon Sep 17 00:00:00 2001 From: Ed_ Date: Wed, 25 Feb 2026 13:29:16 -0500 Subject: [PATCH] chore(conductor): Integrate strict MMA token firewalling and tiered delegation into core workflow --- conductor/workflow.md | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/conductor/workflow.md b/conductor/workflow.md index bbbcadb..4b5d16f 100644 --- a/conductor/workflow.md +++ b/conductor/workflow.md @@ -8,6 +8,7 @@ 4. **High Code Coverage:** Aim for >80% code coverage for all modules 5. **User Experience First:** Every decision should prioritize user experience 6. **Non-Interactive & CI-Aware:** Prefer non-interactive commands. Use `CI=true` for watch-mode tools (tests, linters) to ensure single execution. +7. **MMA Tiered Delegation is Mandatory:** The Conductor acts as a Tier 1/2 Orchestrator. You MUST delegate all non-trivial coding to Tier 3 Workers and all error analysis to Tier 4 QA Agents. Do NOT perform large file writes directly. ## Task Workflow @@ -15,17 +16,20 @@ All tasks follow a strict lifecycle: ### Standard Task Workflow +0. **Initialize MMA Environment:** Before executing the first task of any track, you MUST activate the `mma-orchestrator` skill (`activate_skill mma-orchestrator`). + 1. **Select Task:** Choose the next available task from `plan.md` in sequential order 2. **Mark In Progress:** Before beginning work, edit `plan.md` and change the task from `[ ]` to `[~]` 3. **Write Failing Tests (Red Phase):** - - Create a new test file for the feature or bug fix. - - Write one or more unit tests that clearly define the expected behavior and acceptance criteria for the task. + - **Delegate Test Creation:** Do NOT write test code directly. Spawn a Tier 3 Worker (`run_subagent.ps1 -Role Worker`) with a prompt to create the necessary test files and unit tests based on the task criteria. + - Take the code generated by the Worker and apply it. - **CRITICAL:** Run the tests and confirm that they fail as expected. This is the "Red" phase of TDD. Do not proceed until you have failing tests. 4. **Implement to Pass Tests (Green Phase):** - - Write the minimum amount of application code necessary to make the failing tests pass. + - **Delegate Implementation:** Do NOT write the implementation code directly. Spawn a Tier 3 Worker (`run_subagent.ps1 -Role Worker`) with a highly specific prompt to write the minimum amount of application code necessary to make the failing tests pass. + - Take the code generated by the Worker and apply it. - Run the test suite again and confirm that all tests now pass. This is the "Green" phase. 5. **Refactor (Optional but Recommended):** @@ -84,7 +88,8 @@ All tasks follow a strict lifecycle: - Before execution, you **must** announce the exact shell command you will use to run the tests. - **Example Announcement:** "I will now run the automated test suite to verify the phase. **Command:** `CI=true npm test`" - Execute the announced command. - - If tests fail, you **must** inform the user and begin debugging. You may attempt to propose a fix a **maximum of two times**. If the tests still fail after your second proposed fix, you **must stop**, report the persistent failure, and ask the user for guidance. + - If tests fail with significant output (e.g., a large traceback), **DO NOT** attempt to read the raw `stderr` directly into your context. Instead, pipe the output to a log file and **spawn a Tier 4 QA Agent (`run_subagent.ps1 -Role QA`)** to summarize the failure. + - You **must** inform the user and begin debugging using the QA Agent's summary. You may attempt to propose a fix a **maximum of two times**. If the tests still fail after your second proposed fix, you **must stop**, report the persistent failure, and ask the user for guidance. 4. **Execute Automated API Hook Verification:** - **CRITICAL:** The Conductor agent will now automatically execute verification tasks using the application's API hooks.