-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
fix: add copy-paste command for adversarial review in quick-spec #1910
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -120,6 +120,12 @@ Saved to: {finalFile} | |
| [D] Done - exit workflow | ||
| [P] Party Mode - get expert feedback before dev | ||
|
|
||
| To run adversarial review in a fresh context (recommended for information asymmetry): | ||
|
|
||
| \`\`\` | ||
| /bmad-review-adversarial-general {finalFile} | ||
| \`\`\` | ||
|
|
||
|
Comment on lines
+123
to
+128
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Placement breaks narrative flow and creates UX confusion. The command block interrupts the flow between the menu display (ending line 122) and the "Once you are fully satisfied" guidance (line 131). Readers encounter:
This creates confusion: Should users select [R] from the menu, or copy-paste the command? Why is there a command outside the menu flow? The quick-dev pattern (lines 131-139) correctly places the command AFTER the explanatory text, not before. Move lines 123-128 to appear AFTER line 122 (before the horizontal rule at 129) OR integrate into the "Once you are fully satisfied" paragraph at line 131 with contextual explanation. 🤖 Prompt for AI Agents |
||
| --- | ||
|
|
||
| Once you are fully satisfied with the spec (ideally after **Adversarial Review** and maybe a few rounds of **Advanced Elicitation**), it is recommended to run implementation in a FRESH CONTEXT for best results. | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we are going to be updating all language to say Invoke skill {skill-name} since some tools for whatever dumb reason did not follow convention of / command.