@staff0rd/assist 0.175.0 → 0.177.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 +5 -0
- package/allowed.cli-writes +3 -0
- package/claude/commands/refine.md +74 -0
- package/dist/allowed.cli-writes +3 -0
- package/dist/index.js +699 -450
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -40,6 +40,7 @@ After installation, the `assist` command will be available globally. You can als
|
|
|
40
40
|
- `/draft` - Draft a new backlog item with LLM-assisted questioning
|
|
41
41
|
- `/pr` - Raise a PR with a concise description
|
|
42
42
|
- `/refactor` - Run refactoring checks for code quality
|
|
43
|
+
- `/refine` - Refine an existing backlog item through conversation
|
|
43
44
|
- `/restructure` - Analyze and restructure tightly-coupled files
|
|
44
45
|
- `/review-comments` - Process PR review comments one by one
|
|
45
46
|
- `/jira` - View a Jira work item
|
|
@@ -85,6 +86,9 @@ After installation, the `assist` command will be available globally. You can als
|
|
|
85
86
|
- `assist backlog add` - Add a new backlog item interactively (prompts for type: story/bug)
|
|
86
87
|
- `assist backlog add --name <n> --type <t> --desc <d> --ac <criterion...>` - Add a backlog item from CLI options (used by `/draft`)
|
|
87
88
|
- `assist backlog add-phase <id> <name> --task <t...> [--manual-check <c...>]` - Add a phase to an existing backlog item
|
|
89
|
+
- `assist backlog update <id> [--name <n>] [--desc <d>] [--type <t>] [--ac <criterion...>]` - Update fields on a backlog item
|
|
90
|
+
- `assist backlog update-phase <id> <phase> [--name <n>] [--task <t...>] [--manual-check <c...>]` - Modify a plan phase (name, tasks, or manual checks)
|
|
91
|
+
- `assist backlog remove-phase <id> <phase>` - Remove a plan phase from a backlog item
|
|
88
92
|
- `assist backlog next` - Pick and run the next backlog item, or open `/draft` if none remain
|
|
89
93
|
- `assist backlog start <id>` - Set a backlog item to in-progress
|
|
90
94
|
- `assist backlog done <id>` - Set a backlog item to done
|
|
@@ -182,5 +186,6 @@ After installation, the `assist` command will be available globally. You can als
|
|
|
182
186
|
- `assist next` - Alias for `backlog next -w`
|
|
183
187
|
- `assist draft` (alias: `feat`) - Launch Claude in `/draft` mode, chain into next on `/next` signal
|
|
184
188
|
- `assist bug` - Launch Claude in `/bug` mode, chain into next on `/next` signal
|
|
189
|
+
- `assist refine [id]` - Launch Claude in `/refine` mode to refine a backlog item; prompts for selection when no id given
|
|
185
190
|
- `assist signal next` - Write a next signal to chain into `assist next`
|
|
186
191
|
|
package/allowed.cli-writes
CHANGED
|
@@ -0,0 +1,74 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Refine an existing backlog item through conversation
|
|
3
|
+
allowed_args: "<backlog item id>"
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
You are helping the user refine an existing backlog item through conversation.
|
|
7
|
+
|
|
8
|
+
## Step 1: Load the item
|
|
9
|
+
|
|
10
|
+
Parse `$ARGUMENTS` as a backlog item ID. If no ID was provided, ask the user which item they want to refine.
|
|
11
|
+
|
|
12
|
+
Show the current item state by running:
|
|
13
|
+
|
|
14
|
+
```
|
|
15
|
+
assist backlog view <id> 2>&1
|
|
16
|
+
```
|
|
17
|
+
|
|
18
|
+
Display the output so the user can see the current state.
|
|
19
|
+
|
|
20
|
+
## Step 2: Ask what to refine
|
|
21
|
+
|
|
22
|
+
Ask the user what they want to change or improve about this item. Listen for changes to any of:
|
|
23
|
+
|
|
24
|
+
- **Name** or **description**
|
|
25
|
+
- **Type** (story / bug)
|
|
26
|
+
- **Acceptance criteria**
|
|
27
|
+
- **Plan phases** (add, modify, or remove phases and their tasks)
|
|
28
|
+
- **General feedback** that should be captured as a comment
|
|
29
|
+
|
|
30
|
+
Ask one focused question at a time. Wait for the user's response before continuing.
|
|
31
|
+
|
|
32
|
+
## Step 3: Apply changes
|
|
33
|
+
|
|
34
|
+
Based on the user's input, apply changes using the appropriate commands. Always append `2>&1` to each command.
|
|
35
|
+
|
|
36
|
+
**To update item fields:**
|
|
37
|
+
```
|
|
38
|
+
assist backlog update <id> --name "New name"
|
|
39
|
+
assist backlog update <id> --desc "New description"
|
|
40
|
+
assist backlog update <id> --type story
|
|
41
|
+
assist backlog update <id> --ac "criterion 1" --ac "criterion 2"
|
|
42
|
+
```
|
|
43
|
+
|
|
44
|
+
Note: `--ac` replaces all acceptance criteria, so include the full list (both existing and new).
|
|
45
|
+
|
|
46
|
+
**To modify a plan phase** (phase is 0-indexed):
|
|
47
|
+
```
|
|
48
|
+
assist backlog update-phase <id> <phase> --name "New phase name"
|
|
49
|
+
assist backlog update-phase <id> <phase> --task "Task 1" --task "Task 2"
|
|
50
|
+
assist backlog update-phase <id> <phase> --manual-check "Check 1"
|
|
51
|
+
```
|
|
52
|
+
|
|
53
|
+
Note: `--task` and `--manual-check` replace the full list for that phase, so include all items.
|
|
54
|
+
|
|
55
|
+
**To remove a plan phase:**
|
|
56
|
+
```
|
|
57
|
+
assist backlog remove-phase <id> <phase>
|
|
58
|
+
```
|
|
59
|
+
|
|
60
|
+
**To add a new plan phase:**
|
|
61
|
+
```
|
|
62
|
+
assist backlog add-phase <id> "Phase name" --task "Task 1" --task "Task 2"
|
|
63
|
+
```
|
|
64
|
+
|
|
65
|
+
**To add a comment** (for context, decisions, or notes that don't fit in fields):
|
|
66
|
+
```
|
|
67
|
+
assist backlog comment <id> "Comment text"
|
|
68
|
+
```
|
|
69
|
+
|
|
70
|
+
After applying changes, show the updated item with `assist backlog view <id> 2>&1` so the user can verify.
|
|
71
|
+
|
|
72
|
+
## Step 4: Iterate
|
|
73
|
+
|
|
74
|
+
Ask if there is anything else to refine. Continue the conversation until the user is satisfied.
|
package/dist/allowed.cli-writes
CHANGED