@staff0rd/assist 0.377.0 → 0.378.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/bug.md +1 -1
- package/claude/commands/draft.md +1 -1
- package/dist/commands/sessions/web/bundle.js +103 -103
- package/dist/index.js +15 -7
- package/package.json +1 -1
package/claude/commands/bug.md
CHANGED
|
@@ -17,7 +17,7 @@ Ask short, targeted questions one at a time to fill in any gaps. You need three
|
|
|
17
17
|
2. **Expected behavior** — what should happen?
|
|
18
18
|
3. **Actual behavior** — what happens instead?
|
|
19
19
|
|
|
20
|
-
Before asking the user about existing functionality — how a feature currently works, what a command does, where something lives — investigate the codebase first and answer it yourself. Only ask the user about things the code can't tell you (their intent, what they observed, how to reproduce it).
|
|
20
|
+
Before asking the user about existing functionality — how a feature currently works, what a command does, where something lives — investigate the codebase first and answer it yourself. Do this investigation yourself — do not delegate it to a sub-agent; you need the context in your own working memory to write an accurate bug report. Only ask the user about things the code can't tell you (their intent, what they observed, how to reproduce it).
|
|
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
|
|
package/claude/commands/draft.md
CHANGED
|
@@ -9,7 +9,7 @@ You are helping the user create a well-structured backlog item with a phased imp
|
|
|
9
9
|
|
|
10
10
|
If the user provided a description via $ARGUMENTS, use that as a starting point. Otherwise, ask the user what they want to build — do NOT read any codebase files yet. Wait for their response before doing anything else.
|
|
11
11
|
|
|
12
|
-
Once you have a description (either from $ARGUMENTS or the user's reply), read relevant parts of the codebase to understand the current architecture and patterns as they relate to what's being drafted.
|
|
12
|
+
Once you have a description (either from $ARGUMENTS or the user's reply), read relevant parts of the codebase to understand the current architecture and patterns as they relate to what's being drafted. Do this investigation yourself — do not delegate it to a sub-agent. You need the context in your own working memory to ask good clarifying questions and design the phases.
|
|
13
13
|
|
|
14
14
|
## Step 2: Ask clarifying questions
|
|
15
15
|
|