@staff0rd/assist 0.702.0 → 0.703.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.
- package/claude/commands/draft.md +3 -1
- package/dist/commands/sessions/web/bundle.js +395 -395
- package/dist/index.js +1 -1
- package/package.json +1 -1
package/claude/commands/draft.md
CHANGED
|
@@ -13,7 +13,7 @@ Once you have a description (either from $ARGUMENTS or the user's reply), read r
|
|
|
13
13
|
|
|
14
14
|
## Step 2: Ask clarifying questions
|
|
15
15
|
|
|
16
|
-
Ask 2-4 targeted questions
|
|
16
|
+
Ask 2-4 targeted questions to flesh out the idea. Focus on:
|
|
17
17
|
|
|
18
18
|
- **Scope**: What exactly should this include? What is out of scope?
|
|
19
19
|
- **Done criteria**: What does "done" look like? How will we know it works?
|
|
@@ -22,6 +22,8 @@ Ask 2-4 targeted questions conversationally to flesh out the idea. Focus on:
|
|
|
22
22
|
|
|
23
23
|
Ask one question at a time. Wait for the user's response before asking the next.
|
|
24
24
|
|
|
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
|
+
|
|
25
27
|
## Step 3: Compose the item
|
|
26
28
|
|
|
27
29
|
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 4 and tells you what to do next.
|