phase 3 input disco and output updated

src/core/workflows/brainstorming/steps/step-02b-ai-recommended.md

@@ -141,7 +141,7 @@ Provide deeper insight into each recommended technique:
 
 ### 5. Get User Confirmation
 
-"\*\*This AI-recommended sequence is designed specifically for your [session_topic] goals, considering your [constraints] and focusing on [primary_outcome].
+"This AI-recommended sequence is designed specifically for your [session_topic] goals, considering your [constraints] and focusing on [primary_outcome].
 
 **Does this approach sound perfect for your session?**
 

src/modules/bmb/workflows/create-module/steps/step-01b-continue.md

@@ -72,7 +72,7 @@ Extract current status from frontmatter fields:
 - **Steps Completed:** {stepsCompleted count}/{total steps}
 - **Location:** {bmb_creations_output_folder}/{module_name}
 
-\*\*Progress Summary:"
+Progress Summary:"
 
 Based on stepsCompleted, show:
 

src/modules/bmgd/workflows/3-technical/game-architecture/instructions.md

@@ -659,7 +659,7 @@ Enforcement: "All agents MUST follow this pattern"
 
   </check>
 
-<action>Save document to {output_folder}/architecture.md</action>
+<action>Save document to {planning_artifacts}/architecture.md</action>
 
   <check if="standalone_mode != true">
     <action>Load the FULL file: {output_folder}/bmgd-workflow-status.yaml</action>

src/modules/bmgd/workflows/3-technical/generate-project-context/steps/step-01-discover.md

@@ -43,7 +43,7 @@ Load and analyze project files to identify technologies:
 
 **Architecture Document:**
 
-- Look for `{output_folder}/game-architecture.md` or `{output_folder}/architecture.md`
+- Look for `{output_folder}/game-architecture.md` or `{planning_artifacts}/architecture.md`
 - Extract engine choice with specific version (Unity, Unreal, Godot, custom)
 - Note architectural decisions that affect implementation
 

src/modules/bmgd/workflows/4-production/create-story/workflow.yaml

@@ -22,7 +22,7 @@ variables:
   sprint_status: "{implementation_artifacts}/sprint-status.yaml || {output_folder}/sprint-status.yaml" # Primary source for story tracking
   epics_file: "{output_folder}/epics.md" # Preferred source for epic/story breakdown
   prd_file: "{output_folder}/PRD.md" # Fallback for requirements
-  architecture_file: "{output_folder}/architecture.md" # Optional architecture context
+  architecture_file: "{planning_artifacts}/architecture.md" # Optional architecture context
   tech_spec_file: "" # Will be auto-discovered from docs as tech-spec-epic-{{epic_num}}-*.md
   tech_spec_search_dir: "{project-root}/docs"
   tech_spec_glob_template: "tech-spec-epic-{{epic_num}}*.md"

src/modules/bmm/workflows/1-analysis/create-product-brief/steps/step-01-init.md

@@ -94,18 +94,20 @@ load context documents using smart discovery. Documents can be in the following
 - {product_knowledge}/**
 - docs/**
 
-Also - when searching - documents can be a single markdown file, or a folder with an index and multiple files.
+Also - when searching - documents can be a single markdown file, or a folder with an index and multiple files. For Example, if searching for `*foo*.md` and not found, also search for a folder called *foo*/index.md (which indicates sharded content)
 
 Try to discover the following:
 - Brainstorming Reports (`*brainstorming*.md`)
 - Research Documents (`*research*.md`)
 - Project Documentation (generally multiple documents might be found for this in the `{product_knowledge}` or `docs` folder.)
+- Project Context (`**/project-context.md`)
 
 <critical>Confirm what you have found with the user, along with asking if the user wants to provide anything else. Only after this confirmation will you proceed to follow the loading rules</critical>
 
 **Loading Rules:**
 
 - Load ALL discovered files completely that the user confirmed or provided (no offset/limit)
+- If there is a project context, whatever is relevant should try to be biased in the remainder of this whole workflow process
 - For sharded folders, load ALL files to get complete picture, using the index first to potentially know the potential of each document
 - index.md is a guide to what's relevant whenever available
 - Track all successfully loaded files in frontmatter `inputDocuments` array
@@ -131,6 +133,7 @@ Try to discover the following:
 - Research: {number of research files loaded or "None found"}
 - Brainstorming: {number of brainstorming files loaded or "None found"}
 - Project docs: {number of project files loaded or "None found"}
+- Project Context: {number of project context files loaded or "None found"}
 
 **Files loaded:** {list of specific file names or "No additional documents found"}
 

src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-01-init.md

@@ -59,18 +59,20 @@ Discover and load context documents using smart discovery. Documents can be in t
 - {product_knowledge}/**
 - docs/**
 
-Also - when searching - documents can be a single markdown file, or a folder with an index and multiple files.
+Also - when searching - documents can be a single markdown file, or a folder with an index and multiple files. For Example, if searching for `*foo*.md` and not found, also search for a folder called *foo*/index.md (which indicates sharded content)
 
 Try to discover the following:
 - Product Brief (`*brief*.md`)
 - Research Documents (`*prd*.md`)
 - Project Documentation (generally multiple documents might be found for this in the `{product_knowledge}` or `docs` folder.)
+- Project Context (`**/project-context.md`)
 
 <critical>Confirm what you have found with the user, along with asking if the user wants to provide anything else. Only after this confirmation will you proceed to follow the loading rules</critical>
 
 **Loading Rules:**
 
 - Load ALL discovered files completely that the user confirmed or provided (no offset/limit)
+- If there is a project context, whatever is relevant should try to be biased in the remainder of this whole workflow process
 - For sharded folders, load ALL files to get complete picture, using the index first to potentially know the potential of each document
 - index.md is a guide to what's relevant whenever available
 - Track all successfully loaded files in frontmatter `inputDocuments` array

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

@@ -97,18 +97,20 @@ Discover and load context documents using smart discovery. Documents can be in t
 - {product_knowledge}/**
 - docs/**
 
-Also - when searching - documents can be a single markdown file, or a folder with an index and multiple files.
+Also - when searching - documents can be a single markdown file, or a folder with an index and multiple files. For Example, if searching for `*foo*.md` and not found, also search for a folder called *foo*/index.md (which indicates sharded content)
 
 Try to discover the following:
 - Product Brief (`*brief*.md`)
 - Research Documents (`/*research*.md`)
 - Project Documentation (generally multiple documents might be found for this in the `{product_knowledge}` or `docs` folder.)
+- Project Context (`**/project-context.md`)
 
 <critical>Confirm what you have found with the user, along with asking if the user wants to provide anything else. Only after this confirmation will you proceed to follow the loading rules</critical>
 
 **Loading Rules:**
 
 - Load ALL discovered files completely that the user confirmed or provided (no offset/limit)
+- If there is a project context, whatever is relevant should try to be biased in the remainder of this whole workflow process
 - For sharded folders, load ALL files to get complete picture, using the index first to potentially know the potential of each document
 - index.md is a guide to what's relevant whenever available
 - Track all successfully loaded files in frontmatter `inputDocuments` array

src/modules/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-01-document-discovery.md

@@ -68,23 +68,23 @@ Search for each document type using these patterns:
 
 #### A. PRD Documents
 
-- Whole: `{output_folder}/*prd*.md`
+- Whole: `{planning_artifacts}/*prd*.md`
-- Sharded: `{output_folder}/*prd*/index.md` and related files
+- Sharded: `{planning_artifacts}/*prd*/index.md` and related files
 
 #### B. Architecture Documents
 
-- Whole: `{output_folder}/*architecture*.md`
+- Whole: `{planning_artifacts}/*architecture*.md`
-- Sharded: `{output_folder}/*architecture*/index.md` and related files
+- Sharded: `{planning_artifacts}/*architecture*/index.md` and related files
 
 #### C. Epics & Stories Documents
 
-- Whole: `{output_folder}/*epic*.md`
+- Whole: `{planning_artifacts}/*epic*.md`
-- Sharded: `{output_folder}/*epic*/index.md` and related files
+- Sharded: `{planning_artifacts}/*epic*/index.md` and related files
 
 #### D. UX Design Documents
 
-- Whole: `{output_folder}/*ux*.md`
+- Whole: `{planning_artifacts}/*ux*.md`
-- Sharded: `{output_folder}/*ux*/index.md` and related files
+- Sharded: `{planning_artifacts}/*ux*/index.md` and related files
 
 ### 3. Organize Findings
 

src/modules/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-02-prd-analysis.md

@@ -10,7 +10,7 @@ thisStepFile: '{workflow_path}/steps/step-02-prd-analysis.md'
 nextStepFile: '{workflow_path}/steps/step-03-epic-coverage-validation.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{planning_artifacts}/implementation-readiness-report-{{date}}.md'
-epicsFile: '{output_folder}/*epic*.md' # Will be resolved to actual file
+epicsFile: '{planning_artifacts}/*epic*.md' # Will be resolved to actual file
 ---
 
 # Step 2: PRD Analysis

src/modules/bmm/workflows/3-solutioning/create-architecture/steps/step-01-init.md

@@ -36,7 +36,7 @@ Initialize the Architecture workflow by detecting continuation state, discoverin
 
 First, check if the output document already exists:
 
-- Look for existing {output_folder}||{planning_artifacts} architecture.md or \*\*/architecture/
+- Look for existing {planning_artifacts}/`*architecture*.md`
 - If exists, read the complete file(s) including frontmatter
 - If not exists, this is a fresh workflow
 
@@ -54,58 +54,30 @@ 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. Documents can be in the following locations:
+- {planning_artifacts}/**
+- {output_folder}/**
+- {product_knowledge}/**
+- docs/**
 
-**PRD Document (Priority: Analysis → Main → Sharded → Whole):**
+Also - when searching - documents can be a single markdown file, or a folder with an index and multiple files. For Example, if searching for `*foo*.md` and not found, also search for a folder called *foo*/index.md (which indicates sharded content)
 
-1. Check analysis folders: {output_folder} and {planning_artifacts} for a `*prd*.md`
+Try to discover the following:
-2. If no main files: Check for sharded PRD folder: `**/*prd*/**/*.md`
+- Product Brief (`*brief*.md`)
-3. If sharded folder exists: Load EVERY file in that folder completely
+- Product Requirements Document (`*prd*.md`)
-4. Add discovered files to `inputDocuments` frontmatter
+- UX Design (`*ux-design*.md`) and other
+- Research Documents (`*research*.md`)
+- Project Documentation (generally multiple documents might be found for this in the `{product_knowledge}` or `docs` folder.)
+- Project Context (`**/project-context.md`)
 
-**Epics/Stories Document (Priority: Analysis → Main → Sharded → Whole):**
+<critical>Confirm what you have found with the user, along with asking if the user wants to provide anything else. Only after this confirmation will you proceed to follow the loading rules</critical>
-
-1. Check folders: {output_folder} and {planning_artifacts} for a `*epic*.md`
-2. If no analysis files: Try main folder: `{output_folder}/*epic*.md`
-3. If no main files: Check for sharded epics folder: `{output_folder}/*epic*/**/*.md`
-4. If sharded folder exists: Load EVERY file in that folder completely
-5. Add discovered files to `inputDocuments` frontmatter
-
-**UX Design Specification (Priority: Analysis → Main → Sharded → Whole):**
-
-1. Check folders: {output_folder} and {planning_artifacts} for a `*ux*.md`
-2. If no main files: Check for sharded UX folder: `{output_folder}/*ux*/**/*.md`
-3. If sharded folder exists: Load EVERY file in that folder completely
-4. Add discovered files to `inputDocuments` frontmatter
-
-**Research Documents (Priority: Analysis → Main):**
-
-1. Check folders {output_folder} and {planning_artifacts} for `/research/*research*.md`
-2. If no files: Try folder: `{output_folder}/*research*.md`
-3. Add discovered files to `inputDocuments` frontmatter
-
-**Project Documentation (Existing Projects):**
-
-1. Look for index file: `{project_knowledge}/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 architecture
-5. Add discovered files to `inputDocuments` frontmatter
-6. IF no index.md, ask user which files from the folder to include
-
-**Project Context Rules (Critical for AI Agents):**
-
-1. Check for project context file: `**/project-context.md`
-2. If exists: Load COMPLETE file contents - this contains critical rules for AI agents
-3. Add to frontmatter `hasProjectContext: true` and track file path
-4. Report to user: "Found existing project context with {number_of_rules} agent rules"
-5. This file contains language-specific patterns, testing rules, and implementation guidelines that must be followed
 
 **Loading Rules:**
 
-- Load ALL discovered files completely (no offset/limit)
+- Load ALL discovered files completely that the user confirmed or provided (no offset/limit)
-- For sharded folders, load ALL files to get complete picture
+- If there is a project context, whatever is relevant should try to be biased in the remainder of this whole workflow process
-- For existing projects, use index.md as guide to what's relevant
+- For sharded folders, load ALL files to get complete picture, using the index first to potentially know the potential of each document
+- index.md is a guide to what's relevant whenever available
 - Track all successfully loaded files in frontmatter `inputDocuments` array
 
 #### B. Validate Required Inputs
@@ -117,13 +89,13 @@ Before proceeding, verify we have the essential inputs:
 - If no PRD found: "Architecture requires a PRD to work from. Please run the PRD workflow first or provide the PRD file path."
 - Do NOT proceed without PRD
 
-**Other Inputs:**
+**Other Input that might exist:**
 
-- UX Spec: "Provides UI/UX architectural requirements" (Optional)
+- UX Spec: "Provides UI/UX architectural requirements"
 
 #### C. Create Initial Document
 
-Copy the template from `{installed_path}/architecture-decision-template.md` to `{output_folder}/architecture.md`
+Copy the template from `{installed_path}/architecture-decision-template.md` to `{planning_artifacts}/architecture.md`
 
 #### D. Complete Initialization and Report
 
@@ -131,7 +103,7 @@ Complete setup and report to user:
 
 **Document Setup:**
 
-- Created: `{output_folder}/architecture.md` from template
+- Created: `{planning_artifacts}/architecture.md` from template
 - Initialized frontmatter with workflow state
 
 **Input Documents Discovered:**
@@ -141,7 +113,6 @@ Report what was found:
 **Documents Found:**
 
 - PRD: {number of PRD files loaded or "None found - REQUIRED"}
-- Epics/Stories: {number of epic files loaded or "None found"}
 - UX Design: {number of UX files loaded or "None found"}
 - Research: {number of research files loaded or "None found"}
 - Project docs: {number of project files loaded or "None found"}
@@ -177,6 +148,6 @@ Ready to begin architectural decision making. Do you have any other documents yo
 
 ## NEXT STEP:
 
-After user selects [C] to continue, load `./step-02-context.md` to analyze the project context and begin architectural decision making.
+After user selects [C] to continue, only after ensuring all the template output has been created, then load `./step-02-context.md` to analyze the project context and begin architectural decision making.
 
 Remember: Do NOT proceed to step-02 until user explicitly selects [C] from the menu and setup is confirmed!

src/modules/bmm/workflows/3-solutioning/create-architecture/steps/step-02-context.md

@@ -185,7 +185,7 @@ Show the generated content and present choices:
 
 #### If 'C' (Continue):
 
-- Append the final content to `{output_folder}/architecture.md`
+- Append the final content to `{planning_artifacts}/architecture.md`
 - Update frontmatter: `stepsCompleted: [1, 2]`
 - Load `./step-03-starter.md`
 

src/modules/bmm/workflows/3-solutioning/create-architecture/steps/step-03-starter.md

@@ -292,7 +292,7 @@ Show the generated content and present choices:
 
 #### If 'C' (Continue):
 
-- Append the final content to `{output_folder}/architecture.md`
+- Append the final content to `{planning_artifacts}/architecture.md`
 - Update frontmatter: `stepsCompleted: [1, 2, 3]`
 - Load `./step-04-decisions.md`
 

src/modules/bmm/workflows/3-solutioning/create-architecture/steps/step-04-decisions.md

@@ -279,7 +279,7 @@ Show the generated decisions content and present choices:
 
 #### If 'C' (Continue):
 
-- Append the final content to `{output_folder}/architecture.md`
+- Append the final content to `{planning_artifacts}/architecture.md`
 - Update frontmatter: `stepsCompleted: [1, 2, 3, 4]`
 - Load `./step-05-patterns.md`
 

src/modules/bmm/workflows/3-solutioning/create-architecture/steps/step-05-patterns.md

@@ -320,7 +320,7 @@ Show the generated patterns content and present choices:
 
 #### If 'C' (Continue):
 
-- Append the final content to `{output_folder}/architecture.md`
+- Append the final content to `{planning_artifacts}/architecture.md`
 - Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5]`
 - Load `./step-06-structure.md`
 

src/modules/bmm/workflows/3-solutioning/create-architecture/steps/step-06-structure.md

@@ -340,7 +340,7 @@ Show the generated project structure content and present choices:
 
 #### If 'C' (Continue):
 
-- Append the final content to `{output_folder}/architecture.md`
+- Append the final content to `{planning_artifacts}/architecture.md`
 - Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5, 6]`
 - Load `./step-07-validation.md`
 

src/modules/bmm/workflows/3-solutioning/create-architecture/steps/step-07-validation.md

@@ -320,7 +320,7 @@ Show the validation results and present choices:
 
 #### If 'C' (Continue):
 
-- Append the final content to `{output_folder}/architecture.md`
+- Append the final content to `{planning_artifacts}/architecture.md`
 - Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5, 6, 7]`
 - Load `./step-08-complete.md`
 

src/modules/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md

@@ -116,7 +116,7 @@ Provide specific next steps for implementation:
 
 **Immediate Next Steps:**
 
-1. **Review the complete architecture document** at `{output_folder}/architecture.md`
+1. **Review the complete architecture document** at `{planning_artifacts}/architecture.md`
 2. **Begin with project initialization** using the starter template command documented
 3. **Create first implementation story** for project setup
 4. **Start implementing user stories** following the architectural decisions
@@ -151,7 +151,7 @@ Prepare the final content to append to the document:
 **Architecture Decision Workflow:** COMPLETED ✅
 **Total Steps Completed:** 8
 **Date Completed:** {{current_date}}
-**Document Location:** {output_folder}/architecture.md
+**Document Location:** {planning_artifacts}/architecture.md
 
 ### Final Architecture Deliverables
 
@@ -243,15 +243,15 @@ The chosen starter template and architectural patterns provide a production-read
 
 **Save Final Document:**
 
-- Ensure all content is properly appended to `{output_folder}/architecture.md`
+- Ensure all content is properly appended to `{planning_artifacts}/architecture.md`
 - Update frontmatter with completion status
 - Verify document is complete and coherent
 
 **Workflow Status Update:**
 If not in standalone mode, update workflow status:
 
-- Load `{output_folder}/bmm-workflow-status.yaml`
+- Load `{planning_artifacts}/bmm-workflow-status.yaml`
-- Update workflow_status["create-architecture"] = "{output_folder}/architecture.md"
+- Update workflow_status["create-architecture"] = "{planning_artifacts}/architecture.md"
 - Save file with all structure and comments preserved
 
 ### 6. Present Completion to User
@@ -268,7 +268,7 @@ Your architecture for {{project_name}} is comprehensive, validated, and ready fo
 - Implementation guidance for the development phase
 
 **📍 Where to find it:**
-`{output_folder}/architecture.md`
+`{planning_artifacts}/architecture.md`
 
 **🚀 What's next:**
 

src/modules/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-01-validate-prerequisites.md

@@ -94,7 +94,7 @@ Before proceeding, Ask the user if there are any other documents, or if what you
 
 ### 3. Extract Functional Requirements (FRs)
 
-From the PRD document (full or sharded), extract ALL functional requirements:
+From the PRD document (full or sharded), read then entire document and extract ALL functional requirements:
 
 **Extraction Method:**
 

src/modules/bmm/workflows/4-implementation/create-story/workflow.yaml

@@ -22,7 +22,7 @@ variables:
   sprint_status: "{implementation_artifacts}/sprint-status.yaml || {output_folder}/sprint-status.yaml" # Primary source for story tracking
   epics_file: "{output_folder}/epics.md" # Enhanced epics+stories with BDD and source hints
   prd_file: "{output_folder}/PRD.md" # Fallback for requirements (if not in epics file)
-  architecture_file: "{output_folder}/architecture.md" # Fallback for constraints (if not in epics file)
+  architecture_file: "{planning_artifacts}/architecture.md" # Fallback for constraints (if not in epics file)
   ux_file: "{output_folder}/ux.md" # Fallback for UX requirements (if not in epics file)
   story_title: "" # Will be elicited if not derivable