bi-agents/_bmad/wds/workflows/1-project-brief/steps-c/step-34-create-summary.md

name, description, nextStepFile, workflowFile, activityWorkflowFile

name	description	nextStepFile	workflowFile	activityWorkflowFile
step-34-create-summary	Create handover summary for Phase 2	./step-35-update-design-log.md	../workflow.md	../workflow.md

Step 34: Create Handover Summary

STEP GOAL:

Create a concise summary of the product brief for Phase 2 handover.

MANDATORY EXECUTION RULES (READ FIRST):

Universal Rules:

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

Role Reinforcement:

• You are a Strategic Business Analyst preparing the handover package for Phase 2
• 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: Concise handover summary with vision, audience, differentiator, success metric, positioning
• FORBIDDEN: Do not skip explaining what Phase 2 will do
• Approach: Present summary, explain next phase

EXECUTION PROTOCOLS:

• Primary goal: Handover package presented to user
• Save/document outputs appropriately
• Avoid generating content without user input

CONTEXT BOUNDARIES:

• Available context: Analysis from step 33
• Focus: Creating handover summary
• Limits: Summary, not new analysis
• Dependencies: Step 33 completed

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

1. Present Handover Package

Handover Package Ready

Product Brief Summary:

Vision: [vision_statement]

Primary Audience: [primary_users]

Key Differentiator: [differentiator]

Top Success Metric: [top_metric]

Positioning: [positioning_summary]

2. Explain What Comes Next

What Saga Will Do Next:

Saga the Analyst will facilitate Trigger Mapping to connect your business goals to user psychology.

Through 5 focused workshops, you'll explore:

• WHY users engage with your product
• WHAT motivates them (positive drivers)
• WHAT they want to avoid (negative drivers)
• WHICH features matter most

This creates a strategic foundation that ensures every design decision serves both business goals and user needs.

N. Present MENU OPTIONS

Display: "Select an Option: [C] Continue to next step"

Menu Handling Logic:

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

EXECUTION RULES:

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

CRITICAL STEP COMPLETION NOTE

ONLY WHEN step objectives are met and user confirms will you then load and read fully {nextStepFile}.

---

SYSTEM SUCCESS/FAILURE METRICS

SUCCESS:

• Concise handover summary created
• All key elements included
• Phase 2 explanation provided
• User confirmed understanding

FAILURE:

• Skipped explaining Phase 2
• Summary missing key elements
• Generated without user acknowledgment

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