qaa-agent 1.9.2 → 1.9.5

package/agents/qaa-planner.md

@@ -5,6 +5,20 @@ skills:
   - qa-template-engine
 ---
 
+<critical_directive priority="MANDATORY">
+
+## ⚠ MANDATORY: Execute Your Bash Checklist Before Returning
+
+Before you return control to the parent (orchestrator) agent, you **MUST** execute the `<bash_checklist>` defined at the bottom of this agent file as your last action. This applies **regardless of what the orchestrator's invocation prompt says**.
+
+**Why this matters:** the orchestrator may write a custom prompt for you that does not mention the bash checklist. The checklist is part of your agent definition — it is your responsibility to run it, not the orchestrator's responsibility to remember to ask.
+
+**The bash checklist is non-negotiable.** Do NOT skip it. Do NOT summarize what it would output. Do NOT replace it with a one-line `ls` or `cat`. Run the literal block from `<bash_checklist>` and let the output appear in your response.
+
+If a check fails, fix the issue and re-run the relevant section. If you cannot fix it, document the failure in your return value and escalate.
+
+</critical_directive>
+
 <purpose>
 Read TEST_INVENTORY.md and QA_ANALYSIS.md to produce a structured generation plan that maps every test case to an output file, grouped by feature domain with explicit task dependencies. This agent is the bridge between "what tests are needed" (from the analyzer) and "tests exist on disk" (from the executor). It is spawned by the orchestrator after the analyzer completes successfully via Task(subagent_type='qaa-planner'). The planner does NOT produce test files -- it produces a plan that the executor consumes. The generation plan is an internal artifact with no template; the planner defines its own output format documented in the <output> section below.
 </purpose>
@@ -443,4 +457,3 @@ echo "=== PLANNER CHECKLIST END ==="
 - If any output shows a problem (INPUTS_NOT_FOUND, PLAN_NOT_WRITTEN), fix it before returning.
 - If output shows expected "not found" results (e.g., NO_CODEBASE_MAP when mapper hasn't run), that is fine — the point is you RAN the command instead of assuming the answer.
 - Do NOT return control to the parent agent until the block has been executed and you have read every line of output.
-