bi-agents/_bmad/wds/workflows/6-asset-generation/steps-c/step-01-load-trigger-map-context.md

name, description, nextStepFile

name	description	nextStepFile
step-01-load-trigger-map-context	Establish the strategic foundation by loading relevant Trigger Map context for content creation	./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:

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

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.