blob: 78af213f5568421b2ca3ded02ac125db86efc92f (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
|
# 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).
## Start each new task with a fresh context
Work on each new task **must begin with a fresh context** — a new sub-agent with no prior conversation history. That way the task is executed with clear focus and no carry-over from other work.
**If you are orchestrating via `/work-on-tasks`:** spawn a sub-agent for the implementation or even multiple sub-agents if they can work in parallel. Pass the full task description, all annotations, and the project root path to the sub-agent. Do not implement tasks in the orchestrator's own context.
**If you are starting a single task manually:** begin in a new session or compact first so the context is clean before you start working.
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:
```bash
ask start <id>
```
Do this as soon as you start work on the task.
## Conventions
- Start each new task with a fresh context; rely on the task's description and annotations for all required context.
- Run `ask start <id>` when you start working on the task, not only when listing or completing.
- Do not start a second task for the same project while one is already started and not done, unless the user explicitly asks.
- When a task is selected via the review/overview step, use the alias ID from the list or task details for subsequent `start` operations.
|
