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/bmm/workflows/2-plan-workflows/prd/steps/step-01b-continue.md

5.6 KiB
Raw Blame History

name description workflow_path thisStepFile workflowFile outputFile
step-01b-continue Resume an interrupted PRD workflow from the last completed step {project-root}/_bmad/bmm/workflows/2-plan-workflows/prd {workflow_path}/steps/step-01b-continue.md {workflow_path}/workflow.md {planning_artifacts}/prd.md

Step 1B: Workflow Continuation

STEP GOAL:

Resume the PRD workflow from where it was left off, ensuring smooth continuation with full context restoration.

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 product-focused PM facilitator collaborating with an expert peer
  • ✅ We engage in collaborative dialogue, not command-response
  • ✅ Resume workflow from exact point where it was interrupted

Step-Specific Rules:

  • 💬 FOCUS on understanding where we left off and continuing appropriately
  • 🚫 FORBIDDEN to modify content completed in previous steps
  • 📖 Only reload documents that were already tracked in inputDocuments

EXECUTION PROTOCOLS:

  • 🎯 Show your analysis of current state before taking action
  • Update frontmatter: add this step name to the end of the steps completed array
  • 📖 Only load documents that were already tracked in inputDocuments
  • 🚫 FORBIDDEN to discover new input documents during continuation

CONTEXT BOUNDARIES:

  • Available context: Current document and frontmatter are already loaded
  • Focus: Workflow state analysis and continuation logic only
  • Limits: Don't assume knowledge beyond what's in the document
  • Dependencies: Existing workflow state from previous session

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

1. Analyze Current State

State Assessment: Review the frontmatter to understand:

  • stepsCompleted: Which steps are already done
  • lastStep: The most recently completed step number
  • inputDocuments: What context was already loaded
  • documentCounts: briefs, research, brainstorming, projectDocs counts
  • All other frontmatter variables

2. Restore Context Documents

Context Reloading:

  • For each document in inputDocuments, load the complete file
  • This ensures you have full context for continuation
  • Don't discover new documents - only reload what was previously processed

3. Present Current Progress

Progress Report to User: "Welcome back {{user_name}}! I'm resuming our PRD collaboration for {{project_name}}.

Current Progress:

  • Steps completed: {stepsCompleted}
  • Last worked on: Step {lastStep}
  • Context documents available: {len(inputDocuments)} files

Document Status:

  • Current PRD document is ready with all completed sections
  • Ready to continue from where we left off

Does this look right, or do you want to make any adjustments before we proceed?"

4. Determine Continuation Path

Next Step Logic: Based on lastStep value, determine which step to load next:

  • If lastStep = 1 → Load ./step-02-discovery.md
  • If lastStep = 2 → Load ./step-03-success.md
  • If lastStep = 3 → Load ./step-04-journeys.md
  • If lastStep = 4 → Load ./step-05-domain.md
  • If lastStep = 5 → Load ./step-06-innovation.md
  • If lastStep = 6 → Load ./step-07-project-type.md
  • If lastStep = 7 → Load ./step-08-scoping.md
  • If lastStep = 8 → Load ./step-09-functional.md
  • If lastStep = 9 → Load ./step-10-nonfunctional.md
  • If lastStep = 10 → Load ./step-11-complete.md
  • If lastStep = 11 → Workflow already complete

5. Handle Workflow Completion

If workflow already complete (lastStep = 11): "Great news! It looks like we've already completed the PRD workflow for {{project_name}}.

The final document is ready at {outputFile} with all sections completed through step 11.

Would you like me to:

  • Review the completed PRD with you
  • Suggest next workflow steps (like architecture or epic creation)
  • Start a new PRD revision

What would be most helpful?"

6. Present MENU OPTIONS

If workflow not complete: Display: "Ready to continue with Step {nextStepNumber}?

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

Menu Handling Logic:

  • IF C: Load, read entire file, then execute the appropriate next step file based on lastStep
  • IF Any other comments or queries: respond and redisplay menu

EXECUTION RULES:

  • ALWAYS halt and wait for user input after presenting menu
  • ONLY proceed to next step when user selects 'C'

CRITICAL STEP COMPLETION NOTE

ONLY WHEN [C continue option] is selected and [current state confirmed], will you then load and read fully the appropriate next step file to resume the workflow.

🚨 SYSTEM SUCCESS/FAILURE METRICS

✅ SUCCESS:

  • All previous input documents successfully reloaded
  • Current workflow state accurately analyzed and presented
  • User confirms understanding of progress before continuation
  • Correct next step identified and prepared for loading

❌ SYSTEM FAILURE:

  • Discovering new input documents instead of reloading existing ones
  • Modifying content from already completed steps
  • Loading wrong next step based on lastStep value
  • Proceeding without user confirmation of current state

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