@staff0rd/assist 0.172.3 → 0.172.4

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 CHANGED
@@ -83,7 +83,8 @@ After installation, the `assist` command will be available globally. You can als
83
83
  - `assist backlog init` - Create an empty backlog
84
84
  - `assist backlog list [--status <type>] [-v]` - List all backlog items with status icons
85
85
  - `assist backlog add` - Add a new backlog item interactively (prompts for type: story/bug)
86
- - `assist backlog add --file <path>` - Add a backlog item from a JSON file (used by `/draft`)
86
+ - `assist backlog add --name <n> --type <t> --desc <d> --ac <criterion...>` - Add a backlog item from CLI options (used by `/draft`)
87
+ - `assist backlog add-phase <id> <name> --task <t...> [--manual-check <c...>]` - Add a phase to an existing backlog item
87
88
  - `assist backlog next` - Pick and run the next backlog item, or open `/draft` if none remain
88
89
  - `assist backlog start <id>` - Set a backlog item to in-progress
89
90
  - `assist backlog done <id>` - Set a backlog item to done
@@ -1,4 +1,5 @@
1
1
  assist backlog add
2
+ assist backlog add-phase
2
3
  assist backlog comment
3
4
  assist backlog done
4
5
  assist backlog link
@@ -41,20 +41,9 @@ Ask the user if they want to change anything. Iterate until they confirm.
41
41
 
42
42
  ## Step 5: Save
43
43
 
44
- Once confirmed, pipe the JSON to the CLI. The JSON must match this shape:
45
-
46
- ```json
47
- {
48
- "name": "...",
49
- "type": "bug",
50
- "description": "**Repro:**\n1. ...\n\n**Expected:** ...\n\n**Actual:** ...",
51
- "acceptanceCriteria": ["...", "..."]
52
- }
44
+ Once confirmed, add the item via CLI:
53
45
  ```
54
-
55
- Run:
56
- ```
57
- echo '<the confirmed json>' | assist backlog add --json 2>&1
46
+ assist backlog add --name "Bug title" --type bug --desc "**Repro:**\n1. ...\n\n**Expected:** ...\n\n**Actual:** ..." --ac "criterion 1" --ac "criterion 2" 2>&1
58
47
  ```
59
48
 
60
49
  Then show the user the item was created and suggest they can run `assist backlog run <id>` to start implementation.
@@ -38,7 +38,7 @@ Once you have enough context, propose a complete backlog item. Show it to the us
38
38
 
39
39
  Keep phases small (2-4 tasks each). A typical item should have 2-3 phases.
40
40
 
41
- Most phases should NOT have manual checks — prefer automated verification via the `verify` field on tasks. Only add `manualChecks` to a phase when the checks are genuinely difficult to automate (e.g. visual appearance, UX flow, hardware interaction). Do not add a final phase just for end-to-end verification — a review phase is auto-appended at runtime.
41
+ Most phases should NOT have manual checks. Only add `manualChecks` to a phase when the checks are genuinely difficult to automate (e.g. visual appearance, UX flow, hardware interaction). Do not add a final phase just for end-to-end verification — a review phase is auto-appended at runtime.
42
42
 
43
43
  ## Step 4: Iterate
44
44
 
@@ -46,29 +46,16 @@ Ask the user if they want to change anything. Iterate until they confirm.
46
46
 
47
47
  ## Step 5: Save
48
48
 
49
- Once confirmed, write the JSON to a temp file and add it via the CLI. The JSON must match this shape:
50
-
51
- ```json
52
- {
53
- "name": "...",
54
- "type": "story",
55
- "description": "...",
56
- "acceptanceCriteria": ["...", "..."],
57
- "plan": [
58
- {
59
- "name": "Phase name",
60
- "tasks": [
61
- { "task": "Do something", "verify": "optional verification step" }
62
- ],
63
- "manualChecks": ["optional — only for checks that can't be automated"]
64
- }
65
- ]
66
- }
49
+ Once confirmed, create the item and its phases via CLI commands.
50
+
51
+ First, add the item:
52
+ ```
53
+ assist backlog add --name "Item name" --type story --desc "Description text" --ac "criterion 1" --ac "criterion 2" 2>&1
67
54
  ```
68
55
 
69
- Use the Write tool to save the JSON to a temp file (e.g. `/tmp/backlog-item.json`), then run:
56
+ Then add each phase:
70
57
  ```
71
- assist backlog add --file /tmp/backlog-item.json 2>&1
58
+ assist backlog add-phase <id> "Phase name" --task "Task 1" --task "Task 2" --manual-check "optional check" 2>&1
72
59
  ```
73
60
 
74
61
  Then show the user the item was created and suggest they can run `assist backlog run <id>` to start implementation.
@@ -1,4 +1,5 @@
1
1
  assist backlog add
2
+ assist backlog add-phase
2
3
  assist backlog comment
3
4
  assist backlog done
4
5
  assist backlog link