From 517aa4b16b738c17481ef3b1a7440fe2b871cd9d Mon Sep 17 00:00:00 2001 From: Renn F Date: Tue, 12 May 2026 06:31:43 +0200 Subject: [PATCH] docs(prompts): D4 compel progress() after each commit in developer.md Developer prompt now mandates progress(task_id, message, percentage) after each commit. Wave 1's progress verb was added but no agent called it. The Progress tab stays empty without it. --- agents/prompts/roles/developer.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/agents/prompts/roles/developer.md b/agents/prompts/roles/developer.md index f898c7a9..61e6b612 100644 --- a/agents/prompts/roles/developer.md +++ b/agents/prompts/roles/developer.md @@ -57,7 +57,7 @@ When you respawn, your task is in some lifecycle status. The next call follows f 3. `note(scope='decision', text='')` -> records your reasoning before claiming. 4. `i_will_work_on(task_id, plan="")` -> claims, creates branch, sets `in_progress`. 5. Edit / Write your changes inside the workspace. Run tests via `Bash` after each meaningful change. -6. `commit(message)` after each meaningful change. The commit auto-records a progress entry. Repeat 5-6 until the criteria are met. +6. `commit(message=...)` after each meaningful change. Then `progress(task_id, message="", percentage=<0..100>)` to surface narrative progress to the Plan/Progress tab. Commits are git refs; progress is the human-readable update for QA / PM / CEO. Repeat 5-6 until the criteria are met. 7. If you get stuck (test won't pass, design unclear, deps missing): `note(scope='struggle', text='')` BEFORE moving to `i_am_blocked`. The struggle note gives your PM signal even if you ultimately self-unstick. 8. When a struggle resolves: `note(scope='learning', text='')` so the next agent benefits. 9. `note(scope='reflect', text="")` before submitting. **This reflect note is the artifact behind every acceptance criterion** — it must walk through them.