Skip to content

fix(kanban): keep graph tools orchestrator-only #30022

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
mosaiq-systems wants to merge 1 commit into from
+189 −70
Closed

fix(kanban): keep graph tools orchestrator-only #30022

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 13 additions & 11 deletions agent/prompt_builder.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -230,19 +230,21 @@ def _strip_yaml_frontmatter(content: str) -> str:
"reviewer can approve+unblock or request changes. Reviewing-then-"
"completing is more honest than auto-completing work that still needs "
"eyes on it.\n"
"6. **If follow-up work appears, create it; don't do it.** Use "
"`kanban_create(title=..., assignee=<right-profile>, parents=[your-task-id])` "
"to spawn a child task for the appropriate specialist profile instead of "
"scope-creeping into the next thing.\n"
"6. **Do not grow the graph unless you are software-engineer.** Only "
"dispatcher workers running with `HERMES_PROFILE=software-engineer` may use "
"`kanban_create` or `kanban_link` to decompose implementation work into "
"child tasks. All other workers must record follow-up work in "
"`kanban_comment`, include it in completion metadata, or "
"`kanban_block(reason=...)` if the follow-up is required before completion.\n"
"\n"
"## Orchestrator mode\n"
"## Software-engineer decomposition mode\n"
"\n"
"If your task is itself a decomposition task (e.g. a planner profile given "
"a high-level goal), use `kanban_create` to fan out into child tasks — one "
"per specialist, each with an explicit `assignee` and `parents=[...]` to "
"express dependencies. Then `kanban_complete` your own task with a summary "
"of the decomposition. Do NOT execute the work yourself; your job is "
"routing, not implementation.\n"
"If you are `software-engineer` and your assigned task is decomposition, use "
"`kanban_create` to fan out into child tasks — one per specialist, each "
"with an explicit `assignee` and `parents=[...]` to express dependencies. "
"Use `kanban_link` only to repair or join that dependency topology. Then "
"`kanban_complete` your own task with a summary of the decomposition. Do NOT "
"execute the child work yourself; your job is routing, not implementation.\n"
"\n"
"## Do NOT\n"
"\n"
Expand Down
Loading