@tekmidian/pai 0.14.2 → 0.15.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/cli/index.mjs +1 -1
- package/dist/cli/program.mjs +1 -1
- package/dist/config-C8m-tPhP.mjs.map +1 -1
- package/dist/daemon-mcp/index.mjs +22 -0
- package/dist/daemon-mcp/index.mjs.map +1 -1
- package/dist/{pick-gne3kOJG.mjs → pick-r95zvydr.mjs} +49 -7
- package/dist/pick-r95zvydr.mjs.map +1 -0
- package/dist/skills/Tasks/SKILL.md +22 -0
- package/docs/commands/task.md +1 -0
- package/package.json +1 -1
- package/dist/pick-gne3kOJG.mjs.map +0 -1
|
@@ -64,6 +64,14 @@ pai task add "Short actionable title" \\
|
|
|
64
64
|
--url "hook://..."
|
|
65
65
|
```
|
|
66
66
|
|
|
67
|
+
**Always file into the sub-project for the PAI project you are working in**, using `--into <name>`. It is created if it does not exist:
|
|
68
|
+
|
|
69
|
+
```bash
|
|
70
|
+
pai task add "Title" --into Clickr --owner clickr --body "..."
|
|
71
|
+
```
|
|
72
|
+
|
|
73
|
+
Creating that sub-project is **following the convention, not inventing structure**. Do not file flat into the root out of caution — a flat pile buries findings across projects, and every session that hesitates makes it worse. Only omit `--into` for something genuinely cross-cutting.
|
|
74
|
+
|
|
67
75
|
Rules:
|
|
68
76
|
- **`--body` is not optional in practice.** Enough that the task is actionable months later, or by the user alone, without re-deriving anything. A bare title is a reminder that something was once known — worthless later.
|
|
69
77
|
- **Omit `--owner` when you genuinely do not know.** It lands in the findings inbox for triage. Guessing is worse than leaving it unrouted.
|
|
@@ -94,6 +102,20 @@ For each `unrouted` item, decide with the user: assign an owner, act now, or del
|
|
|
94
102
|
|
|
95
103
|
A label matching nothing does **not** fall through to the container. The user meant somewhere specific; quietly routing elsewhere is worse than not routing.
|
|
96
104
|
|
|
105
|
+
---
|
|
106
|
+
|
|
107
|
+
### At session end
|
|
108
|
+
|
|
109
|
+
`pai end` finalises the session note and TODO.md. It does **not** touch the tracker — it is a mechanical command and deciding what counts as an open item needs judgement.
|
|
110
|
+
|
|
111
|
+
So before ending a session, file anything still open onto the bus yourself:
|
|
112
|
+
|
|
113
|
+
```bash
|
|
114
|
+
pai task add "<open item>" --into <ProjectName> --owner <project> --body "<procedure + reasoning>"
|
|
115
|
+
```
|
|
116
|
+
|
|
117
|
+
Otherwise the open items live only in a session note nobody re-reads, which is the loss the bus exists to prevent. If there is genuinely nothing open, say so rather than filing filler.
|
|
118
|
+
|
|
97
119
|
### Notes
|
|
98
120
|
|
|
99
121
|
- `pai task done <id>` closes a task. Dispatched tasks instruct the receiving session to do this, so work is not dispatched twice.
|
package/docs/commands/task.md
CHANGED
|
@@ -58,6 +58,7 @@ File a task onto the bus
|
|
|
58
58
|
| `--due <date>` | Due date (ISO or natural language) | |
|
|
59
59
|
| `--priority <p>` | p1 (highest) … p4 (default) | |
|
|
60
60
|
| `--url <url>` | Reference — prefer a hook:// URL over a file path | |
|
|
61
|
+
| `--into <sub-project>` | File into this sub-project under the bus root, creating it if absent | |
|
|
61
62
|
|
|
62
63
|
|
|
63
64
|
### pai task dispatch
|