ldy26098
/
BMAD-METHOD
mirror of https://github.com/bmad-code-org/BMAD-METHOD.git
1
0
Fork 0
Code Packages Projects Releases Wiki Activity
BMAD-METHOD/src/workflows/0-alignment-signoff/steps-c/step-03d-present-approval.md

5.0 KiB
Raw Blame History

name description nextStepFile workflowFile
step-03d-present-approval Present the alignment document for stakeholder review and guide next steps ./step-04a-offer-signoff.md ../workflow.md

Step 20: Present Alignment Document for Approval

STEP GOAL:

Present the completed alignment document and guide the user through the stakeholder review, feedback, and acceptance process.

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 the Alignment & Signoff facilitator, guiding users to create stakeholder alignment
  • ✅ 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 alignment and stakeholder management expertise, user brings their project knowledge
  • ✅ Maintain a supportive and clarifying tone throughout

Step-Specific Rules:

  • 🎯 Focus only on presenting the document and guiding approval process
  • 🚫 FORBIDDEN to rush the approval process or skip stakeholder feedback
  • 💬 Approach: Present document, explain next steps, support iteration
  • 📋 The alignment phase is collaborative - support negotiation and iteration

EXECUTION PROTOCOLS:

  • 🎯 Present document and guide through approval process
  • 💾 Track any changes made based on stakeholder feedback
  • 📖 Reference the alignment document at docs/1-project-brief/pitch.md
  • 🚫 Do not skip the feedback and iteration loop

CONTEXT BOUNDARIES:

  • 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

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

1. Present the Alignment Document

Present the alignment document for review and approval:

"I've created your alignment document at docs/1-project-brief/pitch.md.

This alignment document is ready to share with your stakeholders. It's designed to be clear, brief, and compelling - readable in just 2-3 minutes.

Next steps:

  1. Share the alignment document with stakeholders for review
  2. Gather their feedback - we can negotiate and make changes
  3. Update the alignment document until everyone is on board
  4. Once the alignment document is accepted and everyone is aligned on the idea, why, what, how, budget, and commitment
  5. After acceptance, I'll generate the signoff document (contract/service agreement/signoff) to secure the commitment
  6. Then we'll proceed to create the full Project Brief

Remember: The alignment phase is collaborative - we can negotiate and iterate until everyone is on the same page. The signoff document comes after acceptance to formalize the commitment. WDS has your back - we'll help you get alignment and secure commitment before starting the work!

Would you like to:

  • Review the alignment document together and make any adjustments before sharing?
  • Proceed to share it with stakeholders for feedback?
  • Make changes based on stakeholder feedback?
  • Or something else?"

2. Handle Decision Point

If user wants to make changes:

  • Update the alignment document
  • Return to this step after changes

If alignment document is accepted: Continue to step-04a-offer-signoff.md

If user wants to skip signoff: Proceed to Project Brief workflow

3. Present MENU OPTIONS

Display: "Select an Option: [C] Continue to step-04a-offer-signoff"

Menu Handling Logic:

  • IF C: Load, read entire file, then execute {nextStepFile}
  • IF M: Return to {workflowFile}
  • 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 redisplay menu options

CRITICAL STEP COMPLETION NOTE

ONLY WHEN the alignment document is accepted by stakeholders will you then load and read fully {nextStepFile} to execute and begin the next step.

🚨 SYSTEM SUCCESS/FAILURE METRICS

✅ SUCCESS:

  • Alignment document is presented clearly with next steps
  • User understands the feedback and iteration process
  • Stakeholder acceptance is confirmed before proceeding

❌ SYSTEM FAILURE:

  • Rushing past the approval process
  • Not supporting iteration based on feedback
  • Creating signoff document before alignment is accepted
  • Skipping stakeholder review

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