fix(quick-flow): standardize menu shortcuts for intuitive UX (#1401)

* fix(quick-spec): change menu shortcuts to avoid Approve/Advanced confusion

Users were typing 'a' expecting to Approve (since it starts with A) but
triggering Advanced Elicitation instead. Changed shortcuts to:
- [C] Continue (was [Y] Approve)
- [E] Edit (was [C] Changes)

This keeps [A] for Advanced Elicitation consistent with other workflows.

Fixes user-reported UX issue with confusing menu shortcuts.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* fix(quick-dev): standardize menu shortcuts to use intuitive letters

- Change [T] to [P] for "Plan first" (P matches the label)
- Change [1][2][3] to [W][F][S] for findings resolution:
  - [W] Walk through
  - [F] Fix automatically
  - [S] Skip

Consistent with letter-based menu pattern used elsewhere.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
Alex Verkhovsky
2026-01-24 19:15:01 -08:00
committed by GitHub
parent 8bdf21f65b
commit 79959e75ac
3 changed files with 20 additions and 20 deletions

View File

@@ -88,11 +88,11 @@ Use holistic judgment, not mechanical keyword matching.
### No Escalation (simple request)
Display: "**Select:** [T] Plan first (tech-spec) [E] Execute directly"
Display: "**Select:** [P] Plan first (tech-spec) [E] Execute directly"
#### Menu Handling Logic:
- IF T: Direct user to `{quick_spec_workflow}`. **EXIT Quick Dev.**
- IF P: Direct user to `{quick_spec_workflow}`. **EXIT Quick Dev.**
- IF E: Ask for any additional guidance, then **NEXT:** Read fully and follow: `step-02-context-gathering.md`
#### EXECUTION RULES:
@@ -108,13 +108,13 @@ Present: "This looks like a focused feature with multiple components."
Display:
**[T] Create tech-spec first** (recommended)
**[P] Plan first (tech-spec)** (recommended)
**[W] Seems bigger than quick-dev** - Recommend the Full BMad Flow PRD Process
**[E] Execute directly**
#### Menu Handling Logic:
- IF T: Direct to `{quick_spec_workflow}`. **EXIT Quick Dev.**
- IF P: Direct to `{quick_spec_workflow}`. **EXIT Quick Dev.**
- IF W: Direct user to run the PRD workflow instead. **EXIT Quick Dev.**
- IF E: Ask for guidance, then **NEXT:** Read fully and follow: `step-02-context-gathering.md`
@@ -132,12 +132,12 @@ Present: "This sounds like platform/system work."
Display:
**[W] Start BMad Method** (recommended)
**[T] Create tech-spec** (lighter planning)
**[P] Plan first (tech-spec)** (lighter planning)
**[E] Execute directly** - feeling lucky
#### Menu Handling Logic:
- IF T: Direct to `{quick_spec_workflow}`. **EXIT Quick Dev.**
- IF P: Direct to `{quick_spec_workflow}`. **EXIT Quick Dev.**
- IF W: Direct user to run the PRD workflow instead. **EXIT Quick Dev.**
- IF E: Ask for guidance, then **NEXT:** Read fully and follow: `step-02-context-gathering.md`
@@ -154,7 +154,7 @@ Display:
- Mode A (tech-spec): "**NEXT:** read fully and follow: `step-03-execute.md`"
- Mode B (direct, [E] selected): "**NEXT:** Read fully and follow: `step-02-context-gathering.md`"
- Escalation ([T] or [W]): "**EXITING Quick Dev.** Follow the directed workflow."
- Escalation ([P] or [W]): "**EXITING Quick Dev.** Follow the directed workflow."
---

View File

@@ -29,15 +29,15 @@ Present: "How would you like to handle these findings?"
Display:
**[1] Walk through** - Discuss each finding individually
**[2] Auto-fix** - Automatically fix issues classified as "real"
**[3] Skip** - Acknowledge and proceed to commit
**[W] Walk through** - Discuss each finding individually
**[F] Fix automatically** - Automatically fix issues classified as "real"
**[S] Skip** - Acknowledge and proceed to commit
### Menu Handling Logic:
- IF 1: Execute OPTION 1 (Walk Through) below
- IF 2: Execute OPTION 2 (Auto-fix) below
- IF 3: Execute OPTION 3 (Skip) below
- IF W: Execute WALK THROUGH section below
- IF F: Execute FIX AUTOMATICALLY section below
- IF S: Execute SKIP section below
### EXECUTION RULES:
@@ -46,7 +46,7 @@ Display:
---
## OPTION 1: WALK THROUGH
## WALK THROUGH [W]
For each finding in order:
@@ -61,7 +61,7 @@ After all findings processed, summarize what was fixed/skipped.
---
## OPTION 2: AUTO-FIX
## FIX AUTOMATICALLY [F]
1. Filter findings to only those classified as "real"
2. Apply fixes for each real finding
@@ -78,7 +78,7 @@ Skipped (noise/uncertain): F2, F4
---
## OPTION 3: SKIP
## SKIP [S]
1. Acknowledge all findings were reviewed
2. Note that user chose to proceed without fixes

View File

@@ -43,14 +43,14 @@ wipFile: '{implementation_artifacts}/tech-spec-wip.md'
**Present review menu:**
Display: "**Select:** [Y] Approve [C] Changes [Q] Questions [A] Advanced Elicitation [P] Party Mode"
Display: "**Select:** [C] Continue [E] Edit [Q] Questions [A] Advanced Elicitation [P] Party Mode"
**HALT and wait for user selection.**
#### Menu Handling Logic:
- IF Y: Proceed to Section 3 (Finalize the Spec)
- IF C: Proceed to Section 2 (Handle Review Feedback), then return here and redisplay menu
- IF C: Proceed to Section 3 (Finalize the Spec)
- IF E: Proceed to Section 2 (Handle Review Feedback), then return here and redisplay menu
- IF Q: Answer questions, then redisplay this menu
- IF A: Read fully and follow: `{advanced_elicitation}` with current spec content, process enhanced insights, ask user "Accept improvements? (y/n)", if yes update spec then redisplay menu, if no keep original then redisplay menu
- IF P: Read fully and follow: `{party_mode_exec}` with current spec content, process collaborative insights, ask user "Accept changes? (y/n)", if yes update spec then redisplay menu, if no keep original then redisplay menu
@@ -59,7 +59,7 @@ Display: "**Select:** [Y] Approve [C] Changes [Q] Questions [A] Advanced Elicita
#### EXECUTION RULES:
- ALWAYS halt and wait for user input after presenting menu
- ONLY proceed to finalize when user selects 'Y'
- ONLY proceed to finalize when user selects 'C'
- After other menu items execution, return to this menu
### 2. Handle Review Feedback