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
37
38
39
40
41
42
43
44
45
|
# Annotate / update task
Use with `00-context.md`. Project name and global rules apply.
## Reading task context
When working on a task, **always read the full context:** description, summary, and **all annotations**. Annotations often contain progress, challenges, and references to files or documents — use them for further reference.
View full task (including annotations):
```bash
ask info <id>
```
## Annotate a task
```bash
ask annotate <id> "Note about progress or context"
```
While making progress, **add annotations** to reflect progress, challenges, or decisions. You may refer to files, documents, or other resources (paths, doc links, snippets) so the task history stays useful for later work and for the pre-completion review.
Whenever you mention another task inside an annotation (for example, as a dependency or related work), include that other task's alias ID.
## Modify a task
```bash
ask modify <id> +<tag>
ask dep add <id> <dep-id>
ask modify <id> priority:H
```
Use the alias ID shown by `ask list`, `ask ready`, or `ask info` when modifying tasks selected earlier or referenced from annotations or other docs.
## Delete a task
```bash
ask delete <id>
```
## Conventions
- Read description, summary, and all annotations when working on a task.
- Annotate with implementation notes, progress, challenges, and references to files or documents as you go.
- Annotations should be detailed enough that a fresh-context agent can pick up work without needing to ask clarifying questions.
|
