diff options
| author | Paul Buetow <paul@buetow.org> | 2026-02-28 20:17:04 +0200 |
|---|---|---|
| committer | Paul Buetow <paul@buetow.org> | 2026-02-28 20:17:04 +0200 |
| commit | f8b513b3887fc4d594f06b76c1f10342d05edba1 (patch) | |
| tree | 9d76485956ca850b1c9cf1e818a9a7557ae7963e /prompts/skills/taskwarrior-task-management | |
| parent | a82b8f22cc5c1bd3c5116bfe6d80745f890ba643 (diff) | |
update skills
Diffstat (limited to 'prompts/skills/taskwarrior-task-management')
| -rw-r--r-- | prompts/skills/taskwarrior-task-management/references/1-create-task.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/prompts/skills/taskwarrior-task-management/references/1-create-task.md b/prompts/skills/taskwarrior-task-management/references/1-create-task.md index cdb3f8d..7ba98e7 100644 --- a/prompts/skills/taskwarrior-task-management/references/1-create-task.md +++ b/prompts/skills/taskwarrior-task-management/references/1-create-task.md @@ -8,7 +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 taskwarrior-task-management 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 taskwarrior-task-management skill and to continue to the next task after completion. +- **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 taskwarrior-task-management skill. When working on this task, 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, automatically progress to the next task in the list."` This ensures agents (including those with fresh context) know to load and follow the taskwarrior-task-management skill, respect code-quality skills (best-practices, SOLID, beyond-SOLID), and 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. - **Record the task’s UUID for future reference.** After creating a task, resolve its UUID (for example, `task <id> _uuid`) and include it in an annotation such as `UUID: <uuid>` so the exact task can be recovered even if IDs are renumbered. - When tasks refer to other tasks in free text (annotations, descriptions, docs, or commit messages), **use the other task’s UUID**, not just its numeric ID. @@ -22,7 +22,7 @@ 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 taskwarrior-task-management skill. When all tests and sub-agent reviews pass, automatically progress to the next task in the list." +task <id> annotate "Agent: be aware of taskwarrior-task-management skill. When working on this task, 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, automatically progress to the next task in the list." ``` Also add an annotation that records the task’s UUID, for example: @@ -39,7 +39,7 @@ 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 taskwarrior-task-management skill. When all tests and sub-agent reviews pass, automatically progress to the next task in the list."` +After adding (with or without dependency), run the same annotation: `task <id> annotate "Agent: be aware of taskwarrior-task-management skill. When working on this task, 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, automatically progress to the next task in the list."` ## Conventions |
