After completing a scenario, the user can now choose to:
- [N] Define the next scenario
- [D] Jump to Phase 4 and start designing the first page
- [C] Generate the overview (when all scenarios done)
This lets users design one scenario before defining the rest,
creating a more natural workflow.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Restructure Phase 3 scenario creation around a natural conversation
flow instead of a template checklist:
- 8 strategic questions asked in logical order: transaction → business
goal → user & situation → driving forces → device → starting point
→ best outcome → shortest path
- Two modes: conversation (agent asks, user answers) and suggest
(agent answers from Trigger Map, user reviews)
- Broader transaction definition: includes content browsing and
research, not just purchases/bookings
- Agent creates first page specification after Q8, giving Phase 4
a concrete starting point
- Template reordered to match Q1-Q8 dialog flow
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Implement BMad-style IDE handler architecture for WDS:
- Base class (_base-ide.js) with template method pattern
- Dynamic handler discovery via IdeManager
- Priority handlers: Windsurf, Cursor, Claude Code, Cline, GitHub Copilot
- Installer integration after agent compilation step
- Saga activation now branches on starting_point config (pitch vs brief)
- Remove parenthetical hint from learning material prompt
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Removed all pre-selection (all unchecked by default)
- Removed star markers (⭐) - no preferences shown
- Sorted alphabetically for neutral presentation
- Users must actively choose their tools
- Validation still requires at least one selection
Platform-agnostic: WDS works equally well with any AI coding tool
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
- Changed from single-select list to checkbox (multiselect)
- Added full IDE list from BMad: Windsurf, Cursor, Claude Code, GitHub Copilot, Cline, VS Code, Other
- Windsurf and Cursor marked as preferred (pre-checked)
- Validation requires at least one IDE selected
- Updated config.yaml to store ides array instead of single ide
- Updated success message to display multiple IDEs (e.g., "Windsurf or Cursor")
- Ensures WDS commands work cross-platform for all selected IDEs
User request: "Look at the BMad installer, there is a multiselect box for IDEs use the full list from the BMad installer"
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
- Added IDE selection question (Windsurf, VS Code, Cursor, Other)
- Made learning material installation optional with confirm prompt
- Success message now shows selected IDE name
- Store IDE preference in config.yaml
- Installer now has 5 questions (up from 3)
User feedback: "IDE selection is crucial for the installer" and "ask if the learn section should be installed"
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
User feedback: UX design happens IN the scenarios (C), not as separate phase.
Old (incorrect):
- A-Product-Brief
- B-Trigger-Map
- C-UX-Scenarios
- D-UX-Design (redundant!)
- E-Design-System
New (correct):
- A-Product-Brief
- B-Trigger-Map
- C-UX-Scenarios (UX design is done here)
- D-Design-System
4 phases instead of 5 - cleaner and more accurate.
More conversational and explicit:
- 'Get Started with Your Product Brief' (goal-oriented)
- 'Locate the chat window in your IDE' (explicit location)
- 'type:' instead of 'paste this command:' (simpler action)
- Command in quotes to make it clear it's text to type
- Better line breaks for readability
Old message was too technical and vague.
New message:
- Clear numbered steps (1-2-3)
- Specific: 'Open this folder in Windsurf or VS Code'
- Exact command to paste (not just 'tell the AI')
- Clear outcome: 'Saga will greet you by name'
- Cleaner layout with separator
Addresses workshop feedback about confusing instructions.
Workshop feedback: 00-*.md files were confusing and ignored by users.
Changes:
- Remove createFolderGuides() and createProjectInfoFile() methods
- Folders still created but empty (only .gitkeep)
- Agents will create files dynamically during workflows
- Cleaner, less confusing user experience
- Add 3rd question: Output folder name (default: design-process)
- Users can customize to docs/, deliverables/, etc.
- Update config.yaml to use dynamic root_folder
- Update template placeholders to use config.root_folder
Balances simplification (3 questions vs 7+) with useful customization.
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
- Remove mimir-orchestrator.agent.yaml (orchestration layer removed)
- Add activation prompt to Saga for immediate greeting
- Saga now direct entry point (no orchestrator needed)
- Greets user by name and starts Product Brief workflow
Workshop finding: 50% bypassed orchestration, Mimir added complexity.
Direct activation simplifies user journey.
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
- Users can now choose between design-process/, docs/, or deliverables/
- Removes folder auto-detection logic that caused duplicate folders
- Installer creates folders at user's chosen location
- Prevents conflict with project setup workflow
Fixes issue where both design-process/ and docs/ were created.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
createFolderGuides() needs config parameter for template replacements.
This was causing "config is not defined" error during installation.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Publishes to npm on tag push (v*) or manual trigger.
Bypasses local 2FA issues by using NPM_TOKEN secret.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- New option: Full Trigger Map vs Simplified VTC vs Skip
- Synced from bmad-method-wds-expansion
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- New entry point that asks Greenfield vs Brownfield upfront
- Prevents users from going through Phase 1-3 with existing codebases
- Adds project configuration questions
- Updates routing to direct brownfield projects to Phase 8
Synced from bmad-method-wds-expansion.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Step 4 was missing a structured menu at the spec review checkpoint.
This caused agents to skip past the approval step without waiting for
explicit user confirmation.
Added:
- Review menu with [y] Approve, [c] Changes, [q] Questions, [a] Advanced Elicitation, [p] Party Mode
- Explicit HALT instruction
- Menu handling section
This aligns step 4 with the menu-driven pattern used in steps 1-3.
Fixes#1304
Also fixes pre-existing prettier issue in src/modules/cis/module.yaml.
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Mårten Angner
Alex Verkhovsky
Brian Madison
Brian