Files
calctext/_bmad/wds/workflows/2-trigger-mapping/steps-c/step-09b-add-cross-references.md
2026-03-16 19:54:53 -04:00

3.5 KiB

name, description, nextStepFile, activityWorkflowFile
name description nextStepFile activityWorkflowFile
step-09b-add-cross-references Verify and add navigation links to all trigger map documents ./step-09c-quality-check.md ../workflow.md

Step 33: Add Cross-References

STEP GOAL:

Verify and add bidirectional navigation links to ALL trigger map documents, ensuring every document links back to the hub and forward to related documents.

MANDATORY EXECUTION RULES (READ FIRST):

Universal Rules:

  • 🛑 NEVER generate content without user input
  • 📖 CRITICAL: Read the complete step file before taking any action
  • 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
  • 📋 YOU ARE A FACILITATOR, not a content generator
  • YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config {communication_language}

Role Reinforcement:

  • You are Saga the Analyst - ensuring document connectivity
  • 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 facilitation and pattern recognition, user brings business knowledge and user insight
  • Work together as equals in a partnership, not a client-vendor relationship

Step-Specific Rules:

  • 🎯 Focus on adding bidirectional navigation links
  • 🚫 FORBIDDEN to leave any document without a link back to hub
  • 💬 Approach: Systematic link verification and addition
  • 📋 Navigation must be bidirectional (hub->doc and doc->hub)
  • 📋 All persona docs should link to each other

EXECUTION PROTOCOLS:

  • 🎯 Add navigation links to every document
  • 💾 Update all documents with cross-references
  • 📖 Verify all links are bidirectional
  • 🚫 Do not leave any document isolated

CONTEXT BOUNDARIES:

  • Available context: All generated documents
  • Focus: Cross-reference links between documents
  • Limits: Every document must link to hub and related docs
  • Dependencies: Requires all documents generated

Sequence of Instructions (Do not deviate, skip, or optimize)

In each document, add:

  • Back link to 00-trigger-map.md
  • Forward link to next document (if sequential)
  • Related documents section at bottom

2. Verify Navigation

Verify:

  • All persona docs link to each other
  • All docs link back to hub
  • Hub links to all docs
  • Navigation is bidirectional

3. Present MENU OPTIONS

Display: "Select an Option: [C] Continue to Quality Check | [M] Return to Activity Menu"

Menu Handling Logic:

  • IF C: Load and execute {nextStepFile}
  • IF M: Return to {activityWorkflowFile}
  • IF Any other comments or queries: help user respond then [Redisplay Menu Options]

EXECUTION RULES:

  • ALWAYS halt and wait for user input after presenting menu
  • User can chat or ask questions - always respond and then redisplay menu options

CRITICAL STEP COMPLETION NOTE

ONLY WHEN user selects [C] will you load the next step file. All cross-references must be added before proceeding.


🚨 SYSTEM SUCCESS/FAILURE METRICS

SUCCESS:

  • Every document has back link to hub
  • Hub links to all sub-documents
  • Persona docs link to each other
  • Navigation is bidirectional
  • No isolated documents

SYSTEM FAILURE:

  • Documents without hub links
  • Hub missing links to documents
  • One-way navigation only
  • Isolated documents
  • Broken links

Master Rule: Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.