rabbitblood 4ac6cdb293 chore(template): PM system prompt — treat audit summaries as dispatch triggers, not FYIs ... Observed 2026-04-14 morning: audit crons (Security, UIUX, QA) were flowing messages into PM per the PR #26 contract, but PM stopped sub-delegating to Dev Lead ~10 hours ago. Meanwhile audits started opening PRs directly (bypassing Dev Lead), and Dev Lead / BE / FE / DevOps / QA sat idle for 17+ maintenance cycles despite PRs continuing to land. Root cause: PM's system prompt defined delegation behavior for "tasks from CEO" but didn't explicitly treat audit summaries as tasks. PM was reading "audit of SHA X, filed issue #N, top recommendation: fix Y" as a status report and committing it to memory without triggering the dispatch chain. Adds a dedicated "Audit Routing" section to PM's prompt that: - Treats every audit summary with open issue numbers as a dispatch trigger - Specifies routing by category (security→BE, ui→FE, infra→DevOps, qa→QA) - Requires parallel `delegate_task_async` when issues span categories - Makes clean-cycle acks the only no-op case This turns PM from a receptionist into a dispatcher — which was the original intent of the audit-routing contract in #26. Aligns with the north-star goal (keep the team running 24/7): dead idle windows when audits had live issue numbers is a defect in orchestration, not a quiet period.		2026-04-14 08:13:42 -07:00
..
.env.example	initial commit — Molecule AI platform	2026-04-13 11:55:37 -07:00
system-prompt.md	chore(template): PM system prompt — treat audit summaries as dispatch triggers, not FYIs	2026-04-14 08:13:42 -07:00