diff options
| -rw-r--r-- | prompts/commands/work-on-tasks.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/prompts/commands/work-on-tasks.md b/prompts/commands/work-on-tasks.md index 10da5f1..5fd2423 100644 --- a/prompts/commands/work-on-tasks.md +++ b/prompts/commands/work-on-tasks.md @@ -33,16 +33,16 @@ You are the **orchestrator**. You pick tasks, mark them started, launch a sub-ag 2. **Pick the next task** (default strategy: `{{strategy|highest-impact}}`): - Choose one actionable task based on impact, urgency, and clarity - If two tasks are equivalent, prefer the one that unblocks other work - - Run `ask info uuid:<uuid>` to read the full task description and all annotations + - Run `ask info uuid:<uuid> 2>&1 | head -20` to preview the task — this caps the output at 20 lines so long descriptions do not flood the screen 3. **Mark the task started**: - Run `ask start uuid:<uuid>` 4. **Delegate to a fresh sub-agent**: - Spawn a **new sub-agent** with a self-contained prompt that includes: - - The full task description and all annotations (copy them verbatim) + - The task UUID and a one-line summary of what the task is about + - Instruction to run `ask info uuid:<uuid>` as its **first action** to get the full description and all annotations (do not paste the description inline — the sub-agent fetches it fresh, keeping the prompt short) - The absolute path of the project root - - The UUID of the task (so the sub-agent can annotate it) - Instruction to run `ask annotate uuid:<uuid> "<progress notes>"` as it works - Instruction to commit all changes to git when done - Instruction to **not** mark the task done (the orchestrator does that) |