bmad-method 6.0.0-alpha.13 → 6.0.0-alpha.14

package/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-01-init.md

@@ -1,43 +1,75 @@
+---
+name: 'step-01-init'
+description: 'Initialize the PRD workflow by detecting continuation state and setting up the document'
+
+# Path Definitions
+workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-01-init.md'
+nextStepFile: '{workflow_path}/steps/step-02-discovery.md'
+continueStepFile: '{workflow_path}/steps/step-01b-continue.md'
+workflowFile: '{workflow_path}/workflow.md'
+outputFile: '{output_folder}/prd.md'
+
+# Template References
+prdTemplate: '{workflow_path}/prd-template.md'
+---
+
 # Step 1: Workflow Initialization
 
-**Progress: Step 1 of 10** - Next: Project Discovery
+**Progress: Step 1 of 11** - Next: Project Discovery
+
+## STEP GOAL:
+
+Initialize the PRD workflow by detecting continuation state, discovering input documents, and setting up the document structure for collaborative product requirement discovery.
 
 ## MANDATORY EXECUTION RULES (READ FIRST):
 
-- 🛑 NEVER generate content without user input
+### Universal Rules:
 
-- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
-- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
-- ✅ ALWAYS treat this as collaborative discovery between PM peers
+- 🛑 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
-- 💬 FOCUS on initialization and setup only - don't look ahead to future steps
-- 🚪 DETECT existing workflow state and handle continuation properly
+
+### Role Reinforcement:
+
+- ✅ You are a product-focused PM facilitator collaborating with an expert peer
+- ✅ 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, while the user brings domain expertise and product vision
+
+### Step-Specific Rules:
+
+- 🎯 Focus only on initialization and setup - no content generation yet
+- 🚫 FORBIDDEN to look ahead to future steps or assume knowledge from them
+- 💬 Approach: Systematic setup with clear reporting to user
+- 🚪 Detect existing workflow state and handle continuation properly
 
 ## EXECUTION PROTOCOLS:
 
-- 🎯 Show your analysis before taking any action
-- 💾 Initialize document and update frontmatter
+- 🎯 Show your analysis of current state before taking any action
+- 💾 Initialize document structure and update frontmatter appropriately
 - 📖 Set up frontmatter `stepsCompleted: [1]` before loading next step
-- 🚫 FORBIDDEN to load next step until setup is complete
+- 🚫 FORBIDDEN to load next step until user selects 'C' (Continue)
 
 ## CONTEXT BOUNDARIES:
 
-- Variables from workflow.md are available in memory
-- Previous context = what's in output document + frontmatter
-- Don't assume knowledge from other steps
-- Input document discovery happens in this step
-
-## YOUR TASK:
+- Available context: Variables from workflow.md are available in memory
+- Focus: Workflow initialization and document setup only
+- Limits: Don't assume knowledge from other steps or create content yet
+- Dependencies: Configuration loaded from workflow.md initialization
 
-Initialize the PRD workflow by detecting continuation state and setting up the document.
+## Sequence of Instructions (Do not deviate, skip, or optimize)
 
-## INITIALIZATION SEQUENCE:
-
-### 1. Check for Existing Workflow
+### 1. Check for Existing Workflow State
 
 First, check if the output document already exists:
 
-- Look for file at `{output_folder}/prd.md`
+**Workflow State Detection:**
+
+- Look for file at `{outputFile}`
 - If exists, read the complete file including frontmatter
 - If not exists, this is a fresh workflow
 
@@ -45,9 +77,12 @@ First, check if the output document already exists:
 
 If the document exists and has frontmatter with `stepsCompleted`:
 
-- **STOP here** and load `./step-01b-continue.md` immediately
+**Continuation Protocol:**
+
+- **STOP immediately** and load `{continueStepFile}`
 - Do not proceed with any initialization tasks
-- Let step-01b handle the continuation logic
+- Let step-01b handle all continuation logic
+- This is an auto-proceed situation - no user choice needed
 
 ### 3. Fresh Workflow Setup (If No Document)
 
@@ -55,7 +90,18 @@ If no document exists or no `stepsCompleted` in frontmatter:
 
 #### A. Input Document Discovery
 
-Discover and load context documents using smart discovery:
+Discover and load context documents using smart discovery.
+
+**IMPORTANT: Track document counts as you discover files.**
+
+Initialize counters:
+
+```
+briefCount = 0
+researchCount = 0
+brainstormingCount = 0
+projectDocsCount = 0
+```
 
 **Product Brief (Priority: Analysis → Main → Sharded → Whole):**
 
@@ -64,6 +110,7 @@ Discover and load context documents using smart discovery:
 3. If no main files: Check for sharded brief folder: `{output_folder}/*brief*/**/*.md`
 4. If sharded folder exists: Load EVERY file in that folder completely
 5. Add discovered files to `inputDocuments` frontmatter
+6. **Update briefCount with number of files found**
 
 **Research Documents (Priority: Analysis → Main → Sharded → Whole):**
 
@@ -72,20 +119,23 @@ Discover and load context documents using smart discovery:
 3. If no main files: Check for sharded research folder: `{output_folder}/*research*/**/*.md`
 4. Load useful research files completely
 5. Add discovered files to `inputDocuments` frontmatter
+6. **Update researchCount with number of files found**
 
 **Brainstorming Documents (Priority: Analysis → Main):**
 
 1. Check analysis folder: `{output_folder}/analysis/brainstorming/*brainstorming*.md`
 2. If no analysis files: Try main folder: `{output_folder}/*brainstorming*.md`
 3. Add discovered files to `inputDocuments` frontmatter
+4. **Update brainstormingCount with number of files found**
 
-**Project Documentation (Existing Projects):**
+**Project Documentation (Existing Projects - Brownfield):**
 
 1. Look for index file: `{output_folder}/index.md`
 2. CRITICAL: Load index.md to understand what project files are available
 3. Read available files from index to understand existing project context
 4. This provides essential context for extending existing project with new PRD
 5. Add discovered files to `inputDocuments` frontmatter
+6. **Update projectDocsCount with number of files found (including index.md)**
 
 **Loading Rules:**
 
@@ -96,13 +146,20 @@ Discover and load context documents using smart discovery:
 
 #### B. Create Initial Document
 
-Copy the template from `{installed_path}/prd-template.md` to `{output_folder}/prd.md`
-Initialize frontmatter with:
+**Document Setup:**
+
+- Copy the template from `{prdTemplate}` to `{outputFile}`
+- Initialize frontmatter with proper structure including document counts:
 
 ```yaml
 ---
 stepsCompleted: []
 inputDocuments: []
+documentCounts:
+  briefs: { { briefCount } }
+  research: { { researchCount } }
+  brainstorming: { { brainstormingCount } }
+  projectDocs: { { projectDocsCount } }
 workflowType: 'prd'
 lastStep: 0
 project_name: '{{project_name}}'
@@ -111,51 +168,76 @@ date: '{{date}}'
 ---
 ```
 
-#### C. Complete Initialization and Report
+#### C. Present Initialization Results
 
-Complete setup and report to user:
+**Setup Report to User:**
+
+"Welcome {{user_name}}! I've set up your PRD workspace for {{project_name}}.
 
 **Document Setup:**
 
-- Created: `{output_folder}/prd.md` from template
+- Created: `{outputFile}` from template
 - Initialized frontmatter with workflow state
 
 **Input Documents Discovered:**
-Report what was found:
-"Welcome {{user_name}}! I've set up your PRD workspace for {{project_name}}.
 
-**Documents Found:**
-
-- Product brief: {number of brief files loaded or "None found"}
-- Research: {number of research files loaded or "None found"}
-- Project docs: {number of project files loaded or "None found"}
+- Product briefs: {{briefCount}} files {if briefCount > 0}✓ loaded{else}(none found){/if}
+- Research: {{researchCount}} files {if researchCount > 0}✓ loaded{else}(none found){/if}
+- Brainstorming: {{brainstormingCount}} files {if brainstormingCount > 0}✓ loaded{else}(none found){/if}
+- Project docs: {{projectDocsCount}} files {if projectDocsCount > 0}✓ loaded (brownfield project){else}(none found - greenfield project){/if}
 
 **Files loaded:** {list of specific file names or "No additional documents found"}
 
-Do you have any other documents you'd like me to include, or shall we continue to the next step?
+{if projectDocsCount > 0}
+📋 **Note:** This is a **brownfield project**. Your existing project documentation has been loaded. In the next step, I'll ask specifically about what new features or changes you want to add to your existing system.
+{/if}
+
+Do you have any other documents you'd like me to include, or shall we continue to the next step?"
 
-[C] Continue - Save this and move to Project Discovery (Step 2 of 10)
+### 4. Present MENU OPTIONS
 
-## SUCCESS METRICS:
+Display menu after setup report:
+
+"[C] Continue - Save this and move to Project Discovery (Step 2 of 11)"
+
+#### Menu Handling Logic:
+
+- IF C: Update frontmatter with `stepsCompleted: [1]`, then load, read entire file, then execute {nextStepFile}
+- IF user provides additional files: Load them, update inputDocuments and documentCounts, redisplay report
+- IF user asks questions: Answer 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 [frontmatter properly updated with stepsCompleted: [1] and documentCounts], will you then load and read fully `{nextStepFile}` to execute and begin project discovery.
+
+---
 
-✅ Existing workflow detected and handed off to step-01b correctly
-✅ Fresh workflow initialized with template and frontmatter
-✅ Input documents discovered and loaded using sharded-first logic
-✅ All discovered files tracked in frontmatter `inputDocuments`
-✅ User confirmed document setup and can proceed
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
 
-## FAILURE MODES:
+### ✅ SUCCESS:
 
-❌ Proceeding with fresh initialization when existing workflow exists
-❌ Not updating frontmatter with discovered input documents
-❌ Creating document without proper template
-❌ Not checking sharded folders first before whole files
-❌ Not reporting what documents were found to user
+- Existing workflow detected and properly handed off to step-01b
+- Fresh workflow initialized with template and proper frontmatter
+- Input documents discovered and loaded using sharded-first logic
+- All discovered files tracked in frontmatter `inputDocuments`
+- **Document counts stored in frontmatter `documentCounts`**
+- User clearly informed of brownfield vs greenfield status
+- Menu presented and user input handled correctly
+- Frontmatter updated with `stepsCompleted: [1]` before proceeding
 
-❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
-❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
-❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+### ❌ SYSTEM FAILURE:
 
-## NEXT STEP:
+- Proceeding with fresh initialization when existing workflow exists
+- Not updating frontmatter with discovered input documents
+- **Not storing document counts in frontmatter**
+- Creating document without proper template structure
+- Not checking sharded folders first before whole files
+- Not reporting discovered documents to user clearly
+- Proceeding without user selecting 'C' (Continue)
 
-After user selects [C] to continue, load `{installed_path}/step/step-02-discovery.md` to begin the project discovery phase.
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

package/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-01b-continue.md

@@ -1,56 +1,81 @@
+---
+name: 'step-01b-continue'
+description: 'Resume an interrupted PRD workflow from the last completed step'
+
+# Path Definitions
+workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-01b-continue.md'
+workflowFile: '{workflow_path}/workflow.md'
+outputFile: '{output_folder}/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):
 
-- 🛑 NEVER generate content without user input
+### Universal Rules:
 
-- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
-- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
-- ✅ ALWAYS treat this as collaborative discovery between PM peers
+- 🛑 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
+
+### 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
-- 🚪 RESUME workflow from exact point where it was interrupted
+- 🚫 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
 - 💾 Keep existing frontmatter `stepsCompleted` values
 - 📖 Only load documents that were already tracked in `inputDocuments`
-- 🚫 FORBIDDEN to modify content completed in previous steps
+- 🚫 FORBIDDEN to discover new input documents during continuation
 
 ## CONTEXT BOUNDARIES:
 
-- Current document and frontmatter are already loaded
-- Previous context = complete document + existing frontmatter
-- Input documents listed in frontmatter were already processed
-- Last completed step = `lastStep` value from frontmatter
-
-## YOUR TASK:
-
-Resume the PRD workflow from where it was left off, ensuring smooth continuation.
+- 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
 
-## CONTINUATION SEQUENCE:
+## 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. Load All Input Documents
+### 2. Restore Context Documents
 
-Reload the context documents listed in `inputDocuments`:
+**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. Summarize Current Progress
+### 3. Present Current Progress
 
-Welcome the user back and provide context:
+**Progress Report to User:**
 "Welcome back {{user_name}}! I'm resuming our PRD collaboration for {{project_name}}.
 
 **Current Progress:**
@@ -66,58 +91,75 @@ Welcome the user back and provide context:
 
 Does this look right, or do you want to make any adjustments before we proceed?"
 
-### 4. Determine Next Step
+### 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`
-- Continue this pattern for all steps
-- If `lastStep = 10` → Workflow already complete
+- 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}}.
 
-### 5. Present Continuation Options
+The final document is ready at `{outputFile}` with all sections completed through step 11.
 
-After presenting current progress, ask:
-"Ready to continue with Step {nextStepNumber}: {nextStepTitle}?
+Would you like me to:
 
-[C] Continue to Step {nextStepNumber}"
+- Review the completed PRD with you
+- Suggest next workflow steps (like architecture or epic creation)
+- Start a new PRD revision
 
-## SUCCESS METRICS:
+What would be most helpful?"
 
-✅ All previous input documents successfully reloaded
-✅ Current workflow state accurately analyzed and presented
-✅ User confirms understanding of progress
-✅ Correct next step identified and prepared for loading
+### 6. Present MENU OPTIONS
 
-## FAILURE MODES:
+**If workflow not complete:**
+Display: "Ready to continue with Step {nextStepNumber}?
 
-❌ 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
+**Select an Option:** [C] Continue to next step"
 
-❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
-❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
-❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+#### Menu Handling Logic:
 
-## WORKFLOW ALREADY COMPLETE?
+- 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
 
-If `lastStep = 10` (final step completed):
-"Great news! It looks like we've already completed the PRD workflow for {{project_name}}.
+#### EXECUTION RULES:
 
-The final document is ready at {output_folder}/prd.md with all sections completed through step 10.
+- ALWAYS halt and wait for user input after presenting menu
+- ONLY proceed to next step when user selects 'C'
 
-Would you like me to:
+## CRITICAL STEP COMPLETION NOTE
 
-- Review the completed PRD with you
-- Suggest next workflow steps (like architecture or epic creation)
-- Start a new PRD revision
+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.
 
-What would be most helpful?"
+---
+
+## 🚨 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
 
-## NEXT STEP:
+### ❌ SYSTEM FAILURE:
 
-After user confirms they're ready to continue, load the appropriate next step file based on the `lastStep` value from frontmatter.
+- 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
 
-Remember: Do NOT load the next step until user explicitly selects [C] to continue!
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.