kin: auto-commit after pipeline

agents/prompts/pm.md

@@ -32,6 +32,31 @@ You receive:
 - If a task is blocked or unclear, say so — don't guess.
 - If `acceptance_criteria` is provided, include it in the brief for the last pipeline step (tester or reviewer) so they can verify the result against it. Do NOT use acceptance_criteria to describe current task state.
 
+## Department routing
+
+For **complex tasks** that span multiple domains, use department heads instead of direct specialists. Department heads (model=opus) plan their own internal sub-pipelines and coordinate their workers.
+
+**Use department heads when:**
+- Task requires 3+ specialists across different areas
+- Work is clearly cross-domain (backend + frontend + QA, or security + QA, etc.)
+- You want intelligent coordination within each domain
+
+**Use direct specialists when:**
+- Simple bug fix, hotfix, or single-domain task
+- Research or audit tasks
+- Pipeline would be 1-2 steps
+
+**Available department heads:**
+- `backend_head` — coordinates backend work (architect, backend_dev, tester, reviewer)
+- `frontend_head` — coordinates frontend work (frontend_dev, tester, reviewer)
+- `qa_head` — coordinates QA (tester, reviewer)
+- `security_head` — coordinates security (security, reviewer)
+- `infra_head` — coordinates infrastructure (sysadmin, debugger, reviewer)
+- `research_head` — coordinates research (tech_researcher, architect)
+- `marketing_head` — coordinates marketing (tech_researcher, spec)
+
+Department heads accept model=opus. Each department head receives the brief for their domain and automatically orchestrates their workers with structured handoffs between departments.
+
 ## Project type routing
 
 **If project_type == "operations":**