Replace VTC terminology with Trigger Map/strategic context across all workflows
Systematic cleanup of Value Trigger Chain (VTC) references in 60 files across all phases. VTC is replaced with context-appropriate terms: - "Trigger Map" when referencing the Phase 2 artifact - "Strategic context" when referencing the extracted business/persona/forces data - "Value Proposition" for customer-facing value descriptions Remaining VTC references are only in VTC Workshop definition files (vtc-workshop/, create-vtc steps) which will be addressed when those workflows are redesigned. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Mårten Angner
parent
c5a53aad64
commit
437c10cc2f
|
|
@ -53,7 +53,7 @@
|
|||
- Time is tight
|
||||
|
||||
**Process:**
|
||||
1. Load VTC for context
|
||||
1. Load Trigger Map for context
|
||||
2. Consider Customer Awareness
|
||||
3. Apply Golden Circle (WHY → HOW → WHAT)
|
||||
4. Generate options
|
||||
|
|
@ -73,7 +73,7 @@ Load: `{project-root}/_bmad/wds/workflows/6-asset-generation/`
|
|||
|
||||
**6-Step Framework:**
|
||||
1. Define purpose & success criteria
|
||||
2. Load VTC context
|
||||
2. Load Trigger Map context
|
||||
3. Apply Customer Awareness strategy
|
||||
4. Filter with Action Mapping
|
||||
5. Frame with Badass Users
|
||||
|
|
@ -95,7 +95,7 @@ Load: `{project-root}/_bmad/wds/workflows/6-asset-generation/`
|
|||
|
||||
---
|
||||
|
||||
### 2. Value Trigger Chain (VTC)
|
||||
### 2. Trigger Map
|
||||
**Strategic foundation**
|
||||
|
||||
- Business Goal: What are we trying to achieve?
|
||||
|
|
@ -167,7 +167,7 @@ Features (WHAT): 10K templates, smart pricing, e-signatures
|
|||
|
||||
**Think of them as lenses, not sequential steps:**
|
||||
|
||||
1. **VTC** = Which driving force to trigger?
|
||||
1. **Trigger Map** = Which driving force to trigger?
|
||||
2. **Customer Awareness** = What language can they understand?
|
||||
3. **Golden Circle** = In what order should I present?
|
||||
4. **Action Mapping** = Is this enabling action?
|
||||
|
|
@ -203,7 +203,7 @@ Features (WHAT): 10K templates, smart pricing, e-signatures
|
|||
- Golden Circle: ⭐⭐⭐
|
||||
- Badass Users: ⭐⭐
|
||||
- Action Mapping: ⭐
|
||||
- VTC: Always loaded
|
||||
- Trigger Map: Always loaded
|
||||
- Content Purpose: Always defined
|
||||
|
||||
### Feature Description
|
||||
|
|
@ -211,7 +211,7 @@ Features (WHAT): 10K templates, smart pricing, e-signatures
|
|||
- Badass Users: ⭐⭐⭐
|
||||
- Customer Awareness: ⭐⭐
|
||||
- Golden Circle: ⭐
|
||||
- VTC: Always loaded
|
||||
- Trigger Map: Always loaded
|
||||
- Content Purpose: Always defined
|
||||
|
||||
### Error Messages
|
||||
|
|
@ -245,7 +245,7 @@ Features (WHAT): 10K templates, smart pricing, e-signatures
|
|||
**Before creating any strategic content:**
|
||||
|
||||
1. **Define purpose** - What job does this do?
|
||||
2. **Load VTC** - Which driving forces?
|
||||
2. **Load Trigger Map** - Which driving forces?
|
||||
3. **Check awareness** - Where are users?
|
||||
4. **Apply Golden Circle** - WHY → HOW → WHAT
|
||||
5. **Filter with Action** - Does it enable action?
|
||||
|
|
|
|||
|
|
@ -15,8 +15,7 @@
|
|||
### 1. Load Strategic Context
|
||||
|
||||
**Ask yourself:**
|
||||
- Is there a VTC (Value Trigger Chain) for this page/scenario?
|
||||
- What's in the Trigger Map?
|
||||
- What's in the Trigger Map for this page/scenario?
|
||||
- What does the Product Brief say?
|
||||
|
||||
**If missing:** Suggest creating one first. Design without strategy is decoration.
|
||||
|
|
@ -37,7 +36,7 @@
|
|||
|
||||
### 3. Identify User Driving Forces
|
||||
|
||||
**From the VTC/Trigger Map, ask:**
|
||||
**From the Trigger Map, ask:**
|
||||
- What positive driving forces should we trigger? (wishes, desires, aspirations)
|
||||
- What negative driving forces should we address? (fears, frustrations, anxieties)
|
||||
|
||||
|
|
@ -86,7 +85,7 @@ Hero Section:
|
|||
|
||||
Before finalizing any design:
|
||||
|
||||
- [ ] **VTC Connection** - Which driving force does this serve?
|
||||
- [ ] **Trigger Map** - Which driving force does this serve?
|
||||
- [ ] **Business Goal** - How does this support our objectives?
|
||||
- [ ] **Customer Awareness** - Appropriate for their awareness stage?
|
||||
- [ ] **Golden Circle** - WHY before HOW before WHAT?
|
||||
|
|
@ -98,7 +97,7 @@ Before finalizing any design:
|
|||
|
||||
**If you can't connect a design choice to strategy:**
|
||||
1. It might not be needed (remove it)
|
||||
2. You need more strategic context (ask for VTC/Trigger Map)
|
||||
2. You need more strategic context (ask for Trigger Map)
|
||||
3. There's a better alternative (explore options)
|
||||
|
||||
**Never guess.** Always design with intent.
|
||||
|
|
@ -107,7 +106,6 @@ Before finalizing any design:
|
|||
|
||||
## Related Resources
|
||||
|
||||
- **VTC Workshop:** `../../workflows/1-project-brief/_vtc-workshop/`
|
||||
- **Trigger Mapping:** `../../docs/method/phase-2-trigger-mapping-guide.md`
|
||||
- **Customer Awareness:** `../../docs/models/customer-awareness-cycle.md`
|
||||
- **Golden Circle:** `../../docs/models/golden-circle.md`
|
||||
|
|
|
|||
|
|
@ -311,7 +311,7 @@ src/workflows/3-scenarios/data/validation-standards.md
|
|||
**Initial Load (start of Phase 3):**
|
||||
- Product Brief (all 4 documents from Phase 1)
|
||||
- Trigger Map (all documents from Phase 2)
|
||||
- VTCs (Value Trigger Chains)
|
||||
- Strategic context (business goal, persona, driving forces)
|
||||
|
||||
**After each scenario outlined:**
|
||||
```markdown
|
||||
|
|
|
|||
|
|
@ -105,18 +105,16 @@ design_system:
|
|||
|
||||
---
|
||||
|
||||
### 3. Value Trigger Chain (VTC)
|
||||
### 3. Strategic Context (from Trigger Map)
|
||||
**Strategic benchmark for early decisions**
|
||||
|
||||
Created in Step 4 (early in the brief) to provide strategic grounding:
|
||||
Extracted from the Trigger Map to provide strategic grounding:
|
||||
- Business goal
|
||||
- Solution context
|
||||
- User
|
||||
- Target group / persona
|
||||
- Driving forces (positive + negative)
|
||||
- Customer awareness progression
|
||||
|
||||
**See:** VTC micro-guide for Freya (also relevant for Saga)
|
||||
|
||||
---
|
||||
|
||||
### 4. Business Model
|
||||
|
|
|
|||
|
|
@ -562,9 +562,9 @@ Scenario adds:
|
|||
|
||||
---
|
||||
|
||||
## Trigger Map → VTC Connection
|
||||
## Trigger Map → Design Context
|
||||
|
||||
**VTC is extracted from Trigger Map:**
|
||||
**For a specific design task, extract the relevant slice:**
|
||||
|
||||
```
|
||||
Trigger Map (Comprehensive):
|
||||
|
|
@ -573,14 +573,14 @@ Trigger Map (Comprehensive):
|
|||
├── 12 detailed personas
|
||||
└── 40+ driving forces
|
||||
|
||||
VTC (Focused):
|
||||
Design Context (Focused):
|
||||
├── 1 business goal
|
||||
├── 1 user/persona
|
||||
├── 1 persona
|
||||
├── 1 solution context
|
||||
└── 3-5 key driving forces
|
||||
```
|
||||
|
||||
**VTC is the "working copy" for a specific design task.**
|
||||
**The focused context is the "working copy" for a specific design task.**
|
||||
|
||||
---
|
||||
|
||||
|
|
@ -633,7 +633,7 @@ graph TD
|
|||
**Process:**
|
||||
1. Create new version (v2)
|
||||
2. Document what changed and why
|
||||
3. Update any VTCs derived from map
|
||||
3. Review impact on active design work
|
||||
4. Keep old version for reference
|
||||
|
||||
---
|
||||
|
|
@ -642,7 +642,7 @@ graph TD
|
|||
|
||||
- **Phase 2 Workflow:** `../../workflows/2-trigger-mapping/`
|
||||
- **Impact/Effect Mapping Model:** `../../docs/models/impact-effect-mapping.md`
|
||||
- **VTC Guide:** `../../docs/method/value-trigger-chain-guide.md`
|
||||
- **Trigger Mapping Guide:** `../../docs/method/phase-2-trigger-mapping-guide.md`
|
||||
- **Customer Awareness Cycle:** `../../docs/models/customer-awareness-cycle.md`
|
||||
- **Feature Impact Analysis:** Prioritization method based on Impact Mapping
|
||||
|
||||
|
|
|
|||
|
|
@ -90,7 +90,7 @@ Every visual you create should answer: "Why does this design choice trigger the
|
|||
|
||||
You (the designer) act as the bridge between Freya (WDS Designer Agent in Cursor) and Eira (Visual Designer in Nano Banana/image generation tool).
|
||||
|
||||
### Value to Customer (VTC):
|
||||
### Value Proposition:
|
||||
[What value does this product deliver? Why should users care?]
|
||||
|
||||
### Target Audience:
|
||||
|
|
@ -138,7 +138,7 @@ This context will guide all visual generation for this project. Reference these
|
|||
|
||||
```markdown
|
||||
## 🎯 STRATEGIC BRIEF
|
||||
[Why this screen/component matters - connects to VTC and triggers]
|
||||
[Why this screen/component matters - connects to Trigger Map and driving forces]
|
||||
|
||||
## 📋 PROMPT FOR EIRA
|
||||
────────────────────────────────────────────────────────────────
|
||||
|
|
@ -209,7 +209,7 @@ AVOID:
|
|||
### Step 2: Freya Reads Context
|
||||
- Reads: `1-project-brief/product-brief.md`
|
||||
- Reads: `2-strategy/trigger-map.md`
|
||||
- Reads: `2-strategy/vtc.md`
|
||||
- Reads: `2-strategy/trigger-map.md`
|
||||
- Analyzes: Target audience, psychological triggers, brand positioning
|
||||
|
||||
### Step 3: Freya Generates Prompt
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ web_bundle: true
|
|||
|
||||
# Phase 3: Synthesize & Present
|
||||
|
||||
**Goal:** Synthesize the section explorations into a complete alignment document, optionally create a VTC, and present for stakeholder approval.
|
||||
**Goal:** Synthesize the section explorations into a complete alignment document, optionally create strategic context, and present for stakeholder approval.
|
||||
|
||||
**Your Role:** Reflect back what was captured, compile the alignment document, and guide the user through the approval process.
|
||||
|
||||
|
|
|
|||
|
|
@ -47,7 +47,7 @@ Present the completed alignment document and guide the user through the stakehol
|
|||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Available context: Complete alignment document (and VTC if created)
|
||||
- Available context: Complete alignment document (and strategic context if created)
|
||||
- Focus: Presentation and approval process
|
||||
- Limits: Do not create signoff document until alignment is accepted
|
||||
- Dependencies: step-03b (and optionally step-03c) must be completed
|
||||
|
|
|
|||
|
|
@ -87,7 +87,7 @@ Explore 10 alignment document sections (flexible order):
|
|||
|------|------|---------|
|
||||
| 03a | Reflect Back | Synthesize understanding, confirm |
|
||||
| 03b | Synthesize Document | Create alignment document |
|
||||
| 03c | Create VTC | Value Trigger Chain (refs `1-project-brief/vtc-workshop/`) |
|
||||
| 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*)
|
||||
|
|
|
|||
|
|
@ -122,7 +122,7 @@ Store as `brief_level`: complete | simplified
|
|||
**How deep should the user/market analysis go?** (Only ask if greenfield AND not simple)
|
||||
|
||||
[A] **Full Trigger Map** (Recommended for complex) -> Phase 2 enabled
|
||||
[B] **Simplified VTC** -> VTC in Phase 1, skip Phase 2
|
||||
[B] **Simplified** -> Strategic context in Phase 1, skip Phase 2
|
||||
[C] **Skip** (Not recommended) -> Skip Phase 2
|
||||
|
||||
Store as `strategic_analysis`: full | simplified | skip
|
||||
|
|
|
|||
|
|
@ -47,7 +47,7 @@ Phase 0: Project Setup
|
|||
├─→ Tech stack (optional)
|
||||
├─→ Component library (optional)
|
||||
├─→ Brief level (complete/simplified)
|
||||
├─→ Strategic analysis (full/VTC/skip)
|
||||
├─→ Strategic analysis (full/simplified/skip)
|
||||
├─→ Create folder structure
|
||||
└─→ Generate project outline
|
||||
│
|
||||
|
|
@ -102,4 +102,4 @@ Phase 0: Project Setup
|
|||
| Tech Stack | react / vue / wordpress / etc. | Delivery format guidance |
|
||||
| Component Library | shadcn / tailwind / custom | Skip or enable Phase 5 |
|
||||
| Brief Level | complete / simplified | Depth of Phase 1 |
|
||||
| Strategic Analysis | full / simplified / skip | Full Trigger Map or VTC in brief |
|
||||
| Strategic Analysis | full / simplified / skip | Full Trigger Map or simplified in brief |
|
||||
|
|
|
|||
|
|
@ -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`
|
||||
Load, read full file, and execute: `step-04-create-vtc.md` (Create Trigger Map)
|
||||
|
|
|
|||
|
|
@ -42,7 +42,7 @@ Guide the user through a quick, focused session to capture the essential project
|
|||
## CONTEXT BOUNDARIES:
|
||||
- Available context: Project configuration, user name, communication language
|
||||
- Focus: Essential project context in minimal time
|
||||
- Limits: No deep competitive analysis, no VTC, no detailed positioning
|
||||
- Limits: No deep competitive analysis, no Trigger Map, no detailed positioning
|
||||
- Dependencies: Config loaded from `{project-root}/_bmad/wds/config.yaml`
|
||||
|
||||
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
||||
|
|
|
|||
|
|
@ -73,7 +73,7 @@ The dialog should capture:
|
|||
Mark Step 3 complete in `dialog/progress-tracker.md` progress tracker.
|
||||
|
||||
### 6. Present MENU OPTIONS
|
||||
Display: "**Select an Option:** [C] Continue to Create VTC"
|
||||
Display: "**Select an Option:** [C] Continue to Create Trigger Map"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
|
||||
|
|
|
|||
|
|
@ -1,16 +1,16 @@
|
|||
---
|
||||
name: 'step-04-create-vtc'
|
||||
description: 'Create a simplified Value Trigger Chain to crystallize strategic thinking early'
|
||||
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 Value Trigger Chain
|
||||
# Step 4: Create Trigger Map
|
||||
|
||||
## STEP GOAL:
|
||||
Create a simplified Value Trigger Chain (VTC) to crystallize strategic thinking early and guide all subsequent discovery. The VTC serves as a strategic benchmark — capturing Business Goal, Solution, User, Driving Forces, and Customer Awareness.
|
||||
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):
|
||||
|
||||
|
|
@ -22,44 +22,44 @@ Create a simplified Value Trigger Chain (VTC) to crystallize strategic thinking
|
|||
- ✅ 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 VTC based on available context
|
||||
- ✅ 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 VTC leveraging existing Vision and Positioning context
|
||||
- 🎯 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
|
||||
- 📋 VTC is saved separately, NOT added to brief document yet (that happens at Step 12)
|
||||
- 📋 Trigger Map is saved separately, NOT added to brief document yet (that happens at Step 12)
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
- 🎯 Produce a complete VTC (Business Goal, Solution, User, Driving Forces, Customer Awareness)
|
||||
- 💾 Save VTC to `{output_folder}/A-Product-Brief/vtc-primary.yaml`
|
||||
- 📖 Route to VTC Workshop at `../vtc-workshop/workflow.md` if user agrees
|
||||
- 🎯 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: VTC creation as strategic benchmark
|
||||
- Limits: At this stage, estimates are fine — VTC will be refined later
|
||||
- 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 VTC to User
|
||||
Explain VTC components and purpose:
|
||||
### 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 VTC now?"
|
||||
Explain this takes 20-30 minutes and is incredibly valuable for strategic clarity. Ask: "Shall we create the Trigger Map now?"
|
||||
|
||||
### 2. Route to VTC Workshop
|
||||
**If user agrees:** Load and execute the VTC 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.
|
||||
### 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:
|
||||
|
|
@ -69,11 +69,11 @@ Use existing strategic work:
|
|||
- Driving Forces: Infer from positioning (need/opportunity, differentiator)
|
||||
- Customer Awareness: Infer from positioning (where they are now)
|
||||
|
||||
### 4. Save VTC
|
||||
Save to `{output_folder}/A-Product-Brief/vtc-primary.yaml`. VTC is saved but NOT yet added to brief document — that happens during final synthesis.
|
||||
### 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 VTC will serve as strategic benchmark. As discovery continues, we use this VTC to ensure everything aligns. If contradictions arise, either VTC needs adjustment or the discovery finding does not serve strategy.
|
||||
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.
|
||||
|
|
@ -82,8 +82,8 @@ Record: Value/Transformation/Cost framework decisions, how value and transformat
|
|||
|
||||
Mark Step 4 complete in `dialog/progress-tracker.md` progress tracker.
|
||||
|
||||
### 7. If User Declines VTC
|
||||
If user says "Let's skip the VTC 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.
|
||||
### 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"
|
||||
|
|
@ -98,23 +98,23 @@ Display: "**Select an Option:** [C] Continue to Business Model"
|
|||
- User can chat or ask questions - always respond and then redisplay menu options
|
||||
|
||||
## CRITICAL STEP COMPLETION NOTE
|
||||
ONLY WHEN VTC is created (or user declines) and completion is confirmed will you then load and read fully `{nextStepFile}`.
|
||||
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:
|
||||
- VTC created with all components or user explicitly declined
|
||||
- Trigger Map created with all components or user explicitly declined
|
||||
- Existing Vision and Positioning context leveraged (not starting from zero)
|
||||
- VTC saved to correct output location
|
||||
- User understands VTC purpose as strategic benchmark
|
||||
- Trigger Map saved to correct output location
|
||||
- User understands Trigger Map purpose as strategic benchmark
|
||||
- Agent dialog updated
|
||||
|
||||
### ❌ SYSTEM FAILURE:
|
||||
- Started VTC from zero without using existing context
|
||||
- Generated VTC components without user input
|
||||
- Did not save VTC to correct location
|
||||
- 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.
|
||||
|
|
|
|||
|
|
@ -41,7 +41,7 @@ Help the user identify and understand their business model (B2B, B2C, or both) t
|
|||
- 🚫 Avoid generic questions — adapt to context
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
- Available context: Vision, Positioning, VTC from previous steps
|
||||
- Available context: Vision, Positioning, Trigger Map from previous steps
|
||||
- Focus: Business model determination and implications
|
||||
- Limits: Not detailed customer profiles yet — that is next steps
|
||||
- Dependencies: Steps 1-4 completed
|
||||
|
|
|
|||
|
|
@ -48,7 +48,7 @@ Help the user define their ideal business customer profile, including company ch
|
|||
|
||||
## CONTEXT CARRY-FORWARD (READ BEFORE ASKING QUESTIONS):
|
||||
- From Step 3 (Positioning): You already know the target segment and market positioning. DO NOT re-ask "who is this for?" — instead reference: "In positioning, we identified [target segment]. Now let's go deeper into the business customer profile."
|
||||
- From VTC Workshop (if completed): You may already have Value Trigger Chains with user archetypes. Reference those rather than starting from scratch.
|
||||
- From Trigger Map Workshop (if completed): You may already have Trigger Maps with user archetypes. Reference those rather than starting from scratch.
|
||||
- BUILD ON prior answers. If the user already described their customers during positioning, acknowledge that: "You mentioned [X] earlier. Let's build on that — tell me more about the decision-making structure."
|
||||
- RULE: If the user says "I already told you this," immediately acknowledge, reference the earlier answer, and ask only for NEW information.
|
||||
|
||||
|
|
|
|||
|
|
@ -41,7 +41,7 @@ Help the user define their ideal customer profile by exploring who we are design
|
|||
- 🚫 Avoid superficial user descriptions
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
- Available context: Vision, positioning, business model, VTC from previous steps
|
||||
- Available context: Vision, positioning, business model, Trigger Map from previous steps
|
||||
- Focus: User identification and behavioral profiling
|
||||
- Limits: Not detailed personas (that comes in Phase 2) — focus on who and why
|
||||
- Dependencies: Steps 1-5 (or 1-6 if B2B) completed
|
||||
|
|
@ -49,7 +49,7 @@ Help the user define their ideal customer profile by exploring who we are design
|
|||
## CONTEXT CARRY-FORWARD (READ BEFORE ASKING QUESTIONS):
|
||||
- From Step 3 (Positioning): Target segment already defined. DO NOT re-ask "who are your users?" — instead reference: "We've established your positioning targets [segment]. Now let's build behavioral profiles."
|
||||
- From Step 6 (Business Customers, if B2B): Buyer vs end-user distinction already captured. Reference it: "We defined the business buyers in the last step. Now let's focus on the end users who actually interact with the product."
|
||||
- From VTC Workshop (if completed): User archetypes may exist. Use them as starting points rather than re-discovering.
|
||||
- From Trigger Map Workshop (if completed): User archetypes may exist. Use them as starting points rather than re-discovering.
|
||||
- RULE: If the user says "I already told you this," immediately acknowledge, reference the earlier answer, and ask only for NEW information not yet captured.
|
||||
|
||||
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
||||
|
|
|
|||
|
|
@ -40,7 +40,7 @@ Help the user explore and define what success looks like through conversational
|
|||
- Avoid generating content without user input
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
- Available context: Vision, positioning, VTC, business model, target users, product concept
|
||||
- Available context: Vision, positioning, Trigger Map, business model, target users, product concept
|
||||
- Focus: Measurable success criteria with primary/secondary metrics and timeline
|
||||
- Limits: Not business model changes, not competitive analysis
|
||||
- Dependencies: Steps 1-7a completed
|
||||
|
|
|
|||
|
|
@ -40,7 +40,7 @@ Help user explore alternatives and discover their unfair advantage. Explore what
|
|||
- Avoid generating content without user input
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
- Available context: Vision, positioning, VTC, business model, users, success criteria
|
||||
- Available context: Vision, positioning, Trigger Map, business model, users, success criteria
|
||||
- Focus: Competitive landscape and unfair advantage
|
||||
- Limits: Not detailed feature comparison - strategic positioning
|
||||
- Dependencies: Steps 1-8 completed
|
||||
|
|
|
|||
|
|
@ -40,7 +40,7 @@ Establish the technical platform strategy and device support requirements that w
|
|||
- Avoid generating content without user input
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
- Available context: All previous steps (vision, positioning, VTC, business model, users, success criteria, competitive landscape, constraints)
|
||||
- Available context: All previous steps (vision, positioning, Trigger Map, business model, users, success criteria, competitive landscape, constraints)
|
||||
- Focus: Platform and device strategy
|
||||
- Limits: Not detailed technical specs - strategic platform direction
|
||||
- Dependencies: Steps 1-10 completed
|
||||
|
|
|
|||
|
|
@ -40,7 +40,7 @@ Establish the product's communication personality and style for consistent UI mi
|
|||
- Avoid generating content without user input
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
- Available context: Vision, positioning, VTC, business model, users, success criteria, competitive landscape, constraints, platform strategy
|
||||
- Available context: Vision, positioning, Trigger Map, business model, users, success criteria, competitive landscape, constraints, platform strategy
|
||||
- Focus: Communication personality and microcopy style
|
||||
- Limits: Tone of Voice is for UI microcopy (buttons, labels, errors, system messages), NOT strategic content (headlines, feature descriptions, value propositions)
|
||||
- Dependencies: Steps 1-10a completed
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
name: 'step-11a-create-vtc'
|
||||
description: 'Create simplified Value Trigger Chain for strategic summary'
|
||||
description: 'Create simplified Trigger Map for strategic summary'
|
||||
|
||||
# File References
|
||||
nextStepFile: './step-12-create-product-brief.md'
|
||||
|
|
@ -8,10 +8,10 @@ workflowFile: '../workflow.md'
|
|||
activityWorkflowFile: '../workflow.md'
|
||||
---
|
||||
|
||||
# Step 11A: Create Value Trigger Chain
|
||||
# Step 11A: Create Trigger Map
|
||||
|
||||
## STEP GOAL:
|
||||
Create a simplified Value Trigger Chain (VTC) to capture strategic essence for stakeholder communication.
|
||||
Create a simplified Trigger Map to capture strategic essence for stakeholder communication.
|
||||
|
||||
## MANDATORY EXECUTION RULES (READ FIRST):
|
||||
|
||||
|
|
@ -23,33 +23,33 @@ Create a simplified Value Trigger Chain (VTC) to capture strategic essence for s
|
|||
- 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 VTC
|
||||
- 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: VTC creation from Product Brief context - Business Goal, Solution, User, Driving Forces, Customer Awareness
|
||||
- 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 VTC Workshop
|
||||
- Approach: Leverage existing Product Brief context, route to Trigger Map Workshop
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
- Primary goal: VTC created and added to Product Brief
|
||||
- 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 VTC summarizing the product's value chain
|
||||
- Limits: This is a simplified strategic summary, not detailed scenario VTCs
|
||||
- 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 VTC to User
|
||||
### 1. Explain Trigger Map to User
|
||||
|
||||
> "Before we finalize the Product Brief, let's create a Value Trigger Chain (VTC).
|
||||
> "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
|
||||
|
|
@ -60,13 +60,13 @@ Create a simplified Value Trigger Chain (VTC) to capture strategic essence for s
|
|||
>
|
||||
> This will take about 20-30 minutes and gives you a powerful one-page strategic foundation.
|
||||
>
|
||||
> Shall we create the VTC now?"
|
||||
> Shall we create the Trigger Map now?"
|
||||
|
||||
### 2. Route to VTC Workshop
|
||||
### 2. Route to Trigger Map Workshop
|
||||
|
||||
**If user agrees:**
|
||||
|
||||
Load and execute the VTC Workshop Router:
|
||||
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**.
|
||||
|
|
@ -83,21 +83,21 @@ Load and execute the VTC Workshop Router:
|
|||
|
||||
**Don't start from zero** - use the strategic work already completed.
|
||||
|
||||
### 4. Save VTC
|
||||
### 4. Save Trigger Map
|
||||
|
||||
VTC should be saved to:
|
||||
Trigger Map should be saved to:
|
||||
`{output_folder}/A-Product-Brief/vtc-primary.yaml`
|
||||
|
||||
### 5. Add VTC to Brief
|
||||
### 5. Add Trigger Map to Brief
|
||||
|
||||
After VTC is created, add it to the Product Brief document BEFORE the "Next Steps" section:
|
||||
After Trigger Map is created, add it to the Product Brief document BEFORE the "Next Steps" section:
|
||||
|
||||
```markdown
|
||||
---
|
||||
|
||||
## Value Trigger Chain
|
||||
## Trigger Map
|
||||
|
||||
**Strategic Summary** - [View full VTC](./vtc-primary.yaml)
|
||||
**Strategic Summary** - [View full Trigger Map](./vtc-primary.yaml)
|
||||
|
||||
- **Business Goal:** [primary goal]
|
||||
- **Solution:** [solution]
|
||||
|
|
@ -107,33 +107,33 @@ After VTC is created, add it to the Product Brief document BEFORE the "Next Step
|
|||
- *Wants to avoid:* [negative forces]
|
||||
- **Awareness Journey:** [start stage] → [end stage]
|
||||
|
||||
This VTC provides quick strategic reference and will inform all design decisions.
|
||||
This Trigger Map provides quick strategic reference and will inform all design decisions.
|
||||
|
||||
---
|
||||
```
|
||||
|
||||
### 6. Confirm Completion
|
||||
|
||||
> "Excellent! Your Product Brief now includes a Value Trigger Chain.
|
||||
> "Excellent! Your Product Brief now includes a Trigger Map.
|
||||
>
|
||||
> This VTC will:
|
||||
> This Trigger Map will:
|
||||
> - Help you pitch the project to stakeholders
|
||||
> - Guide early design decisions
|
||||
> - Serve as foundation for scenario-specific VTCs in Phase 4
|
||||
> - Serve as foundation for scenario-specific Trigger Maps in Phase 4
|
||||
>
|
||||
> Product Brief is now complete!"
|
||||
|
||||
### 7. If User Declines VTC
|
||||
### 7. If User Declines Trigger Map
|
||||
|
||||
**If user says:** "Let's skip the VTC for now"
|
||||
**If user says:** "Let's skip the Trigger Map for now"
|
||||
|
||||
**Response:**
|
||||
> "No problem! You can create a VTC later using:
|
||||
> "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 VTC anytime."
|
||||
> Product Brief is complete. You can add a Trigger Map anytime."
|
||||
|
||||
Then proceed to mark workflow as complete.
|
||||
|
||||
|
|
@ -141,7 +141,7 @@ Then proceed to mark workflow as complete.
|
|||
**Mandatory:** Append to `dialog/decisions.md` if key decisions were made.
|
||||
|
||||
**Record:**
|
||||
- VTC framework decisions
|
||||
- Trigger Map framework decisions
|
||||
- Value/Transformation/Cost mapping
|
||||
- Strategic insights from framework
|
||||
|
||||
|
|
@ -167,15 +167,15 @@ ONLY WHEN step objectives are met and user confirms will you then load and read
|
|||
## SYSTEM SUCCESS/FAILURE METRICS
|
||||
|
||||
### SUCCESS:
|
||||
- VTC created or user explicitly deferred
|
||||
- Trigger Map created or user explicitly deferred
|
||||
- Product Brief context leveraged (not starting from zero)
|
||||
- VTC saved to correct location
|
||||
- VTC summary added to Product Brief document
|
||||
- Trigger Map saved to correct location
|
||||
- Trigger Map summary added to Product Brief document
|
||||
- User confirmed
|
||||
|
||||
### FAILURE:
|
||||
- Started VTC from zero ignoring existing Product Brief context
|
||||
- Skipped VTC without offering
|
||||
- Generated VTC without user collaboration
|
||||
- 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.
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
name: 'step-02-vtc-consistency'
|
||||
description: 'Verify Value Trigger Chain consistency and validity'
|
||||
description: 'Verify Trigger Map consistency and validity'
|
||||
|
||||
# File References
|
||||
nextStepFile: './step-03-seo-strategy.md'
|
||||
|
|
@ -8,10 +8,10 @@ workflowFile: '../workflow.md'
|
|||
activityWorkflowFile: '../workflow-validate.md'
|
||||
---
|
||||
|
||||
# Validation Step 02: VTC Consistency
|
||||
# Validation Step 02: Trigger Map Consistency
|
||||
|
||||
## STEP GOAL:
|
||||
Verify the Value Trigger Chain(s) form a valid chain from business goals through personas to driving forces.
|
||||
Verify the Trigger Map(s) form a valid chain from business goals through personas to driving forces.
|
||||
|
||||
## MANDATORY EXECUTION RULES (READ FIRST):
|
||||
|
||||
|
|
@ -23,39 +23,39 @@ Verify the Value Trigger Chain(s) form a valid chain from business goals through
|
|||
- YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
|
||||
|
||||
### Role Reinforcement:
|
||||
- You are a Strategic Business Analyst validating VTC chain integrity
|
||||
- You are a Strategic Business Analyst validating Trigger Map chain integrity
|
||||
- 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: VTC completeness, chain validity, cross-VTC consistency
|
||||
- Focus: Trigger Map completeness, chain validity, cross-Trigger Map consistency
|
||||
- FORBIDDEN: Do not skip chain validity checks
|
||||
- Approach: Locate VTCs, check completeness, validate chains, check cross-VTC consistency
|
||||
- Approach: Locate Trigger Maps, check completeness, validate chains, check cross-Trigger Map consistency
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
- Primary goal: VTC consistency verified
|
||||
- Primary goal: Trigger Map consistency verified
|
||||
- Save/document outputs appropriately
|
||||
- Avoid generating content without user input
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
- Available context: VTC files and Product Brief
|
||||
- Available context: Trigger Map files and Product Brief
|
||||
- Focus: Chain validity and consistency
|
||||
- Limits: Validation only, not modification
|
||||
- Dependencies: Step 01 completed
|
||||
|
||||
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
||||
|
||||
### 1. Locate VTC Files
|
||||
### 1. Locate Trigger Map Files
|
||||
|
||||
Check for:
|
||||
- `{output_folder}/A-Product-Brief/vtc-primary.yaml` (Product Pitch VTC)
|
||||
- Any scenario-level VTCs in `{output_folder}/C-UX-Scenarios/`
|
||||
- `{output_folder}/A-Product-Brief/vtc-primary.yaml` (Product Pitch Trigger Map)
|
||||
- Any scenario-level Trigger Maps in `{output_folder}/C-UX-Scenarios/`
|
||||
|
||||
### 2. VTC Completeness
|
||||
### 2. Trigger Map Completeness
|
||||
|
||||
For each VTC:
|
||||
For each Trigger Map:
|
||||
- [ ] `businessGoal` — specific and measurable
|
||||
- [ ] `solution` — describes how we help the user
|
||||
- [ ] `user` — identifies who we're helping
|
||||
|
|
@ -66,23 +66,23 @@ For each VTC:
|
|||
|
||||
### 3. Chain Validity
|
||||
|
||||
- [ ] Business goal in VTC matches a goal in the Product Brief
|
||||
- [ ] User in VTC matches a target user in the Product Brief
|
||||
- [ ] Business goal in Trigger Map matches a goal in the Product Brief
|
||||
- [ ] User in Trigger Map matches a target user in the Product Brief
|
||||
- [ ] Driving forces are specific (not generic like "wants it to work")
|
||||
- [ ] Awareness journey makes logical sense (start ≠ end)
|
||||
|
||||
### 4. Cross-VTC Consistency (if multiple)
|
||||
### 4. Cross-Trigger Map Consistency (if multiple)
|
||||
|
||||
- [ ] No contradictory business goals across VTCs
|
||||
- [ ] No contradictory business goals across Trigger Maps
|
||||
- [ ] Users are distinct or represent different contexts
|
||||
- [ ] Driving forces don't duplicate across VTCs without reason
|
||||
- [ ] Driving forces don't duplicate across Trigger Maps without reason
|
||||
|
||||
### 5. Report
|
||||
|
||||
```
|
||||
## VTC Consistency Report
|
||||
## Trigger Map Consistency Report
|
||||
|
||||
**VTCs found:** [N]
|
||||
**Trigger Maps found:** [N]
|
||||
**All complete:** [Yes/No]
|
||||
**Chain issues:** [N]
|
||||
|
||||
|
|
@ -109,15 +109,15 @@ ONLY WHEN step objectives are met and user confirms will you then load and read
|
|||
## SYSTEM SUCCESS/FAILURE METRICS
|
||||
|
||||
### SUCCESS:
|
||||
- All VTCs located and checked
|
||||
- Completeness verified for each VTC
|
||||
- All Trigger Maps located and checked
|
||||
- Completeness verified for each Trigger Map
|
||||
- Chain validity confirmed
|
||||
- Cross-VTC consistency checked (if multiple)
|
||||
- Cross-Trigger Map consistency checked (if multiple)
|
||||
- Consistency report generated
|
||||
|
||||
### FAILURE:
|
||||
- Skipped chain validity checks
|
||||
- Missed VTC files
|
||||
- Did not check cross-VTC consistency
|
||||
- Missed Trigger Map files
|
||||
- Did not check cross-Trigger Map consistency
|
||||
|
||||
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|
||||
|
|
|
|||
|
|
@ -67,7 +67,7 @@ Check if SEO/keyword content exists in the Content & Language document. If not,
|
|||
### 3. Cross-Phase Readiness
|
||||
|
||||
- [ ] Keyword map is in a format Phase 3 (Scenarios) can reference
|
||||
- [ ] SEO priorities align with user priorities from VTC
|
||||
- [ ] SEO priorities align with user priorities from Trigger Map
|
||||
- [ ] Content structure supports keyword targeting
|
||||
|
||||
### 4. Report
|
||||
|
|
|
|||
|
|
@ -102,7 +102,7 @@ Compile results from all 6 validation steps:
|
|||
| Check | Status | Issues |
|
||||
|-------|--------|--------|
|
||||
| Brief Completeness | pass/warn/fail | [summary] |
|
||||
| VTC Consistency | pass/warn/fail | [summary] |
|
||||
| Trigger Map Consistency | pass/warn/fail | [summary] |
|
||||
| SEO Strategy | pass/warn/fail | [summary] |
|
||||
| Content & Language | pass/warn/fail | [summary] |
|
||||
| Visual Direction | pass/warn/fail | [summary] |
|
||||
|
|
|
|||
|
|
@ -68,9 +68,9 @@
|
|||
|
||||
---
|
||||
|
||||
## Value Trigger Chain
|
||||
## Trigger Map
|
||||
|
||||
**Strategic Summary** - [View full VTC](./vtc-primary.yaml)
|
||||
**Strategic Summary** - [View full Trigger Map](./vtc-primary.yaml)
|
||||
|
||||
This project serves:
|
||||
- **Business Goal:** {{vtc_business_goal}}
|
||||
|
|
@ -83,7 +83,7 @@ This project serves:
|
|||
|
||||
**Awareness Journey:** {{vtc_awareness_start}} → {{vtc_awareness_end}}
|
||||
|
||||
This strategic chain ensures every design decision serves the user's psychology while achieving business goals.
|
||||
This Trigger Map ensures every design decision serves the user's psychology while achieving business goals.
|
||||
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -162,9 +162,9 @@
|
|||
|
||||
---
|
||||
|
||||
## Value Trigger Chain
|
||||
## Trigger Map
|
||||
|
||||
**Strategic Summary** - [View full VTC](./vtc-primary.yaml)
|
||||
**Strategic Summary** - [View full Trigger Map](./vtc-primary.yaml)
|
||||
|
||||
- **Business Goal:** {{vtc_business_goal}}
|
||||
- **Solution:** {{vtc_solution}}
|
||||
|
|
@ -174,7 +174,7 @@
|
|||
- *Wants to avoid:* {{vtc_negative_forces}}
|
||||
- **Awareness Journey:** {{vtc_awareness_start}} → {{vtc_awareness_end}}
|
||||
|
||||
This VTC provides quick strategic reference and will inform all design decisions.
|
||||
This Trigger Map provides quick strategic reference and will inform all design decisions.
|
||||
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -32,7 +32,7 @@ Execute each step in order. Each step produces a section of the final validation
|
|||
| Step | Name | Validates |
|
||||
|------|------|-----------|
|
||||
| 01 | Brief Completeness | All required sections present and filled |
|
||||
| 02 | VTC Consistency | Goals → personas → forces chain is valid |
|
||||
| 02 | Trigger Map Consistency | Goals → personas → forces chain is valid |
|
||||
| 03 | SEO Strategy | Keyword map complete, page assignments clear |
|
||||
| 04 | Content & Language | Tone, personality, guidelines coherent |
|
||||
| 05 | Visual Direction | Brand, style, references documented |
|
||||
|
|
|
|||
|
|
@ -64,7 +64,7 @@ Based on `brief_level`:
|
|||
| 01 | Init | Load context, confirm readiness |
|
||||
| 02 | Vision | Explore and document project vision |
|
||||
| 03 | Positioning | Define market positioning |
|
||||
| 04 | Create VTC | Value Trigger Chain (refs `vtc-workshop/`) |
|
||||
| 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 +74,7 @@ Based on `brief_level`:
|
|||
| 10 | Constraints | Document project constraints |
|
||||
| 10a | Platform Strategy | Define platform approach |
|
||||
| 11 | Tone of Voice | Establish brand voice |
|
||||
| 11a | Create VTC | Second VTC opportunity (refs `vtc-workshop/`) |
|
||||
| 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 |
|
||||
|
|
|
|||
|
|
@ -48,7 +48,7 @@ Determine site type, list all pages/views, assess scale, select approach mode, a
|
|||
|
||||
- Available context: Product Brief data, Trigger Map data loaded in Step 1
|
||||
- Focus: Site classification, page inventory, scale assessment
|
||||
- Limits: No scenario creation, no VTC building — only scope analysis
|
||||
- Limits: No scenario creation, no strategic context building — only scope analysis
|
||||
- Dependencies: Step 1 context must be loaded
|
||||
|
||||
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
||||
|
|
@ -150,7 +150,7 @@ Present to user and **wait for approval**:
|
|||
|
||||
### 6. Present MENU OPTIONS
|
||||
|
||||
Display: "Are you ready to [C] Continue to Building Value Trigger Chains?"
|
||||
Display: "Are you ready to [C] Continue to Building Strategic Context?"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
|
||||
|
|
@ -165,7 +165,7 @@ Display: "Are you ready to [C] Continue to Building Value Trigger Chains?"
|
|||
|
||||
## CRITICAL STEP COMPLETION NOTE
|
||||
|
||||
ONLY WHEN [C continue option] is selected and [user has explicitly approved the scope analysis], will you then load and read fully `{nextStepFile}` to execute and begin building VTCs.
|
||||
ONLY WHEN [C continue option] is selected and [user has explicitly approved the scope analysis], will you then load and read fully `{nextStepFile}` to execute and begin building strategic context.
|
||||
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -1,16 +1,16 @@
|
|||
---
|
||||
name: 'step-03-build-vtcs'
|
||||
description: 'Extract Value Trigger Chains from Trigger Map to identify which scenarios to create'
|
||||
description: 'Build strategic context from Trigger Map to identify which scenarios to create'
|
||||
|
||||
# File References
|
||||
nextStepFile: './step-04-suggest-scenarios.md'
|
||||
---
|
||||
|
||||
# Step 3: Build Value Trigger Chains
|
||||
# Step 3: Build Strategic Context
|
||||
|
||||
## STEP GOAL:
|
||||
|
||||
Extract Value Trigger Chains (VTCs) from the Trigger Map, assign pages to each VTC, prioritize them, and verify complete coverage of all pages.
|
||||
Extract strategic context from the Trigger Map — tracing paths from business goals through personas and driving forces to transactions — assign pages to each scenario chain, prioritize them, and verify complete coverage of all pages.
|
||||
|
||||
## MANDATORY EXECUTION RULES (READ FIRST):
|
||||
|
||||
|
|
@ -32,32 +32,32 @@ Extract Value Trigger Chains (VTCs) from the Trigger Map, assign pages to each V
|
|||
|
||||
### Step-Specific Rules:
|
||||
|
||||
- 🎯 Focus only on building VTCs, assigning pages, and prioritizing
|
||||
- 🎯 Focus only on building strategic context, assigning pages, and prioritizing
|
||||
- 🚫 FORBIDDEN to create scenario outlines — only identify and plan scenarios
|
||||
- 💬 Approach: Systematically trace paths from business goals to user actions
|
||||
- 📋 Every page from the inventory must be assigned to exactly one VTC
|
||||
- 📋 Every page from the inventory must be assigned to exactly one scenario chain
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🔗 Trace complete chains from Business Goal → Persona → Force → Transaction → Scenario
|
||||
- 📋 Answer all 7 Decision Matrix questions for each VTC
|
||||
- 📋 Answer all 7 Decision Matrix questions for each scenario chain
|
||||
- 📊 Assign pages ensuring no repetition and full coverage
|
||||
- 🚫 FORBIDDEN to leave any page unassigned
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Available context: Product Brief, Trigger Map, approved page inventory from Step 2
|
||||
- Focus: VTC extraction, page assignment, prioritization
|
||||
- Focus: Strategic context extraction, page assignment, prioritization
|
||||
- Limits: No scenario outlining, no file creation — only planning
|
||||
- Dependencies: Approved scope analysis from Step 2
|
||||
|
||||
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
||||
|
||||
### 1. Build VTCs
|
||||
### 1. Build Strategic Context Chains
|
||||
|
||||
**What is a Value Trigger Chain?**
|
||||
**What is a strategic context chain?**
|
||||
|
||||
A VTC traces the path from business strategy to user action:
|
||||
A strategic context chain traces the path from business strategy to user action:
|
||||
|
||||
```
|
||||
Business Goal → Persona → Driving Force → Transaction → Scenario
|
||||
|
|
@ -79,7 +79,7 @@ For **each business goal** from the Trigger Map:
|
|||
3. Determine the specific transaction/action that fulfills it
|
||||
4. Name a candidate scenario using the persona's name
|
||||
|
||||
**For each VTC, answer the Decision Matrix (all 7 required):**
|
||||
**For each scenario chain, answer the Decision Matrix (all 7 required):**
|
||||
|
||||
| # | Question | Answer |
|
||||
|---|----------|--------|
|
||||
|
|
@ -91,18 +91,18 @@ For **each business goal** from the Trigger Map:
|
|||
| 6 | What value does user get? | [Tangible outcome] |
|
||||
| 7 | What value does business get? | [Measurable result] |
|
||||
|
||||
### 2. Assign Pages to VTCs
|
||||
### 2. Assign Pages to Scenario Chains
|
||||
|
||||
For each VTC, list which pages from the inventory (Step 02) the user visits.
|
||||
For each scenario chain, list which pages from the inventory (Step 02) the user visits.
|
||||
|
||||
**Rules:**
|
||||
- Each page appears in exactly ONE VTC/scenario (no repetition)
|
||||
- Each page appears in exactly ONE scenario chain (no repetition)
|
||||
- If a page could fit multiple scenarios, assign it to the highest-priority one
|
||||
- Shared elements (navigation, footer) are excluded from page assignment
|
||||
|
||||
### 3. Prioritize
|
||||
|
||||
Rank the VTCs:
|
||||
Rank the scenario chains:
|
||||
|
||||
**Priority 1 — Critical Path:**
|
||||
- Top business goal + primary persona + core product value
|
||||
|
|
@ -118,29 +118,29 @@ Rank the VTCs:
|
|||
|
||||
### 4. Coverage Check
|
||||
|
||||
After building all VTCs, verify:
|
||||
After building all scenario chains, verify:
|
||||
|
||||
- [ ] Every page from inventory is assigned to exactly one VTC
|
||||
- [ ] Every page from inventory is assigned to exactly one scenario chain
|
||||
- [ ] Primary persona has at least one Priority 1 scenario
|
||||
- [ ] Top business goal is addressed by at least one scenario
|
||||
- [ ] No page appears in multiple scenarios
|
||||
|
||||
**If pages are unassigned:** Create additional VTCs or expand existing ones to cover them.
|
||||
**If pages are unassigned:** Create additional scenario chains or expand existing ones to cover them.
|
||||
|
||||
### 5. Present VTC List
|
||||
### 5. Present Scenario Chain List
|
||||
|
||||
Present the complete VTC list:
|
||||
Present the complete scenario chain list:
|
||||
|
||||
```
|
||||
## Value Trigger Chains
|
||||
## Strategic Context Chains
|
||||
|
||||
### Priority 1
|
||||
**VTC-01:** [Business Goal] → [Persona] → [Force] → [Transaction]
|
||||
**Chain 01:** [Business Goal] → [Persona] → [Force] → [Transaction]
|
||||
- Scenario: 01-[slug]
|
||||
- Pages: [list]
|
||||
|
||||
### Priority 2
|
||||
**VTC-02:** [Business Goal] → [Persona] → [Force] → [Transaction]
|
||||
**Chain 02:** [Business Goal] → [Persona] → [Force] → [Transaction]
|
||||
- Scenario: 02-[slug]
|
||||
- Pages: [list]
|
||||
|
||||
|
|
@ -164,7 +164,7 @@ Display: "Are you ready to [C] Continue to Scenario Suggestions?"
|
|||
|
||||
## CRITICAL STEP COMPLETION NOTE
|
||||
|
||||
ONLY WHEN [C continue option] is selected and [VTC list with full page coverage presented], will you then load and read fully `{nextStepFile}` to execute and begin scenario suggestions.
|
||||
ONLY WHEN [C continue option] is selected and [scenario chain list with full page coverage presented], will you then load and read fully `{nextStepFile}` to execute and begin scenario suggestions.
|
||||
|
||||
---
|
||||
|
||||
|
|
@ -172,18 +172,18 @@ ONLY WHEN [C continue option] is selected and [VTC list with full page coverage
|
|||
|
||||
### ✅ SUCCESS:
|
||||
|
||||
- All business goals traced through complete VTC chains
|
||||
- All 7 Decision Matrix questions answered for each VTC
|
||||
- Every page from inventory assigned to exactly one VTC
|
||||
- VTCs prioritized with clear rationale
|
||||
- All business goals traced through complete strategic context chains
|
||||
- All 7 Decision Matrix questions answered for each scenario chain
|
||||
- Every page from inventory assigned to exactly one scenario chain
|
||||
- Scenario chains prioritized with clear rationale
|
||||
- Coverage check passes (all pages assigned, no duplicates)
|
||||
- Complete VTC list presented to user
|
||||
- Complete scenario chain list presented to user
|
||||
- Menu presented and user input handled correctly
|
||||
|
||||
### ❌ SYSTEM FAILURE:
|
||||
|
||||
- Leaving pages unassigned
|
||||
- Assigning pages to multiple VTCs
|
||||
- Assigning pages to multiple scenario chains
|
||||
- Skipping Decision Matrix questions
|
||||
- Creating scenario outlines during this step
|
||||
- Not verifying coverage before proceeding
|
||||
|
|
|
|||
|
|
@ -46,10 +46,10 @@ Present the complete scenario plan to the user for approval before creating any
|
|||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Available context: VTCs from Step 3, page inventory, Trigger Map data
|
||||
- Available context: Strategic context from Step 3, page inventory, Trigger Map data
|
||||
- Focus: Presenting and getting approval for the scenario plan
|
||||
- Limits: No scenario outlining, no file creation — only planning approval
|
||||
- Dependencies: Complete VTC list from Step 3
|
||||
- Dependencies: Complete strategic context chains from Step 3
|
||||
|
||||
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
||||
|
||||
|
|
@ -124,7 +124,7 @@ Scenario names MUST use persona names:
|
|||
User may:
|
||||
- **"Looks good, proceed"** → Continue to menu options
|
||||
- **"Combine X and Y"** → Adjust and re-present
|
||||
- **"Add a scenario for [purpose]"** → Add VTC and re-present
|
||||
- **"Add a scenario for [purpose]"** → Add scenario chain and re-present
|
||||
- **"Focus on just [one flow]"** → Apply selective ignorance, re-present
|
||||
- **"Missing page [X]"** → Add to inventory and assign
|
||||
|
||||
|
|
|
|||
|
|
@ -51,7 +51,7 @@ Define ONE scenario through 8 strategic questions in natural conversation order.
|
|||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Available context: Approved scenario plan from Step 4, VTCs, page inventory, Trigger Map
|
||||
- Available context: Approved scenario plan from Step 4, strategic context, page inventory, Trigger Map
|
||||
- Focus: Detailed outlining of one scenario at a time
|
||||
- Limits: Only outline scenarios from the approved plan
|
||||
- Dependencies: User-approved scenario plan from Step 4
|
||||
|
|
@ -74,7 +74,7 @@ Load the full template: `{scenarioTemplate}`
|
|||
**Two modes — same 8 questions, different driver:**
|
||||
|
||||
- **Conversation mode** (default): YOU ask, the USER answers. One question at a time. Each answer shapes the next question naturally.
|
||||
- **Suggest mode** (when user asks you to suggest): YOU answer all 8 questions based on the Trigger Map, Product Brief, and VTCs. Present the complete scenario to the user for review and adjustment.
|
||||
- **Suggest mode** (when user asks you to suggest): YOU answer all 8 questions based on the Trigger Map, Product Brief, and strategic context. Present the complete scenario to the user for review and adjustment.
|
||||
|
||||
This IS the scenario — when all 8 are answered, the outline writes itself.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
name: step-01-scenario-coverage
|
||||
description: Verify that all Value Trigger Chains from the Trigger Map are covered by at least one scenario
|
||||
description: Verify that all strategic context chains from the Trigger Map are covered by at least one scenario
|
||||
|
||||
# File References
|
||||
nextStepFile: './step-02-navigation-patterns.md'
|
||||
|
|
@ -10,7 +10,7 @@ nextStepFile: './step-02-navigation-patterns.md'
|
|||
|
||||
## STEP GOAL:
|
||||
|
||||
Verify that all Value Trigger Chains (VTCs) from the Trigger Map are covered by at least one scenario, with Priority 1 VTCs having dedicated scenarios.
|
||||
Verify that all strategic context chains from the Trigger Map are covered by at least one scenario, with Priority 1 chains having dedicated scenarios.
|
||||
|
||||
## MANDATORY EXECUTION RULES (READ FIRST):
|
||||
|
||||
|
|
@ -32,22 +32,22 @@ Verify that all Value Trigger Chains (VTCs) from the Trigger Map are covered by
|
|||
|
||||
### Step-Specific Rules:
|
||||
|
||||
- 🎯 Focus only on VTC-to-scenario coverage verification
|
||||
- 🎯 Focus only on strategic-context-to-scenario coverage verification
|
||||
- 🚫 FORBIDDEN to modify any scenario files during validation
|
||||
- 💬 Approach: Systematic cross-referencing of Trigger Map VTCs against scenarios
|
||||
- 💬 Approach: Systematic cross-referencing of Trigger Map strategic context against scenarios
|
||||
- 📋 Report findings with clear severity levels
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 📖 Load both Trigger Map and all scenario files
|
||||
- 🔗 Cross-reference every VTC against scenario coverage
|
||||
- 🔗 Cross-reference every strategic context chain against scenario coverage
|
||||
- 📊 Report with severity levels (Critical/Warning/Pass)
|
||||
- 🚫 FORBIDDEN to skip any VTC during verification
|
||||
- 🚫 FORBIDDEN to skip any chain during verification
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Available context: Trigger Map, all scenario outlines, scenario index
|
||||
- Focus: VTC coverage verification only
|
||||
- Focus: Strategic context coverage verification only
|
||||
- Limits: No scenario modifications, only verification and reporting
|
||||
- Dependencies: All scenario files must exist from Phase 3 creation workflow
|
||||
|
||||
|
|
@ -55,7 +55,7 @@ Verify that all Value Trigger Chains (VTCs) from the Trigger Map are covered by
|
|||
|
||||
### 1. Load Trigger Map Data
|
||||
|
||||
Read `{output_folder}/B-Trigger-Map/trigger-map.md` and extract all VTCs (Business Goal → Persona → Driving Force chains).
|
||||
Read `{output_folder}/B-Trigger-Map/trigger-map.md` and extract all strategic context chains (Business Goal → Persona → Driving Force chains).
|
||||
|
||||
### 2. Load All Scenario Files
|
||||
|
||||
|
|
@ -63,28 +63,28 @@ Read all scenario outlines from `{output_folder}/C-UX-Scenarios/`.
|
|||
|
||||
### 3. Cross-Reference
|
||||
|
||||
For each VTC, verify:
|
||||
- [ ] At least one scenario addresses this VTC
|
||||
- [ ] The scenario Trigger Map Connections section explicitly references the VTC components
|
||||
- [ ] Priority 1 VTCs have dedicated scenarios (not just secondary coverage)
|
||||
For each strategic context chain, verify:
|
||||
- [ ] At least one scenario addresses this chain
|
||||
- [ ] The scenario Trigger Map Connections section explicitly references the strategic context components
|
||||
- [ ] Priority 1 chains have dedicated scenarios (not just secondary coverage)
|
||||
|
||||
### 4. Generate Report
|
||||
|
||||
```
|
||||
## Coverage Report
|
||||
|
||||
| VTC | Persona | Driving Force | Scenario(s) | Status |
|
||||
| Chain | Persona | Driving Force | Scenario(s) | Status |
|
||||
|-----|---------|---------------|-------------|--------|
|
||||
| [Goal] | [Name] | [Force] | [Scenario ID] | ✅/⚠️/❌ |
|
||||
|
||||
**Coverage:** [X]/[Total] VTCs covered ([X]%)
|
||||
**Gaps:** [list uncovered VTCs]
|
||||
**Coverage: [X]/[Total] chains covered ([X]%)
|
||||
**Gaps: [list uncovered chains]]
|
||||
```
|
||||
|
||||
**Severity:**
|
||||
- ❌ Critical: Priority 1 VTC with no scenario
|
||||
- ⚠️ Warning: Priority 2-3 VTC with no scenario
|
||||
- ✅ Pass: VTC covered by at least one scenario
|
||||
- ❌ Critical: Priority 1 chain with no scenario
|
||||
- ⚠️ Warning: Priority 2-3 chain with no scenario
|
||||
- ✅ Pass: Chain covered by at least one scenario
|
||||
|
||||
### 5. Present MENU OPTIONS
|
||||
|
||||
|
|
@ -103,7 +103,7 @@ Display: "Are you ready to [C] Continue to Navigation Patterns validation?"
|
|||
|
||||
## CRITICAL STEP COMPLETION NOTE
|
||||
|
||||
ONLY WHEN [C continue option] is selected and [coverage report generated with all VTCs checked], will you then load and read fully `{nextStepFile}` to execute and begin navigation patterns validation.
|
||||
ONLY WHEN [C continue option] is selected and [coverage report generated with all chains checked], will you then load and read fully `{nextStepFile}` to execute and begin navigation patterns validation.
|
||||
|
||||
---
|
||||
|
||||
|
|
@ -111,16 +111,16 @@ ONLY WHEN [C continue option] is selected and [coverage report generated with al
|
|||
|
||||
### ✅ SUCCESS:
|
||||
|
||||
- All VTCs from Trigger Map identified and cross-referenced
|
||||
- Every VTC checked against scenario coverage
|
||||
- All strategic context chains from Trigger Map identified and cross-referenced
|
||||
- Every chain checked against scenario coverage
|
||||
- Severity levels correctly assigned
|
||||
- Coverage report generated with clear gaps identified
|
||||
- Priority 1 VTCs verified for dedicated scenario coverage
|
||||
- Priority 1 chains verified for dedicated scenario coverage
|
||||
- Menu presented and user input handled correctly
|
||||
|
||||
### ❌ SYSTEM FAILURE:
|
||||
|
||||
- Missing any VTC from the cross-reference
|
||||
- Missing any chain from the cross-reference
|
||||
- Not loading all scenario files
|
||||
- Incorrect severity assignment
|
||||
- Not identifying coverage gaps
|
||||
|
|
|
|||
|
|
@ -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 VTCs](steps-c/step-03-build-vtcs.md) | Extract Value Trigger Chains from Trigger Map |
|
||||
| 03 | [Build Strategic Context](steps-c/step-03-build-vtcs.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 |
|
||||
|
|
|
|||
|
|
@ -67,9 +67,9 @@ Appointment-driven trust-building flow
|
|||
|
||||
## Next Step
|
||||
|
||||
Once you have clarity on all 7 steps (including VTC), **start sketching the journey.**
|
||||
Once you have clarity on all 7 steps (including strategic context), **start sketching the journey.**
|
||||
|
||||
Each sketch serves the path from trigger to mutual success, guided by the VTC.
|
||||
Each sketch serves the path from trigger to mutual success, guided by the Trigger Map.
|
||||
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -196,7 +196,7 @@ This is especially important for storyboards and multi-state specifications wher
|
|||
**Strategic Foundation**
|
||||
- [ ] User situation clearly defined
|
||||
- [ ] Usage context documented
|
||||
- [ ] Trigger Value Chain (VTC) defined and linked
|
||||
- [ ] Strategic context (Trigger Map) defined and linked
|
||||
- [ ] Scenario purpose stated
|
||||
- [ ] Success criteria defined
|
||||
|
||||
|
|
@ -239,7 +239,7 @@ This is especially important for storyboards and multi-state specifications wher
|
|||
**Checklist:**
|
||||
- [ ] Page purpose clearly stated
|
||||
- [ ] Success criteria defined
|
||||
- [ ] VTC reference present
|
||||
- [ ] Trigger Map reference present
|
||||
- [ ] Sections properly separated and named
|
||||
- [ ] Section purposes defined
|
||||
- [ ] Page layout logical and flows well
|
||||
|
|
@ -550,7 +550,7 @@ For rapid validation during active design work:
|
|||
|
||||
**Content (Levels 1-5):**
|
||||
- [ ] Page purpose clear
|
||||
- [ ] VTC reference present
|
||||
- [ ] Trigger Map reference present
|
||||
- [ ] Structural Area Labels complete
|
||||
- [ ] Interactive Area Labels complete
|
||||
- [ ] Multi-language content present
|
||||
|
|
|
|||
|
|
@ -63,7 +63,7 @@ Validate:
|
|||
- Page description paragraph (1-2 paragraphs explaining what page does)
|
||||
- User Situation section (user's context, needs, emotional state)
|
||||
- Page Purpose section (what job page must accomplish)
|
||||
- Success criteria or VTC reference
|
||||
- Success criteria or Trigger Map reference
|
||||
- Emotional context and pain points addressed
|
||||
|
||||
### 2. Generate Diagnostic Report
|
||||
|
|
|
|||
|
|
@ -102,7 +102,7 @@
|
|||
**Checklist:**
|
||||
- [ ] User situation clearly defined
|
||||
- [ ] Usage context documented
|
||||
- [ ] Trigger Value Chain (VTC) defined and linked
|
||||
- [ ] Strategic context (Trigger Map) defined and linked
|
||||
- [ ] Scenario purpose stated
|
||||
- [ ] Success criteria defined
|
||||
|
||||
|
|
@ -134,7 +134,7 @@
|
|||
**Checklist:**
|
||||
- [ ] Page purpose clearly stated
|
||||
- [ ] Success criteria defined
|
||||
- [ ] VTC reference present
|
||||
- [ ] Trigger Map reference present
|
||||
- [ ] Sections properly separated and named
|
||||
- [ ] Section purposes defined
|
||||
- [ ] Page layout logical and flows well
|
||||
|
|
|
|||
|
|
@ -53,7 +53,7 @@ The Dream workflow uses the same steps as Suggest (`./steps-s/`) but with **auto
|
|||
|
||||
### Agent Behavior
|
||||
|
||||
- Make reasonable decisions at each step based on VTC, scenario context, and WDS patterns
|
||||
- Make reasonable decisions at each step based on Trigger Map, scenario context, and WDS patterns
|
||||
- Document decisions and rationale as you go
|
||||
- When uncertain, choose the simpler option
|
||||
- After completion, present a summary of all decisions made
|
||||
|
|
|
|||
|
|
@ -54,7 +54,7 @@ Load and read full config from `{project-root}/_bmad/wds/config.yaml` and resolv
|
|||
|
||||
### 4. Scenario Dashboard
|
||||
|
||||
Read all scenario files from `{output_folder}/C-UX-Scenarios/scenarios/` and display:
|
||||
Read all scenario files from `{output_folder}/C-UX-Scenarios/` and display:
|
||||
|
||||
```
|
||||
Your scenarios and their design status:
|
||||
|
|
@ -78,15 +78,20 @@ When a scenario is selected (or for scenario-independent work), present:
|
|||
```
|
||||
What would you like to do?
|
||||
|
||||
[C] Conceptualize — Explore what the design needs
|
||||
[K] Analyse Sketches — I'll interpret your sketch
|
||||
[S] Suggest Interface — I'll propose a design, checking each step
|
||||
[D] Dream Up Interface — I'll create it all, you review
|
||||
[P] Write Specifications — Detail a page specification
|
||||
[W] Visual Design — Work with visual tools, integrate results
|
||||
[M] Manage Design System — Define/update design system components
|
||||
[V] Validate Specifications — Audit a finished spec
|
||||
[H] Design Delivery — Package DD-XXX, hand off to BMad
|
||||
── Design ──────────────────────────────────────
|
||||
[C] Conceptualize — Explore what the design needs
|
||||
[K] Analyse Sketches — I'll interpret your sketch
|
||||
[S] Suggest Design — I'll propose a design, you confirm each step
|
||||
[D] Dream Up Design — I'll create it all, you review
|
||||
|
||||
── Specify ─────────────────────────────────────
|
||||
[P] Write Specifications — Content, interaction and functionality specs
|
||||
[V] Validate Specs — Audit spec completeness and quality
|
||||
|
||||
── Produce ─────────────────────────────────────
|
||||
[W] Visual Design — Generate assets with Nano Banana, Stitch, etc.
|
||||
[M] Design System — Extract or update shared components
|
||||
[H] Design Delivery — Package for development handoff
|
||||
```
|
||||
|
||||
### Activity Routing
|
||||
|
|
@ -99,7 +104,7 @@ What would you like to do?
|
|||
| [D] | workflow-dream.md | steps-s/ (autonomous mode) |
|
||||
| [P] | workflow-specify.md | steps-p/ |
|
||||
| [W] | workflow-visual.md | steps-w/ |
|
||||
| [M] | workflow-design-system.md | steps-m/ |
|
||||
| [M] | workflow-design-system.md | steps-m/ (extract on 2nd use) |
|
||||
| [V] | workflow-validate.md | steps-v/ |
|
||||
| [H] | workflow-handover.md | steps-h/ |
|
||||
|
||||
|
|
@ -123,7 +128,8 @@ If the scenario has a `design_intent` from Phase 3 handover, pre-select that act
|
|||
|
||||
## OUTPUT
|
||||
|
||||
- `{output_folder}/D-UX-Design/` — page specifications, design system, validation reports
|
||||
- `{output_folder}/C-UX-Scenarios/` — page specifications within scenario page folders
|
||||
- `{output_folder}/D-Design-System/` — shared components and design tokens
|
||||
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -24,7 +24,7 @@ content_purpose:
|
|||
|
||||
model_priorities:
|
||||
primary: ["Customer Awareness ⭐⭐⭐", "Golden Circle ⭐⭐⭐"]
|
||||
secondary: ["Badass Users ⭐⭐", "VTC ⭐⭐"]
|
||||
secondary: ["Badass Users ⭐⭐", "Trigger Map ⭐⭐"]
|
||||
tertiary: ["Action Mapping ⭐"]
|
||||
|
||||
review_question: "Does a Problem Aware hairdresser feel seen and want to learn more?"
|
||||
|
|
@ -60,7 +60,7 @@ content_purpose:
|
|||
model_priorities:
|
||||
primary: ["Badass Users ⭐⭐⭐", "Action Mapping ⭐⭐⭐"]
|
||||
secondary: ["Customer Awareness ⭐"]
|
||||
tertiary: ["Golden Circle ⭐", "VTC ⭐"]
|
||||
tertiary: ["Golden Circle ⭐", "Trigger Map ⭐"]
|
||||
|
||||
review_question: "Can user fix error quickly without feeling frustrated?"
|
||||
```
|
||||
|
|
@ -92,7 +92,7 @@ content_purpose:
|
|||
- "User sees this as competitive advantage worth paying for"
|
||||
|
||||
model_priorities:
|
||||
primary: ["VTC ⭐⭐⭐", "Badass Users ⭐⭐"]
|
||||
primary: ["Trigger Map ⭐⭐⭐", "Badass Users ⭐⭐"]
|
||||
secondary: ["Action Mapping ⭐⭐", "Customer Awareness ⭐"]
|
||||
tertiary: ["Golden Circle ⭐"]
|
||||
|
||||
|
|
@ -102,7 +102,7 @@ content_purpose:
|
|||
**Analysis:**
|
||||
- **Comparison context:** User actively evaluating competitors
|
||||
- **Value connection:** Not just "3x longer" but "saves money/hassle"
|
||||
- **Model priority:** VTC emphasized for understanding driving forces
|
||||
- **Model priority:** Trigger Map emphasized for understanding driving forces
|
||||
- **Testable:** Can assess if users understand and value the advantage
|
||||
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
# Action Filter Example: Hairdresser Newsletter
|
||||
|
||||
**VTC Context:** Hairdresser newsletter signup
|
||||
**Trigger Map Context:** Hairdresser newsletter signup
|
||||
|
||||
**Action Filter:**
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
# Example: Badass Users Framework Applied to Hairdresser Newsletter
|
||||
|
||||
**VTC Context:** Hairdresser newsletter signup
|
||||
**Trigger Map Context:** Hairdresser newsletter signup
|
||||
|
||||
**Empowerment Frame:**
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
# Example: Golden Circle Applied to Hairdresser Newsletter
|
||||
|
||||
**VTC Context:** Hairdresser newsletter signup
|
||||
**Trigger Map Context:** Hairdresser newsletter signup
|
||||
|
||||
**Structural Order:**
|
||||
|
||||
|
|
|
|||
|
|
@ -38,7 +38,7 @@
|
|||
- "Sign up now" (jumping to action without motivation)
|
||||
|
||||
**Connects to:**
|
||||
- User's driving forces (from VTC)
|
||||
- User's driving forces (from Trigger Map)
|
||||
- Current emotional state (from Empowerment Frame)
|
||||
- The problem or aspiration that matters
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
# Example: Hairdresser Newsletter Signup
|
||||
|
||||
**VTC Context:** Hairdresser newsletter signup
|
||||
**Trigger Map Context:** Hairdresser newsletter signup
|
||||
|
||||
**Content Generations:**
|
||||
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@
|
|||
## 1. Synthesize All Context
|
||||
|
||||
Before generating, review and confirm you understand:
|
||||
- [ ] WHO the user is and what drives them (VTC)
|
||||
- [ ] WHO the user is and what drives them (Trigger Map)
|
||||
- [ ] WHERE they are in awareness (START → END)
|
||||
- [ ] WHAT action this content must enable (Action Filter)
|
||||
- [ ] HOW to make them feel capable (Empowerment Frame)
|
||||
|
|
|
|||
|
|
@ -54,7 +54,7 @@ The Content Creation Workshop is a disciplined, multi-model framework for genera
|
|||
- Defines: WHAT must this content accomplish? HOW will we know it worked?
|
||||
- Answers: What's the measurable outcome? Which models should we emphasize?
|
||||
|
||||
### 1. VTC = Strategic Foundation
|
||||
### 1. Trigger Map = Strategic Foundation
|
||||
- Provides: Business goal, solution, user, driving forces, customer awareness positioning
|
||||
- Answers: WHO are we serving? WHAT motivates them? WHERE are they in their journey?
|
||||
|
||||
|
|
@ -81,7 +81,7 @@ The Content Creation Workshop is a disciplined, multi-model framework for genera
|
|||
The workshop follows **7 sequential considerations** (agents can adapt flow naturally):
|
||||
|
||||
0. **Define Content Purpose** - What job must this content do?
|
||||
1. **Load VTC Context** - Establish strategic foundation
|
||||
1. **Load Trigger Map Context** - Establish strategic foundation
|
||||
2. **Apply Customer Awareness Strategy** - Determine appropriate language & information
|
||||
3. **Define Required Action** - Filter for relevance
|
||||
4. **Frame User Empowerment** - Set tone and transformation narrative
|
||||
|
|
@ -115,12 +115,12 @@ When you encounter content creation in a workflow:
|
|||
- Collaborative conversation through considerations
|
||||
- Adapt flow naturally (skip/combine as appropriate)
|
||||
|
||||
3. **Check for VTC** - Does the current context have a defined VTC?
|
||||
3. **Check for Trigger Map** - Does the current context have a Trigger Map?
|
||||
- If YES → Proceed with strategic generation
|
||||
- If NO → Suggest creating a VTC first (route to VTC Workshop)
|
||||
- If NO → Suggest creating a Trigger Map first (route to Phase 2)
|
||||
|
||||
4. **Execute Strategically:**
|
||||
- Consider all strategic layers (VTC, Awareness, Action, Empowerment, Structure)
|
||||
- Consider all strategic layers (Trigger Map, Awareness, Action, Empowerment, Structure)
|
||||
- Emphasize models based on content purpose (see Content Purpose Guide)
|
||||
- Don't force rigid steps - adapt naturally
|
||||
|
||||
|
|
@ -141,7 +141,7 @@ You control the strategic context and mode:
|
|||
2. **Choose your mode:**
|
||||
- Need quick suggestions? → "Suggest content for this hero section"
|
||||
- Want to explore together? → "Let's work through the homepage hero"
|
||||
3. **Provide context** or let agent find it (VTC, page purpose, user state)
|
||||
3. **Provide context** or let agent find it (Trigger Map, page purpose, user state)
|
||||
4. **Review against purpose** - Does it do its job? (objective criteria)
|
||||
5. **Select or refine** - Choose variant or combine elements
|
||||
6. **Iterate if needed** - Purpose not achieved? Refine and regenerate
|
||||
|
|
@ -233,7 +233,7 @@ DESIGNER: "Make headline more fear-focused"
|
|||
- Model priority emphasis
|
||||
|
||||
2. **Strategic Context Document** (shows your thinking)
|
||||
- VTC reference
|
||||
- Trigger Map reference
|
||||
- Awareness journey map
|
||||
- Action requirement
|
||||
- Empowerment frame
|
||||
|
|
@ -306,8 +306,7 @@ DESIGNER: "Make headline more fear-focused"
|
|||
- [Kathy Sierra Badass Users](../../../docs/models/kathy-sierra-badass-users.md)
|
||||
|
||||
**Whiteport Methods:**
|
||||
- [Value Trigger Chain](../../../docs/method/value-trigger-chain-guide.md)
|
||||
- [VTC Advanced Usage](../../../docs/learn/module-06-trigger-mapping/lesson-12-vtc-advanced-usage.md)
|
||||
- [Trigger Mapping Guide](../../../docs/method/trigger-mapping-guide.md)
|
||||
- [Content Purpose Guide](../../../docs/method/content-purpose-guide.md) - **Start here for content effectiveness**
|
||||
|
||||
**Workflows:**
|
||||
|
|
|
|||
|
|
@ -83,7 +83,7 @@ Define measurable or observable outcomes: "User recognizes themselves and contin
|
|||
|
||||
Ask: **"Which strategic models matter most for THIS job?"**
|
||||
|
||||
Present the Model Priority Matrix from the Content Purpose Guide. Different content types emphasize different models (Customer Awareness, Golden Circle, Badass Users, VTC, Action Mapping). Discuss and assign star ratings per model.
|
||||
Present the Model Priority Matrix from the Content Purpose Guide. Different content types emphasize different models (Customer Awareness, Golden Circle, Badass Users, Trigger Map, Action Mapping). Discuss and assign star ratings per model.
|
||||
|
||||
### 6. Document Purpose Definition
|
||||
|
||||
|
|
@ -124,7 +124,7 @@ Display: **"Select an Option:** [C] Continue"
|
|||
|
||||
## CRITICAL STEP COMPLETION NOTE
|
||||
|
||||
ONLY WHEN C is selected and the purpose definition is documented will you load {nextStepFile} to begin loading VTC context.
|
||||
ONLY WHEN C is selected and the purpose definition is documented will you load {nextStepFile} to begin loading Trigger Map context.
|
||||
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ nextStepFile: './step-03-action-filter.md'
|
|||
|
||||
## STEP GOAL:
|
||||
|
||||
Translate the VTC's awareness positioning into a concrete content strategy — determining what language the user can understand, what information they need, what proof is required, and what emotional journey we are facilitating.
|
||||
Translate the Trigger Map's awareness positioning into a concrete content strategy — determining what language the user can understand, what information they need, what proof is required, and what emotional journey we are facilitating.
|
||||
|
||||
## MANDATORY EXECUTION RULES (READ FIRST):
|
||||
|
||||
|
|
@ -44,20 +44,20 @@ Translate the VTC's awareness positioning into a concrete content strategy — d
|
|||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Available context: Purpose definition (Step 0), VTC context (Step 1)
|
||||
- Available context: Purpose definition (Step 0), Trigger Map context (Step 1)
|
||||
- Focus: Translating awareness levels into content strategy decisions
|
||||
- Limits: Do not write content — define the strategy for it
|
||||
- Dependencies: Confirmed VTC with awareness START and END levels
|
||||
- Dependencies: Confirmed Trigger Map with awareness START and END levels
|
||||
|
||||
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
||||
|
||||
### 1. Validate Starting Awareness Level
|
||||
|
||||
Present the START level from VTC and describe what it means. Confirm with user: does this match where users are when they encounter this content?
|
||||
Present the START level from the Trigger Map and describe what it means. Confirm with user: does this match where users are when they encounter this content?
|
||||
|
||||
### 2. Clarify Target Awareness Level
|
||||
|
||||
Present the END level from VTC and describe the shift. Confirm: is this the right awareness goal for this content?
|
||||
Present the END level from the Trigger Map and describe the shift. Confirm: is this the right awareness goal for this content?
|
||||
|
||||
### 3. Determine Awareness-Appropriate Language
|
||||
|
||||
|
|
|
|||
|
|
@ -44,10 +44,10 @@ Apply Action Mapping (Cathy Moore) to identify the specific action the user must
|
|||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Available context: Purpose (Step 0), VTC (Step 1), Awareness Strategy (Step 2)
|
||||
- Available context: Purpose (Step 0), Trigger Map (Step 1), Awareness Strategy (Step 2)
|
||||
- Focus: What action must the user take, and what information enables it
|
||||
- Limits: Do not write content — filter what information to include
|
||||
- Dependencies: VTC and Awareness Strategy from previous steps
|
||||
- Dependencies: Trigger Map and Awareness Strategy from previous steps
|
||||
|
||||
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
||||
|
||||
|
|
@ -63,13 +63,13 @@ Push for specific behaviors, not vague understanding:
|
|||
|
||||
### 2. Connect Action to Business Goal
|
||||
|
||||
Trace the logic: User does [action] → which leads to [outcome] → which drives [business goal from VTC].
|
||||
Trace the logic: User does [action] → which leads to [outcome] → which drives [business goal from Trigger Map].
|
||||
|
||||
Ask: **"Does this action clearly serve the VTC's business goal?"**
|
||||
Ask: **"Does this action clearly serve the Trigger Map's business goal?"**
|
||||
|
||||
### 3. Connect Action to Driving Forces
|
||||
|
||||
From VTC driving forces: **"By taking this action, how does the user move toward their wish or away from their fear?"**
|
||||
From the Trigger Map driving forces: **"By taking this action, how does the user move toward their wish or away from their fear?"**
|
||||
|
||||
### 4. Determine Essential Information
|
||||
|
||||
|
|
@ -96,7 +96,7 @@ action_filter:
|
|||
description: "[Specific action user must be able to take]"
|
||||
success_criteria: "[How we know they can do it]"
|
||||
business_impact:
|
||||
connection: "[How this action drives the VTC business goal]"
|
||||
connection: "[How this action drives the business goal]"
|
||||
logic: "[Action → Outcome → Goal]"
|
||||
user_motivation:
|
||||
positive_driver: "[How action satisfies their wish]"
|
||||
|
|
@ -141,7 +141,7 @@ ONLY WHEN C is selected and the action filter is documented will you load {nextS
|
|||
### ✅ SUCCESS:
|
||||
|
||||
- Specific action identified (not vague "understanding")
|
||||
- Action connects to VTC business goal
|
||||
- Action connects to Trigger Map business goal
|
||||
- Action satisfies user's driving forces
|
||||
- Essential information determined (what enables the action)
|
||||
- Unnecessary information identified (what does not enable action)
|
||||
|
|
|
|||
|
|
@ -44,7 +44,7 @@ Apply Kathy Sierra's Badass Users framework to frame content around user capabil
|
|||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Available context: Purpose (Step 0), VTC (Step 1), Awareness (Step 2), Action Filter (Step 3)
|
||||
- Available context: Purpose (Step 0), Trigger Map (Step 1), Awareness (Step 2), Action Filter (Step 3)
|
||||
- Focus: Framing content around user capability, not product features
|
||||
- Limits: Do not write content — define the empowerment frame for it
|
||||
- Dependencies: Action Filter from Step 3
|
||||
|
|
|
|||
|
|
@ -44,7 +44,7 @@ Apply Simon Sinek's Golden Circle to sequence all content from previous steps in
|
|||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Available context: Purpose (Step 0), VTC (Step 1), Awareness (Step 2), Action Filter (Step 3), Empowerment Frame (Step 4)
|
||||
- Available context: Purpose (Step 0), Trigger Map (Step 1), Awareness (Step 2), Action Filter (Step 3), Empowerment Frame (Step 4)
|
||||
- Focus: Sequencing existing content elements into persuasive order
|
||||
- Limits: Do not write final content — organize the structure for it
|
||||
- Dependencies: All previous steps provide the content elements to sequence
|
||||
|
|
@ -55,7 +55,7 @@ Apply Simon Sinek's Golden Circle to sequence all content from previous steps in
|
|||
|
||||
Ask: **"What's the emotional opening that connects to their driving forces?"**
|
||||
|
||||
Opens with user's current emotional state, connects to driving forces from VTC, makes them care before explaining the solution.
|
||||
Opens with user's current emotional state, connects to driving forces from the Trigger Map, makes them care before explaining the solution.
|
||||
|
||||
### 2. Identify the HOW
|
||||
|
||||
|
|
|
|||
|
|
@ -44,7 +44,7 @@ Generate 2-3 strategically grounded content variations based on all strategic co
|
|||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Available context: All outputs from Steps 0-5 (Purpose, VTC, Awareness, Action, Empowerment, Structure)
|
||||
- Available context: All outputs from Steps 0-5 (Purpose, Trigger Map, Awareness, Action, Empowerment, Structure)
|
||||
- Focus: Synthesizing strategy into actual content text, then refining with user
|
||||
- Limits: Variations are strategic alternatives, not random drafts
|
||||
- Dependencies: Complete WHY-HOW-WHAT structure from Step 5
|
||||
|
|
@ -72,7 +72,7 @@ Ask: **"Which variation resonates most with you?"** Allow selection, combination
|
|||
|
||||
Ask: **"Does this feel aligned with the strategic context?"**
|
||||
|
||||
Check against: VTC business goal, driving forces, awareness level, required action, capability framing, WHY-HOW-WHAT structure.
|
||||
Check against: Trigger Map business goal, driving forces, awareness level, required action, capability framing, WHY-HOW-WHAT structure.
|
||||
|
||||
### 5. Refinement
|
||||
|
||||
|
|
@ -89,7 +89,7 @@ Ask: **"Does this move the user from START to END awareness?"** Verify the journ
|
|||
### 8. Document Final Content
|
||||
|
||||
Save using content-output template with full strategic traceability:
|
||||
- VTC reference, awareness journey, action enabled, empowerment achieved
|
||||
- Trigger Map reference, awareness journey, action enabled, empowerment achieved
|
||||
- Implementation notes (technical, design, language tags, asset needs)
|
||||
|
||||
### 9. Present MENU OPTIONS
|
||||
|
|
|
|||
|
|
@ -11,10 +11,10 @@
|
|||
|
||||
## Strategic Foundation
|
||||
|
||||
### Step 1: VTC Context
|
||||
### Step 1: Trigger Map Context
|
||||
|
||||
```yaml
|
||||
vtc_reference:
|
||||
trigger_map_reference:
|
||||
business_goal: "{goal text}"
|
||||
solution: "{solution name/description}"
|
||||
user:
|
||||
|
|
@ -81,7 +81,7 @@ action_filter:
|
|||
success_criteria: "{How we know they can do it}"
|
||||
|
||||
business_impact:
|
||||
connection: "{How this action drives the VTC business goal}"
|
||||
connection: "{How this action drives the business goal}"
|
||||
logic: "{Action → Outcome → Goal}"
|
||||
|
||||
user_motivation:
|
||||
|
|
@ -293,7 +293,7 @@ WHAT Section:
|
|||
|
||||
**This content serves:**
|
||||
|
||||
- **VTC Business Goal:** {How this drives the goal}
|
||||
- **Business Goal:** {How this drives the goal}
|
||||
- **User Driving Forces:**
|
||||
- Positive: {How it satisfies wish}
|
||||
- Negative: {How it addresses fear}
|
||||
|
|
@ -345,5 +345,5 @@ WHAT Section:
|
|||
---
|
||||
|
||||
_Created using WDS Content Creation Workshop (5-Model Framework)_
|
||||
_Models: VTC, Customer Awareness Cycle, Action Mapping, Badass Users, Golden Circle_
|
||||
_Models: Trigger Map, Customer Awareness Cycle, Action Mapping, Badass Users, Golden Circle_
|
||||
|
||||
|
|
|
|||
|
|
@ -21,7 +21,7 @@ description: Strategic text content generation using the 5-model framework
|
|||
## The Five-Model Framework
|
||||
|
||||
1. **Content Purpose** — The job to do
|
||||
2. **VTC** — Strategic foundation
|
||||
2. **Trigger Map** — Strategic foundation
|
||||
3. **Customer Awareness Cycle** — Content strategy
|
||||
4. **Action Mapping** — Content filter
|
||||
5. **Badass Users** — Tone & frame
|
||||
|
|
|
|||
|
|
@ -158,7 +158,7 @@ Phase 0: Project Setup
|
|||
├─→ Tech stack (optional)
|
||||
├─→ Component library (optional)
|
||||
├─→ Brief level (complete/simplified)
|
||||
├─→ Strategic analysis (full/VTC/skip)
|
||||
├─→ Strategic analysis (full/simplified/skip)
|
||||
├─→ Create folder structure
|
||||
└─→ Generate .wds-project-outline.yaml
|
||||
│
|
||||
|
|
|
|||
|
|
@ -93,7 +93,7 @@ This dialog guides the **AI-assisted UI generation workflow** using Google Stitc
|
|||
|
||||
| Document | Path | Key Elements |
|
||||
|----------|------|--------------|
|
||||
| VTC/Trigger Map | [{path}]({path}) | {Key triggers for this feature} |
|
||||
| Trigger Map | [{path}]({path}) | {Key triggers for this feature} |
|
||||
| User Personas | [{path}]({path}) | {Target personas} |
|
||||
| Product Brief | [{path}]({path}) | {Relevant product goals} |
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue