summaryrefslogtreecommitdiff
path: root/gemfeed
diff options
context:
space:
mode:
authorPaul Buetow <paul@buetow.org>2026-07-08 17:26:52 +0300
committerPaul Buetow <paul@buetow.org>2026-07-08 17:26:52 +0300
commitc8cc52a1ed6c0df34f13a096fd21b1fd6850e3aa (patch)
tree5f4394fd9265a7753eec658d645b30fcfab55d2b /gemfeed
parentaf65ff2efa13a68d2d567c8f8a200175aa15124f (diff)
Update content for md
Diffstat (limited to 'gemfeed')
-rw-r--r--gemfeed/2026-07-09-unveiling-hexai.md5
1 files changed, 5 insertions, 0 deletions
diff --git a/gemfeed/2026-07-09-unveiling-hexai.md b/gemfeed/2026-07-09-unveiling-hexai.md
index 774148b1..6e2621c2 100644
--- a/gemfeed/2026-07-09-unveiling-hexai.md
+++ b/gemfeed/2026-07-09-unveiling-hexai.md
@@ -326,6 +326,11 @@ Urgency: 7.8
Tags: agent
```
+This is where it becomes useful for agentic coding. There is an agent skill and a slash command built on top of `ask`: the `agent-task-management` skill knows how to read and update the `ask` task list, and the `/work-on-tasks` command uses that skill to work through a whole backlog on its own — pick the next actionable task, hand it to a fresh sub-agent, mark it done, and continue until nothing actionable is left. That is pretty useful after a planning session where you created a bunch of tasks with their proper dependencies set: point the agent at the project, run `/work-on-tasks`, and it chews through the queue one task at a time.
+
+[agent-task-management skill](https://codeberg.org/snonux/dotfiles/src/branch/master/prompts/skills/agent-task-management)
+[/work-on-tasks command](https://codeberg.org/snonux/dotfiles/src/branch/master/prompts/commands/work-on-tasks.md)
+
## Running multiple providers side by side
One feature I use more than I expected: per-surface model lists. In `config.toml` you can configure several providers or models for the same entry point, and Hexai fans the request out to all of them in parallel.