tasker-worker profile lacks instruction to file Forgejo issues for code-writing tasks #16

New issue

Closed

opened 2026-07-30 00:25:05 +00:00 by Mark · 0 comments

Mark commented

2026-07-30 00:25:05 +00:00

Owner

Gap: tasker-worker profile lacks instruction to file Forgejo issues for code-writing tasks

What happened (2026-07-29)

A photo-segmentation Vikunja milestone (project 3 = org_mode, tasks 59-63) was routed to the kanban tasker board. Five cards were created (t_fb25b6b9, t_7e4bf156, t_fe3f8f50, t_1533d9e9, t_ff5ac64d). The tasker-worker picked them up, wrote 19 files to /home/b/Projects/easystitch/src/segmentation/ and /tests/segmentation/, marked all cards done. Zero Forgejo issues were filed for any of the work. No commits, no PRs, no review trail.

Root cause

The tasker-worker profile (~/.hermes/profiles/tasker-worker/) is an agentic lane per the kanban-worker skill. It reads the card body and uses judgment to decide what to do. The profile has no instruction or loaded skill that says:

Code-writing work must file a corresponding Forgejo issue with the work tracked
Per the skill itself: "Coding task that needs human review (review-required)" — should block(review-required: ...) not complete

The skill's discipline is correct but lives in the kanban-worker skill, which the tasker-worker may or may not have loaded depending on what kanban_create passed via --skills.

What needs to change

Update ~/.hermes/profiles/tasker-worker/SOUL.md (or equivalent) to include explicit instructions:
- Any card where changed_files would be non-empty → block(review-required: ...), not complete
- Post structured metadata (changed_files, tests_run, tests_passed, diff_path) as a comment before blocking
- When the work produces a fix or feature implementation, file a Forgejo issue in the relevant repo with the diff/work as the body, then block for review
Update the profile's per-card skill loading so kanban-worker is always attached when the tasker-worker spawns
Update the ingress (Vikunja sync) to add --skills kanban-worker when creating cards on the tasker board, so the discipline is in context

Evidence

Vikunja milestone 59-63 (project 3 = org_mode)
Kanban tasker-board cards t_fb25b6b9, t_7e4bf156, t_fe3f8f50, t_1533d9e9, t_ff5ac64d — all done
No Forgejo issues created in window 2026-07-29T20:41-21:25 UTC on Mark/easystitch or Mark/easystitch-service
19 files written to easystitch repo (uncommitted)

Companion issues

See Mark/easystitch#109 for the dirty-tree state this gap produced
See Mark/org_mode (next issue) for the chat-agent-side framing problem that reinforced this gap

## Gap: tasker-worker profile lacks instruction to file Forgejo issues for code-writing tasks ### What happened (2026-07-29) A photo-segmentation Vikunja milestone (project 3 = org_mode, tasks 59-63) was routed to the kanban tasker board. Five cards were created (t_fb25b6b9, t_7e4bf156, t_fe3f8f50, t_1533d9e9, t_ff5ac64d). The tasker-worker picked them up, wrote 19 files to `/home/b/Projects/easystitch/src/segmentation/` and `/tests/segmentation/`, marked all cards `done`. **Zero Forgejo issues were filed** for any of the work. No commits, no PRs, no review trail. ### Root cause The tasker-worker profile (`~/.hermes/profiles/tasker-worker/`) is an **agentic lane** per the `kanban-worker` skill. It reads the card body and uses judgment to decide what to do. The profile has no instruction or loaded skill that says: - Code-writing work must file a corresponding Forgejo issue with the work tracked - Per the skill itself: "Coding task that needs human review (review-required)" — should `block(review-required: ...)` not `complete` The skill's discipline is correct but lives in the `kanban-worker` skill, which the tasker-worker may or may not have loaded depending on what `kanban_create` passed via `--skills`. ### What needs to change 1. Update `~/.hermes/profiles/tasker-worker/SOUL.md` (or equivalent) to include explicit instructions: - Any card where `changed_files` would be non-empty → `block(review-required: ...)`, not `complete` - Post structured metadata (changed_files, tests_run, tests_passed, diff_path) as a comment before blocking - When the work produces a fix or feature implementation, file a Forgejo issue in the relevant repo with the diff/work as the body, then block for review 2. Update the profile's per-card skill loading so `kanban-worker` is always attached when the tasker-worker spawns 3. Update the ingress (Vikunja sync) to add `--skills kanban-worker` when creating cards on the tasker board, so the discipline is in context ### Evidence - Vikunja milestone 59-63 (project 3 = org_mode) - Kanban tasker-board cards t_fb25b6b9, t_7e4bf156, t_fe3f8f50, t_1533d9e9, t_ff5ac64d — all `done` - No Forgejo issues created in window 2026-07-29T20:41-21:25 UTC on Mark/easystitch or Mark/easystitch-service - 19 files written to easystitch repo (uncommitted) ### Companion issues - See Mark/easystitch#109 for the dirty-tree state this gap produced - See Mark/org_mode (next issue) for the chat-agent-side framing problem that reinforced this gap