@staff0rd/assist 0.1031.0 → 0.1032.1

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.
@@ -21,9 +21,15 @@ Before asking the user about existing functionality — how a feature currently
21
21
 
22
22
  Skip questions the user has already answered. Stop asking as soon as you have enough to write a clear bug report — don't over-interrogate.
23
23
 
24
- ## Step 3: Compose the bug report
24
+ ## Step 3: Design the UI change
25
25
 
26
- Compose the bug report'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 4 and tells you what to do next.
26
+ Read the **Designing a new backlog item's UI change** section of `/design` (`~/.claude/skills/design/SKILL.md`) and follow its Decide and Design and review steps for the fix. If it decides the fix's UI change is not substantial, skip this step silently. Otherwise its link step applies in Step 4 and its attach step in Step 5.
27
+
28
+ ## Step 4: Compose the bug report
29
+
30
+ Compose the bug report'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.
31
+
32
+ If Step 3 produced a design, link it from the description as `/design` describes.
27
33
 
28
34
  **Name:** (concise title)
29
35
  **Type:** bug
@@ -53,7 +59,7 @@ The description renders as markdown in both the terminal (`assist backlog show`)
53
59
  **Actual:** what happens instead.
54
60
  ```
55
61
 
56
- ## Step 4: Propose the item
62
+ ## Step 5: Propose the item
57
63
 
58
64
  Propose the item and capture the id it prints. Use `propose`, not `assist backlog add` — `propose` is the reviewed path for an agent-authored item:
59
65
 
@@ -108,9 +114,13 @@ assist backlog add-activity a<id> slack "<permalink>" --url "<permalink>" --titl
108
114
 
109
115
  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.
110
116
 
117
+ ### Attach the design
118
+
119
+ If Step 3 published a design artifact, attach it to the created item as `/design` describes. If Step 3 was skipped, skip this step.
120
+
111
121
  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.
112
122
 
113
- If the conversation established that more items still need to be filed (e.g. a follow-up item, or one in another repo), do not signal yet — create each remaining item now, repeating Steps 3 and 4 for it.
123
+ If the conversation established that more items still need to be filed (e.g. a follow-up item, or one in another repo), do not signal yet — create each remaining item now, repeating Steps 3 to 5 for it.
114
124
 
115
125
  Finally, once the last item is created, signal that the bug-filing task is complete, passing every item id created in this session (a-prefixed, e.g. `a555 a556`):
116
126
 
@@ -28,3 +28,40 @@ Follow the workflow the system prompt lays out — ask clarifying questions firs
28
28
  The design system prompt is written for a filesystem-based project, so it talks about saving HTML files. In Claude Code the file is the intermediate, not the deliverable: **publish the finished design as an artifact** so the user gets a URL they can open and share. Do not deliver a scratchpad path.
29
29
 
30
30
  Load the `artifact-design` skill before writing the page, write the HTML to a file, then publish that file with the `Artifact` tool. When iterating, edit the same file and publish again so the URL stays stable. Keep a design on disk only as a working intermediate, or when the user asks for a file specifically.
31
+
32
+ ## Designing a new backlog item's UI change
33
+
34
+ `/draft` and `/bug` follow this section while creating an item. It is the single source of the design step for both.
35
+
36
+ ### Decide
37
+
38
+ From what the user described and answered, decide whether the item 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 section entirely and do not mention it.
39
+
40
+ ### Design and review
41
+
42
+ If it is substantial, do not ask whether to design it — follow Steps 1-4 above for the item's UI, applying them to what the user described and answered in place of `$ARGUMENTS`. Publish the design as an artifact, then raise each review round with `ask-design` instead of iterating in chat. Write a short markdown summary of the design (what it shows and the choices to weigh in on) to a scratch file and run, as a background task, doing no other work until it returns:
43
+
44
+ ```
45
+ assist ask-design --url '<artifact-url>' --title '<design title>' --body - < <summary-file>
46
+ ```
47
+
48
+ - **Approved** (exit 0) — fold every printed comment into the design, republishing to the same URL, then move on.
49
+ - **Rejected** (non-zero, printing the reason and comments) — revise the design to address each one, republish to the same artifact URL, and re-run `ask-design` for the next round. Repeat until approved.
50
+ - To revise while a round is still pending, re-run `ask-design` directly; the earlier task exits 0 as superseded — ignore its result.
51
+ - If it prints the design link and exits 0 without `Approved.` (not in an assist web session), ask the user in chat instead and iterate there — editing the same file and republishing to the same URL — until they say they are happy with it.
52
+
53
+ Keep the artifact's URL and name for the two steps below.
54
+
55
+ ### Link it from the description
56
+
57
+ When composing the item, add a `## Design` section to its description with the artifact URL, so the implementer builds against it.
58
+
59
+ ### Attach it to the created item
60
+
61
+ Once `propose` has created the item, attach the artifact so it renders as a linked design row in the Activity section:
62
+
63
+ ```
64
+ assist backlog add-activity a<id> design "<artifact-url>" --url "<artifact-url>" --title "<artifact name>" 2>&1
65
+ ```
66
+
67
+ Use the artifact URL verbatim for both the ref and `--url`, and the artifact's name for `--title`.
@@ -26,26 +26,13 @@ If the harness provides a structured question tool, ask each question with it
26
26
 
27
27
  ## Step 3: Design the UI change
28
28
 
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/skills/design/SKILL.md`) for the story's UI, applying it to what the user described and answered. Publish the design as an artifact, then raise each review round with `ask-design` instead of iterating in chat. Write a short markdown summary of the design (what it shows and the choices to weigh in on) to a scratch file and run, as a background task, doing no other work until it returns:
32
-
33
- ```
34
- assist ask-design --url '<artifact-url>' --title '<design title>' --body - < <summary-file>
35
- ```
36
-
37
- - **Approved** (exit 0) — fold every printed comment into the design, republishing to the same URL, then move on.
38
- - **Rejected** (non-zero, printing the reason and comments) — revise the design to address each one, republish to the same artifact URL, and re-run `ask-design` for the next round. Repeat until approved.
39
- - To revise while a round is still pending, re-run `ask-design` directly; the earlier task exits 0 as superseded — ignore its result.
40
- - If it prints the design link and exits 0 without `Approved.` (not in an assist web session), ask the user in chat instead and iterate there — editing the same file and republishing to the same URL — until they say they are happy with it.
41
-
42
- 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).
29
+ Read the **Designing a new backlog item's UI change** section of `/design` (`~/.claude/skills/design/SKILL.md`) and follow its Decide and Design and review steps for the story. If it decides the change is not substantial, skip this step silently. Otherwise its link step applies in Step 4 and its attach step in Step 5.
43
30
 
44
31
  ## Step 4: Compose the item
45
32
 
46
33
  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.
47
34
 
48
- 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.
35
+ If Step 3 produced a design, link it from the description as `/design` describes.
49
36
 
50
37
  **Name:** (concise title)
51
38
  **Type:** story or bug
@@ -174,13 +161,7 @@ Use the same permalink verbatim for both the ref and `--url`, and the item's nam
174
161
 
175
162
  ### Attach the design
176
163
 
177
- 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:
178
-
179
- ```
180
- assist backlog add-activity a<id> design "<artifact-url>" --url "<artifact-url>" --title "<artifact name>" 2>&1
181
- ```
182
-
183
- 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.
164
+ If Step 3 published a design artifact, attach it to the created item as `/design` describes. If Step 3 was skipped, skip this step.
184
165
 
185
166
  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.
186
167