ldy26098
/
BMAD-METHOD
mirror of https://github.com/bmad-code-org/BMAD-METHOD.git
1
0
Fork 0
Code Packages Projects Releases Wiki Activity

Remove VTC concept entirely — use Trigger Map directly 

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>
This commit is contained in:
Mårten Angner 2026-02-25 19:15:32 +01:00
parent b2508adfbd
commit 4774ee20e9
43 changed files with 257 additions and 3433 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
src/workflows/0-alignment-signoff/data/03-synthesize-present-routing.md
View File

@ -18,8 +18,7 @@ web_bundle: true
|---|------|---------|
| 01 | [Reflect Back](01-reflect-back.md) | Reflect back what you've captured from all sections |
| 02 | [Synthesize Document](02-synthesize-document.md) | Compile into alignment document using pitch template |
| 03 | [Create VTC](03-create-vtc.md) | Optional: Create Value Trigger Chain for strategic clarity |
| 04 | [Present for Approval](04-present-for-approval.md) | Present to stakeholders, handle feedback, iterate |
| 03 | [Present for Approval](04-present-for-approval.md) | Present to stakeholders, handle feedback, iterate |
**Key principle:** The alignment phase is collaborative and iterative. Refine until everyone is on board.

4
src/workflows/0-alignment-signoff/steps-c/step-03b-synthesize-document.md
View File

@ -3,7 +3,7 @@ name: 'step-03b-synthesize-document'
description: 'Create the alignment document from all explored and confirmed sections'
# File References
nextStepFile: './step-03c-create-vtc.md'
nextStepFile: './step-03d-present-approval.md'
workflowFile: '../workflow.md'
---
@ -86,7 +86,7 @@ Help crystallize into a clear, compelling narrative using framework thinking:
### 4. Present MENU OPTIONS
Display: "**Select an Option:** [C] Continue to step-03c-create-vtc"
Display: "**Select an Option:** [C] Continue to Present for Approval"
#### Menu Handling Logic:
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}

148
src/workflows/0-alignment-signoff/steps-c/step-03c-create-vtc.md
View File

@ -1,148 +0,0 @@
---
name: 'step-03c-create-vtc'
description: 'Create a simplified Value Trigger Chain to strengthen the pitch with strategic clarity'
# File References
nextStepFile: './step-03d-present-approval.md'
workflowFile: '../workflow.md'
---
# Step 19: Create Value Trigger Chain
## STEP GOAL:
Create a simplified VTC (Value Trigger Chain) to add strategic clarity to the pitch document before presenting to stakeholders.
## MANDATORY EXECUTION RULES (READ FIRST):
### Universal Rules:
- 🛑 NEVER generate content without user input
- 📖 CRITICAL: Read the complete step file before taking any action
- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
- 📋 YOU ARE A FACILITATOR, not a content generator
- ✅ YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
### Role Reinforcement:
- ✅ You are the Alignment & Signoff facilitator, guiding users to create stakeholder alignment
- ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role
- ✅ We engage in collaborative dialogue, not command-response
- ✅ You bring alignment and stakeholder management expertise, user brings their project knowledge
- ✅ Maintain a supportive and clarifying tone throughout
### Step-Specific Rules:
- 🎯 Focus only on creating the VTC or handling decline
- 🚫 FORBIDDEN to force VTC creation - user can decline
- 💬 Approach: Offer VTC creation, leverage existing pitch context
- 📋 Don't start from zero - use strategic work already completed in pitch sections
## EXECUTION PROTOCOLS:
- 🎯 Create VTC or handle decline gracefully
- 💾 Save VTC to `docs/1-project-brief/vtc-primary.yaml`
- 📖 Load VTC Workshop Router at `../../1-project-brief/vtc-workshop/workflow.md` if user agrees
- 🚫 Do not force VTC creation
## CONTEXT BOUNDARIES:
- Available context: Complete alignment document from step-03b
- Focus: VTC creation as strategic enhancement
- Limits: Optional step - user can decline
- Dependencies: step-03b must be completed
## Sequence of Instructions (Do not deviate, skip, or optimize)
### 1. Offer VTC Creation
"Before we present this for approval, let's create a Value Trigger Chain (VTC) to add strategic clarity to your pitch.
A VTC is a simplified strategic summary that captures:
- **Business Goal** - What measurable outcome you want
- **Solution** - What you're building
- **User** - Who the primary user is
- **Driving Forces** - What motivates them (positive + negative)
- **Customer Awareness** - Where they start and where you move them
This takes about 20-30 minutes and gives stakeholders a clear, strategic view of the project. It will be added to your pitch document.
Shall we create the VTC now?"
### 2. If User Agrees
Load and execute the VTC Workshop Router:
`../../1-project-brief/vtc-workshop/workflow.md`
**Note:** At pitch stage, there's typically NO Trigger Map yet, so router will likely send you to the **Creation Workshop**.
#### Leverage Pitch Context
**Important:** You have extensive context from the pitch sections! Use it:
- **Business Goal:** From "Value We'll Create" and "Why It Matters"
- **Solution:** From "Recommended Solution"
- **User:** From "Why It Matters" (who we help)
- **Driving Forces:** Infer from "Why It Matters" and "Cost of Inaction"
- **Customer Awareness:** Infer from "The Realization" and solution approach
**Don't start from zero** - use the strategic work already completed.
#### Save VTC
VTC should be saved to:
`docs/1-project-brief/vtc-primary.yaml`
#### Add VTC to Pitch
After VTC is created, add it to the pitch document using the template placeholders.
### 3. If User Declines
**If user says:** "Let's skip the VTC for now"
**Response:**
> "No problem! You can create a VTC later using:
> `{project-root}/_bmad/wds/workflows/1-project-brief/vtc-workshop/workflow.md`
>
> However, I recommend creating it before presenting to stakeholders. It takes 30 minutes and provides powerful strategic clarity that helps secure buy-in.
>
> You can also add it after stakeholder feedback if needed."
Then proceed to next step.
### 4. Present MENU OPTIONS
Display: "**Select an Option:** [C] Continue to step-03d-present-approval"
#### Menu Handling Logic:
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
- IF M: Return to {workflowFile}
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
#### EXECUTION RULES:
- ALWAYS halt and wait for user input after presenting menu
- ONLY proceed to next step when user selects 'C'
- User can chat or ask questions - always respond and then redisplay menu options
## CRITICAL STEP COMPLETION NOTE
ONLY WHEN the VTC is created (or declined) will you then load and read fully `{nextStepFile}` to execute and begin the next step.
---
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
### ✅ SUCCESS:
- VTC is created leveraging pitch context (or gracefully declined)
- VTC is saved to correct location if created
- VTC is added to pitch document if created
- User's choice to skip is respected
### ❌ SYSTEM FAILURE:
- Forcing VTC creation when user declines
- Starting VTC from scratch instead of leveraging pitch context
- Not saving VTC to correct location
- Not offering the skip option
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

2
src/workflows/0-alignment-signoff/workflow.md
View File

@ -87,7 +87,6 @@ Explore 10 alignment document sections (flexible order):
|------|------|---------|
| 03a | Reflect Back | Synthesize understanding, confirm |
| 03b | Synthesize Document | Create alignment document |
| 03c | Create Trigger Map | Trigger Map (refs `1-project-brief/vtc-workshop/`) |
| 03d | Present for Approval | Share with stakeholders |
### Phase 4: Generate Signoff (step-04*)
@ -139,7 +138,6 @@ Explore 10 alignment document sections (flexible order):
## OUTPUT
- **Alignment Document**: `{output_folder}/A-Product-Brief/pitch.md`
- **Value Trigger Chain**: `{output_folder}/A-Product-Brief/vtc-primary.yaml`
- **Signoff Document**: `{output_folder}/A-Product-Brief/contract.md` (or `service-agreement.md` or `signoff.md`)
---

1
src/workflows/0-project-setup/templates/folder-guides/00-trigger-map.template.md
View File

@ -23,7 +23,6 @@ This folder feeds directly into Phase 4 (UX Scenarios). Every page spec should t
**Learn more:**
- WDS Course Module 06: Trigger Mapping — Connect Business Goals to User Psychology
- WDS Course Module 06, Lessons 4–8: The Five Workshops
- WDS Course Tutorial 06b: Value Trigger Chain
---

2
src/workflows/1-project-brief/data/positioning-synthesize.md
View File

@ -129,4 +129,4 @@ stepsCompleted: ['step-01-init.md', 'step-02-vision.md', 'step-03-positioning.md
positioning: '[final positioning statement]'
```
Load, read full file, and execute: `step-04-create-vtc.md` (Create Trigger Map)
Load, read full file, and execute: `step-05-business-model.md` (Business Model)

2
src/workflows/1-project-brief/steps-c/step-03-positioning.md
View File

@ -3,7 +3,7 @@ name: 'step-03-positioning'
description: 'Help user explore and articulate their positioning through natural conversation'
# File References
nextStepFile: './step-04-create-vtc.md'
nextStepFile: './step-05-business-model.md'
workflowFile: '../workflow.md'
---

120
src/workflows/1-project-brief/steps-c/step-04-create-vtc.md
View File

@ -1,120 +0,0 @@
---
name: 'step-04-create-vtc'
description: 'Create a simplified Trigger Map to crystallize strategic thinking early'
# File References
nextStepFile: './step-05-business-model.md'
workflowFile: '../workflow.md'
---
# Step 4: Create Trigger Map
## STEP GOAL:
Create a simplified Trigger Map to crystallize strategic thinking early and guide all subsequent discovery. The Trigger Map serves as a strategic benchmark — capturing Business Goal, Solution, User, Driving Forces, and Customer Awareness.
## MANDATORY EXECUTION RULES (READ FIRST):
### Universal Rules:
- 🛑 NEVER generate content without user input
- 📖 CRITICAL: Read the complete step file before taking any action
- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
- 📋 YOU ARE A FACILITATOR, not a content generator
- ✅ YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
### Role Reinforcement:
- ✅ You are Saga, a strategic facilitator helping create Trigger Map based on available context
- ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role
- ✅ We engage in collaborative dialogue, not command-response
- ✅ You bring structured strategic thinking, user brings domain expertise
- ✅ Maintain focused, strategic tone throughout
### Step-Specific Rules:
- 🎯 Focus on creating Trigger Map leveraging existing Vision and Positioning context
- 🚫 FORBIDDEN to start from zero — use the strategic work already completed
- 💬 Approach: Leverage existing context, fill gaps collaboratively
- 📋 Trigger Map is saved separately, NOT added to brief document yet (that happens at Step 12)
## EXECUTION PROTOCOLS:
- 🎯 Produce a complete Trigger Map (Business Goal, Solution, User, Driving Forces, Customer Awareness)
- 💾 Save Trigger Map to `{output_folder}/A-Product-Brief/vtc-primary.yaml`
- 📖 Route to Trigger Map Workshop at `../vtc-workshop/workflow.md` if user agrees
- 🚫 Avoid starting from zero — leverage Vision and Positioning
## CONTEXT BOUNDARIES:
- Available context: Vision from Step 2, Positioning from Step 3
- Focus: Trigger Map creation as strategic benchmark
- Limits: At this stage, estimates are fine — Trigger Map will be refined later
- Dependencies: Steps 1-3 completed
## Sequence of Instructions (Do not deviate, skip, or optimize)
### 1. Explain Trigger Map to User
Explain Trigger Map components and purpose:
- Business Goal — What measurable outcome we want
- Solution — What we are building
- User — Who the primary user is
- Driving Forces — What motivates them (positive + negative)
- Customer Awareness — Where they start and where we move them
Explain this takes 20-30 minutes and is incredibly valuable for strategic clarity. Ask: "Shall we create the Trigger Map now?"
### 2. Route to Trigger Map Workshop
**If user agrees:** Load and execute the Trigger Map Workshop Router at `../vtc-workshop/workflow.md`. Since Product Brief stage typically has NO Trigger Map yet, the router will likely send to the Creation Workshop.
### 3. Leverage Vision and Positioning Context
Use existing strategic work:
- Solution: From vision (what we are building)
- Business Goal: Infer from vision (what outcome we want)
- User: From positioning (target_customer)
- Driving Forces: Infer from positioning (need/opportunity, differentiator)
- Customer Awareness: Infer from positioning (where they are now)
### 4. Save Trigger Map
Save to `{output_folder}/A-Product-Brief/vtc-primary.yaml`. Trigger Map is saved but NOT yet added to brief document — that happens during final synthesis.
### 5. Confirm Completion
Explain that Trigger Map will serve as strategic benchmark. As discovery continues, we use this Trigger Map to ensure everything aligns. If contradictions arise, either Trigger Map needs adjustment or the discovery finding does not serve strategy.
### 6. Agent Dialog Update
**Mandatory:** Append to `dialog/decisions.md` if key decisions were made.
Record: Value/Transformation/Cost framework decisions, how value and transformation connect, key insights about user journey.
Mark Step 4 complete in `dialog/progress-tracker.md` progress tracker.
### 7. If User Declines Trigger Map
If user says "Let's skip the Trigger Map for now," explain they can create it later using `_bmad/wds/workflows/1-project-brief/vtc-workshop/workflow.md`. Recommend creating it before pitching to stakeholders or starting Phase 4. Then proceed to next step.
### 8. Present MENU OPTIONS
Display: "**Select an Option:** [C] Continue to Business Model"
#### Menu Handling Logic:
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
- IF M: Return to {workflowFile}
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
#### EXECUTION RULES:
- ALWAYS halt and wait for user input after presenting menu
- User can chat or ask questions - always respond and then redisplay menu options
## CRITICAL STEP COMPLETION NOTE
ONLY WHEN Trigger Map is created (or user declines) and completion is confirmed will you then load and read fully `{nextStepFile}`.
---
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
### ✅ SUCCESS:
- Trigger Map created with all components or user explicitly declined
- Existing Vision and Positioning context leveraged (not starting from zero)
- Trigger Map saved to correct output location
- User understands Trigger Map purpose as strategic benchmark
- Agent dialog updated
### ❌ SYSTEM FAILURE:
- Started Trigger Map from zero without using existing context
- Generated Trigger Map components without user input
- Did not save Trigger Map to correct location
- Skipped confirmation with user
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

2
src/workflows/1-project-brief/steps-c/step-11-tone-of-voice.md
View File

@ -3,7 +3,7 @@ name: 'step-11-tone-of-voice'
description: 'Establish the product communication personality and style'
# File References
nextStepFile: './step-11a-create-vtc.md'
nextStepFile: './step-12-create-product-brief.md'
workflowFile: '../workflow.md'
activityWorkflowFile: '../workflow.md'
---

181
src/workflows/1-project-brief/steps-c/step-11a-create-vtc.md
View File

@ -1,181 +0,0 @@
---
name: 'step-11a-create-vtc'
description: 'Create simplified Trigger Map for strategic summary'
# File References
nextStepFile: './step-12-create-product-brief.md'
workflowFile: '../workflow.md'
activityWorkflowFile: '../workflow.md'
---
# Step 11A: Create Trigger Map
## STEP GOAL:
Create a simplified Trigger Map to capture strategic essence for stakeholder communication.
## MANDATORY EXECUTION RULES (READ FIRST):
### Universal Rules:
- NEVER generate content without user input
- CRITICAL: Read the complete step file before taking any action
- CRITICAL: When loading next step with 'C', ensure entire file is read
- YOU ARE A FACILITATOR, not a content generator
- YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
### Role Reinforcement:
- You are a Strategic Business Analyst helping distill the Product Brief into a focused Trigger Map
- If you already have been given a name, communication_style and persona, continue to use those while playing this new role
- We engage in collaborative dialogue, not command-response
- You bring structured thinking and facilitation skills, user brings domain expertise and product vision
- Maintain collaborative and strategic tone throughout
### Step-Specific Rules:
- Focus: Trigger Map creation from Product Brief context - Business Goal, Solution, User, Driving Forces, Customer Awareness
- FORBIDDEN: Do not start from zero - use the strategic work already completed
- Approach: Leverage existing Product Brief context, route to Trigger Map Workshop
## EXECUTION PROTOCOLS:
- Primary goal: Trigger Map created and added to Product Brief
- Save/document outputs appropriately
- Avoid generating content without user input
## CONTEXT BOUNDARIES:
- Available context: Complete Product Brief content from steps 1-11
- Focus: Strategic Trigger Map summarizing the product's value chain
- Limits: This is a simplified strategic summary, not detailed scenario Trigger Maps
- Dependencies: Steps 1-11 completed
## Sequence of Instructions (Do not deviate, skip, or optimize)
### 1. Explain Trigger Map to User
> "Before we finalize the Product Brief, let's create a Trigger Map.
>
> This is a simplified strategic summary that captures:
> - **Business Goal** - What measurable outcome we want
> - **Solution** - What we're building
> - **User** - Who the primary user is
> - **Driving Forces** - What motivates them (positive + negative)
> - **Customer Awareness** - Where they start and where we move them
>
> This will take about 20-30 minutes and gives you a powerful one-page strategic foundation.
>
> Shall we create the Trigger Map now?"
### 2. Route to Trigger Map Workshop
**If user agrees:**
Load and execute the Trigger Map Workshop Router:
`../vtc-workshop/workflow.md`
**Note:** Since Product Brief stage typically has NO Trigger Map yet, the router will likely send you to the **Creation Workshop**.
### 3. Leverage Product Brief Context
**Important:** You have extensive context from the Product Brief! Use it:
- **Business Goal:** From success_criteria
- **Solution:** From vision
- **User:** From ideal_user_profile
- **Driving Forces:** Infer from positioning, need/opportunity, and user profile
- **Customer Awareness:** Infer from positioning and target customer
**Don't start from zero** - use the strategic work already completed.
### 4. Save Trigger Map
Trigger Map should be saved to:
`{output_folder}/A-Product-Brief/vtc-primary.yaml`
### 5. Add Trigger Map to Brief
After Trigger Map is created, add it to the Product Brief document BEFORE the "Next Steps" section:
```markdown
---
## Trigger Map
**Strategic Summary** - [View full Trigger Map](./vtc-primary.yaml)
- **Business Goal:** [primary goal]
- **Solution:** [solution]
- **User:** [user name/type]
- **Driving Forces:**
- *Wants to:* [positive forces]
- *Wants to avoid:* [negative forces]
- **Awareness Journey:** [start stage] → [end stage]
This Trigger Map provides quick strategic reference and will inform all design decisions.
---
```
### 6. Confirm Completion
> "Excellent! Your Product Brief now includes a Trigger Map.
>
> This Trigger Map will:
> - Help you pitch the project to stakeholders
> - Guide early design decisions
> - Serve as foundation for scenario-specific Trigger Maps in Phase 4
>
> Product Brief is now complete!"
### 7. If User Declines Trigger Map
**If user says:** "Let's skip the Trigger Map for now"
**Response:**
> "No problem! You can create a Trigger Map later using:
> `../vtc-workshop/workflow.md`
>
> However, I recommend creating it before pitching to stakeholders or starting Phase 4 (UX Design). It takes 30 minutes and provides valuable strategic clarity.
>
> Product Brief is complete. You can add a Trigger Map anytime."
Then proceed to mark workflow as complete.
### 8. Agent Dialog Update
**Mandatory:** Append to `dialog/decisions.md` if key decisions were made.
**Record:**
- Trigger Map framework decisions
- Value/Transformation/Cost mapping
- Strategic insights from framework
**Then:** Mark Step 11a complete in `dialog/progress-tracker.md` progress tracker
### N. Present MENU OPTIONS
Display: "**Select an Option:** [C] Continue to next step"
#### Menu Handling Logic:
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
- IF M: Return to {workflowFile} or {activityWorkflowFile}
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
#### EXECUTION RULES:
- ALWAYS halt and wait for user input after presenting menu
- User can chat or ask questions - always respond and then redisplay menu options
## CRITICAL STEP COMPLETION NOTE
ONLY WHEN step objectives are met and user confirms will you then load and read fully `{nextStepFile}`.
---
## SYSTEM SUCCESS/FAILURE METRICS
### SUCCESS:
- Trigger Map created or user explicitly deferred
- Product Brief context leveraged (not starting from zero)
- Trigger Map saved to correct location
- Trigger Map summary added to Product Brief document
- User confirmed
### FAILURE:
- Started Trigger Map from zero ignoring existing Product Brief context
- Skipped Trigger Map without offering
- Generated Trigger Map without user collaboration
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

2
src/workflows/1-project-brief/steps-v/step-01-brief-completeness.md
View File

@ -3,7 +3,7 @@ name: 'step-01-brief-completeness'
description: 'Verify Product Brief contains all required sections'
# File References
nextStepFile: './step-02-vtc-consistency.md'
nextStepFile: './step-02-trigger-map-consistency.md'
workflowFile: '../workflow.md'
activityWorkflowFile: '../workflow-validate.md'
---

6
src/workflows/1-project-brief/steps-v/step-02-vtc-consistency.md → src/workflows/1-project-brief/steps-v/step-02-trigger-map-consistency.md
View File

@ -1,5 +1,5 @@
---
name: 'step-02-vtc-consistency'
name: 'step-02-trigger-map-consistency'
description: 'Verify Trigger Map consistency and validity'
# File References
@ -50,8 +50,8 @@ Verify the Trigger Map(s) form a valid chain from business goals through persona
### 1. Locate Trigger Map Files
Check for:
- `{output_folder}/A-Product-Brief/vtc-primary.yaml` (Product Pitch Trigger Map)
- Any scenario-level Trigger Maps in `{output_folder}/C-UX-Scenarios/`
- `{output_folder}/B-Trigger-Map/00-trigger-map.md` (Trigger Map hub document)
- Persona documents in `{output_folder}/B-Trigger-Map/`
### 2. Trigger Map Completeness

18
src/workflows/1-project-brief/templates/pitch.template.md
View File

@ -68,22 +68,14 @@
---
## Trigger Map
**Strategic Summary** - [View full Trigger Map](./vtc-primary.yaml)
## Business Context
This project serves:
- **Business Goal:** {{vtc_business_goal}}
- **Solution:** {{vtc_solution}}
- **Primary User:** {{vtc_user}}
- **Primary Goal:** {{business_goal}}
- **Solution:** {{solution}}
- **Target Users:** {{target_users}}
**What drives them:**
- *Wants to:* {{vtc_positive_forces}}
- *Wants to avoid:* {{vtc_negative_forces}}
**Awareness Journey:** {{vtc_awareness_start}} → {{vtc_awareness_end}}
This Trigger Map ensures every design decision serves the user's psychology while achieving business goals.
*Detailed strategic analysis (personas, driving forces, prioritization) is developed in Phase 2: Trigger Mapping.*
---

16
src/workflows/1-project-brief/templates/project-brief.template.md
View File

@ -162,19 +162,13 @@
---
## Trigger Map
## Business Context
**Strategic Summary** - [View full Trigger Map](./vtc-primary.yaml)
- **Primary Goal:** {{business_goal}}
- **Solution:** {{solution}}
- **Target Users:** {{target_users}}
- **Business Goal:** {{vtc_business_goal}}
- **Solution:** {{vtc_solution}}
- **User:** {{vtc_user}}
- **Driving Forces:**
- *Wants to:* {{vtc_positive_forces}}
- *Wants to avoid:* {{vtc_negative_forces}}
- **Awareness Journey:** {{vtc_awareness_start}} → {{vtc_awareness_end}}
This Trigger Map provides quick strategic reference and will inform all design decisions.
*Full strategic analysis (business goals, personas, driving forces) is developed in [Phase 2: Trigger Mapping](../B-Trigger-Map/).*
---

210
src/workflows/1-project-brief/templates/vtc-template.yaml
View File

@ -1,210 +0,0 @@
# Value Trigger Chain Template
# See: docs/method/value-trigger-chain-guide.md
vtc:
# ==========================================
# BUSINESS GOAL
# What measurable outcome do we want?
# ==========================================
business_goal:
primary: "500 newsletter signups in Q1"
secondary: "" # Optional: Secondary goal this also supports
# ==========================================
# SOLUTION
# What are we building to achieve this goal?
# ==========================================
solution: "Landing page with trend insights lead magnet"
# ==========================================
# USER
# Who is the primary user for this solution?
# ==========================================
user:
name: "Harriet"
description: "Hairdresser, ambitious, small-town salon owner"
context: "Late evening, researching industry trends online"
current_state: "Wants to stay ahead of local competitors"
priority: "" # Optional: Priority score from Trigger Map
# ==========================================
# DRIVING FORCES
# What motivates this user?
# ==========================================
driving_forces:
# Positive: Wishes, aspirations, what they want to achieve
positive:
- "Wish to be the local beauty authority"
- "Wish to attract premium clients"
- "Wish to be seen as cutting-edge"
# Negative: Fears, frustrations, what they want to avoid
negative:
- "Fear of missing industry trends"
- "Fear of losing clients to trendier salons"
- "Avoid appearing outdated"
# ==========================================
# CUSTOMER AWARENESS
# Where user starts → where we move them
# ==========================================
customer_awareness:
start: "Problem Aware" # Knows: Need to stay current
end: "Product Aware" # Knows: Our newsletter helps
# Awareness stages:
# - Unaware: Doesn't know problem exists
# - Problem Aware: Knows problem, doesn't know solutions
# - Solution Aware: Knows solutions exist, doesn't know yours
# - Product Aware: Knows your solution exists
# - Most Aware: Has used, loved, advocates
# ==========================================
# METADATA (Optional but recommended)
# ==========================================
metadata:
# Creation information
created_date: "2025-12-31"
created_by: "Product Team"
version: "1.0"
# Source tracking
source: "creation" # "creation" (from scratch) or "trigger_map" (extracted)
trigger_map_path: "" # If extracted from Trigger Map, path to source
# Priorities (if from Trigger Map)
business_goal_priority: "" # e.g., "1" or "High"
user_priority: "" # e.g., "1" or "High"
# Usage context
purpose: "product_pitch" # "product_pitch", "scenario", "prototype", etc.
phase: "Phase 1" # WDS phase where this VTC is used
# Related files
related_documents:
- "" # Path to Product Brief, Scenario, etc.
# ==========================================
# NOTES & RATIONALE
# ==========================================
notes: |
Creation context:
- Why this VTC was created
- Key decisions made during workshop
- Important insights captured
Selection rationale (if from Trigger Map):
- Why these specific driving forces were chosen
- Why this user/goal combination
- Any refinements made from original map
Usage guidance:
- How this VTC should inform design
- What questions it should answer
- Where it applies
ALPHA FEEDBACK (please document):
- Actual workshop duration: [X minutes]
- Steps that were unclear: [which steps?]
- What was missing: [gaps?]
- What worked well: [successes?]
- Suggestions: [improvements?]
# ==========================================
# REFINEMENTS (Optional)
# Track changes from Trigger Map if applicable
# ==========================================
refinements:
- type: "" # "added", "modified", "clarified"
element: "" # What was changed
original: "" # Original from Trigger Map
updated: "" # Updated version in this VTC
reason: "" # Why the change was made
# ==========================================
# VALIDATION CHECKLIST
# ==========================================
validation:
coherence: false # Does this tell a coherent story?
actionable: false # Can designers make decisions from this?
specific: false # Are driving forces specific enough?
realistic: false # Does awareness progression make sense?
measurable: false # Is business goal measurable?
focused: false # Is this focused (not trying to serve everyone)?
# ==========================================
# EXAMPLE APPLICATIONS
# How this VTC informs design decisions
# ==========================================
applications:
# Examples of how this VTC guides design
# Remove this section in actual VTC files
content_examples:
- element: "Hero headline"
vtc_reasoning: "Addresses 'fear of missing trends' directly"
result: "'Never Miss a Trend: Weekly Insights for Ambitious Stylists'"
- element: "CTA button"
vtc_reasoning: "Aspirational language matching 'wish to be authority'"
result: "'Join the Authority Circle' (not just 'Subscribe')"
design_examples:
- element: "Visual style"
vtc_reasoning: "User wants to be seen as cutting-edge"
result: "Modern, premium aesthetic (not traditional salon look)"
- element: "Social proof"
vtc_reasoning: "Reduces 'fear of appearing outdated'"
result: "Testimonials from successful salon owners"
# ==========================================
# USAGE INSTRUCTIONS
# ==========================================
# HOW TO USE THIS TEMPLATE:
#
# 1. Copy this file to your project location:
# - Product Pitch: docs/A-Product-Brief/vtc-primary.yaml
# - Scenario: docs/C-UX-Scenarios/[scenario-name]/vtc.yaml
#
# 2. Fill in all sections with your VTC data
#
# 3. Remove example applications section (it's just for reference)
#
# 4. Complete validation checklist - all should be true
#
# 5. Use this VTC to inform ALL design decisions for this scope:
# - Content creation (what to say, how to say it)
# - Interaction design (what actions to enable)
# - Visual design (what aesthetic matches user psychology)
# - Microcopy (what tone builds confidence)
#
# 6. When making design decisions, ask:
# "Does this serve the business goal by triggering these driving forces
# while moving the user forward in customer awareness?"
#
# If yes → Good design decision
# If no → Reconsider
# ==========================================
# MAINTENANCE
# ==========================================
# WHEN TO UPDATE VTC:
# - Business goal changes
# - Learn new insights about user
# - Discover additional driving forces
# - Awareness progression needs adjustment
# - Solution scope changes
#
# VERSION CONTROL:
# - Keep old versions (vtc-v1.yaml, vtc-v2.yaml)
# - Document what changed and why
# - Update related documents (scenarios, pitch, etc.)
#
# CONSISTENCY:
# - If extracted from Trigger Map, periodically check alignment
# - If Trigger Map updates significantly, review VTC
# - Multiple VTCs from same map should be consistent in priorities

137
src/workflows/1-project-brief/vtc-workshop/steps-c/step-01a-define-business-goal.md
View File

@ -1,137 +0,0 @@
---
name: 'step-01a-define-business-goal'
description: 'Define a clear, measurable business goal for the VTC'
# File References
nextStepFile: './step-02a-identify-solution.md'
workflowFile: '../../workflow.md'
activityWorkflowFile: '../workflow.md'
---
# Step 1: Define Business Goal
## STEP GOAL:
Establish what measurable outcome we want to achieve - one clear, measurable business goal that this solution serves.
## MANDATORY EXECUTION RULES (READ FIRST):
### Universal Rules:
- NEVER generate content without user input
- CRITICAL: Read the complete step file before taking any action
- CRITICAL: When loading next step with 'C', ensure entire file is read
- YOU ARE A FACILITATOR, not a content generator
- YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
### Role Reinforcement:
- You are a Strategic Business Analyst facilitating VTC creation from scratch
- If you already have been given a name, communication_style and persona, continue to use those while playing this new role
- We engage in collaborative dialogue, not command-response
- You bring structured thinking and facilitation skills, user brings domain expertise and product vision
- Maintain collaborative and strategic tone throughout
### Step-Specific Rules:
- Focus: One clear, measurable business goal
- FORBIDDEN: Do not accept vague or unmeasurable goals without refinement
- Approach: Ask, probe for specificity, validate measurability, confirm
## EXECUTION PROTOCOLS:
- Primary goal: Business goal captured and validated
- Save/document outputs appropriately
- Avoid generating content without user input
## CONTEXT BOUNDARIES:
- Available context: Project brief, user's business context
- Focus: Business goal definition
- Limits: One primary goal per VTC
- Dependencies: VTC workshop routing completed
## Sequence of Instructions (Do not deviate, skip, or optimize)
### 1. Ask for Business Goal
> "What does success look like for the business? What measurable outcome do we want?"
**Follow-up if vague:**
- "Can we measure this?"
- "When would we know we've achieved it?"
- "What's the specific number or metric?"
### 2. Apply Guidelines
**Good goals are:**
- Specific and measurable
- Time-bound (if relevant)
- Achievable
- One primary goal (can mention secondary)
**Examples of GOOD goals:**
- "500 newsletter signups in Q1"
- "30% increase in premium conversions"
- "Reduce support tickets by 40%"
- "80% user activation rate"
**Examples of BAD goals:**
- "More engagement" (not measurable)
- "Better user experience" (vague)
- "Increase everything" (not focused)
### 3. Capture Format
```yaml
business_goal: "[Specific, measurable outcome with timeframe if relevant]"
```
### 4. Validation Checklist
Before proceeding, confirm:
- [ ] Goal is measurable (has number/metric)
- [ ] Goal is specific (not vague)
- [ ] Goal is achievable (realistic)
- [ ] Goal is focused (one primary goal)
- [ ] User confirms this is the right goal
**If any checkbox is unchecked:** Refine the goal before proceeding.
### 5. Handle Common Issues
**Issue:** User provides multiple goals
> "Let's pick ONE primary goal for this VTC. We can create additional VTCs for other goals. Which goal does THIS solution primarily serve?"
**Issue:** Goal is too vague ("better experience")
> "How would we measure 'better'? What specific outcome would show we've succeeded?"
**Issue:** Goal is aspirational but not measurable ("be the leader")
> "What metric would show we're the leader? Market share? Revenue? User count?"
### N. Present MENU OPTIONS
Display: "**Select an Option:** [C] Continue to next step"
#### Menu Handling Logic:
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
- IF M: Return to {workflowFile} or {activityWorkflowFile}
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
#### EXECUTION RULES:
- ALWAYS halt and wait for user input after presenting menu
- User can chat or ask questions - always respond and then redisplay menu options
## CRITICAL STEP COMPLETION NOTE
ONLY WHEN step objectives are met and user confirms will you then load and read fully `{nextStepFile}`.
---
## SYSTEM SUCCESS/FAILURE METRICS
### SUCCESS:
- Clear, measurable business goal captured
- Goal validated against all checklist items
- User confirmed the goal
- Foundation established for VTC
### FAILURE:
- Accepted vague or unmeasurable goal
- Skipped validation checklist
- Generated goal without user input
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

127
src/workflows/1-project-brief/vtc-workshop/steps-c/step-01b-load-trigger-map.md
View File

@ -1,127 +0,0 @@
---
name: 'step-01b-load-trigger-map'
description: 'Load and verify existing Trigger Map for VTC extraction'
# File References
nextStepFile: './step-02b-select-business-goal.md'
workflowFile: '../../workflow.md'
activityWorkflowFile: '../workflow.md'
---
# Step 1: Load Trigger Map
## STEP GOAL:
Access existing Trigger Map and verify it's ready for VTC extraction.
## MANDATORY EXECUTION RULES (READ FIRST):
### Universal Rules:
- NEVER generate content without user input
- CRITICAL: Read the complete step file before taking any action
- CRITICAL: When loading next step with 'C', ensure entire file is read
- YOU ARE A FACILITATOR, not a content generator
- YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
### Role Reinforcement:
- You are a Strategic Business Analyst facilitating VTC selection from an existing Trigger Map
- If you already have been given a name, communication_style and persona, continue to use those while playing this new role
- We engage in collaborative dialogue, not command-response
- You bring structured thinking and facilitation skills, user brings domain expertise and product vision
- Maintain collaborative and strategic tone throughout
### Step-Specific Rules:
- Focus: Load Trigger Map, verify it contains necessary elements
- FORBIDDEN: Do not proceed without verifying the map has business goals, users, and driving forces
- Approach: Ask for path, load, verify contents, handle incomplete maps
## EXECUTION PROTOCOLS:
- Primary goal: Trigger Map loaded and verified
- Save/document outputs appropriately
- Avoid generating content without user input
## CONTEXT BOUNDARIES:
- Available context: Project config, Trigger Map location
- Focus: Map loading and verification
- Limits: Verification only, not modification
- Dependencies: VTC workshop routing completed (Selection path chosen)
## Sequence of Instructions (Do not deviate, skip, or optimize)
### 1. Ask for Trigger Map Location
> "What's the path to your Trigger Map document?"
**Expected locations:**
- `{output_folder}/B-Trigger-Map/trigger-map.md`
- `{output_folder}/B-Trigger-Map/trigger-map.yaml`
- `{output_folder}/B-Trigger-Map/00-trigger-map.md`
### 2. Load and Verify
**Check Trigger Map contains:**
- [ ] Business goals (with priorities if available)
- [ ] Target groups/users (with descriptions)
- [ ] Driving forces per user (positive and negative)
- [ ] Priorities/scores (optional but helpful)
**Confirm availability:**
```
Found Trigger Map with:
- [X] business goals
- [X] target groups/users
- [Y] total driving forces
- Priorities: [Yes/No]
Ready to extract VTC!
```
### 3. Handle Incomplete Map
**Missing elements?**
**Option A** - Pause and complete map:
> "Your Trigger Map seems incomplete. Should we finish mapping first, or work with what we have?"
**Option B** - Switch to Creation Workshop:
> "Since the Trigger Map isn't complete, would you prefer to create a VTC from scratch instead?"
### 4. Capture Map Reference
```yaml
metadata:
source: "trigger_map"
trigger_map_path: "[path to map file]"
trigger_map_date: "[last modified date]"
```
### N. Present MENU OPTIONS
Display: "**Select an Option:** [C] Continue to next step"
#### Menu Handling Logic:
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
- IF M: Return to {workflowFile} or {activityWorkflowFile}
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
#### EXECUTION RULES:
- ALWAYS halt and wait for user input after presenting menu
- User can chat or ask questions - always respond and then redisplay menu options
## CRITICAL STEP COMPLETION NOTE
ONLY WHEN step objectives are met and user confirms will you then load and read fully `{nextStepFile}`.
---
## SYSTEM SUCCESS/FAILURE METRICS
### SUCCESS:
- Trigger Map located and loaded
- Contents verified (goals, users, forces present)
- Map reference metadata captured
- Ready for VTC extraction
### FAILURE:
- Proceeded without verifying map contents
- Did not handle incomplete map scenario
- Skipped verification checklist
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

133
src/workflows/1-project-brief/vtc-workshop/steps-c/step-02a-identify-solution.md
View File

@ -1,133 +0,0 @@
---
name: 'step-02a-identify-solution'
description: 'Define what specific solution is being built to achieve the business goal'
# File References
nextStepFile: './step-03a-describe-user.md'
workflowFile: '../../workflow.md'
activityWorkflowFile: '../workflow.md'
---
# Step 2: Identify Solution
## STEP GOAL:
Define what we're building to achieve the business goal - the specific thing itself, not the features.
## MANDATORY EXECUTION RULES (READ FIRST):
### Universal Rules:
- NEVER generate content without user input
- CRITICAL: Read the complete step file before taking any action
- CRITICAL: When loading next step with 'C', ensure entire file is read
- YOU ARE A FACILITATOR, not a content generator
- YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
### Role Reinforcement:
- You are a Strategic Business Analyst facilitating VTC creation from scratch
- If you already have been given a name, communication_style and persona, continue to use those while playing this new role
- We engage in collaborative dialogue, not command-response
- You bring structured thinking and facilitation skills, user brings domain expertise and product vision
- Maintain collaborative and strategic tone throughout
### Step-Specific Rules:
- Focus: Name the specific thing being built, not the features
- FORBIDDEN: Do not accept vague descriptions like "a great experience"
- Approach: Ask, clarify type, test connection to business goal, confirm
## EXECUTION PROTOCOLS:
- Primary goal: Solution identified and validated
- Save/document outputs appropriately
- Avoid generating content without user input
## CONTEXT BOUNDARIES:
- Available context: Business goal from step 1
- Focus: Solution definition
- Limits: The thing itself, not feature lists
- Dependencies: Step 01a completed
## Sequence of Instructions (Do not deviate, skip, or optimize)
### 1. Ask for Solution
> "What are you building to achieve [business goal]?"
**Follow-up for clarity:**
- "What type of thing is this? (page, flow, feature, system)"
- "Where will users encounter this?"
### 2. Apply Guidelines
**Be specific about WHAT this is:**
- Not a feature list
- The thing itself
- Bridge between business and user
**Good Examples:**
- "Landing page with lead magnet offer"
- "Onboarding flow for new users"
- "Premium upgrade prompt in app"
- "Self-service help center"
- "Checkout flow redesign"
**Bad Examples:**
- "A great experience" (too vague)
- "Lots of features to help users" (not specific)
- "Mobile app" (too broad - which part?)
### 3. Capture Format
```yaml
solution: "[The specific thing being built]"
```
### 4. Validation Checklist
Before proceeding, confirm:
- [ ] Solution is specific (not vague)
- [ ] Solution directly serves the business goal
- [ ] Solution is something users will interact with
- [ ] Solution is focused (not too broad)
- [ ] User confirms this is what they're building
### 5. Test the Connection
**Ask:** "How does [solution] achieve [business goal]?"
**Should have clear answer:**
- "Landing page gets newsletter signups"
- "Onboarding flow activates users"
**If unclear:** Solution might be wrong or too vague.
### N. Present MENU OPTIONS
Display: "**Select an Option:** [C] Continue to next step"
#### Menu Handling Logic:
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
- IF M: Return to {workflowFile} or {activityWorkflowFile}
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
#### EXECUTION RULES:
- ALWAYS halt and wait for user input after presenting menu
- User can chat or ask questions - always respond and then redisplay menu options
## CRITICAL STEP COMPLETION NOTE
ONLY WHEN step objectives are met and user confirms will you then load and read fully `{nextStepFile}`.
---
## SYSTEM SUCCESS/FAILURE METRICS
### SUCCESS:
- Specific solution identified
- Connection to business goal validated
- User confirmed the solution
- Solution is focused and user-facing
### FAILURE:
- Accepted vague solution description
- Skipped connection test to business goal
- Generated solution without user input
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

138
src/workflows/1-project-brief/vtc-workshop/steps-c/step-02b-select-business-goal.md
View File

@ -1,138 +0,0 @@
---
name: 'step-02b-select-business-goal'
description: 'Choose which business goal from Trigger Map this VTC serves'
# File References
nextStepFile: './step-03b-select-user.md'
workflowFile: '../../workflow.md'
activityWorkflowFile: '../workflow.md'
---
# Step 2: Select Business Goal
## STEP GOAL:
Choose which business goal from the Trigger Map this VTC serves.
## MANDATORY EXECUTION RULES (READ FIRST):
### Universal Rules:
- NEVER generate content without user input
- CRITICAL: Read the complete step file before taking any action
- CRITICAL: When loading next step with 'C', ensure entire file is read
- YOU ARE A FACILITATOR, not a content generator
- YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
### Role Reinforcement:
- You are a Strategic Business Analyst facilitating VTC selection from an existing Trigger Map
- If you already have been given a name, communication_style and persona, continue to use those while playing this new role
- We engage in collaborative dialogue, not command-response
- You bring structured thinking and facilitation skills, user brings domain expertise and product vision
- Maintain collaborative and strategic tone throughout
### Step-Specific Rules:
- Focus: Present available goals, guide selection, handle goals not in map
- FORBIDDEN: Do not select a goal without user confirmation
- Approach: Present goals from map, user selects, handle edge cases, capture
## EXECUTION PROTOCOLS:
- Primary goal: Business goal selected from Trigger Map
- Save/document outputs appropriately
- Avoid generating content without user input
## CONTEXT BOUNDARIES:
- Available context: Loaded Trigger Map from step 1
- Focus: Business goal selection
- Limits: One primary goal per VTC
- Dependencies: Step 01b completed
## Sequence of Instructions (Do not deviate, skip, or optimize)
### 1. Present Available Goals
Show user all business goals from Trigger Map:
> "Your Trigger Map has these business goals:
>
> 1. [Goal 1] - Priority: [score/rank]
> 2. [Goal 2] - Priority: [score/rank]
> 3. [Goal 3] - Priority: [score/rank]
>
> Which goal does this [solution/scenario] primarily serve?"
### 2. User Selects
**One primary goal** - This VTC will focus here
**Can note secondary:**
> "Does this also support another goal?"
If yes, capture but keep one primary.
### 3. Handle Goal Not in Map
**User:** "Actually, none of these goals fit. This is about [different goal]."
**Options:**
**A) Add to Trigger Map now:**
1. Pause VTC workshop
2. Add new goal to Trigger Map
3. Resume with new goal available
**B) Add to VTC and note for map update:**
1. Use new goal in this VTC
2. Note: "Add to Trigger Map: [new goal]"
3. Update map in separate session
**C) Refine existing goal:**
1. Adjust wording for clarity
2. Use refined version in VTC
3. Consider updating map
**Recommendation:** If this is a significant gap, pause and update the Trigger Map. It will benefit all future VTCs.
### 4. Capture Format
```yaml
business_goal:
primary: "[Selected goal from map]"
priority: "[Priority from map]"
secondary: "[Optional secondary goal]"
```
### 5. Validation
- [ ] Goal selected makes sense for this solution/scenario?
- [ ] User confirms this is the right focus?
### N. Present MENU OPTIONS
Display: "**Select an Option:** [C] Continue to next step"
#### Menu Handling Logic:
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
- IF M: Return to {workflowFile} or {activityWorkflowFile}
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
#### EXECUTION RULES:
- ALWAYS halt and wait for user input after presenting menu
- User can chat or ask questions - always respond and then redisplay menu options
## CRITICAL STEP COMPLETION NOTE
ONLY WHEN step objectives are met and user confirms will you then load and read fully `{nextStepFile}`.
---
## SYSTEM SUCCESS/FAILURE METRICS
### SUCCESS:
- Available goals presented from Trigger Map
- User selected primary goal
- Goal not in map handled appropriately (if applicable)
- Selection captured with priority
### FAILURE:
- Selected goal without user confirmation
- Did not present available options
- Skipped handling goal-not-in-map scenario
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

147
src/workflows/1-project-brief/vtc-workshop/steps-c/step-03a-describe-user.md
View File

@ -1,147 +0,0 @@
---
name: 'step-03a-describe-user'
description: 'Identify and describe the primary user with psychological depth'
# File References
nextStepFile: './step-04a-positive-driving-forces.md'
workflowFile: '../../workflow.md'
activityWorkflowFile: '../workflow.md'
---
# Step 3: Describe User
## STEP GOAL:
Create a rich description of ONE primary user who will use this solution - going beyond demographics to psychology.
## MANDATORY EXECUTION RULES (READ FIRST):
### Universal Rules:
- NEVER generate content without user input
- CRITICAL: Read the complete step file before taking any action
- CRITICAL: When loading next step with 'C', ensure entire file is read
- YOU ARE A FACILITATOR, not a content generator
- YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
### Role Reinforcement:
- You are a Strategic Business Analyst facilitating VTC creation from scratch
- If you already have been given a name, communication_style and persona, continue to use those while playing this new role
- We engage in collaborative dialogue, not command-response
- You bring structured thinking and facilitation skills, user brings domain expertise and product vision
- Maintain collaborative and strategic tone throughout
### Step-Specific Rules:
- Focus: ONE primary user with psychological depth, not just demographics
- FORBIDDEN: Do not accept demographics-only descriptions without probing deeper
- Approach: Ask, probe for psychology, capture rich description, validate
## EXECUTION PROTOCOLS:
- Primary goal: Rich user description captured
- Save/document outputs appropriately
- Avoid generating content without user input
## CONTEXT BOUNDARIES:
- Available context: Business goal and solution from steps 1-2
- Focus: User description with psychological depth
- Limits: One primary user per VTC
- Dependencies: Step 02a completed
## Sequence of Instructions (Do not deviate, skip, or optimize)
### 1. Ask for User Description
> "Who is the primary user for this solution? Tell me about them."
**Follow-up questions:**
- "What's their role or context?"
- "What are their key traits or characteristics?"
- "When/where do they encounter this solution?"
- "What are they trying to accomplish?"
### 2. Apply Guidelines
**Go beyond demographics to psychology:**
- Not just "female, 35, urban"
- Include mindset, goals, context
- Make them feel like a real person
**Focus on ONE primary user:**
- Can add others later with separate VTCs
- Multiple users = multiple VTCs
### 3. Use Template
```
[Name] ([role/context], [key traits])
Context: [when/where they encounter solution]
Current state: [what they're trying to accomplish]
```
**Example:**
```
Harriet (hairdresser, ambitious, small-town salon owner)
Context: Late evening, researching industry trends online
Current state: Wants to stay ahead of local competitors
```
### 4. Capture Format
```yaml
user:
name: "[Name or type]"
description: "[Role, traits, context]"
context: "[When/where they encounter solution]"
current_state: "[What they're trying to accomplish]"
```
### 5. Validation Checklist
Before proceeding, confirm:
- [ ] Can you picture this person?
- [ ] Clear why they'd care about this solution?
- [ ] Understand what they're trying to achieve?
- [ ] Description feels real (not generic)?
- [ ] User confirms this matches their target?
### 6. Handle Common Issues
**Issue:** User gives demographics only ("women 25-45")
> "Let's go deeper. Pick ONE person from that group. What's their name? What are they trying to achieve? What's their mindset?"
**Issue:** User wants multiple people
> "For THIS VTC, let's focus on one primary user. We can create additional VTCs for other users. Who matters most for this solution?"
**Issue:** Too generic ("busy professional")
> "Can you be more specific? What kind of professional? What makes them busy? What are they trying to accomplish?"
### N. Present MENU OPTIONS
Display: "**Select an Option:** [C] Continue to next step"
#### Menu Handling Logic:
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
- IF M: Return to {workflowFile} or {activityWorkflowFile}
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
#### EXECUTION RULES:
- ALWAYS halt and wait for user input after presenting menu
- User can chat or ask questions - always respond and then redisplay menu options
## CRITICAL STEP COMPLETION NOTE
ONLY WHEN step objectives are met and user confirms will you then load and read fully `{nextStepFile}`.
---
## SYSTEM SUCCESS/FAILURE METRICS
### SUCCESS:
- Rich user description captured with psychological depth
- User feels like a real person, not a demographic
- Validation checklist passed
- User confirmed the description
### FAILURE:
- Accepted demographics-only description
- Skipped psychological depth probing
- Generated user description without user input
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

142
src/workflows/1-project-brief/vtc-workshop/steps-c/step-03b-select-user.md
View File

@ -1,142 +0,0 @@
---
name: 'step-03b-select-user'
description: 'Choose which user/target group from Trigger Map this VTC focuses on'
# File References
nextStepFile: './step-04b-select-driving-forces.md'
workflowFile: '../../workflow.md'
activityWorkflowFile: '../workflow.md'
---
# Step 3: Select User
## STEP GOAL:
Choose which user/target group from the Trigger Map this VTC focuses on.
## MANDATORY EXECUTION RULES (READ FIRST):
### Universal Rules:
- NEVER generate content without user input
- CRITICAL: Read the complete step file before taking any action
- CRITICAL: When loading next step with 'C', ensure entire file is read
- YOU ARE A FACILITATOR, not a content generator
- YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
### Role Reinforcement:
- You are a Strategic Business Analyst facilitating VTC selection from an existing Trigger Map
- If you already have been given a name, communication_style and persona, continue to use those while playing this new role
- We engage in collaborative dialogue, not command-response
- You bring structured thinking and facilitation skills, user brings domain expertise and product vision
- Maintain collaborative and strategic tone throughout
### Step-Specific Rules:
- Focus: Present users connected to selected goal, guide selection, handle users not in map
- FORBIDDEN: Do not select a user without user confirmation
- Approach: Present users from map, user selects one primary, handle edge cases, capture
## EXECUTION PROTOCOLS:
- Primary goal: User/target group selected from Trigger Map
- Save/document outputs appropriately
- Avoid generating content without user input
## CONTEXT BOUNDARIES:
- Available context: Trigger Map and selected business goal from steps 1-2
- Focus: User selection
- Limits: One primary user per VTC
- Dependencies: Step 02b completed
## Sequence of Instructions (Do not deviate, skip, or optimize)
### 1. Present Available Users
Show users connected to selected business goal:
> "For [selected goal], your Trigger Map has these target groups:
>
> 1. [User 1 - brief description]
> Priority: [score]
> Key driving forces: [top 2-3]
>
> 2. [User 2 - brief description]
> Priority: [score]
> Key driving forces: [top 2-3]
>
> Which user is primary for this [solution/scenario]?"
### 2. User Selects
**One primary user** for this VTC
**If multiple users important:**
> "We can create additional VTCs for other users. For THIS VTC, let's focus on one."
### 3. Handle User Not in Map
**User:** "None of these users match. My scenario is for [different user type]."
**Options:**
**A) Add to Trigger Map now:**
1. Pause VTC workshop
2. Add new user/target group to Trigger Map
3. Map their driving forces
4. Resume with new user available
**B) Switch to Creation Workshop:**
1. If this is a one-off scenario
2. Create VTC from scratch for this user
3. Consider adding to Trigger Map later
**C) Adapt existing user:**
1. Pick closest match
2. Note variations in VTC
3. Consider if map needs new segment
**Recommendation:** If this represents a significant new user segment, add to Trigger Map. Future scenarios will benefit.
### 4. Capture Format
```yaml
user:
name: "[Selected user name from map]"
description: "[From Trigger Map]"
context: "[From Trigger Map]"
priority: "[Priority score from map]"
```
### 5. Validation
- [ ] User selection makes sense for this solution/scenario?
- [ ] User confirms this is primary target?
### N. Present MENU OPTIONS
Display: "**Select an Option:** [C] Continue to next step"
#### Menu Handling Logic:
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
- IF M: Return to {workflowFile} or {activityWorkflowFile}
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
#### EXECUTION RULES:
- ALWAYS halt and wait for user input after presenting menu
- User can chat or ask questions - always respond and then redisplay menu options
## CRITICAL STEP COMPLETION NOTE
ONLY WHEN step objectives are met and user confirms will you then load and read fully `{nextStepFile}`.
---
## SYSTEM SUCCESS/FAILURE METRICS
### SUCCESS:
- Available users presented from Trigger Map with priorities
- User selected primary target
- User not in map handled appropriately (if applicable)
- Selection captured with priority
### FAILURE:
- Selected user without confirmation
- Did not present available options with context
- Skipped handling user-not-in-map scenario
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

163
src/workflows/1-project-brief/vtc-workshop/steps-c/step-04a-positive-driving-forces.md
View File

@ -1,163 +0,0 @@
---
name: 'step-04a-positive-driving-forces'
description: 'Discover what the user WANTS to achieve - aspirations and wishes'
# File References
nextStepFile: './step-05a-negative-driving-forces.md'
workflowFile: '../../workflow.md'
activityWorkflowFile: '../workflow.md'
---
# Step 4: Identify Positive Driving Forces
## STEP GOAL:
Discover what the user WANTS to achieve - their aspirations, wishes, and what makes them want to engage with the solution.
## MANDATORY EXECUTION RULES (READ FIRST):
### Universal Rules:
- NEVER generate content without user input
- CRITICAL: Read the complete step file before taking any action
- CRITICAL: When loading next step with 'C', ensure entire file is read
- YOU ARE A FACILITATOR, not a content generator
- YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
### Role Reinforcement:
- You are a Strategic Business Analyst facilitating VTC creation from scratch
- If you already have been given a name, communication_style and persona, continue to use those while playing this new role
- We engage in collaborative dialogue, not command-response
- You bring structured thinking and facilitation skills, user brings domain expertise and product vision
- Maintain collaborative and strategic tone throughout
### Step-Specific Rules:
- Focus: Aspirations, not just functional needs - emotionally resonant wishes
- FORBIDDEN: Do not accept only functional needs without probing for emotional aspirations
- Approach: Ask, probe for emotions, capture 2-3 strong wishes, validate
## EXECUTION PROTOCOLS:
- Primary goal: 2-3 positive driving forces captured
- Save/document outputs appropriately
- Avoid generating content without user input
## CONTEXT BOUNDARIES:
- Available context: Business goal, solution, user description from steps 1-3
- Focus: Positive driving forces (wishes, aspirations)
- Limits: 2-3 forces, quality over quantity
- Dependencies: Step 03a completed
## Sequence of Instructions (Do not deviate, skip, or optimize)
### 1. Ask for Positive Forces
> "What does [user name] WANT to achieve? What would make them feel successful?"
**Probing questions:**
- "What would 'winning' look like for them?"
- "What outcome would they be proud of?"
- "What would they brag about to colleagues/friends?"
- "What capability would transform their work/life?"
### 2. Apply Guidelines
**Think aspirations, not just functional needs:**
- Not: "Upload files"
- Yes: "Wish to feel organized and in control"
**What would they feel:**
- Proud of?
- Excited about?
- Validated by?
- Transformed by?
**Aim for 2-3 strong wishes:**
- Quality over quantity
- Specific enough to inform design
- Emotionally resonant
### 3. Reference Examples
**Hairdresser (Harriet):**
- "Wish to be the local beauty authority"
- "Wish to attract premium clients"
- "Wish to be seen as cutting-edge"
**Developer (reviewing code):**
- "Wish to be helpful to teammates"
- "Wish to catch critical bugs"
- "Wish to be recognized for thorough reviews"
**Small business owner:**
- "Wish to understand finances clearly"
- "Wish to make confident decisions"
- "Wish to prove business is growing"
### 4. Capture Format
```yaml
driving_forces:
positive:
- "Wish to [aspiration]"
- "Wish to [aspiration]"
- "Wish to [aspiration]"
```
### 5. Validation Checklist
Before proceeding, confirm:
- [ ] Forces feel true for this user?
- [ ] Specific enough to inform design?
- [ ] Emotionally resonant (not just functional)?
- [ ] 2-3 forces captured (not too many)?
- [ ] User agrees these motivate their target?
### 6. Handle Common Issues
**Issue:** Forces too generic ("want to save time")
> "Save time doing WHAT specifically? WHY does saving that time matter to them? What would they do with that time?"
**Issue:** Too many wishes listed (7+)
> "Which 2-3 matter MOST? If we could only address three, which would transform their experience?"
**Issue:** Only functional needs ("need to upload files")
> "Why do they need that? What would having that enable them to achieve? What would they feel?"
### 7. Design Hint
These positive forces should inform:
- Success messaging
- Aspirational content
- Celebration moments
- Value proposition
### N. Present MENU OPTIONS
Display: "**Select an Option:** [C] Continue to next step"
#### Menu Handling Logic:
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
- IF M: Return to {workflowFile} or {activityWorkflowFile}
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
#### EXECUTION RULES:
- ALWAYS halt and wait for user input after presenting menu
- User can chat or ask questions - always respond and then redisplay menu options
## CRITICAL STEP COMPLETION NOTE
ONLY WHEN step objectives are met and user confirms will you then load and read fully `{nextStepFile}`.
---
## SYSTEM SUCCESS/FAILURE METRICS
### SUCCESS:
- 2-3 emotionally resonant positive forces captured
- Forces are specific enough to inform design
- Validation checklist passed
- User confirmed the aspirations
### FAILURE:
- Accepted only functional needs without emotional depth
- Captured too many or too few forces
- Generated forces without user input
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

154
src/workflows/1-project-brief/vtc-workshop/steps-c/step-04b-select-driving-forces.md
View File

@ -1,154 +0,0 @@
---
name: 'step-04b-select-driving-forces'
description: 'Choose 2-5 most relevant driving forces from Trigger Map for this VTC'
# File References
nextStepFile: './step-05b-define-solution.md'
workflowFile: '../../workflow.md'
activityWorkflowFile: '../workflow.md'
---
# Step 4: Select Driving Forces
## STEP GOAL:
Choose 2-5 most relevant driving forces from the Trigger Map for this VTC.
## MANDATORY EXECUTION RULES (READ FIRST):
### Universal Rules:
- NEVER generate content without user input
- CRITICAL: Read the complete step file before taking any action
- CRITICAL: When loading next step with 'C', ensure entire file is read
- YOU ARE A FACILITATOR, not a content generator
- YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
### Role Reinforcement:
- You are a Strategic Business Analyst facilitating VTC selection from an existing Trigger Map
- If you already have been given a name, communication_style and persona, continue to use those while playing this new role
- We engage in collaborative dialogue, not command-response
- You bring structured thinking and facilitation skills, user brings domain expertise and product vision
- Maintain collaborative and strategic tone throughout
### Step-Specific Rules:
- Focus: Present available forces, guide selection of 2-5, handle forces not in map
- FORBIDDEN: Do not select forces without user confirmation; do not include all forces (lose focus)
- Approach: Present forces with priorities, guide selection criteria, handle missing forces, capture
## EXECUTION PROTOCOLS:
- Primary goal: 2-5 relevant driving forces selected from Trigger Map
- Save/document outputs appropriately
- Avoid generating content without user input
## CONTEXT BOUNDARIES:
- Available context: Trigger Map, selected goal, selected user from steps 1-3
- Focus: Driving forces selection
- Limits: 2-5 total, mix of positive and negative
- Dependencies: Step 03b completed
## Sequence of Instructions (Do not deviate, skip, or optimize)
### 1. Present Available Forces
Show all driving forces for selected user:
> "For [selected user], your Trigger Map shows:
>
> **Positive (Wishes):**
> 1. [Force 1] - Priority: [score]
> 2. [Force 2] - Priority: [score]
> 3. [Force 3] - Priority: [score]
>
> **Negative (Fears/Avoid):**
> 1. [Force 1] - Priority: [score]
> 2. [Force 2] - Priority: [score]
> 3. [Force 3] - Priority: [score]"
### 2. Guide Selection
> "Which of these driving forces does [this solution/scenario] directly address?
>
> Pick 2-5 total (mix of positive and negative) that are most relevant here."
**Selection criteria:**
- Does THIS solution actually address this force?
- Balance positive and negative
- Don't include everything (lose focus)
- Higher priority forces are good candidates
### 3. Handle Driving Force Missing
**User:** "None of these capture [specific driving force]. But that's critical for this scenario!"
**This is valuable discovery!** Using the map reveals gaps.
**Options:**
**A) Add to Trigger Map now:**
1. Pause VTC workshop
2. Add new driving force to Trigger Map
3. Assign priority
4. Resume and select it
**B) Add to VTC and note for map:**
1. Use new force in this VTC
2. Note: "Add to Trigger Map: [new force]"
3. Update map after workshop
**C) Reword existing force:**
1. Take closest match from map
2. Refine wording in VTC
3. Consider updating map
**Recommendation:** If you discovered this force is critical, add it to the map. Other scenarios likely need it too.
### 4. Capture Format
```yaml
driving_forces:
positive:
- "[Selected wish 1 from map]"
- "[Selected wish 2 from map]"
negative:
- "[Selected fear 1 from map]"
- "[Selected fear 2 from map]"
```
### 5. Validation
- [ ] Selected forces directly addressed by this solution?
- [ ] Focused enough (not too many)?
- [ ] Includes both positive and negative?
- [ ] User confirms these are the right ones?
- [ ] If adding new forces, documented for map update?
### N. Present MENU OPTIONS
Display: "**Select an Option:** [C] Continue to next step"
#### Menu Handling Logic:
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
- IF M: Return to {workflowFile} or {activityWorkflowFile}
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
#### EXECUTION RULES:
- ALWAYS halt and wait for user input after presenting menu
- User can chat or ask questions - always respond and then redisplay menu options
## CRITICAL STEP COMPLETION NOTE
ONLY WHEN step objectives are met and user confirms will you then load and read fully `{nextStepFile}`.
---
## SYSTEM SUCCESS/FAILURE METRICS
### SUCCESS:
- Available forces presented with priorities
- 2-5 forces selected with balance of positive and negative
- Missing forces handled and documented (if applicable)
- User confirmed selection
### FAILURE:
- Selected forces without user confirmation
- Included all forces without focus
- Did not handle missing force scenario
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

195
src/workflows/1-project-brief/vtc-workshop/steps-c/step-05a-negative-driving-forces.md
View File

@ -1,195 +0,0 @@
---
name: 'step-05a-negative-driving-forces'
description: 'Discover what the user FEARS or wants to avoid - anxieties and frustrations'
# File References
nextStepFile: './step-06a-customer-awareness.md'
workflowFile: '../../workflow.md'
activityWorkflowFile: '../workflow.md'
---
# Step 5: Identify Negative Driving Forces
## STEP GOAL:
Discover what the user FEARS or wants to avoid - their anxieties, frustrations, and what pushes them away from failure.
## MANDATORY EXECUTION RULES (READ FIRST):
### Universal Rules:
- NEVER generate content without user input
- CRITICAL: Read the complete step file before taking any action
- CRITICAL: When loading next step with 'C', ensure entire file is read
- YOU ARE A FACILITATOR, not a content generator
- YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
### Role Reinforcement:
- You are a Strategic Business Analyst facilitating VTC creation from scratch
- If you already have been given a name, communication_style and persona, continue to use those while playing this new role
- We engage in collaborative dialogue, not command-response
- You bring structured thinking and facilitation skills, user brings domain expertise and product vision
- Maintain collaborative and strategic tone throughout
### Step-Specific Rules:
- Focus: Anxieties and frustrations, not just functional dislikes
- FORBIDDEN: Do not accept mild or generic fears without probing deeper
- Approach: Ask, probe for real fears, capture 2-3 strong forces, validate, review combined forces
## EXECUTION PROTOCOLS:
- Primary goal: 2-3 negative driving forces captured and combined forces reviewed
- Save/document outputs appropriately
- Avoid generating content without user input
## CONTEXT BOUNDARIES:
- Available context: Business goal, solution, user, positive forces from steps 1-4
- Focus: Negative driving forces (fears, anxieties, frustrations)
- Limits: 2-3 forces, total 4-6 combined with positive
- Dependencies: Step 04a completed
## Sequence of Instructions (Do not deviate, skip, or optimize)
### 1. Ask for Negative Forces
> "What does [user name] FEAR or want to avoid? What keeps them up at night?"
**Probing questions:**
- "What are they worried about?"
- "What would be embarrassing or costly?"
- "What would feel like failure?"
- "What friction do they currently experience?"
- "What do they NOT want to happen?"
### 2. Apply Guidelines
**Think anxieties and frustrations:**
- Not: "Don't want slow system"
- Yes: "Fear of wasting hours on complex tools"
**What do they fear:**
- Losing?
- Missing?
- Being seen as?
- Experiencing?
**Aim for 2-3 strong fears:**
- Often opposite side of positive forces
- Specific and emotionally real
- Inform risk reduction in design
### 3. Reference Examples
**Hairdresser (Harriet):**
- "Fear of missing industry trends"
- "Fear of losing clients to trendier salons"
- "Avoid appearing outdated to clients"
**Developer (reviewing code):**
- "Fear of missing critical bugs"
- "Fear of slowing down teammates"
- "Avoid looking careless or rushed"
**Small business owner:**
- "Fear of making wrong financial decisions"
- "Fear of tax compliance issues"
- "Avoid feeling stupid about numbers"
### 4. Note Connection to Positive Forces
**Notice patterns:**
- Positive: "Wish to be authority" <-> Negative: "Fear of appearing outdated"
- Positive: "Wish to catch bugs" <-> Negative: "Fear of missing bugs"
**Both sides of same coin** - this is good! Shows coherent psychology.
### 5. Capture Format
```yaml
driving_forces:
positive:
- "[from previous step]"
negative:
- "Fear of [anxiety]"
- "Fear of [frustration]"
- "Avoid [problem]"
```
### 6. Validation Checklist
Before proceeding, confirm:
- [ ] Forces feel true for this user?
- [ ] Specific enough to inform design?
- [ ] Connect to positive forces (opposite sides)?
- [ ] 2-3 forces captured (total 4-6 positive + negative)?
- [ ] User agrees these are real anxieties?
### 7. Handle Common Issues
**Issue:** Forces too mild ("don't like complexity")
> "What's the REAL fear behind that? What happens if they encounter complexity? What cost do they pay?"
**Issue:** Only negative stated as positive inverse ("want to not fail")
> "What ARE they afraid of specifically? What would failure look like?"
**Issue:** Too many fears (overwhelming)
> "Which 2-3 fears are strongest? Which would prevent them from using this solution?"
### 8. Review Combined Forces
**At this point, review ALL driving forces together:**
```yaml
driving_forces:
positive:
- "[wish 1]"
- "[wish 2]"
- "[wish 3]"
negative:
- "[fear 1]"
- "[fear 2]"
```
**Ask:** "Do these forces tell a coherent story about what drives [user name]?"
If yes -> Proceed
If no -> Refine before moving forward
### 9. Design Hint
These negative forces should inform:
- Risk reduction features
- Reassurance messaging
- Error prevention
- Trust signals
- Recovery paths
### N. Present MENU OPTIONS
Display: "**Select an Option:** [C] Continue to next step"
#### Menu Handling Logic:
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
- IF M: Return to {workflowFile} or {activityWorkflowFile}
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
#### EXECUTION RULES:
- ALWAYS halt and wait for user input after presenting menu
- User can chat or ask questions - always respond and then redisplay menu options
## CRITICAL STEP COMPLETION NOTE
ONLY WHEN step objectives are met and user confirms will you then load and read fully `{nextStepFile}`.
---
## SYSTEM SUCCESS/FAILURE METRICS
### SUCCESS:
- 2-3 emotionally real negative forces captured
- Forces connect to positive forces (coherent psychology)
- Combined forces reviewed and validated
- User confirmed the anxieties
### FAILURE:
- Accepted mild or generic fears without depth
- Skipped combined forces review
- Generated forces without user input
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

117
src/workflows/1-project-brief/vtc-workshop/steps-c/step-05b-define-solution.md
View File

@ -1,117 +0,0 @@
---
name: 'step-05b-define-solution'
description: 'Define what solution is being built - NOT in Trigger Map, solutions stay out of map'
# File References
nextStepFile: './step-06b-customer-awareness.md'
workflowFile: '../../workflow.md'
activityWorkflowFile: '../workflow.md'
---
# Step 5: Define Solution
## STEP GOAL:
Define what we're building - solutions are NOT in the Trigger Map, they are defined per VTC as the bridge between business goal and user.
## MANDATORY EXECUTION RULES (READ FIRST):
### Universal Rules:
- NEVER generate content without user input
- CRITICAL: Read the complete step file before taking any action
- CRITICAL: When loading next step with 'C', ensure entire file is read
- YOU ARE A FACILITATOR, not a content generator
- YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
### Role Reinforcement:
- You are a Strategic Business Analyst facilitating VTC selection from an existing Trigger Map
- If you already have been given a name, communication_style and persona, continue to use those while playing this new role
- We engage in collaborative dialogue, not command-response
- You bring structured thinking and facilitation skills, user brings domain expertise and product vision
- Maintain collaborative and strategic tone throughout
### Step-Specific Rules:
- Focus: Specific solution definition, test connection to map elements
- FORBIDDEN: Do not accept vague solution descriptions
- Approach: Ask, apply guidelines, test chain connection, validate
## EXECUTION PROTOCOLS:
- Primary goal: Solution defined and validated against map elements
- Save/document outputs appropriately
- Avoid generating content without user input
## CONTEXT BOUNDARIES:
- Available context: Trigger Map, selected goal, user, forces from steps 1-4
- Focus: Solution definition (new element, not from map)
- Limits: Specific, focused, user-facing
- Dependencies: Step 04b completed
## Sequence of Instructions (Do not deviate, skip, or optimize)
### 1. Ask for Solution
> "What solution are you building to serve this VTC?"
**Reminder:** This is the bridge between business goal and user.
### 2. Apply Guidelines
Same as Creation Workshop - specific about WHAT this is:
**Good examples:**
- "Landing page with newsletter signup"
- "Onboarding flow for new users"
- "User profile settings page"
**Bad examples:**
- "A great experience" (too vague)
- "Lots of features" (not specific)
### 3. Capture Format
```yaml
solution: "[Specific solution being built]"
```
### 4. Test Connection
Business Goal (from map) -> Solution (new) -> User (from map) -> Forces (from map)
Does this chain make sense?
### 5. Validation
- [ ] Solution is specific?
- [ ] Solution serves selected business goal?
- [ ] Solution connects to selected user and forces?
### N. Present MENU OPTIONS
Display: "**Select an Option:** [C] Continue to next step"
#### Menu Handling Logic:
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
- IF M: Return to {workflowFile} or {activityWorkflowFile}
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
#### EXECUTION RULES:
- ALWAYS halt and wait for user input after presenting menu
- User can chat or ask questions - always respond and then redisplay menu options
## CRITICAL STEP COMPLETION NOTE
ONLY WHEN step objectives are met and user confirms will you then load and read fully `{nextStepFile}`.
---
## SYSTEM SUCCESS/FAILURE METRICS
### SUCCESS:
- Specific solution defined
- Chain connection tested (goal -> solution -> user -> forces)
- User confirmed the solution
- Solution bridges business goal and user
### FAILURE:
- Accepted vague solution description
- Skipped chain connection test
- Generated solution without user input
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

216
src/workflows/1-project-brief/vtc-workshop/steps-c/step-06a-customer-awareness.md
View File

@ -1,216 +0,0 @@
---
name: 'step-06a-customer-awareness'
description: 'Define where user starts and where we move them in their awareness journey'
# File References
nextStepFile: './step-07a-review-and-save.md'
workflowFile: '../../workflow.md'
activityWorkflowFile: '../workflow.md'
---
# Step 6: Position Customer Awareness
## STEP GOAL:
Define where user starts and where we move them in their awareness journey - explore what the user knows NOW, and what transformation we want to create.
## MANDATORY EXECUTION RULES (READ FIRST):
### Universal Rules:
- NEVER generate content without user input
- CRITICAL: Read the complete step file before taking any action
- CRITICAL: When loading next step with 'C', ensure entire file is read
- YOU ARE A FACILITATOR, not a content generator
- YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
### Role Reinforcement:
- You are a Strategic Business Analyst facilitating VTC creation from scratch
- If you already have been given a name, communication_style and persona, continue to use those while playing this new role
- We engage in collaborative dialogue, not command-response
- You bring structured thinking and facilitation skills, user brings domain expertise and product vision
- Maintain collaborative and strategic tone throughout
### Step-Specific Rules:
- Focus: Customer awareness start and end positions with realistic progression
- FORBIDDEN: Do not skip validating realistic progression (usually 1-2 stages)
- Approach: Explore current state, define transformation, validate realistic progression, storytelling validation
## EXECUTION PROTOCOLS:
- Primary goal: Customer awareness journey defined and validated
- Save/document outputs appropriately
- Avoid generating content without user input
## CONTEXT BOUNDARIES:
- Available context: Business goal, solution, user, driving forces from steps 1-5
- Focus: Customer awareness positioning
- Limits: Realistic progression, usually 1-2 stages
- Dependencies: Step 05a completed
## Sequence of Instructions (Do not deviate, skip, or optimize)
### 1. Understand Current State (6A)
**Start with exploration:**
> "Let's understand where [user name] is right now. When they encounter [solution], what's going on in their head?"
**Ask progressively:**
**"Do they know something's wrong?"**
- If NO: "Interesting - so they don't even realize there's a problem yet. What would make them suddenly notice?" -> Starting at **Unaware**
- If YES: "Okay, they know something's not working. Tell me more about that..."
**"What language are they using?"**
> "When they talk about this problem - to themselves or others - what words do they use?"
**Listen for:**
- Generic problem language -> **Problem Aware**
- Comparing solutions -> **Solution Aware**
- Mentioning your product -> **Product Aware**
- Sharing their experience -> **Most Aware**
**"What are they looking for?"**
> "If they're searching for help, what would they type into Google?"
**Examples show awareness:**
- "how to fix [problem]" -> Problem Aware
- "best tools for [need]" -> Solution Aware
- "[your product name] review" -> Product Aware
**"Have they tried anything?"**
> "Are they already trying other solutions? Or still figuring out if solutions exist?"
**Reveals:**
- Never tried anything -> Problem Aware
- Tried competitors -> Solution Aware
- Using your free version -> Product Aware
- Paying customer -> Most Aware
**Capture their current position:**
```yaml
customer_awareness:
start: "[One of: Unaware / Problem Aware / Solution Aware / Product Aware / Most Aware]"
start_context: "[What they know, what they're looking for, language they use]"
```
**The 5 stages:** Unaware -> Problem Aware -> Solution Aware -> Product Aware -> Most Aware
### 2. Define Desired Transformation (6B)
> "After they interact with [solution], what should change in their understanding?"
**"What will they realize?"**
> "What new insight or understanding will they gain?"
**"What will they be able to articulate?"**
> "After this experience, if they told a friend about it, what would they say?"
**"What action becomes possible?"**
> "What can they do NOW that they couldn't before?"
**Actions show awareness level:**
- Admit problem -> Problem Aware
- Compare solutions -> Solution Aware
- Try your product -> Product Aware
- Recommend it -> Most Aware
### 3. Validate Realistic Progression (6C)
> "So they're starting at [start stage]. Where's realistic to move them with [this solution]?"
**Important:** Usually move 1-2 stages, not jumping from Unaware -> Most Aware
**Guide with questions:**
- "Is this a quick interaction or deep engagement?"
- "Will they actually USE it, or just learn about it?"
- "What's preventing bigger jump?"
**Capture:**
```yaml
customer_awareness:
start: "[Current stage]"
start_context: "[What they know/feel NOW]"
end: "[Target stage]"
end_context: "[What they'll know/feel AFTER]"
transformation: "[Key shift that happens]"
```
### 4. Validation Through Storytelling
**Ask user to tell the story:**
> "Walk me through their awareness journey: They start knowing what? -> They encounter this solution -> They realize what? -> They end up able to do what?"
**Listen for:** Coherent narrative, Realistic transformation, Matches driving forces, Supports business goal
**If story doesn't flow** - one of the stages is wrong.
### 5. Common Patterns Reference
| Context | Typical Journey |
|---------|-----------------|
| **Landing Pages** | Problem/Solution -> Product Aware |
| **Onboarding** | Product -> Most Aware |
| **Educational Content** | Unaware -> Problem Aware |
| **Feature Announcements** | Most Aware -> Most Aware (deepen) |
### 6. Handle Common Issues
**Issue:** User wants to jump multiple stages
> "That's the ultimate goal, but THIS interaction likely moves them 1-2 stages. What's the next realistic step?"
**Issue:** User not sure about stages
> "Let's think about it this way: What do they know BEFORE? What should they know AFTER?"
**Issue:** Starting and ending are the same stage
> "If awareness doesn't change, what IS changing? Maybe we're maintaining Most Aware, or maybe the starting point needs adjustment?"
### 7. How This Guides Design
**Content Strategy:**
- **Start stage** -> what language to use (theirs, not yours)
- **End stage** -> what message to deliver (the transformation)
- **Gap between** -> how much explanation needed
**Tone:** Earlier = exploratory, educational | Later = direct, action-oriented
**Depth:**
- Unaware: Need context (why should I care?)
- Problem Aware: Need options (what solves this?)
- Solution Aware: Need differentiation (why yours?)
- Product Aware: Need proof (does it work?)
- Most Aware: Need expansion (what else?)
### N. Present MENU OPTIONS
Display: "**Select an Option:** [C] Continue to next step"
#### Menu Handling Logic:
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
- IF M: Return to {workflowFile} or {activityWorkflowFile}
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
#### EXECUTION RULES:
- ALWAYS halt and wait for user input after presenting menu
- User can chat or ask questions - always respond and then redisplay menu options
## CRITICAL STEP COMPLETION NOTE
ONLY WHEN step objectives are met and user confirms will you then load and read fully `{nextStepFile}`.
---
## SYSTEM SUCCESS/FAILURE METRICS
### SUCCESS:
- Customer awareness start and end defined
- Progression is realistic (1-2 stages)
- Storytelling validation passed
- Transformation is clear and actionable
- User confirmed the awareness journey
### FAILURE:
- Skipped realistic progression validation
- Accepted unrealistic stage jumps without questioning
- Generated awareness positions without user input
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

123
src/workflows/1-project-brief/vtc-workshop/steps-c/step-06b-customer-awareness.md
View File

@ -1,123 +0,0 @@
---
name: 'step-06b-customer-awareness'
description: 'Define awareness start/end - typically NOT in Trigger Map, defined per scenario'
# File References
nextStepFile: './step-07b-review-and-save.md'
workflowFile: '../../workflow.md'
activityWorkflowFile: '../workflow.md'
---
# Step 6: Position Customer Awareness
## STEP GOAL:
Define awareness start/end positions - typically NOT in the Trigger Map, defined per scenario. Explore what user knows NOW and what transformation happens.
## MANDATORY EXECUTION RULES (READ FIRST):
### Universal Rules:
- NEVER generate content without user input
- CRITICAL: Read the complete step file before taking any action
- CRITICAL: When loading next step with 'C', ensure entire file is read
- YOU ARE A FACILITATOR, not a content generator
- YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
### Role Reinforcement:
- You are a Strategic Business Analyst facilitating VTC selection from an existing Trigger Map
- If you already have been given a name, communication_style and persona, continue to use those while playing this new role
- We engage in collaborative dialogue, not command-response
- You bring structured thinking and facilitation skills, user brings domain expertise and product vision
- Maintain collaborative and strategic tone throughout
### Step-Specific Rules:
- Focus: Customer awareness start and end with context, realistic progression
- FORBIDDEN: Do not skip storytelling validation of the awareness journey
- Approach: Use same exploratory approach as Creation Workshop, capture with context, validate through story
## EXECUTION PROTOCOLS:
- Primary goal: Customer awareness journey defined and validated
- Save/document outputs appropriately
- Avoid generating content without user input
## CONTEXT BOUNDARIES:
- Available context: Trigger Map, selected goal, user, forces, solution from steps 1-5
- Focus: Customer awareness positioning (new element, not from map)
- Limits: Realistic progression, usually 1-2 stages
- Dependencies: Step 05b completed
## Sequence of Instructions (Do not deviate, skip, or optimize)
### 1. Quick Exploration Questions
**Current State:**
1. **"Do they know something's wrong?"**
2. **"What language are they using?"** (when talking about this)
3. **"What are they looking for?"** (search terms, questions)
4. **"Have they tried anything?"** (your product, competitors, nothing)
**Desired Transformation:**
1. **"What will they realize?"** (new insight)
2. **"What will they be able to articulate?"** (to a friend)
3. **"What action becomes possible?"** (what can they DO now)
### 2. Capture with Context
```yaml
customer_awareness:
start: "[Stage]"
start_context: "[What they know/feel NOW]"
end: "[Stage]"
end_context: "[What they'll know/feel AFTER]"
transformation: "[Key shift that happens]"
```
**Example:**
```yaml
customer_awareness:
start: "Solution Aware"
start_context: "Researching design tools, overwhelmed by options"
end: "Product Aware"
end_context: "Knows WDS exists, understands it's agent-based, considering trial"
transformation: "From 'tools are complex' to 'this specific approach might work'"
```
### 3. Validate Through Story
**Ask user:**
> "Walk me through their awareness journey in this scenario."
Story should flow naturally and match the selected driving forces from Trigger Map.
### N. Present MENU OPTIONS
Display: "**Select an Option:** [C] Continue to next step"
#### Menu Handling Logic:
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
- IF M: Return to {workflowFile} or {activityWorkflowFile}
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
#### EXECUTION RULES:
- ALWAYS halt and wait for user input after presenting menu
- User can chat or ask questions - always respond and then redisplay menu options
## CRITICAL STEP COMPLETION NOTE
ONLY WHEN step objectives are met and user confirms will you then load and read fully `{nextStepFile}`.
---
## SYSTEM SUCCESS/FAILURE METRICS
### SUCCESS:
- Customer awareness start and end defined with context
- Transformation clearly articulated
- Storytelling validation passed
- Journey matches selected driving forces
### FAILURE:
- Skipped storytelling validation
- Defined positions without context
- Generated awareness positions without user input
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

250
src/workflows/1-project-brief/vtc-workshop/steps-c/step-07a-review-and-save.md
View File

@ -1,250 +0,0 @@
---
name: 'step-07a-review-and-save'
description: 'Validate completeness and save the VTC - final step of Creation Workshop'
# File References
workflowFile: '../../workflow.md'
activityWorkflowFile: '../workflow.md'
---
# Step 7: Review and Save VTC
## STEP GOAL:
Validate completeness and save the VTC for use - review the complete VTC for coherence, then save it to the appropriate location.
## MANDATORY EXECUTION RULES (READ FIRST):
### Universal Rules:
- NEVER generate content without user input
- CRITICAL: Read the complete step file before taking any action
- CRITICAL: When loading next step with 'C', ensure entire file is read
- YOU ARE A FACILITATOR, not a content generator
- YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
### Role Reinforcement:
- You are a Strategic Business Analyst completing the VTC Creation Workshop
- If you already have been given a name, communication_style and persona, continue to use those while playing this new role
- We engage in collaborative dialogue, not command-response
- You bring structured thinking and facilitation skills, user brings domain expertise and product vision
- Maintain collaborative and strategic tone throughout
### Step-Specific Rules:
- Focus: Read back complete VTC, validate with 4 questions, refine if needed, determine save location, save
- FORBIDDEN: Do not skip any of the 4 validation questions
- Approach: Present VTC, validate coherence/actionability/specificity/realism, refine, save, communicate
## EXECUTION PROTOCOLS:
- Primary goal: VTC validated, saved, and user understands what they have
- Save/document outputs appropriately
- Avoid generating content without user input
## CONTEXT BOUNDARIES:
- Available context: All VTC elements from steps 1-6
- Focus: Review, validation, and save
- Limits: Finalizing, not starting new work
- Dependencies: Steps 01a-06a completed
## Sequence of Instructions (Do not deviate, skip, or optimize)
### 1. Read Back Complete VTC (7A)
**Present the full VTC to user:**
```yaml
vtc:
business_goal: "[goal]"
solution: "[solution]"
user:
name: "[name]"
description: "[description]"
context: "[context]"
driving_forces:
positive:
- "[wish 1]"
- "[wish 2]"
negative:
- "[fear 1]"
- "[fear 2]"
customer_awareness:
start: "[start stage]"
end: "[end stage]"
```
### 2. Validate with Questions (7B)
**Ask each validation question:**
**Coherence:**
> "Does this tell a coherent story?"
- Business goal -> Solution -> User -> Forces -> Awareness
- Does it flow logically?
- Does each piece connect to the others?
**Actionable:**
> "Can you make design decisions from this?"
- Specific enough to guide choices?
- Clear what would/wouldn't serve this VTC?
- Could someone else use this?
**Specific:**
> "Are the driving forces specific enough?"
- Go beyond generic?
- Emotionally resonant?
- Different from other users?
**Realistic:**
> "Does the awareness progression make sense?"
- Can solution realistically move user that far?
- Appropriate for this interaction type?
- Supports business goal?
**All YES?** -> VTC is ready to save
**Any NO?** -> Refine that specific element
### 3. Quick Refinement (7C) - if needed
**If any validation failed:**
1. Identify which element needs work
2. Return to that step briefly
3. Make adjustment
4. Re-validate
**Keep momentum** - don't get stuck perfecting. "Good enough to guide design" is the bar.
### 4. Determine Save Location (7D)
**Ask:**
> "What is this VTC for?"
**If Product Pitch:**
- Location: `{output_folder}/A-Product-Brief/vtc-primary.yaml`
- Purpose: Stakeholder communication, strategic alignment
**If Scenario:**
- Location: `{output_folder}/C-UX-Scenarios/[scenario-name]/vtc.yaml`
- Purpose: Guide scenario design decisions
**If Prototype/Other:**
- Location: `{output_folder}/[appropriate-folder]/vtc-[name].yaml`
- Purpose: As defined by user
### 5. Create VTC File (7E)
**Use template:** Copy from `../../templates/vtc-template.yaml`
**Fill in all sections:**
```yaml
vtc:
business_goal: "[captured value]"
solution: "[captured value]"
user:
name: "[captured value]"
description: "[captured value]"
context: "[captured value]"
driving_forces:
positive: [captured values]
negative: [captured values]
customer_awareness:
start: "[captured value]"
end: "[captured value]"
metadata:
created_date: "[today's date]"
created_by: "[team/person]"
version: "1.0"
source: "creation"
purpose: "[product_pitch / scenario / etc]"
phase: "[WDS phase]"
notes: |
Created: [date]
Context: [why this VTC was created]
Key decisions made:
- [Important choices during workshop]
- [Insights captured]
Usage guidance:
- [How this VTC should inform design]
```
**Save file to determined location**
### 6. Communicate What They Have (7F)
**Explain to user:**
> "Excellent! We've created a Value Trigger Chain that shows:
>
> **Business Goal:** [goal]
> **User:** [name] who wants to [positive force] and avoid [negative force]
> **Solution:** [solution] that moves them from [start] to [end] awareness
>
> This VTC will guide all design decisions for [context]. Every piece of content, every interaction, every design choice should serve this strategic chain.
>
> **Next time you're making a design decision, ask:**
> 'Does this serve the business goal by triggering these driving forces while moving the user forward in awareness?'
>
> If yes -> Good decision
> If no -> Reconsider"
### 7. Define Next Actions (7G)
**If Product Pitch:**
> "Next steps:
> 1. Add this VTC to your pitch document
> 2. Structure pitch narrative around this chain
> 3. Use it to explain strategic reasoning to stakeholders
> 4. Can evolve into full Trigger Map later as project grows"
**If Scenario:**
> "Next steps:
> 1. Use this VTC to guide page design in this scenario
> 2. All content should address these driving forces
> 3. Track if you're actually moving users through awareness
> 4. Create additional VTCs for other scenarios as needed"
### 8. Completion Checklist
- [ ] VTC validated with all 4 questions
- [ ] VTC saved to appropriate location
- [ ] Metadata completed (date, source, purpose)
- [ ] Notes section filled with context
- [ ] User understands what they have
- [ ] User knows how to use VTC
- [ ] Next actions defined
### N. Present MENU OPTIONS
Display: "**Select an Option:** [M] Return to workflow menu"
#### Menu Handling Logic:
- IF M: Return to {workflowFile} or {activityWorkflowFile}
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
#### EXECUTION RULES:
- ALWAYS halt and wait for user input after presenting menu
- User can chat or ask questions - always respond and then redisplay menu options
## CRITICAL STEP COMPLETION NOTE
This is the FINAL step of the VTC Creation Workshop. Workshop is complete.
---
## SYSTEM SUCCESS/FAILURE METRICS
### SUCCESS:
- Complete VTC presented and validated
- All 4 validation questions answered YES
- VTC saved to correct location with metadata
- User understands what they have and how to use it
- Next actions defined
### FAILURE:
- Skipped validation questions
- Saved without metadata or notes
- Did not communicate value to user
- Left user without clear next actions
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

191
src/workflows/1-project-brief/vtc-workshop/steps-c/step-07b-review-and-save.md
View File

@ -1,191 +0,0 @@
---
name: 'step-07b-review-and-save'
description: 'Validate complete VTC with source attribution and save - final step of Selection Workshop'
# File References
workflowFile: '../../workflow.md'
activityWorkflowFile: '../workflow.md'
---
# Step 7: Review and Save VTC
## STEP GOAL:
Validate complete VTC, refine if needed, and save with source attribution back to the Trigger Map.
## MANDATORY EXECUTION RULES (READ FIRST):
### Universal Rules:
- NEVER generate content without user input
- CRITICAL: Read the complete step file before taking any action
- CRITICAL: When loading next step with 'C', ensure entire file is read
- YOU ARE A FACILITATOR, not a content generator
- YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
### Role Reinforcement:
- You are a Strategic Business Analyst completing the VTC Selection Workshop
- If you already have been given a name, communication_style and persona, continue to use those while playing this new role
- We engage in collaborative dialogue, not command-response
- You bring structured thinking and facilitation skills, user brings domain expertise and product vision
- Maintain collaborative and strategic tone throughout
### Step-Specific Rules:
- Focus: Read back VTC, final refinement check, validate with 4 questions, save with source metadata
- FORBIDDEN: Do not skip source metadata or selection rationale documentation
- Approach: Present VTC, check for map gaps, validate, save with traceability, communicate
## EXECUTION PROTOCOLS:
- Primary goal: VTC validated, saved with source attribution, user understands traceability
- Save/document outputs appropriately
- Avoid generating content without user input
## CONTEXT BOUNDARIES:
- Available context: All VTC elements from steps 1-6 plus Trigger Map
- Focus: Review, validation, and save with source attribution
- Limits: Finalizing, not starting new work
- Dependencies: Steps 01b-06b completed
## Sequence of Instructions (Do not deviate, skip, or optimize)
### 1. Read Back Complete VTC
```yaml
vtc:
business_goal:
primary: "[From Trigger Map]"
priority: "[From map]"
solution: "[Newly defined]"
user:
name: "[From Trigger Map]"
description: "[From map]"
priority: "[From map]"
driving_forces:
positive: "[Selected from map]"
negative: "[Selected from map]"
customer_awareness:
start: "[Newly defined]"
end: "[Newly defined]"
metadata:
source: "trigger_map"
trigger_map_path: "[path]"
extracted_date: "[today]"
```
### 2. Final Refinement Check
> "Now that you see the complete VTC, did using the Trigger Map for this real scenario reveal anything we should capture?"
**Ask:**
- Missing elements we should add to VTC?
- Wording that needs adjustment?
- Gaps we should update in Trigger Map?
**If refinements needed:**
- Make adjustments to VTC
- Document what should update in Trigger Map
- Note: "Refinements made during final review: [changes]"
**If refinements reveal major Trigger Map gaps:**
- Consider pausing to update Trigger Map
- Document urgency: "now/soon/later"
**If VTC perfect as-is:**
- Great! Trigger Map is robust
### 3. Validation
Same 4 questions as Creation Workshop:
1. **Coherence:** Does this tell a coherent story?
2. **Actionable:** Can designers make decisions from this?
3. **Specific:** Are driving forces specific enough?
4. **Realistic:** Does awareness progression make sense?
**All YES?** -> Save
**Any NO?** -> Refine and re-validate
### 4. Save Location
**Product Pitch:** `{output_folder}/A-Product-Brief/vtc-primary.yaml`
**Scenario:** `{output_folder}/C-UX-Scenarios/[scenario-name]/vtc.yaml`
### 5. Include Source Metadata
```yaml
metadata:
source: "trigger_map"
trigger_map_path: "[path to source map]"
extracted_date: "[date]"
business_goal_priority: "[from map]"
user_priority: "[from map]"
notes: |
Extracted from Trigger Map for [purpose]
Selection rationale:
- Chose [goal] because [reason]
- Chose [user] because [reason]
- Selected these driving forces because [reason]
Refinements made during workshop:
- [Any changes/additions during selection]
- [What should update in Trigger Map]
Trigger Map update recommendations:
- Element: [what] | Urgency: [now/soon/later] | Reason: [why]
```
### 6. Communicate to User
> "Excellent! We've extracted a focused VTC from your Trigger Map.
>
> **Advantage:** This VTC is backed by your strategic research and remains consistent with your map's priorities.
>
> **Traceability:** We've documented the source, so if your Trigger Map evolves, we can update this VTC accordingly."
### 7. Define Next Actions
Same as Creation Workshop - based on context (Pitch or Scenario).
### 8. Completion Checklist
- [ ] VTC validated
- [ ] Saved to correct location
- [ ] Source metadata included
- [ ] Selection rationale documented
- [ ] User understands traceability
- [ ] Next actions defined
### N. Present MENU OPTIONS
Display: "**Select an Option:** [M] Return to workflow menu"
#### Menu Handling Logic:
- IF M: Return to {workflowFile} or {activityWorkflowFile}
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
#### EXECUTION RULES:
- ALWAYS halt and wait for user input after presenting menu
- User can chat or ask questions - always respond and then redisplay menu options
## CRITICAL STEP COMPLETION NOTE
This is the FINAL step of the VTC Selection Workshop. Workshop is complete.
---
## SYSTEM SUCCESS/FAILURE METRICS
### SUCCESS:
- Complete VTC presented with source attribution
- Final refinement check completed
- All 4 validation questions answered YES
- VTC saved with source metadata and selection rationale
- User understands traceability to Trigger Map
- Next actions defined
### FAILURE:
- Skipped source metadata
- Did not document selection rationale
- Saved without traceability
- Did not check for Trigger Map gaps
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

209
src/workflows/1-project-brief/vtc-workshop/workflow.md
View File

@ -1,209 +0,0 @@
---
name: vtc-workshop
description: Create or select VTC based on available strategic context (Trigger Map or from scratch)
web_bundle: true
---
# Value Trigger Chain (VTC) Workshop
**Goal:** Create a Value Trigger Chain to connect business goals, user needs, and driving forces
**Your Role:** Strategic facilitator helping create or select VTC based on available context (Trigger Map or from scratch)
---
## WORKFLOW ARCHITECTURE
This uses **step-file architecture** with **routing logic**:
### Core Principles
- **Context-Based Routing**: Selection (if Trigger Map exists) or Creation (from scratch)
- **Strategic Foundation**: VTC connects business goals → solution → user → driving forces → awareness
- **Flexibility**: Can be created early (Product Pitch) or scenario-specific
- **YAML Output**: Structured format for reuse across project
### Critical Rules
- 🎯 **ALWAYS** determine context first (Trigger Map exists?)
- 🔀 **ALWAYS** route to appropriate workshop based on context
- 📊 **ALWAYS** output YAML format
- 🎯 **ALWAYS** capture 2-5 driving forces (positive and negative)
- 📍 **ALWAYS** define customer awareness journey (start → end)
---
## WHEN TO USE
Use this workflow when:
- ✅ Creating Product Pitch (need primary VTC)
- ✅ Defining new scenario (need scenario-specific VTC)
- ✅ Need strategic clarity before design
- ✅ Want to connect business goals to user needs
Skip this workflow when:
- ❌ VTC already exists for this context
- ❌ No strategic planning needed (pure visual design)
- ❌ Working from existing detailed requirements
---
## ROUTING DECISION
**First Question:** "Do you have a completed Trigger Map?"
### Route A: VTC Selection Workshop
**IF YES** - Trigger Map exists
**Use when:**
- Trigger Map is completed
- Want to extract VTC from existing strategic work
- Need consistency with Trigger Map
- Multiple scenarios need VTCs
**Benefits:**
- Leverage existing research
- Maintain consistency
- Faster (select vs. imagine)
**Steps folder:** `steps-c/` (step-01b through step-07b)
---
### Route B: VTC Creation Workshop
**IF NO** - No Trigger Map yet
**Use when:**
- No Trigger Map available
- Early stage (Product Pitch)
- Quick project needing lightweight approach
- Standalone scenario/prototype
**Benefits:**
- Get started immediately
- No Trigger Map overhead
- Sufficient for simple projects
**Steps folder:** `steps-c/` (step-01a through step-07a)
---
## CONTEXT TO PROVIDE
When routing to either workshop, gather:
**Project Context:**
- Project name
- Current phase (Pitch or Scenario Definition)
- Purpose of this VTC (what will it be used for?)
**For Selection Workshop (if Trigger Map exists):**
- Path to Trigger Map document
- Number of business goals mapped
- Number of users/personas mapped
- Current scenario being defined (if applicable)
**For Creation Workshop (if no map):**
- Brief project description
- Who is the primary user? (if known)
- What problem are we solving? (if known)
---
## AGENT INSTRUCTIONS
1. Ask: "Do you have a completed Trigger Map?"
2. Based on answer, route to appropriate workshop
3. Provide context information to that workshop
4. Run the selected workshop
5. Save resulting VTC to appropriate location
6. Confirm completion with user
**Example Dialog:**
```
Agent: "I'll help you create a Value Trigger Chain for [context].
Do you have a completed Trigger Map for this project?"
User: "No, not yet."
Agent: "Perfect! I'll guide you through creating a VTC from scratch.
This will take about 30 minutes. Let's start with your
business goal..."
[Proceeds to Creation Workshop]
```
---
## FIRST STEP EXECUTION
**After routing decision:**
**IF Selection Workshop:**
Load, read and execute `steps-c/step-01b-load-trigger-map.md`
**IF Creation Workshop:**
Load, read and execute `steps-c/step-01a-define-business-goal.md`
**Template:** `../templates/vtc-template.yaml`
---
## OUTPUT
**Completed VTC (YAML format):**
```yaml
businessGoal: [What business wants to achieve]
solution: [How we help user achieve their goal]
user: [Who we're helping]
drivingForces:
positive:
- [What they want/hope for]
- [Another positive driver]
negative:
- [What they fear/avoid]
- [Another negative driver]
customerAwareness:
start: [Where they are now]
end: [Where they need to be]
```
**Destination:**
- Product Pitch: `docs/A-Product-Brief/vtc-primary.yaml`
- Scenario: `docs/C-UX-Scenarios/[scenario-name]/vtc.yaml`
---
## EXAMPLE USE CASES
### Use Case 1: Product Pitch (No Trigger Map)
→ Route to Creation Workshop
→ Create primary VTC from scratch
→ Save to `docs/A-Product-Brief/vtc-primary.yaml`
### Use Case 2: Scenario Definition (Trigger Map Exists)
→ Route to Selection Workshop
→ Select business goal + user from Trigger Map
→ Customize driving forces for scenario
→ Save to `docs/C-UX-Scenarios/[scenario]/vtc.yaml`
### Use Case 3: Multiple Scenarios
→ Route to Selection Workshop for each
→ Create variant VTCs from same Trigger Map
→ Maintain consistency across scenarios
---
## ALPHA STATUS
**This workshop is in ALPHA** - feedback needed.
Please document:
- Where you got stuck
- What took longer than estimated
- What needs clarification
- What's missing
Add feedback to VTC file notes section.

2
src/workflows/1-project-brief/workflow.md
View File

@ -64,7 +64,6 @@ Based on `brief_level`:
| 01 | Init | Load context, confirm readiness |
| 02 | Vision | Explore and document project vision |
| 03 | Positioning | Define market positioning |
| 04 | Create Trigger Map | Strategic foundation (refs `vtc-workshop/`) |
| 05 | Business Model | Define revenue/business model |
| 06 | Business Customers | Identify B2B customers (if applicable) |
| 07 | Target Users | Define end users |
@ -74,7 +73,6 @@ Based on `brief_level`:
| 10 | Constraints | Document project constraints |
| 10a | Platform Strategy | Define platform approach |
| 11 | Tone of Voice | Establish brand voice |
| 11a | Create Trigger Map | Second Trigger Map opportunity (refs `vtc-workshop/`) |
| 12 | Create Product Brief | Generate the Product Brief document |
| 13 | Content Init | Initialize content & language strategy |
| 14 | Personality | Define brand personality |

2
src/workflows/3-scenarios/steps-c/step-02-analyze-scope.md
View File

@ -3,7 +3,7 @@ name: 'step-02-analyze-scope'
description: 'Determine site type, list all pages/views, assess scale, and select approach mode'
# File References
nextStepFile: './step-03-build-vtcs.md'
nextStepFile: './step-03-build-strategic-context.md'
---
# Step 2: Analyze Scope & Scale Strategy

2
src/workflows/3-scenarios/steps-c/step-03-build-vtcs.md → src/workflows/3-scenarios/steps-c/step-03-build-strategic-context.md
View File

@ -1,5 +1,5 @@
---
name: 'step-03-build-vtcs'
name: 'step-03-build-strategic-context'
description: 'Build strategic context from Trigger Map to identify which scenarios to create'
# File References

2
src/workflows/3-scenarios/workflow.md
View File

@ -51,7 +51,7 @@ This uses **step-file architecture** for disciplined execution:
|---|------|---------|
| 01 | [Load Context](steps-c/step-01-load-context.md) | Read all prerequisite artifacts, detect project state |
| 02 | [Analyze Scope](steps-c/step-02-analyze-scope.md) | Determine site type, pages, scale strategy (user checkpoint) |
| 03 | [Build Strategic Context](steps-c/step-03-build-vtcs.md) | Extract strategic context from Trigger Map |
| 03 | [Build Strategic Context](steps-c/step-03-build-strategic-context.md) | Extract strategic context from Trigger Map |
| 04 | [Suggest Scenarios](steps-c/step-04-suggest-scenarios.md) | Present scenario plan for approval (user checkpoint) |
| 05 | [Outline Scenario](steps-c/step-05-outline-scenario.md) | Detail ONE scenario (loops for each) |
| 06 | [Generate Overview](steps-c/step-06-generate-overview.md) | Create 00-ux-scenarios.md index file |

4
src/workflows/4-ux-design/data/scenario-init/06-shortest-path.md
View File

@ -83,9 +83,9 @@ With all 5 questions answered, you have:
- ✅ Mutual success (where to end)
- ✅ Shortest path (how to get there)
**→ Proceed to [Step 6: Create VTC](06-create-vtc.md)**
**→ Proceed to [Step 7: Reference Trigger Map](07-reference-trigger-map.md)**
Before sketching, crystallize this scenario's strategy into a Value Trigger Chain.
Before sketching, identify the relevant Trigger Map context for this scenario.
---

132
src/workflows/4-ux-design/data/scenario-init/07-create-vtc.md
View File

@ -1,132 +0,0 @@
# 6. Create Value Trigger Chain for Scenario
**Purpose:** Crystallize scenario strategy before sketching
---
## Why Now?
You've defined:
- ✅ Feature that delivers value
- ✅ Entry point
- ✅ Mental state
- ✅ Mutual success
- ✅ Shortest path
**Perfect time to create a VTC** - you have everything needed.
This VTC will guide every page, every interaction, every word in this scenario.
---
## Agent Instructions
> "Before we start sketching, let's create a Value Trigger Chain for this scenario.
>
> This captures the strategic essence:
> - Business Goal (from mutual success - business side)
> - Solution (this scenario/feature)
> - User (primary target group)
> - Driving Forces (from mental state and Trigger Map)
> - Customer Awareness (where they start → where they end up)
>
> This takes 10-15 minutes since we have the Trigger Map. It'll guide every design decision.
>
> Shall we create the scenario VTC?"
---
## Route to VTC Workshop
**If user agrees:**
Load and execute the VTC Workshop Router:
`{project-root}/_bmad/wds/workflows/1-project-brief/vtc-workshop/workflow.md`
**Since Trigger Map exists:** Router will likely send you to **Selection Workshop** (10-15 mins).
---
## Leverage Context
**Important:** You have rich context from scenario init! Use it:
- **Business Goal:** From mutual success (business side)
- **Solution:** The feature/scenario just defined
- **User:** Primary target group from Trigger Map
- **Entry Point/Mental State:** For Customer Awareness starting point
- **Mutual Success:** For Customer Awareness ending point
- **Driving Forces:** From Trigger Map for this user
**Scenario init IS strategic discovery** - use it!
---
## Save VTC
VTC should be saved to:
`{output_folder}/C-UX-Scenarios/[scenario-name]/vtc.yaml`
Example: `docs/C-UX-Scenarios/1.1-parent-onboarding/vtc.yaml`
---
## Confirm and Set Expectation
> "Excellent! This scenario now has its own VTC.
>
> As we sketch each page, we'll use this VTC to ensure:
> - Every interaction addresses these driving forces
> - Every message moves them through awareness
> - Every design choice serves mutual success
>
> The VTC is your strategic compass. When in doubt, check the VTC.
>
> Ready to start sketching?"
---
## If User Declines VTC
**If user says:** "Let's skip the VTC and sketch"
**Response:**
> "I strongly recommend creating the VTC first. Here's why:
>
> Without it, design becomes opinion-based:
> - 'I like this button here'
> - 'This color feels right'
> - 'Users probably want this'
>
> With VTC, design becomes strategic:
> - 'This button triggers their wish to [driving force]'
> - 'This message addresses their fear of [driving force]'
> - 'This moves them from [awareness start] to [awareness end]'
>
> It takes 15 minutes and saves hours of redesign.
>
> Still want to skip?"
**If still declines:**
> "Okay, but I recommend creating VTC before presenting to stakeholders. You can add it anytime using:
> `{project-root}/_bmad/wds/workflows/1-project-brief/vtc-workshop/workflow.md`"
Then proceed to sketching without VTC (not ideal).
---
## Next Step
After VTC is created:
**Start sketching the scenario journey!**
Each sketch should:
- Serve the VTC driving forces
- Move user through awareness progression
- Support shortest path to mutual success
---
*Strategic clarity achieved - now sketch with purpose!*

80
src/workflows/4-ux-design/data/scenario-init/07-reference-trigger-map.md Normal file
View File

@ -0,0 +1,80 @@
# 7. Reference Trigger Map for Scenario
**Purpose:** Identify the relevant Trigger Map nodes for this scenario before sketching
---
## Why Now?
You've defined:
- Feature that delivers value
- Entry point
- Mental state
- Mutual success
- Shortest path
**Perfect time to anchor the scenario to the Trigger Map.** Pick the specific business goal, persona, and driving forces that apply to this scenario.
---
## Agent Instructions
> "Before we start sketching, let's identify the Trigger Map context for this scenario.
>
> From your Trigger Map, which of these apply to this scenario?
> - **Business Goal** — which goal does this scenario serve?
> - **User** — which persona is this scenario for?
> - **Driving Forces** — which positive and negative drivers are most relevant?
>
> This anchors every design decision to strategy."
---
## Process
1. **Load the Trigger Map** from `{output_folder}/B-Trigger-Map/00-trigger-map.md`
2. **Present the business goals** — ask which one this scenario primarily serves
3. **Present the personas** — confirm which persona this scenario targets
4. **Present driving forces** for that persona — ask which 2-4 are most relevant here
5. **Summarize** the selected context
This is a **selection exercise**, not a workshop. It takes 2-3 minutes.
---
## Save Context
Note the selected Trigger Map context in the scenario overview file:
```markdown
## Trigger Map Context
**Business Goal:** [selected goal from Trigger Map]
**Persona:** [selected persona]
**Key Driving Forces:**
- Positive: [selected positive drivers]
- Negative: [selected negative drivers]
```
---
## If No Trigger Map Exists
If the Trigger Map hasn't been created yet:
- Inform the user: "There's no Trigger Map for this project yet. I'd recommend completing Phase 2 (Trigger Mapping) first — it gives us the strategic foundation for design decisions."
- If the user wants to proceed anyway, use whatever business context is available from the Product Brief and note the gap.
---
## Next Step
**Start sketching the scenario journey!**
Each sketch should:
- Serve the selected driving forces
- Support the shortest path to mutual success
- Address the target persona's needs
---
*Strategic context identified — now sketch with purpose!*

4
src/workflows/4-ux-design/data/scenario-init/scenario-init-guide.md
View File

@ -43,9 +43,9 @@ What does winning look like for both business and user?
Minimum steps from starting point to mutual success
### [7. Create Value Trigger Chain](07-create-vtc.md)
### [7. Reference Trigger Map](07-reference-trigger-map.md)
Crystallize scenario strategy before sketching
Identify the relevant Trigger Map context for this scenario
---

2
src/workflows/6-asset-generation/data/content-creation-workshop-guide.md
View File

@ -285,7 +285,7 @@ DESIGNER: "Make headline more fear-focused"
**Micro-Steps:**
- `steps/workflow.md` - Sequential execution guide
- `steps/step-00-define-purpose.md`
- `steps/step-01-load-vtc-context.md`
- `steps/step-01-load-trigger-map-context.md`
- `steps/step-02-awareness-strategy.md`
- `steps/step-03-action-filter.md`
- `steps/step-04-empowerment-frame.md`

2
src/workflows/6-asset-generation/steps-c/step-00-define-purpose.md
View File

@ -1,7 +1,7 @@
---
name: 'step-00-define-purpose'
description: 'Define the measurable job and purpose for content before generation begins'
nextStepFile: './step-01-load-vtc-context.md'
nextStepFile: './step-01-load-trigger-map-context.md'
---
# Step 0: Define Content Purpose

147
src/workflows/6-asset-generation/steps-c/step-01-load-trigger-map-context.md Normal file
View File

@ -0,0 +1,147 @@
---
name: 'step-01-load-trigger-map-context'
description: 'Establish the strategic foundation by loading relevant Trigger Map context for content creation'
nextStepFile: './step-02-awareness-strategy.md'
---
# Step 1: Load Trigger Map Context
## STEP GOAL:
Load the relevant Trigger Map context — WHO we are serving, WHAT motivates them, and WHERE they are in their awareness journey — so that all content decisions are anchored in strategy, not guesswork.
## MANDATORY EXECUTION RULES (READ FIRST):
### Universal Rules:
- NEVER generate content without user input
- CRITICAL: Read the complete step file before taking any action
- CRITICAL: When loading next step with 'C', ensure entire file is read
- YOU ARE A FACILITATOR, not a content generator
- YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
### Role Reinforcement:
- You are a strategic content analyst loading the Trigger Map foundation
- If you already have been given a name, communication_style and identity, continue to use those while playing this new role
- We engage in collaborative dialogue, not command-response
- You bring strategic methodology, user brings their project knowledge
- Maintain a thorough, investigative tone — the context must be correct before proceeding
### Step-Specific Rules:
- Focus ONLY on loading and validating the Trigger Map context
- FORBIDDEN to generate content text or apply awareness strategy in this step
- If no Trigger Map exists, flag the gap and work with whatever context is available
- Ensure all fields are populated before proceeding
## EXECUTION PROTOCOLS:
- Follow the Sequence of Instructions exactly
- Document Trigger Map context for traceability
- Check for Trigger Map in project documentation before asking user
- FORBIDDEN to proceed without confirmed strategic context
## CONTEXT BOUNDARIES:
- Available context: Purpose definition from Step 0, project configuration
- Focus: Loading and validating the correct Trigger Map context for this content
- Limits: Do not apply the context yet — just load and confirm it
- Dependencies: Purpose definition from Step 0
## Sequence of Instructions (Do not deviate, skip, or optimize)
### 1. Load the Trigger Map
Search project documentation:
- Check `{output_folder}/B-Trigger-Map/00-trigger-map.md` (the hub document)
- Check persona documents in `{output_folder}/B-Trigger-Map/`
- If no Trigger Map folder exists, check Product Brief for business context
### 2. Identify the Relevant Context
Ask: **"Which business goal and persona does this content serve?"**
- Present the business goals from the Trigger Map — which one applies?
- Present the personas — which one is the target audience for this content?
- Present driving forces for that persona — which are most relevant?
### 3. Present and Confirm Context
Display the selected context:
```
Business Goal: [selected goal from Trigger Map]
Persona: [persona name and description]
Driving Forces:
- Positive: [relevant positive drivers]
- Negative: [relevant negative drivers]
Customer Awareness: [START level] → [END level]
```
Ask: **"Is this the right strategic context for this content? Any adjustments?"**
### 4. Handle Missing Trigger Map
If no Trigger Map exists:
- Explain that the Trigger Map (Phase 2) provides the strategic foundation for content
- Recommend completing Phase 2 first for best results
- If the user wants to proceed anyway, use whatever context is available from the Product Brief
- Note the gap and flag that content may need revision after the Trigger Map is completed
### 5. Document Context
Save the confirmed context:
```yaml
trigger_map_context:
business_goal: "[goal text]"
persona:
name: "[persona name]"
description: "[brief persona description]"
driving_forces:
positive: "[relevant positive drivers]"
negative: "[relevant negative drivers]"
customer_awareness:
start: "[awareness level where user begins]"
end: "[awareness level we want them to reach]"
```
### 6. Present MENU OPTIONS
Display: **"Select an Option:** [C] Continue"
#### Menu Handling Logic:
- IF C: Save context, then load, read entire file, then execute {nextStepFile}
- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#6-present-menu-options)
#### EXECUTION RULES:
- ALWAYS halt and wait for user input after presenting menu
- ONLY proceed to next step when user selects 'C'
- User can chat or ask questions — always respond and then end with display again of the menu options
## CRITICAL STEP COMPLETION NOTE
ONLY WHEN C is selected and the Trigger Map context is confirmed and documented will you load {nextStepFile} to begin applying the Customer Awareness Strategy.
---
## SYSTEM SUCCESS/FAILURE METRICS
### SUCCESS:
- Trigger Map context is identified and loaded
- All fields are populated (goal, persona, driving forces, awareness)
- User confirms this is the correct context for this content
- Context is documented for traceability
### FAILURE:
- Proceeding without confirmed strategic context
- Generating content text in this step
- Applying awareness strategy before context is loaded
- Not waiting for user input at menu
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

150
src/workflows/6-asset-generation/steps-c/step-01-load-vtc-context.md
View File

@ -1,150 +0,0 @@
---
name: 'step-01-load-vtc-context'
description: 'Establish the strategic foundation by loading Value Trigger Chain context for content creation'
nextStepFile: './step-02-awareness-strategy.md'
---
# Step 1: Load VTC Context
## STEP GOAL:
Load the Value Trigger Chain (VTC) that defines the strategic context — WHO we are serving, WHAT motivates them, and WHERE they are in their awareness journey — so that all content decisions are anchored in strategy, not guesswork.
## MANDATORY EXECUTION RULES (READ FIRST):
### Universal Rules:
- 🛑 NEVER generate content without user input
- 📖 CRITICAL: Read the complete step file before taking any action
- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
- 📋 YOU ARE A FACILITATOR, not a content generator
- ✅ YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
### Role Reinforcement:
- ✅ You are a strategic content analyst loading the VTC foundation
- ✅ If you already have been given a name, communication_style and identity, continue to use those while playing this new role
- ✅ We engage in collaborative dialogue, not command-response
- ✅ You bring strategic methodology for VTC loading, user brings their project knowledge
- ✅ Maintain a thorough, investigative tone — the VTC must be correct before proceeding
### Step-Specific Rules:
- 🎯 Focus ONLY on loading and validating the VTC context
- 🚫 FORBIDDEN to generate content text or apply awareness strategy in this step
- 💬 If no VTC exists, offer to route to VTC Workshop or flag risk
- 📋 Ensure all VTC fields are populated before proceeding
## EXECUTION PROTOCOLS:
- 🎯 Follow the Sequence of Instructions exactly
- 💾 Document VTC context for traceability
- 📖 Check for existing VTCs in project documentation before asking user
- 🚫 FORBIDDEN to proceed without a confirmed VTC
## CONTEXT BOUNDARIES:
- Available context: Purpose definition from Step 0, project configuration
- Focus: Loading and validating the correct VTC for this content
- Limits: Do not apply the VTC yet — just load and confirm it
- Dependencies: Purpose definition from Step 0
## Sequence of Instructions (Do not deviate, skip, or optimize)
### 1. Check for Existing VTCs
Search project documentation for VTCs:
- Check project documentation and scenario definitions
- Check page specifications
- Look for VTC references in trigger map
### 2. Identify the Correct VTC
Ask: **"Which VTC applies to this content section?"**
- Is there an existing VTC for this page/scenario?
- If multiple VTCs exist, which one is active here?
- If no VTC exists, offer to create one (route to VTC Workshop) or flag risk
### 3. Present and Confirm VTC
Display the selected VTC:
```
Business Goal: [goal]
Solution: [solution being designed]
User: [persona name and description]
Driving Forces:
- Wish: [positive motivator]
- Fear: [negative motivator]
Customer Awareness: [START level] → [END level]
```
Ask: **"Is this the correct VTC for this content? Any adjustments needed?"**
### 4. Handle Missing VTC
If no VTC exists:
- Explain that VTC is needed for strategic content
- Ask: "Should we create a VTC now?"
- If YES: Route to VTC Workshop
- If NO: Flag risk and continue with limited context
### 5. Document VTC Context
Save the confirmed VTC reference:
```yaml
vtc_reference:
business_goal: "[goal text]"
solution: "[solution name/description]"
user:
name: "[persona name]"
description: "[brief persona description]"
driving_forces:
positive: "[wish/aspiration]"
negative: "[fear/frustration]"
customer_awareness:
start: "[awareness level where user begins]"
end: "[awareness level we want them to reach]"
```
### 6. Present MENU OPTIONS
Display: **"Select an Option:** [C] Continue"
#### Menu Handling Logic:
- IF C: Save VTC context, then load, read entire file, then execute {nextStepFile}
- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#6-present-menu-options)
#### EXECUTION RULES:
- ALWAYS halt and wait for user input after presenting menu
- ONLY proceed to next step when user selects 'C'
- User can chat or ask questions — always respond and then end with display again of the menu options
## CRITICAL STEP COMPLETION NOTE
ONLY WHEN C is selected and the VTC is confirmed and documented will you load {nextStepFile} to begin applying the Customer Awareness Strategy.
---
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
### ✅ SUCCESS:
- VTC is identified and loaded
- All VTC fields are populated (goal, solution, user, driving forces, awareness)
- User confirms this is the correct VTC for this content
- VTC is documented for traceability
### ❌ SYSTEM FAILURE:
- Proceeding without a confirmed VTC
- Generating content text in this step
- Applying awareness strategy before VTC is loaded
- Not offering VTC Workshop route when no VTC exists
- Not waiting for user input at menu
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

2
src/workflows/6-asset-generation/workflow-content.md
View File

@ -36,7 +36,7 @@ Execute steps in `./steps-c/`:
| Step | File | Purpose |
|------|------|---------|
| 00 | step-00-define-purpose.md | Define content purpose |
| 01 | step-01-load-vtc-context.md | Load VTC context |
| 01 | step-01-load-trigger-map-context.md | Load Trigger Map context |
| 02 | step-02-awareness-strategy.md | Awareness strategy |
| 03 | step-03-action-filter.md | Action mapping filter |
| 04 | step-04-empowerment-frame.md | Empowerment framing |