Update

3 files changed, 14 insertions, 2 deletions

diff --git a/prompts/skills/project-taskwarrior/1-create-task.md b/prompts/skills/project-taskwarrior/1-create-task.md
index 62a430b..3c39cb3 100644
--- a/prompts/skills/project-taskwarrior/1-create-task.md
+++ b/prompts/skills/project-taskwarrior/1-create-task.md
@@ -8,6 +8,7 @@ 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`).
 - **When an agent creates a task, always add the tag `+agent`** so agent-created tasks can be identified.
+- **After creating a task, add an annotation** so any agent working on the task is reminded to use this skill and to auto-progress: `task <id> annotate "Agent: be aware of project-taskwarrior skill. When all tests and sub-agent reviews pass, automatically progress to the next task in the list."` This ensures agents (including those with fresh context) know to load and follow the project-taskwarrior skill and to continue to the next task after completion.
 - **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.
 
 ## Add a task
@@ -16,6 +17,12 @@ Use with `00-context.md`. Project name and global rules apply. New tasks get `+a
 task add project:<name> +<tag> +agent "Description"
 ```
 
+Then add the agent-awareness annotation (use the ID from the add output):
+
+```bash
+task <id> annotate "Agent: be aware of project-taskwarrior skill. When all tests and sub-agent reviews pass, automatically progress to the next task in the list."
+```
+
 ## With dependency
 
 ```bash
@@ -24,6 +31,8 @@ task add project:<name> +<tag> +agent "Description" depends:<id>
 
 Multiple dependencies: `depends:<id1>,<id2>`.
 
+After adding (with or without dependency), run the same annotation: `task <id> annotate "Agent: be aware of project-taskwarrior skill. When all tests and sub-agent reviews pass, automatically progress to the next task in the list."`
+
 ## Conventions
 
 - **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.
diff --git a/prompts/skills/project-taskwarrior/3-complete-task.md b/prompts/skills/project-taskwarrior/3-complete-task.md
index df03f85..c82e595 100644
--- a/prompts/skills/project-taskwarrior/3-complete-task.md
+++ b/prompts/skills/project-taskwarrior/3-complete-task.md
@@ -48,6 +48,8 @@ If the answer suggests improvements or inconsistencies, address them first. Only
 task <id> done
 ```
 
+7. **Automatically progress to the next task in the list.** After marking the task done, if there are more agent-managed tasks in the project (e.g. `task project:<name> +agent list` shows pending/ready tasks), start the next one: load `00-context.md` and `2-start-task.md`, pick the next task from the list (respecting dependencies and "one task in progress" rule), and begin work on it. Do not stop after completing a task when a next task is available — continue to the next task in the list.
+
 ## Conventions
 
 - When creating or changing tests, add negative tests (invalid input, errors, failure paths) wherever plausible; the review sub-agent will check for this.
@@ -56,3 +58,4 @@ task <id> done
 - **On completion, commit all changes to git** before running `task <id> done`; do not leave uncommitted work when marking a task complete.
 - Complete with `task <id> done` only after completion criteria, self-review(s), first review, addressing all comments, follow-up sub-agent review, and git commit are satisfied.
 - When completing a task, note which tasks were unblocked (dependents that became ready), if any.
+- **After completing a task, automatically progress to the next task in the list** (when all tests and sub-agent reviews pass and the task is done). Start the next ready task in `project:<name> +agent`; do not stop unless no next task is available or the user asks to stop.
diff --git a/prompts/skills/project-taskwarrior/SKILL.md b/prompts/skills/project-taskwarrior/SKILL.md
index bcc9708..c32e5a4 100644
--- a/prompts/skills/project-taskwarrior/SKILL.md
+++ b/prompts/skills/project-taskwarrior/SKILL.md
@@ -27,6 +27,6 @@ Always load `00-context.md` first (project name resolution and global rules); th
 
 ## Task lifecycle (overview)
 
-1. Create task → 2. Start task → 3. Annotate as you go → 4. **Completion criteria** (best practices, compilable, all tests pass, negative tests where plausible) → 5. Sub-agent review (fresh context) → 6. Main agent addresses all review comments → 7. **Second sub-agent review** (fresh context again) to confirm fixes → 8. **Commit all changes to git** → 9. Complete task
+1. Create task → 2. Start task → 3. Annotate as you go → 4. **Completion criteria** (best practices, compilable, all tests pass, negative tests where plausible) → 5. Sub-agent review (fresh context) → 6. Main agent addresses all review comments → 7. **Second sub-agent review** (fresh context again) to confirm fixes → 8. **Commit all changes to git** → 9. Complete task → 10. **Automatically progress to the next task in the list** (when all tests and sub-agent reviews pass).
 
-A task is not done until criteria are met, all review comments are addressed, a second sub-agent review has confirmed the code, and all changes are committed to git. Details are in `3-complete-task.md`.
+A task is not done until criteria are met, all review comments are addressed, a second sub-agent review has confirmed the code, and all changes are committed to git. After completing a task, start the next task in the list (if any). Details are in `3-complete-task.md`.