From d3ec6430653de0e6ca65dd5ca7ece54cdde4e1ae Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Tue, 24 Mar 2026 19:00:12 +0200 Subject: Update 2-start-task.md: clarify task requirements, add "Finding a task" section with example usage --- prompts/skills/agent-task-management/references/2-start-task.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/prompts/skills/agent-task-management/references/2-start-task.md b/prompts/skills/agent-task-management/references/2-start-task.md index 1ea248f..d5dbc93 100644 --- a/prompts/skills/agent-task-management/references/2-start-task.md +++ b/prompts/skills/agent-task-management/references/2-start-task.md @@ -1,11 +1,17 @@ # Start task -Use with `00-context.md`. Project name and global rules apply (including one task in progress per project unless the user says otherwise). Only start tasks that have both `project:` and the `+agent` tag — use UUIDs from `ask list` output. +Use with `00-context.md`. Project name and global rules apply (including one task in progress per project unless the user says otherwise). ## Start each new task with a fresh context Work on each new task **must begin with a fresh context** — e.g. a new session or a sub-agent with no prior conversation. That way the task is executed with clear focus and no carry-over from other work. The task itself should already contain references to all required context (added when the task was created); read the task description and all annotations to get files, docs, and specs before starting. +## Finding a task + +```bash +ask ready | head +``` + ## Mark task as started When you begin working on a task, **always mark it as started** so current work is visible: -- cgit v1.2.3