summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPaul Buetow <paul@buetow.org>2026-03-23 21:33:06 +0200
committerPaul Buetow <paul@buetow.org>2026-03-23 21:33:06 +0200
commite6350999ce83c29b117af7b6b40e740ff3682d6f (patch)
tree3d12df6859d83872b6eeb694a8f16910a4e5446d
parenta011d05c158d0a272323ddcce09600219c5c67e2 (diff)
Update
-rw-r--r--fish/conf.d/ai.fish4
-rw-r--r--prompts/skills/agent-task-management/SKILL.md4
-rw-r--r--prompts/skills/agent-task-management/references/1-create-task.md7
3 files changed, 6 insertions, 9 deletions
diff --git a/fish/conf.d/ai.fish b/fish/conf.d/ai.fish
index 4e2296d..f88701b 100644
--- a/fish/conf.d/ai.fish
+++ b/fish/conf.d/ai.fish
@@ -1,6 +1,6 @@
abbr -a suggest hexai
abbr -a explain 'hexai explain'
-if test -f ~/git/hyperstack/hyperstack.fish
- source ~/git/hyperstack/hyperstack.fish
+if test -f ~/git/hypr/hypr.fish
+ source ~/git/hypr/hypr.fish
end
diff --git a/prompts/skills/agent-task-management/SKILL.md b/prompts/skills/agent-task-management/SKILL.md
index 2a426ef..c69dc8e 100644
--- a/prompts/skills/agent-task-management/SKILL.md
+++ b/prompts/skills/agent-task-management/SKILL.md
@@ -16,11 +16,9 @@ Valid examples:
- `ask add +cli "Add feature X"`
- `ask info uuid:<uuid>`
- `ask start uuid:<uuid>`
-- `ask annotate <short-uuid> "progress note"`
+- `ask annotate uuid:<uuid> "progress note"`
- `ask done uuid:<uuid>`
-**UUID selector quirk:** `ask annotate` requires the **short 8-character UUID** (first segment only, no `uuid:` prefix), e.g. `ask annotate 530ac084 "note"`. Using `uuid:<full-uuid>` with `ask annotate` fails. All other subcommands (`info`, `start`, `done`, `dep`, etc.) accept `uuid:<full-uuid>` normally.
-
Invalid examples:
- `ask agent-task-management ...`
diff --git a/prompts/skills/agent-task-management/references/1-create-task.md b/prompts/skills/agent-task-management/references/1-create-task.md
index 10b93aa..02d1448 100644
--- a/prompts/skills/agent-task-management/references/1-create-task.md
+++ b/prompts/skills/agent-task-management/references/1-create-task.md
@@ -8,9 +8,8 @@ Use with `00-context.md`. Project name and global rules apply. New tasks get `+a
- **Create tasks in smaller chunks that fit into the context window.** Break work into multiple tasks so that each task's scope, description, and required context (refs, files, docs) can fit in one context window when the agent works on it with a fresh context. Do not create single tasks that would require more context than available.
- **Every task MUST have at least one tag** for sub-project/feature/area (e.g. `+integrationtests`, `+flamegraph`, `+bpf`, `+cli`, `+refactor`, `+bugfix`).
- **After creating a task, add annotation** — one with the agent workflow reminder:
- **Important:** `ask annotate` requires the short 8-character UUID (first segment, no `uuid:` prefix). Using `uuid:<full-uuid>` fails for `annotate`.
```
- ask annotate <short-uuid> "Agent workflow: load the agent-task-management skill as instructions only, not as a shell command. Use only normal ask subcommand syntax. Also load and apply: (1) the best-practices skill for the programming language used in the project, (2) solid-principles. When all tests and sub-agent reviews pass, commit and automatically progress to the next ready task."
+ ask annotate uuid:<uuid> "Agent workflow: load the agent-task-management skill as instructions only, not as a shell command. Use only normal ask subcommand syntax. Also load and apply: (1) the best-practices skill for the programming language used in the project, (2) solid-principles. When all tests and sub-agent reviews pass, commit and automatically progress to the next ready task."
```
- **Include references to all context required** to work on the task. So that work can be done with a fresh context, every task must list or link everything needed: relevant files, docs, specs, other tasks, or project guidelines (e.g. paths, doc links, `AGENTS.md`, `README` sections). Put these in the task description or in an initial annotation so that an agent starting with no prior conversation has everything they need in the task itself.
@@ -24,10 +23,10 @@ Use with `00-context.md`. Project name and global rules apply. New tasks get `+a
ask add +<tag> "Description"
```
-Then add the workflow annotation and UUID annotation. The UUID returned by `ask add` is the full UUID; use only its **first 8 characters** (short UUID) for `ask annotate`:
+Then add the workflow annotation using `uuid:<full-uuid>` as returned by `ask add`:
```bash
-ask annotate <short-uuid> "Agent workflow: load the agent-task-management skill as instructions only, not as a shell command. Never run ask agent-task-management ... or other natural-language ask commands. Use only normal ask subcommand syntax. Also load and apply: (1) the best-practices skill for the programming language used in the project, (2) solid-principles, and (3) beyond-solid-principles. When all tests and sub-agent reviews pass, commit and automatically progress to the next ready task."
+ask annotate uuid:<uuid> "Agent workflow: load the agent-task-management skill as instructions only, not as a shell command. Never run ask agent-task-management ... or other natural-language ask commands. Use only normal ask subcommand syntax. Also load and apply: (1) the best-practices skill for the programming language used in the project, (2) solid-principles, and (3) beyond-solid-principles. When all tests and sub-agent reviews pass, commit and automatically progress to the next ready task."
```
## With dependency