@kitsy/coop 2.2.4 → 2.3.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/README.md +17 -5
- package/dist/index.js +894 -265
- package/package.json +4 -4
package/README.md
CHANGED
|
@@ -33,7 +33,11 @@ coop config artifacts.dir docs/agent-artifacts
|
|
|
33
33
|
```
|
|
34
34
|
|
|
35
35
|
Agent contract notes:
|
|
36
|
-
- `coop complete task <id>` requires the task to already be in `in_review`.
|
|
36
|
+
- `coop complete <id>` / `coop complete task <id>` requires the task to already be in `in_review`.
|
|
37
|
+
- `coop start <id>` / `coop start task <id>` can resume a blocked task directly into `in_progress` when the effective transition map allows `blocked -> in_progress`.
|
|
38
|
+
- `coop unblock <id>` / `coop unblock task <id>` always lands on `todo`; it does not restore the prior state.
|
|
39
|
+
- `coop workflow transitions show|set|add|remove|reset` is the primary CLI surface for workspace transition policy.
|
|
40
|
+
- multi-step recovery auto-hops write a transition audit artifact; direct transitions do not.
|
|
37
41
|
- balanced initial prompts are the recommended default for normal implementation sessions.
|
|
38
42
|
- if an agent is unsure about selection, transitions, artifacts, or whether it should continue, it should call the matching focused `help-ai` topic command instead of guessing.
|
|
39
43
|
- strict initial prompts tell agents to stop after completing the selected task instead of auto-picking another one.
|
|
@@ -44,12 +48,17 @@ Both entrypoints operate on the nearest parent `.coop/` workspace. If no workspa
|
|
|
44
48
|
|
|
45
49
|
COOP v2 stores project data under `.coop/projects/<project.id>/...` and keeps workspace selection in `.coop/config.yml`.
|
|
46
50
|
|
|
51
|
+
Command shape rule:
|
|
52
|
+
- When a command accepts an entity reference, the entity noun is optional. For example, `coop show PM-100` and `coop show task PM-100` are equivalent.
|
|
53
|
+
- Commands without an entity reference, such as `coop next`, remain task-first workflow surfaces.
|
|
54
|
+
|
|
47
55
|
Current implemented command families:
|
|
48
56
|
- `coop`
|
|
49
57
|
- `coop init [--name <name>] [--id <id>] [--aliases <csv>] [--naming <template>] [--yes]`
|
|
50
58
|
- `coop project list|create|use|show`
|
|
51
59
|
- `coop naming`
|
|
52
60
|
- `coop naming preview <title> [--template <template>]`
|
|
61
|
+
- `coop naming token default show|set|clear <token> [value]`
|
|
53
62
|
- `coop create task ...`
|
|
54
63
|
- `coop create task --acceptance <csv> --tests-required <csv> --authority-ref <ref> --derived-ref <ref>`
|
|
55
64
|
- `coop create task --from-file <path> | --stdin`
|
|
@@ -61,12 +70,15 @@ Current implemented command families:
|
|
|
61
70
|
- `coop create idea ...`
|
|
62
71
|
- `coop create track ...`
|
|
63
72
|
- `coop create delivery ... [--commit] [--user <user>] [--force]`
|
|
64
|
-
- `coop next
|
|
65
|
-
- `coop pick
|
|
66
|
-
- `coop start
|
|
67
|
-
- `coop review|complete|block|unblock|cancel|reopen
|
|
73
|
+
- `coop next [--track <track>] [--delivery <delivery>]`
|
|
74
|
+
- `coop pick [id] [--track <track>] [--delivery <delivery>] [--claim] [--to <assignee>]`
|
|
75
|
+
- `coop start [id] [--claim] [--to <assignee>]`
|
|
76
|
+
- `coop review|complete|block|unblock|cancel|reopen <id>`
|
|
77
|
+
- `coop rename <id> <alias>`
|
|
78
|
+
- `coop workflow transitions show|set|add|remove|reset`
|
|
68
79
|
- `coop assign task <id> --to <assignee> [--actor <actor>]`
|
|
69
80
|
- `coop list tasks|ideas|alias ...`
|
|
81
|
+
- `coop list tasks --completed|--todo|--blocked|--all`
|
|
70
82
|
- `coop show task|idea ...`
|
|
71
83
|
- `coop transition task ... [--user <user>] [--force]`
|
|
72
84
|
- `coop graph validate|next|show|critical-path ...`
|