From d756b793224dfbd5e9c528368da2e304fe46b46b Mon Sep 17 00:00:00 2001 From: ak95asb Date: Wed, 25 Feb 2026 13:03:15 +0530 Subject: [PATCH] fix(quick-spec): fix slash command formatting and file path quoting in step-04 - Add `/` prefix to `quick-dev` slash command references for clarity - Quote `{finalFile}` in copy-paste commands to handle spaces in paths - Update wording from "To run" to "Load and follow" for precision - Add inline note clarifying both are BMAD slash commands/skills --- .../quick-spec/steps/step-04-review.md | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/src/bmm/workflows/bmad-quick-flow/quick-spec/steps/step-04-review.md b/src/bmm/workflows/bmad-quick-flow/quick-spec/steps/step-04-review.md index ae8ee8c3f..4088c9910 100644 --- a/src/bmm/workflows/bmad-quick-flow/quick-spec/steps/step-04-review.md +++ b/src/bmm/workflows/bmad-quick-flow/quick-spec/steps/step-04-review.md @@ -124,18 +124,20 @@ Saved to: {finalFile} 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. -To run **Adversarial Review** in a fresh context (recommended for information asymmetry): +Load and follow **Adversarial Review** in a fresh context (recommended for information asymmetry): \`\`\` -/bmad-review-adversarial-general {finalFile} +/bmad-review-adversarial-general "{finalFile}" \`\`\` -To start **development** in a fresh context: +Load and follow **development** in a fresh context: \`\`\` -quick-dev {finalFile} +/quick-dev "{finalFile}" \`\`\` +_(Both are slash commands — prefix `/` invokes a BMAD skill or workflow.)_ + This ensures the agent has clean context focused solely on its task. ``` @@ -185,7 +187,7 @@ b) **HALT and wait for user selection.** When you're ready to implement, run: ``` -quick-dev {finalFile} +/quick-dev {finalFile} ``` Ship it!"