From b27968826d38692c2b1c2fe83b19e4f7150d5c5e Mon Sep 17 00:00:00 2001
From: Marc R Kellerman <9411143+mkellerman@users.noreply.github.com>
Date: Tue, 4 Nov 2025 23:04:08 -0800
Subject: [PATCH] feat: add new debug agent and workflows

---
 src/modules/bmm/agents/debug.agent.yaml       |  74 +++++
 src/modules/bmm/knowledge/debug-index.csv     |   5 +
 src/modules/bmm/knowledge/debug/README.md     |  32 ++
 .../bmm/knowledge/debug/common-defects.md     | 206 ++++++++++++
 .../debug/debug-inspection-checklist.md       | 118 +++++++
 .../bmm/knowledge/debug/debug-patterns.md     | 303 ++++++++++++++++++
 .../knowledge/debug/root-cause-checklist.md   | 118 +++++++
 .../debug/assert-analyze/workflow.yaml        |  11 +
 .../debug/debug-report/workflow.yaml          |  11 +
 .../debug/delta-minimize/workflow.yaml        |  11 +
 .../workflows/debug/inspect/instructions.md   |  36 +++
 .../bmm/workflows/debug/inspect/workflow.yaml |  33 ++
 .../workflows/debug/instrument/workflow.yaml  |  11 +
 .../debug/pattern-analysis/instructions.md    |  35 ++
 .../debug/pattern-analysis/workflow.yaml      |  33 ++
 .../debug/quick-debug/instructions.md         |  31 ++
 .../workflows/debug/quick-debug/workflow.yaml |  33 ++
 .../debug/root-cause/instructions.md          |  36 +++
 .../workflows/debug/root-cause/workflow.yaml  |  33 ++
 .../workflows/debug/static-scan/workflow.yaml |  11 +
 .../debug/validate-fix/workflow.yaml          |  11 +
 .../debug/walkthrough-prep/workflow.yaml      |  11 +
 .../debug/wolf-fence/instructions.md          |  42 +++
 .../workflows/debug/wolf-fence/workflow.yaml  |  33 ++
 24 files changed, 1278 insertions(+)
 create mode 100644 src/modules/bmm/agents/debug.agent.yaml
 create mode 100644 src/modules/bmm/knowledge/debug-index.csv
 create mode 100644 src/modules/bmm/knowledge/debug/README.md
 create mode 100644 src/modules/bmm/knowledge/debug/common-defects.md
 create mode 100644 src/modules/bmm/knowledge/debug/debug-inspection-checklist.md
 create mode 100644 src/modules/bmm/knowledge/debug/debug-patterns.md
 create mode 100644 src/modules/bmm/knowledge/debug/root-cause-checklist.md
 create mode 100644 src/modules/bmm/workflows/debug/assert-analyze/workflow.yaml
 create mode 100644 src/modules/bmm/workflows/debug/debug-report/workflow.yaml
 create mode 100644 src/modules/bmm/workflows/debug/delta-minimize/workflow.yaml
 create mode 100644 src/modules/bmm/workflows/debug/inspect/instructions.md
 create mode 100644 src/modules/bmm/workflows/debug/inspect/workflow.yaml
 create mode 100644 src/modules/bmm/workflows/debug/instrument/workflow.yaml
 create mode 100644 src/modules/bmm/workflows/debug/pattern-analysis/instructions.md
 create mode 100644 src/modules/bmm/workflows/debug/pattern-analysis/workflow.yaml
 create mode 100644 src/modules/bmm/workflows/debug/quick-debug/instructions.md
 create mode 100644 src/modules/bmm/workflows/debug/quick-debug/workflow.yaml
 create mode 100644 src/modules/bmm/workflows/debug/root-cause/instructions.md
 create mode 100644 src/modules/bmm/workflows/debug/root-cause/workflow.yaml
 create mode 100644 src/modules/bmm/workflows/debug/static-scan/workflow.yaml
 create mode 100644 src/modules/bmm/workflows/debug/validate-fix/workflow.yaml
 create mode 100644 src/modules/bmm/workflows/debug/walkthrough-prep/workflow.yaml
 create mode 100644 src/modules/bmm/workflows/debug/wolf-fence/instructions.md
 create mode 100644 src/modules/bmm/workflows/debug/wolf-fence/workflow.yaml

diff --git a/src/modules/bmm/agents/debug.agent.yaml b/src/modules/bmm/agents/debug.agent.yaml
new file mode 100644
index 00000000..819f5398
--- /dev/null
+++ b/src/modules/bmm/agents/debug.agent.yaml
@@ -0,0 +1,74 @@
+# Debug Specialist Agent Definition
+
+agent:
+  metadata:
+    id: bmad/bmm/agents/debug.md
+    name: Diana
+    title: Debug Specialist & Root Cause Analyst
+    icon: 🔍
+    module: bmm
+
+  persona:
+    role: Expert Debug Specialist & Software Inspector
+    identity: Debug specialist who uses formal inspection methodologies to achieve high defect detection rates. Specializes in systematic bug analysis, root cause investigation, and defect resolution using proven methodologies like Fagan inspection (60-90% defect detection rate), binary search debugging, and fishbone analysis.
+    communication_style: Systematic, methodical, analytical, thorough, detail-oriented. Presents findings with clear evidence trails and structured analysis. Uses precise technical language while remaining accessible to stakeholders.
+    principles:
+      - I believe in systematic inspection over ad-hoc debugging, using proven methodologies like Fagan inspection to achieve consistently high defect detection rates.
+      - My approach focuses on root causes rather than symptoms, ensuring fixes address underlying issues and prevent recurrence.
+      - I maintain comprehensive documentation trails to capture lessons learned and build organizational knowledge.
+      - Every defect is an opportunity to improve processes and prevent similar issues.
+      - I assess impact and risk systematically, prioritizing fixes based on severity and scope.
+      - My recommendations are always evidence-based, backed by thorough analysis and clear reasoning.
+
+  knowledge:
+    index_file: "{project-root}/bmad/bmm/knowledge/debug/debug-index.csv"
+    base_path: "{project-root}/bmad/bmm/knowledge/debug/"
+
+  menu:
+    - trigger: inspect
+      workflow: "{project-root}/bmad/bmm/workflows/debug/inspect/workflow.yaml"
+      description: Execute comprehensive Fagan inspection workflow
+
+    - trigger: quick-debug
+      workflow: "{project-root}/bmad/bmm/workflows/debug/quick-debug/workflow.yaml"
+      description: Rapid triage and initial analysis for simple issues
+
+    - trigger: pattern-analysis
+      workflow: "{project-root}/bmad/bmm/workflows/debug/pattern-analysis/workflow.yaml"
+      description: Analyze recent commits and code changes for defect patterns
+
+    - trigger: root-cause
+      workflow: "{project-root}/bmad/bmm/workflows/debug/root-cause/workflow.yaml"
+      description: Execute focused root cause analysis using fishbone methodology
+
+    - trigger: validate-fix
+      workflow: "{project-root}/bmad/bmm/workflows/debug/validate-fix/workflow.yaml"
+      description: Verify proposed fix addresses root cause without side effects
+
+    - trigger: debug-report
+      workflow: "{project-root}/bmad/bmm/workflows/debug/debug-report/workflow.yaml"
+      description: Generate comprehensive debug report from current session
+
+    - trigger: wolf-fence
+      workflow: "{project-root}/bmad/bmm/workflows/debug/wolf-fence/workflow.yaml"
+      description: Execute binary search debugging to isolate bug location
+
+    - trigger: delta-minimize
+      workflow: "{project-root}/bmad/bmm/workflows/debug/delta-minimize/workflow.yaml"
+      description: Automatically reduce failing test case to minimal reproduction
+
+    - trigger: assert-analyze
+      workflow: "{project-root}/bmad/bmm/workflows/debug/assert-analyze/workflow.yaml"
+      description: Analyze code for missing assertions and invariants
+
+    - trigger: static-scan
+      workflow: "{project-root}/bmad/bmm/workflows/debug/static-scan/workflow.yaml"
+      description: Perform comprehensive static analysis for common defects
+
+    - trigger: instrument
+      workflow: "{project-root}/bmad/bmm/workflows/debug/instrument/workflow.yaml"
+      description: Design strategic logging and monitoring points
+
+    - trigger: walkthrough-prep
+      workflow: "{project-root}/bmad/bmm/workflows/debug/walkthrough-prep/workflow.yaml"
+      description: Generate materials for code walkthrough session
diff --git a/src/modules/bmm/knowledge/debug-index.csv b/src/modules/bmm/knowledge/debug-index.csv
new file mode 100644
index 00000000..d8f82a4a
--- /dev/null
+++ b/src/modules/bmm/knowledge/debug-index.csv
@@ -0,0 +1,5 @@
+id,name,description,tags,fragment_file
+debug-inspection,Debug Inspection Checklist,"Systematic checklist for Fagan inspection methodology","inspection,checklist,fagan",knowledge/debug-inspection-checklist.md
+root-cause,Root Cause Checklist,"Fishbone methodology for root cause analysis","root-cause,analysis,checklist",knowledge/root-cause-checklist.md
+common-defects,Common Defects Reference,"Catalog of frequently occurring defect patterns","defects,patterns,reference",knowledge/common-defects.md
+debug-patterns,Debug Patterns Guide,"Proven debugging strategies and methodologies","debugging,patterns,strategies",knowledge/debug-patterns.md
\ No newline at end of file
diff --git a/src/modules/bmm/knowledge/debug/README.md b/src/modules/bmm/knowledge/debug/README.md
new file mode 100644
index 00000000..119fad54
--- /dev/null
+++ b/src/modules/bmm/knowledge/debug/README.md
@@ -0,0 +1,32 @@
+# Debug Knowledge Base
+
+## Overview
+
+This knowledge base contains systematic debugging methodologies, checklists, and reference materials for Diana, the Debug Specialist & Root Cause Analyst.
+
+## Knowledge Fragments
+
+### Core Debugging Resources
+
+1. **debug-inspection-checklist.md** - Comprehensive Fagan inspection methodology with 6-phase systematic review process
+2. **root-cause-checklist.md** - Fishbone analysis and 5-whys methodology for systematic root cause investigation
+3. **common-defects.md** - Reference catalog of frequently occurring defect patterns with classification and prevention strategies
+4. **debug-patterns.md** - Common debugging strategies, anti-patterns to avoid, and best practices
+
+### Usage in Workflows
+
+Each workflow references specific knowledge fragments:
+
+- **Inspect Workflow** → Uses `debug-inspection-checklist.md` for systematic Fagan inspection
+- **Root Cause Workflow** → Uses `root-cause-checklist.md` for fishbone and 5-whys analysis
+- **Quick Debug Workflow** → Uses `debug-patterns.md` for rapid pattern recognition
+- **Pattern Analysis Workflow** → Uses `common-defects.md` for defect classification
+- **Static Scan Workflow** → Uses `common-defects.md` for automated defect detection
+
+## Knowledge Integration
+
+The debug-index.csv file maps knowledge fragments to specific use cases and tags, enabling efficient knowledge retrieval during debugging sessions.
+
+## Maintenance
+
+Knowledge fragments are maintained as part of the BMAD module structure and updated based on debugging experience and lessons learned from resolved incidents.
diff --git a/src/modules/bmm/knowledge/debug/common-defects.md b/src/modules/bmm/knowledge/debug/common-defects.md
new file mode 100644
index 00000000..69d71772
--- /dev/null
+++ b/src/modules/bmm/knowledge/debug/common-defects.md
@@ -0,0 +1,206 @@
+# common-defects
+
+Reference guide for common software defects and their characteristics.
+
+## Defect Classification System
+
+### By Origin
+
+1. **Requirements Defects** - Ambiguous, incomplete, or incorrect requirements
+2. **Design Defects** - Architectural flaws, poor design decisions
+3. **Coding Defects** - Implementation errors, logic mistakes
+4. **Testing Defects** - Inadequate test coverage, wrong test assumptions
+5. **Deployment Defects** - Configuration errors, environment issues
+6. **Documentation Defects** - Outdated, incorrect, or missing documentation
+
+### By Type
+
+#### Logic Defects
+
+- **Algorithm Errors:** Incorrect implementation of business logic
+- **Control Flow Issues:** Wrong branching, loop errors
+- **Boundary Violations:** Off-by-one, overflow, underflow
+- **State Management:** Invalid state transitions, race conditions
+
+#### Data Defects
+
+- **Input Validation:** Missing or incorrect validation
+- **Data Corruption:** Incorrect data manipulation
+- **Type Errors:** Wrong data types, failed conversions
+- **Persistence Issues:** Failed saves, data loss
+
+#### Interface Defects
+
+- **API Misuse:** Incorrect parameter passing, wrong method calls
+- **Integration Errors:** Component communication failures
+- **Protocol Violations:** Incorrect message formats
+- **Version Incompatibility:** Breaking changes not handled
+
+#### Performance Defects
+
+- **Memory Leaks:** Unreleased resources
+- **Inefficient Algorithms:** O(n²) where O(n) possible
+- **Database Issues:** N+1 queries, missing indexes
+- **Resource Contention:** Deadlocks, bottlenecks
+
+#### Security Defects
+
+- **Injection Flaws:** SQL, XSS, command injection
+- **Authentication Issues:** Weak auth, session problems
+- **Authorization Flaws:** Privilege escalation, IDOR
+- **Data Exposure:** Sensitive data leaks, weak encryption
+
+## Severity Classification
+
+### Critical (P0)
+
+- **Definition:** System unusable, data loss, security breach
+- **Response Time:** Immediate
+- **Examples:**
+  - Application crash on startup
+  - Data corruption or loss
+  - Security vulnerability actively exploited
+  - Complete feature failure
+
+### High (P1)
+
+- **Definition:** Major feature broken, significant impact
+- **Response Time:** Within 24 hours
+- **Examples:**
+  - Core functionality impaired
+  - Performance severely degraded
+  - Workaround exists but difficult
+  - Affects many users
+
+### Medium (P2)
+
+- **Definition:** Feature impaired, moderate impact
+- **Response Time:** Within sprint
+- **Examples:**
+  - Non-core feature broken
+  - Easy workaround available
+  - Cosmetic issues with functional impact
+  - Affects some users
+
+### Low (P3)
+
+- **Definition:** Minor issue, minimal impact
+- **Response Time:** Next release
+- **Examples:**
+  - Cosmetic issues
+  - Minor inconvenience
+  - Edge case scenarios
+  - Documentation errors
+
+## Root Cause Categories
+
+### Development Process
+
+1. **Inadequate Requirements:** Missing acceptance criteria
+2. **Poor Communication:** Misunderstood requirements
+3. **Insufficient Review:** Code review missed issues
+4. **Time Pressure:** Rushed implementation
+
+### Technical Factors
+
+1. **Complexity:** System too complex to understand fully
+2. **Technical Debt:** Accumulated shortcuts causing issues
+3. **Tool Limitations:** Development tools inadequate
+4. **Knowledge Gap:** Team lacks necessary expertise
+
+### Testing Gaps
+
+1. **Missing Tests:** Scenario not covered
+2. **Wrong Assumptions:** Tests based on incorrect understanding
+3. **Environment Differences:** Works in test, fails in production
+4. **Data Issues:** Test data not representative
+
+### Organizational Issues
+
+1. **Process Failures:** Procedures not followed
+2. **Resource Constraints:** Insufficient time/people
+3. **Training Gaps:** Team not properly trained
+4. **Culture Issues:** Quality not prioritized
+
+## Detection Methods
+
+### Static Analysis
+
+- **Code Review:** Manual inspection by peers
+- **Linting:** Automated style and error checking
+- **Security Scanning:** SAST tools
+- **Complexity Analysis:** Cyclomatic complexity metrics
+
+### Dynamic Analysis
+
+- **Unit Testing:** Component-level testing
+- **Integration Testing:** Component interaction testing
+- **System Testing:** End-to-end testing
+- **Performance Testing:** Load and stress testing
+
+### Runtime Monitoring
+
+- **Error Tracking:** Sentry, Rollbar
+- **APM Tools:** Application performance monitoring
+- **Log Analysis:** Centralized logging
+- **User Reports:** Bug reports from users
+
+### Formal Methods
+
+- **Fagan Inspection:** Systematic peer review
+- **Code Walkthroughs:** Step-by-step review
+- **Pair Programming:** Real-time review
+- **Test-Driven Development:** Test-first approach
+
+## Prevention Strategies
+
+### Process Improvements
+
+1. **Clear Requirements:** Use user stories with acceptance criteria
+2. **Design Reviews:** Architecture review before coding
+3. **Code Standards:** Enforce coding guidelines
+4. **Automated Testing:** CI/CD with comprehensive tests
+
+### Technical Practices
+
+1. **Defensive Programming:** Validate inputs, handle errors
+2. **Design Patterns:** Use proven solutions
+3. **Refactoring:** Regular code improvement
+4. **Documentation:** Keep docs current
+
+### Team Practices
+
+1. **Knowledge Sharing:** Regular tech talks, documentation
+2. **Pair Programming:** Collaborative development
+3. **Code Reviews:** Mandatory peer review
+4. **Retrospectives:** Learn from mistakes
+
+### Tool Support
+
+1. **Static Analyzers:** SonarQube, ESLint
+2. **Test Frameworks:** Jest, Pytest, JUnit
+3. **CI/CD Pipelines:** Jenkins, GitHub Actions
+4. **Monitoring Tools:** Datadog, New Relic
+
+## Defect Metrics
+
+### Detection Metrics
+
+- **Defect Density:** Defects per KLOC
+- **Detection Rate:** Defects found per time period
+- **Escape Rate:** Defects reaching production
+- **Mean Time to Detect:** Average detection time
+
+### Resolution Metrics
+
+- **Fix Rate:** Defects fixed per time period
+- **Mean Time to Fix:** Average fix time
+- **Reopen Rate:** Defects reopened after fix
+- **Fix Effectiveness:** First-time fix success rate
+
+### Quality Metrics
+
+- **Test Coverage:** Percentage of code tested
+- **Code Complexity:** Average cyclomatic complexity
+- **Technical Debt:** Estimated remediation effort
+- **Customer Satisfaction:** User-reported issues
diff --git a/src/modules/bmm/knowledge/debug/debug-inspection-checklist.md b/src/modules/bmm/knowledge/debug/debug-inspection-checklist.md
new file mode 100644
index 00000000..dcb2f723
--- /dev/null
+++ b/src/modules/bmm/knowledge/debug/debug-inspection-checklist.md
@@ -0,0 +1,118 @@
+# debug-inspection-checklist
+
+Comprehensive checklist for Fagan inspection methodology.
+
+## Phase 1: Planning Checklist
+
+- [ ] Bug description clearly documented
+- [ ] Inspection scope defined (code, tests, config, docs)
+- [ ] Affected components identified
+- [ ] Stakeholders notified
+- [ ] Success criteria established
+- [ ] Time allocated for inspection
+
+## Phase 2: Overview Checklist
+
+- [ ] Recent commits reviewed (last 20-50)
+- [ ] Feature specifications reviewed
+- [ ] Related documentation gathered
+- [ ] Environment details captured
+- [ ] Previous similar issues researched
+- [ ] Impact scope assessed
+
+## Phase 3: Preparation Checklist
+
+### Code Analysis
+
+- [ ] Static analysis performed
+- [ ] Code complexity measured
+- [ ] Anti-patterns identified
+- [ ] Security vulnerabilities checked
+- [ ] Performance bottlenecks assessed
+
+### Test Analysis
+
+- [ ] Test coverage reviewed
+- [ ] Failed tests analyzed
+- [ ] Missing test scenarios identified
+- [ ] Test quality assessed
+- [ ] Edge cases evaluated
+
+### Configuration Analysis
+
+- [ ] Environment settings reviewed
+- [ ] Configuration drift checked
+- [ ] Dependencies verified
+- [ ] Version compatibility confirmed
+- [ ] Resource limits checked
+
+## Phase 4: Inspection Meeting Checklist
+
+### Defect Categories Reviewed
+
+- [ ] Logic defects (algorithms, control flow)
+- [ ] Interface defects (API, parameters)
+- [ ] Data defects (types, validation)
+- [ ] Documentation defects (outdated, incorrect)
+- [ ] Performance defects (inefficiencies)
+- [ ] Security defects (vulnerabilities)
+
+### Analysis Completed
+
+- [ ] Root cause identified
+- [ ] Evidence documented
+- [ ] Impact severity assessed
+- [ ] Defects categorized by priority
+- [ ] Pattern analysis performed
+
+## Phase 5: Rework Planning Checklist
+
+- [ ] Fix proposals generated
+- [ ] Trade-offs analyzed
+- [ ] Test strategy designed
+- [ ] Risk assessment completed
+- [ ] Implementation timeline created
+- [ ] Regression test plan defined
+- [ ] Rollback plan prepared
+
+## Phase 6: Follow-up Checklist
+
+- [ ] Fix effectiveness validated
+- [ ] All tests passing
+- [ ] Documentation updated
+- [ ] Lessons learned captured
+- [ ] Debug report completed
+- [ ] Prevention measures identified
+- [ ] Knowledge shared with team
+
+## Quality Gates
+
+### Inspection Completeness
+
+- [ ] All 6 phases executed
+- [ ] All checklists completed
+- [ ] Evidence trail documented
+- [ ] Peer review conducted
+
+### Fix Validation
+
+- [ ] Fix addresses root cause
+- [ ] No side effects introduced
+- [ ] Performance acceptable
+- [ ] Security maintained
+- [ ] Tests comprehensive
+
+### Documentation
+
+- [ ] Debug report generated
+- [ ] Code comments updated
+- [ ] README updated if needed
+- [ ] Runbook updated if needed
+- [ ] Team wiki updated
+
+## Sign-off
+
+- [ ] Developer reviewed
+- [ ] QA validated
+- [ ] Team lead approved
+- [ ] Stakeholders informed
diff --git a/src/modules/bmm/knowledge/debug/debug-patterns.md b/src/modules/bmm/knowledge/debug/debug-patterns.md
new file mode 100644
index 00000000..ad238ea2
--- /dev/null
+++ b/src/modules/bmm/knowledge/debug/debug-patterns.md
@@ -0,0 +1,303 @@
+# debug-patterns
+
+Common defect patterns and debugging strategies.
+
+## Common Defect Patterns
+
+### 1. Null/Undefined Reference Errors
+
+**Pattern:** Accessing properties or methods on null/undefined objects
+**Indicators:**
+
+- TypeError: Cannot read property 'X' of undefined
+- NullPointerException
+- Segmentation fault
+
+**Common Causes:**
+
+- Missing null checks
+- Asynchronous data not yet loaded
+- Optional dependencies not injected
+- Incorrect initialization order
+
+**Detection Strategy:**
+
+- Add defensive null checks
+- Use optional chaining (?.)
+- Initialize with safe defaults
+- Validate inputs at boundaries
+
+### 2. Race Conditions
+
+**Pattern:** Multiple threads/processes accessing shared resources
+**Indicators:**
+
+- Intermittent failures
+- Works in debug but fails in production
+- Order-dependent behavior
+- Data corruption
+
+**Common Causes:**
+
+- Missing synchronization
+- Incorrect lock ordering
+- Shared mutable state
+- Async operations without proper await
+
+**Detection Strategy:**
+
+- Add logging with timestamps
+- Use thread-safe data structures
+- Implement proper locking mechanisms
+- Review async/await usage
+
+### 3. Memory Leaks
+
+**Pattern:** Memory usage grows over time without release
+**Indicators:**
+
+- Increasing memory consumption
+- Out of memory errors
+- Performance degradation over time
+- GC pressure
+
+**Common Causes:**
+
+- Event listeners not removed
+- Circular references
+- Large objects in closures
+- Cache without eviction
+
+**Detection Strategy:**
+
+- Profile memory usage
+- Review object lifecycle
+- Check event listener cleanup
+- Implement cache limits
+
+### 4. Off-by-One Errors
+
+**Pattern:** Incorrect loop boundaries or array indexing
+**Indicators:**
+
+- ArrayIndexOutOfBounds
+- Missing first/last element
+- Infinite loops
+- Fence post errors
+
+**Common Causes:**
+
+- Confusion between length and last index
+- Inclusive vs exclusive ranges
+- Loop condition errors
+- Zero-based vs one-based indexing
+
+**Detection Strategy:**
+
+- Review loop conditions carefully
+- Test boundary cases
+- Use forEach/map when possible
+- Add assertions for array bounds
+
+### 5. Type Mismatches
+
+**Pattern:** Incorrect data types passed or compared
+**Indicators:**
+
+- Type errors at runtime
+- Unexpected coercion behavior
+- Failed validations
+- Serialization errors
+
+**Common Causes:**
+
+- Weak typing assumptions
+- Missing type validation
+- Incorrect type conversions
+- API contract violations
+
+**Detection Strategy:**
+
+- Add runtime type checking
+- Use TypeScript/type hints
+- Validate at API boundaries
+- Review type coercion rules
+
+### 6. Resource Exhaustion
+
+**Pattern:** Running out of system resources
+**Indicators:**
+
+- Too many open files
+- Connection pool exhaustion
+- Thread pool starvation
+- Disk space errors
+
+**Common Causes:**
+
+- Resources not properly closed
+- Missing connection pooling
+- Unbounded growth
+- Inadequate limits
+
+**Detection Strategy:**
+
+- Implement try-finally blocks
+- Use connection pooling
+- Set resource limits
+- Monitor resource usage
+
+### 7. Concurrency Deadlocks
+
+**Pattern:** Threads waiting for each other indefinitely
+**Indicators:**
+
+- Application hangs
+- Threads in BLOCKED state
+- No progress being made
+- Timeout errors
+
+**Common Causes:**
+
+- Circular wait conditions
+- Lock ordering violations
+- Nested synchronized blocks
+- Resource starvation
+
+**Detection Strategy:**
+
+- Always acquire locks in same order
+- Use lock-free data structures
+- Implement timeout mechanisms
+- Avoid nested locks
+
+### 8. SQL Injection Vulnerabilities
+
+**Pattern:** Unvalidated input in SQL queries
+**Indicators:**
+
+- Unexpected database errors
+- Data breaches
+- Malformed query errors
+- Authorization bypasses
+
+**Common Causes:**
+
+- String concatenation for queries
+- Missing input validation
+- Inadequate escaping
+- Dynamic query construction
+
+**Detection Strategy:**
+
+- Use parameterized queries
+- Validate all inputs
+- Review dynamic SQL
+- Implement least privilege
+
+### 9. Infinite Recursion
+
+**Pattern:** Function calling itself without termination
+**Indicators:**
+
+- Stack overflow errors
+- Maximum call stack exceeded
+- Application crashes
+- Memory exhaustion
+
+**Common Causes:**
+
+- Missing base case
+- Incorrect termination condition
+- Circular dependencies
+- Mutual recursion errors
+
+**Detection Strategy:**
+
+- Review base cases
+- Add recursion depth limits
+- Test edge cases
+- Use iteration when possible
+
+### 10. Cache Invalidation Issues
+
+**Pattern:** Stale data served from cache
+**Indicators:**
+
+- Outdated information displayed
+- Inconsistent state
+- Changes not reflected
+- Data synchronization issues
+
+**Common Causes:**
+
+- Missing invalidation logic
+- Incorrect cache keys
+- Race conditions in updates
+- TTL too long
+
+**Detection Strategy:**
+
+- Review invalidation triggers
+- Implement cache versioning
+- Use appropriate TTLs
+- Add cache bypass for testing
+
+## Anti-Patterns to Avoid
+
+### 1. Shotgun Debugging
+
+Making random changes hoping something works
+
+### 2. Blame the Compiler
+
+Assuming the problem is in the framework/language
+
+### 3. Programming by Coincidence
+
+Not understanding why a fix works
+
+### 4. Copy-Paste Solutions
+
+Using solutions without understanding them
+
+### 5. Ignoring Warnings
+
+Dismissing compiler/linter warnings
+
+## Debugging Best Practices
+
+### 1. Systematic Approach
+
+- Reproduce consistently
+- Isolate the problem
+- Form hypotheses
+- Test systematically
+
+### 2. Use Scientific Method
+
+- Observe symptoms
+- Form hypothesis
+- Design experiment
+- Test and validate
+
+### 3. Maintain Debug Log
+
+- Document what you tried
+- Record what worked/failed
+- Note patterns observed
+- Track time spent
+
+### 4. Leverage Tools
+
+- Debuggers
+- Profilers
+- Static analyzers
+- Log aggregators
+
+### 5. Collaborate
+
+- Pair debugging
+- Code reviews
+- Knowledge sharing
+- Post-mortems
diff --git a/src/modules/bmm/knowledge/debug/root-cause-checklist.md b/src/modules/bmm/knowledge/debug/root-cause-checklist.md
new file mode 100644
index 00000000..45aef885
--- /dev/null
+++ b/src/modules/bmm/knowledge/debug/root-cause-checklist.md
@@ -0,0 +1,118 @@
+# root-cause-checklist
+
+Systematic checklist for root cause analysis.
+
+## Problem Definition
+
+- [ ] Problem clearly stated
+- [ ] Symptoms documented
+- [ ] Timeline established
+- [ ] Affected components identified
+- [ ] Impact quantified
+- [ ] Success criteria defined
+
+## Fishbone Analysis Categories
+
+### People Factors
+
+- [ ] Knowledge gaps assessed
+- [ ] Communication issues reviewed
+- [ ] Training needs identified
+- [ ] User behavior analyzed
+- [ ] Team dynamics considered
+
+### Process Factors
+
+- [ ] Development process reviewed
+- [ ] Deployment procedures checked
+- [ ] Code review practices assessed
+- [ ] Testing processes evaluated
+- [ ] Documentation processes reviewed
+
+### Technology Factors
+
+- [ ] Framework limitations identified
+- [ ] Library issues checked
+- [ ] Tool configurations reviewed
+- [ ] Infrastructure problems assessed
+- [ ] Integration issues evaluated
+
+### Environment Factors
+
+- [ ] Environment differences documented
+- [ ] Resource constraints checked
+- [ ] External dependencies reviewed
+- [ ] Network issues assessed
+- [ ] Configuration drift analyzed
+
+### Data Factors
+
+- [ ] Input validation reviewed
+- [ ] Data integrity checked
+- [ ] State management assessed
+- [ ] Race conditions evaluated
+- [ ] Data flow analyzed
+
+### Method Factors
+
+- [ ] Algorithm correctness verified
+- [ ] Design patterns reviewed
+- [ ] Architecture decisions assessed
+- [ ] Performance strategies evaluated
+- [ ] Security measures reviewed
+
+## 5-Whys Analysis
+
+- [ ] Initial problem stated
+- [ ] First why answered
+- [ ] Second why answered
+- [ ] Third why answered
+- [ ] Fourth why answered
+- [ ] Fifth why answered (root cause)
+- [ ] Additional whys if needed
+- [ ] Causation chain documented
+
+## Evidence Collection
+
+- [ ] Logs collected
+- [ ] Metrics gathered
+- [ ] Code examined
+- [ ] Tests reviewed
+- [ ] Documentation checked
+- [ ] User reports compiled
+- [ ] Monitoring data analyzed
+
+## Validation
+
+- [ ] Root cause reproducible
+- [ ] Alternative causes eliminated
+- [ ] Evidence supports conclusion
+- [ ] Peer review conducted
+- [ ] Confidence level assessed
+
+## Action Planning
+
+- [ ] Immediate actions defined
+- [ ] Short-term solutions planned
+- [ ] Long-term prevention designed
+- [ ] Process improvements identified
+- [ ] Responsibilities assigned
+- [ ] Timeline established
+
+## Documentation
+
+- [ ] Analysis documented
+- [ ] Evidence archived
+- [ ] Recommendations clear
+- [ ] Lessons learned captured
+- [ ] Report generated
+- [ ] Stakeholders informed
+
+## Follow-up
+
+- [ ] Fix implemented
+- [ ] Effectiveness verified
+- [ ] Monitoring in place
+- [ ] Recurrence prevented
+- [ ] Knowledge transferred
+- [ ] Process updated
diff --git a/src/modules/bmm/workflows/debug/assert-analyze/workflow.yaml b/src/modules/bmm/workflows/debug/assert-analyze/workflow.yaml
new file mode 100644
index 00000000..e931c6f7
--- /dev/null
+++ b/src/modules/bmm/workflows/debug/assert-analyze/workflow.yaml
@@ -0,0 +1,11 @@
+# Assert Analyze Workflow Configuration
+name: "assert-analyze"
+description: "Analyze code for missing assertions and invariants to improve defensive programming."
+author: "Diana"
+
+config_source: "{project-root}/bmad/bmm/config.yaml"
+output_folder: "{config_source}:output_folder"
+installed_path: "{project-root}/bmad/bmm/workflows/debug/assert-analyze"
+instructions: "{installed_path}/instructions.md"
+knowledge_base: "{project-root}/bmad/bmm/knowledge/debug/common-defects.md"
+standalone: true
diff --git a/src/modules/bmm/workflows/debug/debug-report/workflow.yaml b/src/modules/bmm/workflows/debug/debug-report/workflow.yaml
new file mode 100644
index 00000000..445921a6
--- /dev/null
+++ b/src/modules/bmm/workflows/debug/debug-report/workflow.yaml
@@ -0,0 +1,11 @@
+# Debug Report Workflow Configuration
+name: "debug-report"
+description: "Generate comprehensive debug report from current session with findings and recommendations."
+author: "Diana"
+
+config_source: "{project-root}/bmad/bmm/config.yaml"
+output_folder: "{config_source}:output_folder"
+installed_path: "{project-root}/bmad/bmm/workflows/debug/debug-report"
+instructions: "{installed_path}/instructions.md"
+knowledge_base: "{project-root}/bmad/bmm/knowledge/debug/debug-patterns.md"
+standalone: true
diff --git a/src/modules/bmm/workflows/debug/delta-minimize/workflow.yaml b/src/modules/bmm/workflows/debug/delta-minimize/workflow.yaml
new file mode 100644
index 00000000..3a2ed96a
--- /dev/null
+++ b/src/modules/bmm/workflows/debug/delta-minimize/workflow.yaml
@@ -0,0 +1,11 @@
+# Delta Minimize Workflow Configuration
+name: "delta-minimize"
+description: "Automatically reduce failing test case to minimal reproduction by systematic elimination."
+author: "Diana"
+
+config_source: "{project-root}/bmad/bmm/config.yaml"
+output_folder: "{config_source}:output_folder"
+installed_path: "{project-root}/bmad/bmm/workflows/debug/delta-minimize"
+instructions: "{installed_path}/instructions.md"
+knowledge_base: "{project-root}/bmad/bmm/knowledge/debug/debug-patterns.md"
+standalone: true
diff --git a/src/modules/bmm/workflows/debug/inspect/instructions.md b/src/modules/bmm/workflows/debug/inspect/instructions.md
new file mode 100644
index 00000000..4263d5de
--- /dev/null
+++ b/src/modules/bmm/workflows/debug/inspect/instructions.md
@@ -0,0 +1,36 @@
+# Fagan Inspection Instructions
+
+## Overview
+
+Execute a comprehensive Fagan inspection workflow to achieve 60-90% defect detection rates through systematic code review methodology.
+
+## Methodology
+
+This workflow implements the formal Fagan inspection process:
+
+1. **Planning Phase** - Define scope, select participants, schedule sessions
+2. **Overview Phase** - Present code context and objectives to inspection team
+3. **Preparation Phase** - Individual reviewers study code using checklists
+4. **Inspection Meeting** - Systematic review to identify defects (not solutions)
+5. **Rework Phase** - Author addresses identified defects
+6. **Follow-up Phase** - Verify defect resolution
+
+## Knowledge Integration
+
+Consult the debug inspection checklist for systematic defect detection patterns and common issue categories.
+
+## Process Steps
+
+1. Load inspection checklist from knowledge base
+2. Define inspection scope and objectives
+3. Identify code artifacts for review
+4. Apply systematic inspection methodology
+5. Document findings with severity classification
+6. Generate inspection report with actionable recommendations
+
+## Expected Outputs
+
+- Comprehensive defect inventory
+- Severity-classified issue list
+- Inspection metrics and effectiveness data
+- Recommended next steps for resolution
diff --git a/src/modules/bmm/workflows/debug/inspect/workflow.yaml b/src/modules/bmm/workflows/debug/inspect/workflow.yaml
new file mode 100644
index 00000000..1c183ac8
--- /dev/null
+++ b/src/modules/bmm/workflows/debug/inspect/workflow.yaml
@@ -0,0 +1,33 @@
+# Fagan Inspection Workflow Configuration
+name: "inspect"
+description: "Execute comprehensive Fagan inspection workflow for systematic defect detection with 60-90% efficiency rates."
+author: "Diana"
+
+# Critical variables from config
+config_source: "{project-root}/bmad/bmm/config.yaml"
+output_folder: "{config_source}:output_folder"
+user_name: "{config_source}:user_name"
+communication_language: "{config_source}:communication_language"
+document_output_language: "{config_source}:document_output_language"
+user_skill_level: "{config_source}:user_skill_level"
+date: system-generated
+
+# Module path and component files
+installed_path: "{project-root}/bmad/bmm/workflows/debug/inspect"
+template: false
+instructions: "{installed_path}/instructions.md"
+
+# Knowledge base integration
+knowledge_base: "{project-root}/bmad/bmm/knowledge/debug/debug-inspection-checklist.md"
+
+standalone: true
+
+web_bundle:
+  name: "inspect"
+  description: "Execute comprehensive Fagan inspection workflow for systematic defect detection with 60-90% efficiency rates."
+  author: "Diana"
+  instructions: "bmad/bmm/workflows/debug/inspect/instructions.md"
+  template: false
+  web_bundle_files:
+    - "bmad/bmm/workflows/debug/inspect/instructions.md"
+    - "bmad/bmm/knowledge/debug/debug-inspection-checklist.md"
diff --git a/src/modules/bmm/workflows/debug/instrument/workflow.yaml b/src/modules/bmm/workflows/debug/instrument/workflow.yaml
new file mode 100644
index 00000000..0cb98b5c
--- /dev/null
+++ b/src/modules/bmm/workflows/debug/instrument/workflow.yaml
@@ -0,0 +1,11 @@
+# Instrument Workflow Configuration
+name: "instrument"
+description: "Design strategic logging and monitoring points for enhanced debugging visibility."
+author: "Diana"
+
+config_source: "{project-root}/bmad/bmm/config.yaml"
+output_folder: "{config_source}:output_folder"
+installed_path: "{project-root}/bmad/bmm/workflows/debug/instrument"
+instructions: "{installed_path}/instructions.md"
+knowledge_base: "{project-root}/bmad/bmm/knowledge/debug/debug-patterns.md"
+standalone: true
diff --git a/src/modules/bmm/workflows/debug/pattern-analysis/instructions.md b/src/modules/bmm/workflows/debug/pattern-analysis/instructions.md
new file mode 100644
index 00000000..06a6153a
--- /dev/null
+++ b/src/modules/bmm/workflows/debug/pattern-analysis/instructions.md
@@ -0,0 +1,35 @@
+# Pattern Analysis Instructions
+
+## Overview
+
+Analyze recent commits, code changes, and development patterns to identify systematic defect patterns and areas of risk concentration.
+
+## Analysis Dimensions
+
+1. **Temporal Patterns** - Timing of defect introduction
+2. **Spatial Patterns** - Code regions with high defect density
+3. **Author Patterns** - Developer-specific issue trends
+4. **Change Patterns** - Types of modifications causing issues
+5. **Dependency Patterns** - Component interaction problems
+6. **Testing Patterns** - Coverage gaps and blind spots
+
+## Process Steps
+
+1. **Data Collection** - Gather commit history, bug reports, test results
+2. **Pattern Recognition** - Identify recurring defect categories
+3. **Hotspot Analysis** - Map defect concentration areas
+4. **Trend Analysis** - Track pattern evolution over time
+5. **Risk Assessment** - Evaluate pattern impact and likelihood
+6. **Prevention Strategy** - Recommend pattern-breaking interventions
+
+## Knowledge Integration
+
+Reference common defects catalog for pattern matching and classification of identified issues.
+
+## Expected Outputs
+
+- Defect pattern summary with frequency data
+- Risk hotspot identification and mapping
+- Trend analysis with predictive indicators
+- Targeted prevention recommendations
+- Process improvement suggestions
diff --git a/src/modules/bmm/workflows/debug/pattern-analysis/workflow.yaml b/src/modules/bmm/workflows/debug/pattern-analysis/workflow.yaml
new file mode 100644
index 00000000..15b6fa52
--- /dev/null
+++ b/src/modules/bmm/workflows/debug/pattern-analysis/workflow.yaml
@@ -0,0 +1,33 @@
+# Pattern Analysis Workflow Configuration
+name: "pattern-analysis"
+description: "Analyze recent commits and code changes for defect patterns and systematic issues."
+author: "Diana"
+
+# Critical variables from config
+config_source: "{project-root}/bmad/bmm/config.yaml"
+output_folder: "{config_source}:output_folder"
+user_name: "{config_source}:user_name"
+communication_language: "{config_source}:communication_language"
+document_output_language: "{config_source}:document_output_language"
+user_skill_level: "{config_source}:user_skill_level"
+date: system-generated
+
+# Module path and component files
+installed_path: "{project-root}/bmad/bmm/workflows/debug/pattern-analysis"
+template: false
+instructions: "{installed_path}/instructions.md"
+
+# Knowledge base integration
+knowledge_base: "{project-root}/bmad/bmm/knowledge/debug/common-defects.md"
+
+standalone: true
+
+web_bundle:
+  name: "pattern-analysis"
+  description: "Analyze recent commits and code changes for defect patterns and systematic issues."
+  author: "Diana"
+  instructions: "bmad/bmm/workflows/debug/pattern-analysis/instructions.md"
+  template: false
+  web_bundle_files:
+    - "bmad/bmm/workflows/debug/pattern-analysis/instructions.md"
+    - "bmad/bmm/knowledge/debug/common-defects.md"
diff --git a/src/modules/bmm/workflows/debug/quick-debug/instructions.md b/src/modules/bmm/workflows/debug/quick-debug/instructions.md
new file mode 100644
index 00000000..f50b9dda
--- /dev/null
+++ b/src/modules/bmm/workflows/debug/quick-debug/instructions.md
@@ -0,0 +1,31 @@
+# Quick Debug Instructions
+
+## Overview
+
+Perform rapid triage and initial analysis for simple issues requiring immediate attention or time-critical situations.
+
+## When to Use
+
+- Production issues requiring immediate response
+- Simple bugs with obvious symptoms
+- Initial triage before deeper investigation
+- Time-critical debugging scenarios
+
+## Process Steps
+
+1. **Symptom Capture** - Document observed behavior and error conditions
+2. **Environment Assessment** - Verify system state and recent changes
+3. **Pattern Matching** - Apply common debug patterns from knowledge base
+4. **Quick Verification** - Test immediate hypotheses
+5. **Triage Decision** - Determine if quick fix is appropriate or deeper analysis needed
+
+## Knowledge Integration
+
+Leverage debug patterns guide for rapid pattern recognition and common issue resolution strategies.
+
+## Expected Outputs
+
+- Issue classification and severity assessment
+- Initial hypothesis with supporting evidence
+- Quick fix recommendations (if applicable)
+- Escalation path for complex issues requiring full investigation
diff --git a/src/modules/bmm/workflows/debug/quick-debug/workflow.yaml b/src/modules/bmm/workflows/debug/quick-debug/workflow.yaml
new file mode 100644
index 00000000..c6575800
--- /dev/null
+++ b/src/modules/bmm/workflows/debug/quick-debug/workflow.yaml
@@ -0,0 +1,33 @@
+# Quick Debug Workflow Configuration
+name: "quick-debug"
+description: "Rapid triage and initial analysis for simple issues requiring immediate attention."
+author: "Diana"
+
+# Critical variables from config
+config_source: "{project-root}/bmad/bmm/config.yaml"
+output_folder: "{config_source}:output_folder"
+user_name: "{config_source}:user_name"
+communication_language: "{config_source}:communication_language"
+document_output_language: "{config_source}:document_output_language"
+user_skill_level: "{config_source}:user_skill_level"
+date: system-generated
+
+# Module path and component files
+installed_path: "{project-root}/bmad/bmm/workflows/debug/quick-debug"
+template: false
+instructions: "{installed_path}/instructions.md"
+
+# Knowledge base integration
+knowledge_base: "{project-root}/bmad/bmm/knowledge/debug/debug-patterns.md"
+
+standalone: true
+
+web_bundle:
+  name: "quick-debug"
+  description: "Rapid triage and initial analysis for simple issues requiring immediate attention."
+  author: "Diana"
+  instructions: "bmad/bmm/workflows/debug/quick-debug/instructions.md"
+  template: false
+  web_bundle_files:
+    - "bmad/bmm/workflows/debug/quick-debug/instructions.md"
+    - "bmad/bmm/knowledge/debug/debug-patterns.md"
diff --git a/src/modules/bmm/workflows/debug/root-cause/instructions.md b/src/modules/bmm/workflows/debug/root-cause/instructions.md
new file mode 100644
index 00000000..00d52786
--- /dev/null
+++ b/src/modules/bmm/workflows/debug/root-cause/instructions.md
@@ -0,0 +1,36 @@
+# Root Cause Analysis Instructions
+
+## Overview
+
+Execute systematic root cause analysis using fishbone (Ishikawa) methodology to identify underlying system issues beyond immediate symptoms.
+
+## Fishbone Methodology
+
+Systematic analysis across six primary categories:
+
+1. **Methods** - Processes, procedures, standards
+2. **Machines** - Tools, technology, infrastructure
+3. **Materials** - Data, inputs, dependencies
+4. **Measurements** - Metrics, monitoring, detection
+5. **Environment** - Context, conditions, constraints
+6. **People** - Skills, training, communication
+
+## Process Steps
+
+1. **Problem Definition** - Clearly articulate the observed issue
+2. **Category Analysis** - Systematically examine each fishbone category
+3. **Contributing Factor Identification** - Map potential causes to categories
+4. **Evidence Collection** - Gather supporting data for hypotheses
+5. **Root Cause Prioritization** - Rank causes by likelihood and impact
+6. **Verification Testing** - Validate root cause hypotheses
+
+## Knowledge Integration
+
+Use root cause checklist for systematic category exploration and common cause patterns.
+
+## Expected Outputs
+
+- Comprehensive fishbone diagram
+- Prioritized root cause candidates with evidence
+- Verification plan for top hypotheses
+- Preventive measures to avoid recurrence
diff --git a/src/modules/bmm/workflows/debug/root-cause/workflow.yaml b/src/modules/bmm/workflows/debug/root-cause/workflow.yaml
new file mode 100644
index 00000000..3c9f430a
--- /dev/null
+++ b/src/modules/bmm/workflows/debug/root-cause/workflow.yaml
@@ -0,0 +1,33 @@
+# Root Cause Analysis Workflow Configuration
+name: "root-cause"
+description: "Execute focused root cause analysis using fishbone methodology to identify underlying system issues."
+author: "Diana"
+
+# Critical variables from config
+config_source: "{project-root}/bmad/bmm/config.yaml"
+output_folder: "{config_source}:output_folder"
+user_name: "{config_source}:user_name"
+communication_language: "{config_source}:communication_language"
+document_output_language: "{config_source}:document_output_language"
+user_skill_level: "{config_source}:user_skill_level"
+date: system-generated
+
+# Module path and component files
+installed_path: "{project-root}/bmad/bmm/workflows/debug/root-cause"
+template: false
+instructions: "{installed_path}/instructions.md"
+
+# Knowledge base integration
+knowledge_base: "{project-root}/bmad/bmm/knowledge/debug/root-cause-checklist.md"
+
+standalone: true
+
+web_bundle:
+  name: "root-cause"
+  description: "Execute focused root cause analysis using fishbone methodology to identify underlying system issues."
+  author: "Diana"
+  instructions: "bmad/bmm/workflows/debug/root-cause/instructions.md"
+  template: false
+  web_bundle_files:
+    - "bmad/bmm/workflows/debug/root-cause/instructions.md"
+    - "bmad/bmm/knowledge/debug/root-cause-checklist.md"
diff --git a/src/modules/bmm/workflows/debug/static-scan/workflow.yaml b/src/modules/bmm/workflows/debug/static-scan/workflow.yaml
new file mode 100644
index 00000000..ff3dae5a
--- /dev/null
+++ b/src/modules/bmm/workflows/debug/static-scan/workflow.yaml
@@ -0,0 +1,11 @@
+# Static Scan Workflow Configuration
+name: "static-scan"
+description: "Perform comprehensive static analysis for common defects using automated tools and manual inspection."
+author: "Diana"
+
+config_source: "{project-root}/bmad/bmm/config.yaml"
+output_folder: "{config_source}:output_folder"
+installed_path: "{project-root}/bmad/bmm/workflows/debug/static-scan"
+instructions: "{installed_path}/instructions.md"
+knowledge_base: "{project-root}/bmad/bmm/knowledge/debug/common-defects.md"
+standalone: true
diff --git a/src/modules/bmm/workflows/debug/validate-fix/workflow.yaml b/src/modules/bmm/workflows/debug/validate-fix/workflow.yaml
new file mode 100644
index 00000000..7510c793
--- /dev/null
+++ b/src/modules/bmm/workflows/debug/validate-fix/workflow.yaml
@@ -0,0 +1,11 @@
+# Validate Fix Workflow Configuration
+name: "validate-fix"
+description: "Verify proposed fix addresses root cause without introducing side effects or regressions."
+author: "Diana"
+
+config_source: "{project-root}/bmad/bmm/config.yaml"
+output_folder: "{config_source}:output_folder"
+installed_path: "{project-root}/bmad/bmm/workflows/debug/validate-fix"
+instructions: "{installed_path}/instructions.md"
+knowledge_base: "{project-root}/bmad/bmm/knowledge/debug/debug-inspection-checklist.md"
+standalone: true
diff --git a/src/modules/bmm/workflows/debug/walkthrough-prep/workflow.yaml b/src/modules/bmm/workflows/debug/walkthrough-prep/workflow.yaml
new file mode 100644
index 00000000..45782ae2
--- /dev/null
+++ b/src/modules/bmm/workflows/debug/walkthrough-prep/workflow.yaml
@@ -0,0 +1,11 @@
+# Walkthrough Prep Workflow Configuration
+name: "walkthrough-prep"
+description: "Generate materials for code walkthrough session including inspection guides and focus areas."
+author: "Diana"
+
+config_source: "{project-root}/bmad/bmm/config.yaml"
+output_folder: "{config_source}:output_folder"
+installed_path: "{project-root}/bmad/bmm/workflows/debug/walkthrough-prep"
+instructions: "{instructions_path}/instructions.md"
+knowledge_base: "{project-root}/bmad/bmm/knowledge/debug/debug-inspection-checklist.md"
+standalone: true
diff --git a/src/modules/bmm/workflows/debug/wolf-fence/instructions.md b/src/modules/bmm/workflows/debug/wolf-fence/instructions.md
new file mode 100644
index 00000000..0adaf65d
--- /dev/null
+++ b/src/modules/bmm/workflows/debug/wolf-fence/instructions.md
@@ -0,0 +1,42 @@
+# Wolf Fence Binary Search Debugging Instructions
+
+## Overview
+
+Execute binary search debugging methodology to efficiently isolate bug location through systematic code region elimination.
+
+## Wolf Fence Principle
+
+"There's one wolf in Alaska; how do you find it? First build a fence down the middle of the state, wait for the wolf to howl, then go to the side where you heard it."
+
+## Methodology
+
+1. **Define Search Space** - Identify code region containing the bug
+2. **Bisection Strategy** - Divide region into two equal parts
+3. **Test Point Selection** - Choose midpoint for testing
+4. **Behavior Verification** - Determine which half contains the bug
+5. **Recursive Narrowing** - Repeat process on identified half
+6. **Isolation Completion** - Continue until bug location is isolated
+
+## Process Steps
+
+1. **Establish Known Good/Bad Points** - Verify working and failing states
+2. **Binary Division** - Split code/data/timeline into halves
+3. **Midpoint Testing** - Insert test points or checkpoints
+4. **Result Analysis** - Determine which side exhibits the bug
+5. **Range Refinement** - Focus search on problematic half
+6. **Iteration** - Repeat until precise location identified
+
+## Application Scenarios
+
+- Code regression debugging
+- Data corruption location
+- Timeline-based issue isolation
+- Configuration problem hunting
+- Memory corruption detection
+
+## Expected Outputs
+
+- Precise bug location identification
+- Minimal reproduction case
+- Verification test points
+- Isolated code region for detailed analysis
diff --git a/src/modules/bmm/workflows/debug/wolf-fence/workflow.yaml b/src/modules/bmm/workflows/debug/wolf-fence/workflow.yaml
new file mode 100644
index 00000000..9ad7cca5
--- /dev/null
+++ b/src/modules/bmm/workflows/debug/wolf-fence/workflow.yaml
@@ -0,0 +1,33 @@
+# Wolf Fence Binary Search Debugging Workflow Configuration
+name: "wolf-fence"
+description: "Execute binary search debugging to isolate bug location efficiently through systematic code region elimination."
+author: "Diana"
+
+# Critical variables from config
+config_source: "{project-root}/bmad/bmm/config.yaml"
+output_folder: "{config_source}:output_folder"
+user_name: "{config_source}:user_name"
+communication_language: "{config_source}:communication_language"
+document_output_language: "{config_source}:document_output_language"
+user_skill_level: "{config_source}:user_skill_level"
+date: system-generated
+
+# Module path and component files
+installed_path: "{project-root}/bmad/bmm/workflows/debug/wolf-fence"
+template: false
+instructions: "{installed_path}/instructions.md"
+
+# Knowledge base integration
+knowledge_base: "{project-root}/bmad/bmm/knowledge/debug/debug-patterns.md"
+
+standalone: true
+
+web_bundle:
+  name: "wolf-fence"
+  description: "Execute binary search debugging to isolate bug location efficiently through systematic code region elimination."
+  author: "Diana"
+  instructions: "bmad/bmm/workflows/debug/wolf-fence/instructions.md"
+  template: false
+  web_bundle_files:
+    - "bmad/bmad/bmm/workflows/debug/wolf-fence/instructions.md"
+    - "bmad/bmm/knowledge/debug/debug-patterns.md"