From dc11ca23f87009673038de8987a72ce12841c46c Mon Sep 17 00:00:00 2001 From: Renn F Date: Tue, 12 May 2026 06:31:56 +0200 Subject: [PATCH] docs(prompts): D4 compel triage() first on respawn in cell_pm.md Cell PM prompt now mandates triage() as the first call on every respawn, before re-decomposing. Smoke run 3 showed PMs re-decomposing blindly and hitting spine-cap; triage shows them existing children and prevents the over-decomposition pattern. --- agents/prompts/roles/cell_pm.md | 1 + 1 file changed, 1 insertion(+) diff --git a/agents/prompts/roles/cell_pm.md b/agents/prompts/roles/cell_pm.md index 266cea2b..cdc07497 100644 --- a/agents/prompts/roles/cell_pm.md +++ b/agents/prompts/roles/cell_pm.md @@ -64,6 +64,7 @@ You merge what your developers submit (leaf PRs into your cell branch via `compl ## Workflow +0. **On every respawn, FIRST call `triage()`** to see what's already in your queue — new pending children, blocked subtasks needing unblock, awaiting_pm_review subtasks needing your merge. If anything is in flight from your previous respawn, deal with it BEFORE re-decomposing or re-delegating. The spine-type concurrency cap will block duplicate delegations anyway. 1. `evidence(task_id="")` -> read the description, acceptance criteria, parent context, **the list of children that already exist**, and Main PM's journal entries to understand intent. 2. **If your task already has subtasks (any non-terminal child), do NOT delegate again.** You are being respawned to coordinate, not to re-decompose. Skip to step 7 (`i_am_idle` until a child needs you) or step 8 (review a child in `awaiting_pm_review`). 3. `note(scope='decision', task_id="", text="")` — the decision note explains your delegation rationale to QA / Main PM / future agents reading the journal.