calctext/_bmad/wds/workflows/2-trigger-mapping/steps-c/step-07g-quality-check.md

name, description, nextStepFile, activityWorkflowFile, qualityChecklist

name	description	nextStepFile	activityWorkflowFile	qualityChecklist
step-07g-quality-check	Verify all documents are complete, consistent, and properly cross-linked	./step-08a-mermaid-init-structure.md	../workflow.md	../data/quality-checklist.md

Step 23: Quality Check & Verification

STEP GOAL:

Ensure all generated documents are complete, consistent, and properly cross-linked by running through a comprehensive 13-dimension quality checklist and fixing any issues found.

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 - verifying completeness and quality
• ✅ 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 systematic quality verification across all documents
• 🚫 FORBIDDEN to skip any quality dimension or approve with known issues
• 💬 Approach: Systematic checklist-driven verification
• 📋 Fix any issues found before marking as complete
• 📋 Reference {qualityChecklist} for complete checklist

EXECUTION PROTOCOLS:

• 🎯 Verify all 13 quality dimensions
• 💾 Fix any issues found during verification
• 📖 Present verification results to user
• 🚫 Do not approve with unresolved issues

CONTEXT BOUNDARIES:

• Available context: All generated documents
• Focus: Quality verification across all dimensions
• Limits: Must check ALL dimensions - no shortcuts
• Dependencies: Requires all documents generated

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

1. Run Quality Verification

Verify all generated documents across 13 quality dimensions:

1. File Structure - All required files exist with consistent naming
2. Mermaid Diagram - Renders correctly, proper styling
3. Content Consistency - Names, numbers, timelines match across docs
4. Language Quality - Empowering, organic transformation language
5. Cross-References - All links working between documents
6. Persona Completeness - All 13 sections, 6 driving forces with Promises/Answers
7. Hub Document (00) - On-page summaries, flywheel, ~220-250 lines
8. Business Goals (01) - THE ENGINE marked, metrics complete, ~150-160 lines
9. Key Insights (05) - Flywheel, focus areas, design implications, ~145-155 lines
10. Feature Impact (06) - Scoring system, prioritization (if exists)
11. Priority Tiers - Consistent emojis and language throughout
12. Driving Forces - Each has specific Product Promise/Answer
13. Formatting - Markdown, headers, links, emojis render correctly

If any check fails: Identify document, re-read step instructions, make corrections, re-verify.

2. Present Verification Results

Output: "Trigger Map Documentation Complete & Verified!

Created Structure:

B-Trigger-Map/
 00-trigger-map.md          ([X] lines) - Hub with diagram & navigation
 01-Business-Goals.md        ([X] lines) - Objectives & flywheel
 02-[Primary Name].md       ([X] lines) - Primary persona
 03-[Secondary Name].md     ([X] lines) - Secondary persona
 04-[Tertiary Name].md      ([X] lines) - Tertiary persona [if exists]
 05-Key-Insights.md         ([X] lines) - Strategic implications
 06-Feature-Impact.md       ([X] lines) - Feature prioritization [if completed]

Quality Verified:

• All cross-links working
• Mermaid diagram renders correctly
• Language is empowering and organic
• All 6 driving forces have Product Promises/Answers
• Priority tiers consistent throughout
• Transformation journey clearly described

Primary Target: [Primary Persona Name] THE ENGINE: [PRIMARY GOAL statement]

Ready for Phase 3: Platform Requirements or Phase 4: UX Design!"

Mark workflow as complete and return to main trigger mapping flow.

3. Present MENU OPTIONS

Display: "Select an Option: [C] Continue to Mermaid Diagram Generation | [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 quality checks must pass before proceeding.

---

🚨 SYSTEM SUCCESS/FAILURE METRICS

✅ SUCCESS:

• All 13 quality dimensions verified
• Any issues found were fixed and re-verified
• All documents complete and consistent
• Cross-references working
• Verification results presented to user
• Document structure summary shown

❌ SYSTEM FAILURE:

• Skipping quality dimensions
• Approving with known issues
• Not fixing found issues
• Not re-verifying after corrections
• Not presenting verification results

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