@staff0rd/assist 0.1011.3 → 0.1013.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/claude/commands/draft.md +24 -4
- package/claude/commands/refine.md +24 -3
- package/dist/commands/sessions/web/bundle.js +403 -403
- package/dist/index.js +9 -4
- package/package.json +1 -1
package/claude/commands/draft.md
CHANGED
|
@@ -24,9 +24,19 @@ Ask one question at a time. Wait for the user's response before asking the next.
|
|
|
24
24
|
|
|
25
25
|
If the harness provides a structured question tool, ask each question with it — one question per call, with fixed options and a recommended default where they apply. Only fall back to plain chat text when no such tool exists.
|
|
26
26
|
|
|
27
|
-
## Step 3:
|
|
27
|
+
## Step 3: Design the UI change
|
|
28
28
|
|
|
29
|
-
|
|
29
|
+
From the clarifying answers, decide whether the story involves a **substantial UI change** — a new screen, panel, view or component, or a reworked layout or interaction flow. A trivial UI change (a label, a button, a tweak to an existing control) or no UI change at all is not substantial: skip this step entirely and do not mention it.
|
|
30
|
+
|
|
31
|
+
If it is substantial, do not ask whether to design it — follow `/design` (`~/.claude/commands/design.md`) for the story's UI, applying it to what the user described and answered. Publish the design as an artifact, give the user its URL, and iterate on it with them — editing the same file and republishing to the same URL — until they say they are happy with it. Only then move on.
|
|
32
|
+
|
|
33
|
+
Keep the artifact's URL and name: the item's description references the design (Step 4), and the artifact is attached to the item once it is created (Step 5).
|
|
34
|
+
|
|
35
|
+
## Step 4: Compose the item
|
|
36
|
+
|
|
37
|
+
Compose the item's content, but do not show it to the user yet and do not work out where the review should happen — `propose` decides that in Step 5 and tells you what to do next.
|
|
38
|
+
|
|
39
|
+
If Step 3 produced a design, the description links to it (e.g. a `## Design` section with the artifact URL) so the implementer builds against it.
|
|
30
40
|
|
|
31
41
|
**Name:** (concise title)
|
|
32
42
|
**Type:** story or bug
|
|
@@ -94,7 +104,7 @@ If it reports the key is not set, plan docs updates as the change needs them.
|
|
|
94
104
|
|
|
95
105
|
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 appended to every plan automatically, and authoring one is rejected.
|
|
96
106
|
|
|
97
|
-
## Step
|
|
107
|
+
## Step 5: Propose the item
|
|
98
108
|
|
|
99
109
|
Propose the item and capture the id it prints. Use `propose`, not `assist backlog add` plus `add-phase` — `propose` is the reviewed path for an agent-authored item, and it writes the item and every phase on a single approval:
|
|
100
110
|
|
|
@@ -153,9 +163,19 @@ assist backlog add-activity a<id> slack "<permalink>" --url "<permalink>" --titl
|
|
|
153
163
|
|
|
154
164
|
Use the same permalink verbatim for both the ref and `--url`, and the item's name for `--title`. If no Slack thread was referenced, skip this step.
|
|
155
165
|
|
|
166
|
+
### Attach the design
|
|
167
|
+
|
|
168
|
+
If Step 3 published a design artifact, attach it to the created item so it renders as a linked design row in the Activity section:
|
|
169
|
+
|
|
170
|
+
```
|
|
171
|
+
assist backlog add-activity a<id> design "<artifact-url>" --url "<artifact-url>" --title "<artifact name>" 2>&1
|
|
172
|
+
```
|
|
173
|
+
|
|
174
|
+
Use the artifact URL verbatim for both the ref and `--url`, and the artifact's name for `--title`. If Step 3 was skipped, skip this step.
|
|
175
|
+
|
|
156
176
|
Then show the user the item was created. If `propose` printed `Started a backlog run session for a<id>.`, the user chose **Approve & start** and implementation is already running — say so, and do not suggest running it. Otherwise suggest they can run `assist backlog run a<id>` to start implementation.
|
|
157
177
|
|
|
158
|
-
If the conversation established that more items still need to be drafted (e.g. a follow-up item, or one in another repo), do not signal yet — draft each remaining item now, repeating Steps 3
|
|
178
|
+
If the conversation established that more items still need to be drafted (e.g. a follow-up item, or one in another repo), do not signal yet — draft each remaining item now, repeating Steps 3 to 5 for it.
|
|
159
179
|
|
|
160
180
|
Finally, once the last item is created, signal that the drafting task is complete, passing every item id created in this session (a-prefixed, e.g. `a555 a556`):
|
|
161
181
|
|
|
@@ -99,11 +99,32 @@ assist backlog comment <id> "Comment text"
|
|
|
99
99
|
|
|
100
100
|
After applying changes, show the updated item with `assist backlog view <id> 2>&1` so the user can verify.
|
|
101
101
|
|
|
102
|
-
## Step 4:
|
|
102
|
+
## Step 4: Design the UI change
|
|
103
103
|
|
|
104
|
-
|
|
104
|
+
Check the item's Activity section (from `assist backlog view <id>`) for an existing `design` row, then decide whether a design is needed. A **substantial UI change** is a new screen, panel, view or component, or a reworked layout or interaction flow; a trivial UI change (a label, a button, a tweak to an existing control) or no UI change at all is not.
|
|
105
105
|
|
|
106
|
-
|
|
106
|
+
- **No `design` activity** and the item, as refined, involves a substantial UI change — produce a new design.
|
|
107
|
+
- **An existing `design` activity** and this refinement changes the UI substantially — update that design, republishing to its existing artifact URL rather than creating a new one.
|
|
108
|
+
- Otherwise — skip this step entirely and do not mention it.
|
|
109
|
+
|
|
110
|
+
When a design is needed, do not ask whether to design it — follow `/design` (`~/.claude/commands/design.md`) for the item's UI, applying it to the item as refined. To update an existing design, read the artifact at its URL first and build on it, publishing back to the same URL. Give the user the artifact's URL and iterate on it with them — editing the same file and republishing to the same URL — until they say they are happy with it.
|
|
111
|
+
|
|
112
|
+
Then keep the item in sync with the design:
|
|
113
|
+
|
|
114
|
+
- **Description** — make sure it links to the design (e.g. a `## Design` section with the artifact URL) so the implementer builds against it. Add the link if it is missing or points elsewhere, using `update-field --desc` with the full description.
|
|
115
|
+
- **Activity** — if the design is new, attach it so it renders as a linked design row in the Activity section:
|
|
116
|
+
|
|
117
|
+
```
|
|
118
|
+
assist backlog add-activity <id> design "<artifact-url>" --url "<artifact-url>" --title "<artifact name>" 2>&1
|
|
119
|
+
```
|
|
120
|
+
|
|
121
|
+
Use the artifact URL verbatim for both the ref and `--url`, and the artifact's name for `--title`. A republished design keeps its URL, so its existing activity needs no change.
|
|
122
|
+
|
|
123
|
+
## Step 5: Iterate
|
|
124
|
+
|
|
125
|
+
Ask if there is anything else to refine. Continue the conversation until the user is satisfied, revisiting Step 4 whenever a further refinement changes the UI substantially.
|
|
126
|
+
|
|
127
|
+
## Step 6: Signal completion
|
|
107
128
|
|
|
108
129
|
Once the user confirms they are done refining — and any new items the conversation called for (e.g. a split-out follow-up) have been created — signal that the task is complete, passing the ids of any items created in this session:
|
|
109
130
|
|