1 files changed, 14 insertions, 14 deletions
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 5755475..0d472df 100644
--- a/prompts/skills/agent-task-management/references/1-create-task.md
+++ b/prompts/skills/agent-task-management/references/1-create-task.md
@@ -9,7 +9,7 @@ Use with `00-context.md`. Project name and global rules apply. New tasks get `+a
 - **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:
   ```
-  ~/go/bin/ask annotate <id> "Agent workflow: load the agent-task-management skill as instructions only, not as a shell command. Use only normal ~/go/bin/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 <id> "Agent workflow: load the agent-task-management skill as instructions only, not as a shell command. Use only normal ~/go/bin/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.
@@ -17,28 +17,28 @@ Use with `00-context.md`. Project name and global rules apply. New tasks get `+a
 
 ## Add a task
 
-`~/go/bin/ask add` already injects `project:<name> +agent`, so only add the extra feature tag(s), optional priority, optional `depends:` modifier, and description.
+`ask add` already injects `project:<name> +agent`, so only add the extra feature tag(s), optional priority, optional `depends:` modifier, and description.
 
 **Each part must be a separate shell argument — never quote tag and description together:**
 
 ```bash
-~/go/bin/ask add +<tag> "Description"
-~/go/bin/ask add priority:H +<tag> "Description"
-~/go/bin/ask add priority:M +<tag> "Description"
-~/go/bin/ask add +<tag> depends:<id1>,<id2> "Description"
+ask add +<tag> "Description"
+ask add priority:H +<tag> "Description"
+ask add priority:M +<tag> "Description"
+ask add +<tag> depends:<id1>,<id2> "Description"
 ```
 
 Do NOT do this (causes tag/priority to appear in the description instead of being applied):
 ```bash
-~/go/bin/ask add "+<tag> Description"           # wrong: tag and desc in one quoted string
-~/go/bin/ask add "+<tag> -p M Description"      # wrong: everything in one quoted arg
+ask add "+<tag> Description"           # wrong: tag and desc in one quoted string
+ask add "+<tag> -p M Description"      # wrong: everything in one quoted arg
 ```
 
-`~/go/bin/ask add` prints `created task <alias-id>`. Reuse that alias ID directly for follow-up commands:
+`ask add` prints `created task <alias-id>`. Reuse that alias ID directly for follow-up commands:
 
 ```bash
-id=$(~/go/bin/ask add +<tag> "Description" | sed -n 's/^created task //p')
-~/go/bin/ask annotate "$id" "Agent workflow: load the agent-task-management skill as instructions only, not as a shell command. Never run ~/go/bin/ask agent-task-management ... or other natural-language ~/go/bin/ask commands. Use only normal ~/go/bin/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."
+id=$(ask add +<tag> "Description" | sed -n 's/^created task //p')
+ask annotate "$id" "Agent workflow: load the agent-task-management skill as instructions only, not as a shell command. Never run ~/go/bin/ask agent-task-management ... or other natural-language ~/go/bin/ask commands. Use only normal ~/go/bin/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
@@ -46,13 +46,13 @@ id=$(~/go/bin/ask add +<tag> "Description" | sed -n 's/^created task //p')
 Add dependencies inline during task creation:
 
 ```bash
-id=$(~/go/bin/ask add +<tag> depends:<dep-id> "Description" | sed -n 's/^created task //p')
+id=$(ask add +<tag> depends:<dep-id> "Description" | sed -n 's/^created task //p')
 ```
 
 Multiple dependencies:
 
 ```bash
-id=$(~/go/bin/ask add +<tag> depends:<dep-id1>,<dep-id2> "Description" | sed -n 's/^created task //p')
+id=$(ask add +<tag> depends:<dep-id1>,<dep-id2> "Description" | sed -n 's/^created task //p')
 ```
 
 After adding (with or without dependency), run the same annotations using that alias ID directly.
@@ -61,6 +61,6 @@ After adding (with or without dependency), run the same annotations using that a
 
 - **Keep tasks small:** each task should be a chunk that fits in the context window (description + refs + work to do). Split large efforts into multiple dependent tasks.
 - Pick or create a meaningful tag for the sub-project or feature.
-- **Always check for dependencies:** before adding a task, determine if it depends on other tasks in the project; if so, add `depends:<id>,...` during `~/go/bin/ask add`.
+- **Always check for dependencies:** before adding a task, determine if it depends on other tasks in the project; if so, add `depends:<id>,...` during `ask add`.
 - Add dependencies when one task must complete before another can start.
 - When creating a task, add references to all required context (files, docs, specs) so the task is self-contained for fresh-context work.