The VTC (Value Trigger Chain) was a separate concept that extracted
specific nodes from the Trigger Map into a YAML file. This caused
agents to run trigger mapping during Phase 1 (Product Brief), forcing
users to repeat the work in Phase 2. Observed in Monday workshop.
Architectural fix:
- Phase 1 is casual business discovery, NOT trigger mapping
- Phase 2 is where the Trigger Map gets built (unchanged)
- When scenarios/content need strategic context, they reference
the Trigger Map directly — no separate VTC concept needed
Removed (19 files deleted):
- 1-project-brief/vtc-workshop/ (14 step files + workflow)
- step-04-create-vtc.md and step-11a-create-vtc.md from Phase 1
- step-03c-create-vtc.md from Phase 0 alignment
- vtc-template.yaml
Renamed:
- step-03-build-vtcs.md → step-03-build-strategic-context.md
- step-02-vtc-consistency.md → step-02-trigger-map-consistency.md
- step-01-load-vtc-context.md → step-01-load-trigger-map-context.md
- 07-create-vtc.md → 07-reference-trigger-map.md
Rewritten:
- Phase 4 scenario init: "create VTC" → lightweight "pick from Trigger Map"
- Phase 6 content: load context from Trigger Map, not from VTC
- Templates: "Trigger Map" section → "Business Context" (Phase 1 scope)
Zero VTC references remain in src/.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Suggest workflow: Component Extraction Check prompts user to extract
shared elements when starting the 2nd+ page in a scenario
- Dream workflow: Auto-extracts shared components and reports in summary
- Spec audit Level 3: Cross-Page Duplicate Detection compares sections
across all pages, flags exact/near duplicates with severity levels
- Fix Freya role name (Scenario Architect → Facilitator)
- Remove duplicate trigger-map reference in Eira guide
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Systematic cleanup of Value Trigger Chain (VTC) references in 60 files across
all phases. VTC is replaced with context-appropriate terms:
- "Trigger Map" when referencing the Phase 2 artifact
- "Strategic context" when referencing the extracted business/persona/forces data
- "Value Proposition" for customer-facing value descriptions
Remaining VTC references are only in VTC Workshop definition files (vtc-workshop/,
create-vtc steps) which will be addressed when those workflows are redesigned.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Freya menu: simpler descriptions, logical grouping (SC/UX/SP/SA/GA/DS/DD)
- Freya menu: remove AD and ST, add SC (Scenarios) and SP (Specifications)
- Fix VTC reference in freya agent and workflow-conceptualize
- Conceptualize: save findings to page spec, not separate notes file
- Conceptualize: offer Excalidraw sketching, user sketch first
- Conceptualize: require reading existing specs before drawing
- Conceptualize: no annotations on wireframes rule
- Add Excalidraw tool guide and update tools guide
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
After designing a page, the agent asks what's next: outline and design
the next page in the scenario [N], return to dashboard [R], or validate
[V]. Choosing [N] runs Phase 3's page outline dialog (purpose + exit
action) then designs the page, creating a continuous loop.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
[O] Outline now walks through pages as a conversation: for each page,
ask what the user accomplishes and what interaction moves them forward.
Interactions that leave the page create new steps; interactions that
stay on the page become storyboard items within the page spec.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
[S] → [O] Outline scenario pages. User can cycle through pages
one at a time and stop whenever they want, rather than creating
all at once.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Instead of always creating all page folders, the post-scenario menu
now offers: [N] next scenario, [S] scaffold all page folders,
[D] create first page and design, [C] generate overview. Page folder
structure uses NN.step-slug naming with Sketches/ subfolder.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Phase 4 now checks for existing Phase 3 scenarios before page design.
If no scenario exists, redirects user to Phase 3's 8-question dialog
instead of attempting a lighter inline version.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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>
- 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>
Mårten Angner