bmad-method 6.0.0-alpha.19 → 6.0.0-alpha.20

package/src/modules/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-06-resolve-findings.md

@@ -0,0 +1,140 @@
+---
+name: 'step-06-resolve-findings'
+description: 'Handle review findings interactively, apply fixes, update tech-spec with final status'
+
+workflow_path: '{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-dev'
+thisStepFile: '{workflow_path}/steps/step-06-resolve-findings.md'
+---
+
+# Step 6: Resolve Findings
+
+**Goal:** Handle adversarial review findings interactively, apply fixes, finalize tech-spec.
+
+---
+
+## AVAILABLE STATE
+
+From previous steps:
+
+- `{baseline_commit}` - Git HEAD at workflow start
+- `{execution_mode}` - "tech-spec" or "direct"
+- `{tech_spec_path}` - Tech-spec file (if Mode A)
+- Findings table from step-05
+
+---
+
+## RESOLUTION OPTIONS
+
+Present choice to user:
+
+```
+How would you like to handle these findings?
+
+**[1] Walk through** - Discuss each finding individually
+**[2] Auto-fix** - Automatically fix issues classified as "real"
+**[3] Skip** - Acknowledge and proceed to commit
+```
+
+---
+
+## OPTION 1: WALK THROUGH
+
+For each finding in order:
+
+1. Present the finding with context
+2. Ask: **fix now / skip / discuss**
+3. If fix: Apply the fix immediately
+4. If skip: Note as acknowledged, continue
+5. If discuss: Provide more context, re-ask
+6. Move to next finding
+
+After all findings processed, summarize what was fixed/skipped.
+
+---
+
+## OPTION 2: AUTO-FIX
+
+1. Filter findings to only those classified as "real"
+2. Apply fixes for each real finding
+3. Report what was fixed:
+
+```
+**Auto-fix Applied:**
+- F1: {description of fix}
+- F3: {description of fix}
+...
+
+Skipped (noise/uncertain): F2, F4
+```
+
+---
+
+## OPTION 3: SKIP
+
+1. Acknowledge all findings were reviewed
+2. Note that user chose to proceed without fixes
+3. Continue to completion
+
+---
+
+## UPDATE TECH-SPEC (Mode A only)
+
+If `{execution_mode}` is "tech-spec":
+
+1. Load `{tech_spec_path}`
+2. Update status to "Completed"
+3. Add review notes:
+   ```
+   ## Review Notes
+   - Adversarial review completed
+   - Findings: {count} total, {fixed} fixed, {skipped} skipped
+   - Resolution approach: {walk-through/auto-fix/skip}
+   ```
+4. Save changes
+
+---
+
+## COMPLETION OUTPUT
+
+```
+**Review complete. Ready to commit.**
+
+**Implementation Summary:**
+- {what was implemented}
+- Files modified: {count}
+- Tests: {status}
+- Review findings: {X} addressed, {Y} skipped
+
+{Explain what was implemented based on user_skill_level}
+```
+
+---
+
+## WORKFLOW COMPLETE
+
+This is the final step. The Quick Dev workflow is now complete.
+
+User can:
+
+- Commit changes
+- Run additional tests
+- Start new Quick Dev session
+
+---
+
+## SUCCESS METRICS
+
+- User presented with resolution options
+- Chosen approach executed correctly
+- Fixes applied cleanly (if applicable)
+- Tech-spec updated with final status (Mode A)
+- Completion summary provided
+- User understands what was implemented
+
+## FAILURE MODES
+
+- Not presenting resolution options
+- Auto-fixing "noise" or "uncertain" findings
+- Not updating tech-spec after resolution (Mode A)
+- No completion summary
+- Leaving user unclear on next steps

package/src/modules/bmm/workflows/bmad-quick-flow/quick-dev/workflow.md

@@ -0,0 +1,51 @@
+---
+name: quick-dev
+description: 'Flexible development - execute tech-specs OR direct instructions with optional planning.'
+---
+
+# Quick Dev Workflow
+
+**Goal:** Execute implementation tasks efficiently, either from a tech-spec or direct user instructions.
+
+**Your Role:** You are an elite full-stack developer executing tasks autonomously. Follow patterns, ship code, run tests. Every response moves the project forward.
+
+---
+
+## WORKFLOW ARCHITECTURE
+
+This uses **step-file architecture** for focused execution:
+
+- Each step loads fresh to combat "lost in the middle"
+- State persists via variables: `{baseline_commit}`, `{execution_mode}`, `{tech_spec_path}`
+- Sequential progression through implementation phases
+
+---
+
+## INITIALIZATION
+
+### Configuration Loading
+
+Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
+
+- `user_name`, `communication_language`, `user_skill_level`
+- `output_folder`, `sprint_artifacts`
+- `date` as system-generated current datetime
+
+### Paths
+
+- `installed_path` = `{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-dev`
+- `project_context` = `**/project-context.md` (load if exists)
+- `project_levels` = `{project-root}/_bmad/bmm/workflows/workflow-status/project-levels.yaml`
+
+### Related Workflows
+
+- `create_tech_spec_workflow` = `{project-root}/_bmad/bmm/workflows/bmad-quick-flow/create-tech-spec/workflow.yaml`
+- `workflow_init` = `{project-root}/_bmad/bmm/workflows/workflow-status/init/workflow.yaml`
+- `party_mode_exec` = `{project-root}/_bmad/core/workflows/party-mode/workflow.md`
+- `advanced_elicitation` = `{project-root}/_bmad/core/tasks/advanced-elicitation.xml`
+
+---
+
+## EXECUTION
+
+Load and execute `steps/step-01-mode-detection.md` to begin the workflow.

package/src/modules/bmm/workflows/document-project/instructions.md

@@ -1,7 +1,7 @@
 # Document Project Workflow Router
 
-<critical>The workflow execution engine is governed by: {project-root}/\_bmad/core/tasks/workflow.xml</critical>
-<critical>You MUST have already loaded and processed: {project-root}/\_bmad/bmm/workflows/document-project/workflow.yaml</critical>
+<critical>The workflow execution engine is governed by: {project-root}/_bmad/core/tasks/workflow.xml</critical>
+<critical>You MUST have already loaded and processed: {project-root}/_bmad/bmm/workflows/document-project/workflow.yaml</critical>
 <critical>Communicate all responses in {communication_language}</critical>
 
 <workflow>
@@ -83,40 +83,39 @@ Would you like to:
 Your choice [1/2/3]:
 </ask>
 
-    <check if="user selects 1">
-      <action>Set resume_mode = true</action>
-      <action>Set workflow_mode = {{mode}}</action>
-      <action>Load findings summaries from state file</action>
-      <action>Load cached project_type_id(s) from state file</action>
-
-      <critical>CONDITIONAL CSV LOADING FOR RESUME:</critical>
-      <action>For each cached project_type_id, load ONLY the corresponding row from: {documentation_requirements_csv}</action>
-      <action>Skip loading project-types.csv and architecture_registry.csv (not needed on resume)</action>
-      <action>Store loaded doc requirements for use in remaining steps</action>
+  <check if="user selects 1">
+    <action>Set resume_mode = true</action>
+    <action>Set workflow_mode = {{mode}}</action>
+    <action>Load findings summaries from state file</action>
+    <action>Load cached project_type_id(s) from state file</action>
 
-      <action>Display: "Resuming {{workflow_mode}} from {{current_step}} with cached project type(s): {{cached_project_types}}"</action>
+    <critical>CONDITIONAL CSV LOADING FOR RESUME:</critical>
+    <action>For each cached project_type_id, load ONLY the corresponding row from: {documentation_requirements_csv}</action>
+    <action>Skip loading project-types.csv and architecture_registry.csv (not needed on resume)</action>
+    <action>Store loaded doc requirements for use in remaining steps</action>
 
-      <check if="workflow_mode == deep_dive">
-        <action>Load and execute: {installed_path}/workflows/deep-dive-instructions.md with resume context</action>
-      </check>
+    <action>Display: "Resuming {{workflow_mode}} from {{current_step}} with cached project type(s): {{cached_project_types}}"</action>
 
-      <check if="workflow_mode == initial_scan OR workflow_mode == full_rescan">
-        <action>Load and execute: {installed_path}/workflows/full-scan-instructions.md with resume context</action>
-      </check>
+    <check if="workflow_mode == deep_dive">
+      <action>Load and execute: {installed_path}/workflows/deep-dive-instructions.md with resume context</action>
     </check>
 
-    <check if="user selects 2">
-      <action>Create archive directory: {output_folder}/.archive/</action>
-      <action>Move old state file to: {output_folder}/.archive/project-scan-report-{{timestamp}}.json</action>
-      <action>Set resume_mode = false</action>
-      <action>Continue to Step 0.5</action>
+    <check if="workflow_mode == initial_scan OR workflow_mode == full_rescan">
+      <action>Load and execute: {installed_path}/workflows/full-scan-instructions.md with resume context</action>
     </check>
 
-    <check if="user selects 3">
-      <action>Display: "Exiting workflow without changes."</action>
-      <action>Exit workflow</action>
-    </check>
+  </check>
+
+  <check if="user selects 2">
+    <action>Create archive directory: {output_folder}/.archive/</action>
+    <action>Move old state file to: {output_folder}/.archive/project-scan-report-{{timestamp}}.json</action>
+    <action>Set resume_mode = false</action>
+    <action>Continue to Step 0.5</action>
+  </check>
 
+  <check if="user selects 3">
+    <action>Display: "Exiting workflow without changes."</action>
+    <action>Exit workflow</action>
   </check>
 
   <check if="state file age >= 24 hours">

package/src/modules/bmm/workflows/document-project/workflow.yaml

@@ -6,7 +6,7 @@ author: "BMad"
 
 # Critical variables
 config_source: "{project-root}/_bmad/bmm/config.yaml"
-output_folder: "{config_source}:output_folder"
+output_folder: "{config_source}:project_knowledge"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
 document_output_language: "{config_source}:document_output_language"
@@ -15,7 +15,6 @@ date: system-generated
 
 # Module path and component files
 installed_path: "{project-root}/_bmad/bmm/workflows/document-project"
-template: false # This is an action workflow with multiple output files
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
 
@@ -23,7 +22,7 @@ validation: "{installed_path}/checklist.md"
 documentation_requirements_csv: "{installed_path}/documentation-requirements.csv"
 
 # Output configuration - Multiple files generated in output folder
-# Primary output: {output_folder}/index.md
+# Primary output: {output_folder}/project-documentation/
 # Additional files generated by sub-workflows based on project structure
 
 standalone: true

package/src/modules/bmm/workflows/generate-project-context/project-context-template.md

@@ -2,7 +2,8 @@
 project_name: '{{project_name}}'
 user_name: '{{user_name}}'
 date: '{{date}}'
-sections_completed: []
+sections_completed: ['technology_stack']
+existing_patterns_found: { { number_of_patterns_discovered } }
 ---
 
 # Project Context for AI Agents

package/src/modules/bmm/workflows/generate-project-context/steps/step-01-discover.md

@@ -33,7 +33,7 @@ Discover the project's technology stack, existing patterns, and critical impleme
 
 First, check if project context already exists:
 
-- Look for file at `{output_folder}/project-context.md`
+- Look for file at `{project_knowledge}/project-context.md or {project-root}/**/project-context.md`
 - If exists: Read complete file to understand existing rules
 - Present to user: "Found existing project context with {number_of_sections} sections. Would you like to update this or create a new one?"
 
@@ -43,7 +43,7 @@ Load and analyze project files to identify technologies:
 
 **Architecture Document:**
 
-- Look for `{output_folder}/architecture.md`
+- Look for `{planning_artifacts}/architecture.md`
 - Extract technology choices with specific versions
 - Note architectural decisions that affect implementation
 
@@ -55,7 +55,7 @@ Load and analyze project files to identify technologies:
 
 **Configuration Files:**
 
-- Look for TypeScript config (`tsconfig.json`)
+- Look for project language specific configs ( example: `tsconfig.json`)
 - Build tool configs (webpack, vite, next.config.js, etc.)
 - Linting and formatting configs (.eslintrc, .prettierrc, etc.)
 - Testing configurations (jest.config.js, vitest.config.ts, etc.)
@@ -123,17 +123,7 @@ Based on discovery, create or update the context document:
 #### A. Fresh Document Setup (if no existing context)
 
 Copy template from `{installed_path}/project-context-template.md` to `{output_folder}/project-context.md`
-Initialize frontmatter with:
-
-```yaml
----
-project_name: '{{project_name}}'
-user_name: '{{user_name}}'
-date: '{{date}}'
-sections_completed: ['technology_stack']
-existing_patterns_found: { { number_of_patterns_discovered } }
----
-```
+Initialize frontmatter fields.
 
 #### B. Existing Document Update
 
@@ -190,4 +180,4 @@ Ready to create/update your project context. This will help AI agents implement
 
 After user selects [C] to continue, load `./step-02-generate.md` to collaboratively generate the specific project context rules.
 
-Remember: Do NOT proceed to step-02 until user explicitly selects [C] from the menu and discovery is confirmed!
+Remember: Do NOT proceed to step-02 until user explicitly selects [C] from the menu and discovery is confirmed and the initial file has been written as directed in this discovery step!

package/src/modules/bmm/workflows/generate-project-context/steps/step-02-generate.md

@@ -28,8 +28,8 @@ This step will generate content and present choices for each rule category:
 
 ## PROTOCOL INTEGRATION:
 
-- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml
-- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode
+- When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml
+- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode
 - PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed
 - User accepts/rejects protocol changes before proceeding
 

package/src/modules/bmm/workflows/testarch/atdd/atdd-checklist-template.md

@@ -290,13 +290,14 @@ test('should do something', async ({ {fixtureName} }) => {
 
 ## Next Steps
 
-1. **Review this checklist** with team in standup or planning
-2. **Run failing tests** to confirm RED phase: `{test_command_all}`
-3. **Begin implementation** using implementation checklist as guide
-4. **Work one test at a time** (red → green for each)
-5. **Share progress** in daily standup
-6. **When all tests pass**, refactor code for quality
-7. **When refactoring complete**, manually update story status to 'done' in sprint-status.yaml
+1. **Share this checklist and failing tests** with the dev workflow (manual handoff)
+2. **Review this checklist** with team in standup or planning
+3. **Run failing tests** to confirm RED phase: `{test_command_all}`
+4. **Begin implementation** using implementation checklist as guide
+5. **Work one test at a time** (red → green for each)
+6. **Share progress** in daily standup
+7. **When all tests pass**, refactor code for quality
+8. **When refactoring complete**, manually update story status to 'done' in sprint-status.yaml
 
 ---
 

package/src/modules/bmm/workflows/testarch/atdd/checklist.md

@@ -184,6 +184,7 @@ Before starting this workflow, verify:
   - [ ] Red-green-refactor workflow
   - [ ] Execution commands
   - [ ] Next steps for DEV team
+- [ ] Output shared with DEV workflow (manual handoff; not auto-consumed)
 
 ### All Tests Verified to Fail (RED Phase)
 

package/src/modules/bmm/workflows/testarch/atdd/instructions.md

@@ -772,6 +772,7 @@ After completing this workflow, provide a summary:
 5. Share progress in daily standup
 
 **Output File**: {output_file}
+**Manual Handoff**: Share `{output_file}` and failing tests with the dev workflow (not auto-consumed).
 
 **Knowledge Base References Applied**:
 

package/src/modules/bmm/workflows/testarch/automate/checklist.md

@@ -13,6 +13,7 @@ Before starting this workflow, verify:
 **Halt only if:** Framework scaffolding is completely missing (run `framework` workflow first)
 
 **Note:** BMad artifacts (story, tech-spec, PRD) are OPTIONAL - workflow can run without them
+**Note:** `automate` generates tests; it does not run `*atdd` or `*test-review`. If ATDD outputs exist, use them as input and avoid duplicate coverage.
 
 ---
 
@@ -421,6 +422,7 @@ Before starting this workflow, verify:
 
 **With atdd Workflow:**
 
+- [ ] ATDD artifacts provided or located (manual handoff; `atdd` not auto-run)
 - [ ] Existing ATDD tests checked (if story had ATDD workflow run)
 - [ ] Expansion beyond ATDD planned (edge cases, negative paths)
 - [ ] No duplicate coverage with ATDD tests

package/src/modules/bmm/workflows/testarch/ci/checklist.md

@@ -9,6 +9,8 @@
 - [ ] Team agrees on CI platform
 - [ ] Access to CI platform settings (if updating)
 
+Note: CI setup is typically a one-time task per repo and can be run any time after the test framework is configured.
+
 ## Process Steps
 
 ### Step 1: Preflight Checks

package/src/modules/bmm/workflows/testarch/ci/instructions.md

@@ -11,6 +11,8 @@
 
 Scaffolds a production-ready CI/CD quality pipeline with test execution, burn-in loops for flaky test detection, parallel sharding, artifact collection, and notification configuration. This workflow creates platform-specific CI configuration optimized for fast feedback and reliable test execution.
 
+Note: This is typically a one-time setup per repo; run it any time after the test framework exists, ideally before feature work starts.
+
 ---
 
 ## Preflight Requirements

package/src/modules/bmm/workflows/testarch/nfr-assess/checklist.md

@@ -5,6 +5,8 @@
 
 ---
 
+Note: `nfr-assess` evaluates existing evidence; it does not run tests or CI workflows.
+
 ## Prerequisites Validation
 
 - [ ] Implementation is deployed and accessible for evaluation

package/src/modules/bmm/workflows/testarch/nfr-assess/nfr-report-template.md

@@ -6,6 +6,8 @@
 
 ---
 
+Note: This assessment summarizes existing evidence; it does not run tests or CI workflows.
+
 ## Executive Summary
 
 **Assessment:** {PASS_COUNT} PASS, {CONCERNS_COUNT} CONCERNS, {FAIL_COUNT} FAIL

package/src/modules/bmm/workflows/testarch/test-design/checklist.md

@@ -152,7 +152,8 @@
 
 ### Workflow Dependencies
 
-- [ ] Can proceed to `atdd` workflow with P0 scenarios
+- [ ] Can proceed to `*atdd` workflow with P0 scenarios
+- [ ] `*atdd` is a separate workflow and must be run explicitly (not auto-run)
 - [ ] Can proceed to `automate` workflow with full coverage plan
 - [ ] Risk assessment informs `gate` workflow criteria
 - [ ] Integrates with `ci` workflow execution order
@@ -176,7 +177,7 @@
 1. [ ] Review risk assessment with team
 2. [ ] Prioritize mitigation for high-priority risks (score ≥6)
 3. [ ] Allocate resources per estimates
-4. [ ] Run `atdd` workflow to generate P0 tests
+4. [ ] Run `*atdd` workflow to generate P0 tests (separate workflow; not auto-run)
 5. [ ] Set up test data factories and fixtures
 6. [ ] Schedule team review of test design document
 

package/src/modules/bmm/workflows/testarch/test-design/instructions.md

@@ -764,7 +764,7 @@ After completing this workflow, provide a summary:
 
 1. Review risk assessment with team
 2. Prioritize mitigation for high-risk items (score ≥6)
-3. Run `atdd` workflow to generate failing tests for P0 scenarios
+3. Run `*atdd` to generate failing tests for P0 scenarios (separate workflow; not auto-run by `*test-design`)
 4. Allocate resources per effort estimates
 5. Set up test data factories and fixtures
 ```

package/src/modules/bmm/workflows/testarch/test-design/test-design-template.md

@@ -246,6 +246,15 @@
 
 ---
 
+---
+
+## Follow-on Workflows (Manual)
+
+- Run `*atdd` to generate failing P0 tests (separate workflow; not auto-run).
+- Run `*automate` for broader coverage once implementation exists.
+
+---
+
 ## Approval
 
 **Test Design Approved By:**

package/src/modules/bmm/workflows/testarch/test-review/checklist.md

@@ -6,6 +6,8 @@ Use this checklist to validate that the test quality review workflow completed s
 
 ## Prerequisites
 
+Note: `test-review` is optional and only audits existing tests; it does not generate tests.
+
 ### Test File Discovery
 
 - [ ] Test file(s) identified for review (single/directory/suite scope)

package/src/modules/bmm/workflows/testarch/test-review/test-review-template.md

@@ -7,6 +7,8 @@
 
 ---
 
+Note: This review audits existing tests; it does not generate tests.
+
 ## Executive Summary
 
 **Overall Assessment**: {Excellent | Good | Acceptable | Needs Improvement | Critical Issues}

package/src/modules/bmm/workflows/testarch/trace/checklist.md

@@ -16,6 +16,7 @@ This checklist covers **two sequential phases**:
 
 - [ ] Acceptance criteria are available (from story file OR inline)
 - [ ] Test suite exists (or gaps are acknowledged and documented)
+- [ ] If tests are missing, recommend `*atdd` (trace does not run it automatically)
 - [ ] Test directory path is correct (`test_dir` variable)
 - [ ] Story file is accessible (if using BMad mode)
 - [ ] Knowledge base is loaded (test-priorities, traceability, risk-governance)

package/src/modules/bmm/workflows/testarch/trace/instructions.md

@@ -52,6 +52,8 @@ This workflow operates in two sequential phases to validate test coverage and de
 - If acceptance criteria are completely missing, halt and request them
 - If Phase 2 enabled but test execution results missing, warn and skip gate decision
 
+Note: `*trace` never runs `*atdd` automatically; it only recommends running it when tests are missing.
+
 ---
 
 ## PHASE 1: REQUIREMENTS TRACEABILITY

package/src/modules/bmm/workflows/testarch/trace/trace-template.md

@@ -6,6 +6,8 @@
 
 ---
 
+Note: This workflow does not generate tests. If gaps exist, run `*atdd` or `*automate` to create coverage.
+
 ## PHASE 1: REQUIREMENTS TRACEABILITY
 
 ### Coverage Summary

package/src/modules/bmm/workflows/workflow-status/init/instructions.md

@@ -1,6 +1,6 @@
 # Workflow Init - Project Setup Instructions
 
-<critical>The workflow execution engine is governed by: {project-root}/\_bmad/core/tasks/workflow.xml</critical>
+<critical>The workflow execution engine is governed by: {project-root}/_bmad/core/tasks/workflow.xml</critical>
 <critical>You MUST have already loaded and processed: workflow-init/workflow.yaml</critical>
 <critical>Communicate in {communication_language} with {user_name}</critical>
 <critical>This workflow handles BOTH new projects AND legacy projects following the BMad Method</critical>
@@ -15,7 +15,7 @@
 - BMM artifacts: PRD, epics, architecture, UX, brief, research, brainstorm
 - Implementation: stories, sprint-status, workflow-status
 - Codebase: source directories, package files, git repo
-- Check both {output_folder} and {sprint_artifacts} locations
+- Check both {output_folder} and {implementation_artifacts} locations
   </action>
 
 <action>Categorize into one of these states:

package/src/modules/bmm/workflows/workflow-status/init/workflow.yaml

@@ -6,7 +6,7 @@ author: "BMad"
 # Critical variables from config
 config_source: "{project-root}/_bmad/bmm/config.yaml"
 output_folder: "{config_source}:output_folder"
-sprint_artifacts: "{config_source}:sprint_artifacts"
+implementation_artifacts: "{config_source}:implementation_artifacts"
 user_name: "{config_source}:user_name"
 project_name: "{config_source}:project_name"
 communication_language: "{config_source}:communication_language"

package/src/modules/bmm/workflows/workflow-status/instructions.md

@@ -1,7 +1,7 @@
 # Workflow Status Check - Multi-Mode Service
 
-<critical>The workflow execution engine is governed by: {project-root}/\_bmad/core/tasks/workflow.xml</critical>
-<critical>You MUST have already loaded and processed: {project-root}/\_bmad/bmm/workflows/workflow-status/workflow.yaml</critical>
+<critical>The workflow execution engine is governed by: {project-root}/_bmad/core/tasks/workflow.xml</critical>
+<critical>You MUST have already loaded and processed: {project-root}/_bmad/bmm/workflows/workflow-status/workflow.yaml</critical>
 <critical>This workflow operates in multiple modes: interactive (default), validate, data, init-check, update</critical>
 <critical>Other workflows can call this as a service to avoid duplicating status logic</critical>
 <critical>⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever.</critical>

package/src/modules/bmm/workflows/workflow-status/workflow.yaml

@@ -6,6 +6,8 @@ author: "BMad"
 # Critical variables from config
 config_source: "{project-root}/_bmad/bmm/config.yaml"
 output_folder: "{config_source}:output_folder"
+planning_artifacts: "{config_source}:planning_artifacts"
+implementation_artifacts: "{config_source}:implementation_artifacts"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
 document_output_language: "{config_source}:document_output_language"
@@ -23,7 +25,7 @@ template: "{installed_path}/workflow-status-template.yaml"
 path_files: "{installed_path}/paths/"
 
 # Output configuration - reads existing status
-default_output_file: "{output_folder}/bmm-workflow-status.yaml"
+default_output_file: "{planning_artifacts}/bmm-workflow-status.yaml"
 
 standalone: true
 

package/src/modules/cis/{readme.md → docs/index.md}

@@ -17,8 +17,6 @@ CIS provides structured creative methodologies through distinctive agent persona
 
 ## Specialized Agents
 
-[View detailed agent descriptions →](./agents/README.md)
-
 - **Carson** - Brainstorming Specialist (energetic facilitator)
 - **Maya** - Design Thinking Maestro (jazz-like improviser)
 - **Dr. Quinn** - Problem Solver (detective-scientist hybrid)
@@ -27,7 +25,7 @@ CIS provides structured creative methodologies through distinctive agent persona
 
 ## Interactive Workflows
 
-[View all workflows →](./workflows/README.md)
+[View all workflows →](../workflows/README.md)
 
 **5 Workflows** with **150+ Creative Techniques:**
 
@@ -144,9 +142,7 @@ CIS workflows integrate with:
 
 ## Related Documentation
 
-- **[Workflow Guide](./workflows/README.md)** - Detailed workflow instructions
-- **[Agent Personas](./agents/README.md)** - Full agent descriptions
-- **[BMM Integration](../bmm/README.md)** - Development workflow connection
+- **[BMM Documentation](../../bmm/docs/index.md)** - Core BMad Method documentation
 
 ---