diff options
| -rw-r--r-- | prompts/skills/agent-task-management/references/1-create-task.md | 4 |
1 files changed, 2 insertions, 2 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 0d472df..b9f1699 100644 --- a/prompts/skills/agent-task-management/references/1-create-task.md +++ b/prompts/skills/agent-task-management/references/1-create-task.md @@ -6,7 +6,7 @@ Use with `00-context.md`. Project name and global rules apply. New tasks get `+a - **When creating a new task, always check whether the new task depends on other (existing) tasks.** If it does, add those dependencies inline with `depends:<id>,...` while creating the task. - **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`). +- **Every task MUST have at least one tag** for sub-project/feature/area (e.g. `+integrationtests`, `+flamegraph`, `+bpf`, `+cli`, `+refactor`, `+bugfix`). **Tag names cannot contain hyphens (`-`)**; use camelCase or concatenated words instead (e.g. `+bugfix` not `+bug-fix`). - **After creating a task, add annotation** — one with the agent workflow reminder: ``` 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." @@ -60,7 +60,7 @@ After adding (with or without dependency), run the same annotations using that a ## 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. -- Pick or create a meaningful tag for the sub-project or feature. +- Pick or create a meaningful tag for the sub-project or feature. **Tags cannot contain hyphens (`-`)** — use camelCase or concatenated words (e.g. `+codeReview`, `+bugfix`). - **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. |