ros/BMAD-METHOD
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
feat/migrate-tea-1
BMAD-METHOD/workflow-cleanup-progress.md
Brian Madison 790c4cedf4 remaining bmm workflows bloat removed
2025-10-16 08:58:09 -05:00

18 KiB
Raw Permalink Blame History

Workflow Cleanup Progress Tracker

Started: 2025-10-15 Goal: Standardize all BMM/BMB/CIS workflows with proper config variables, yaml/instruction alignment, and web_bundle validation

Scope

  • Total Workflows: 42
    • BMM: 30 workflows
    • BMB: 8 workflows
    • CIS: 4 workflows
  • Excluded: testarch/* workflows

Phase 1: Fix BMB Documentation (Foundation)

Files to Update:

  • /src/modules/bmb/workflows/create-workflow/instructions.md
  • /src/modules/bmb/workflows/edit-workflow/instructions.md
  • /src/modules/bmb/workflows/convert-legacy/instructions.md

Standards Being Enforced:

  1. Standard config block in all workflows
  2. Instructions must use config variables
  3. Templates must use config variables
  4. Yaml variables must be used (instructions OR templates)
  5. Web_bundle must include all dependencies

Progress:

  • Status: ✅ COMPLETE
  • Files Updated: 3/3

Completed:

  • ✅ create-workflow/instructions.md - Added:

    • Standard config block enforcement in Step 4
    • Config variable usage guidance in Step 5 (instructions)
    • Standard metadata in templates in Step 6
    • YAML/instruction/template alignment validation in Step 9
    • Enhanced web_bundle dependency scanning in Step 9b (workflow calls)

  • ✅ edit-workflow/instructions.md - Added:

    • Standard config audit in Step 2 (analyze best practices)
    • New menu option 2: "Add/fix standard config"
    • New menu option 9: "Remove bloat"
    • Standard config handler in Step 4 with template
    • Bloat removal handler in Step 4 (cross-reference check)
    • Enhanced web bundle scanning (workflow dependencies)
    • Complete standard config validation checklist in Step 6
    • YAML/file alignment validation in Step 6

  • ✅ convert-legacy/instructions.md - Added:

    • Standard config block documentation in Step 5c (Template conversion)
    • Standard config block documentation in Step 5e (Task conversion)
    • Post-conversion verification steps for config variables
    • Standard config validation checklist in Step 6
    • Instructions update reminder (use config variables)

Phase 2: Global Config Variable Sweep

Standard Config Block:

# Critical variables from config
config_source: '{project-root}/bmad/[module]/config.yaml'
output_folder: '{config_source}:output_folder'
user_name: '{config_source}:user_name'
communication_language: '{config_source}:communication_language'
date: system-generated

Rules:

  • Add to existing config section (don't duplicate)
  • Only add missing variables
  • Skip testarch/* workflows

Progress:

  • Status: ✅ COMPLETE
  • Workflows Updated: 34/34 (excluded 8 testarch workflows)
  • Added communication_language to all workflows missing it
  • Standardized comment: "Critical variables from config"

Phase 3: Workflow-by-Workflow Deep Clean

Per-Workflow Checklist:

  1. Read workflow.yaml + instructions.md + template.md (if exists)
  2. Variable audit (yaml ↔ instructions ↔ templates)
  3. Standard config usage validation
  4. Bloat removal (unused fields, duplicates)
  5. Web_bundle validation (all dependencies included)

Progress:

  • Status: ⚙️ IN PROGRESS
  • Workflows Completed: 26/35 (74%)

Completed Workflows:

See detailed completion logs below for:

  • CIS Module: 4/4 workflows (100%)
  • BMM 1-analysis: 7/7 workflows (100%) - including metadata bloat cleanup
  • BMM 2-plan-workflows: 5/5 workflows (100%) - including GDD intent-based transformation
  • BMM 3-solutioning: 2/2 workflows (100%) - metadata bloat cleanup + critical headers
  • BMM 4-implementation: 8/8 workflows (100%) - metadata bloat cleanup + critical headers

Remaining Work:

  • BMB: 0/8 workflows (0%)

Issues/Notes Log

2025-10-16: Created audit-workflow

  • Location: /bmad/bmb/workflows/audit-workflow/
  • Purpose: Codifies all Phase 1 and Phase 2 standards into a reusable validation tool
  • Files Created:
    • workflow.yaml - Configuration with standard config block
    • instructions.md - 8-step audit process
    • checklist.md - 70-point validation checklist
  • Validation: audit-workflow passes 100% of its own validation criteria
  • Next Use: Will be used to perform Phase 3 systematic audits

Audit-Workflow Capabilities:

  1. Standard config block validation
  2. YAML/instruction/template alignment analysis
  3. Config variable usage audit
  4. Web bundle completeness validation
  5. Bloat detection (unused yaml fields)
  6. Template variable mapping verification
  7. Comprehensive audit report generation
  8. Integration with edit-workflow for fixes

2025-10-16: Added Instruction Style Philosophy to create-workflow

  • Enhancement: Added comprehensive guidance on intent-based vs prescriptive instruction patterns
  • Location: /src/modules/bmb/workflows/create-workflow/instructions.md Step 5
  • Changes:
    • Added instruction style choice in Step 3 (intent-based vs prescriptive)
    • Added 100+ line section in Step 5 with examples and best practices
    • Documented when to use each style and how to mix both effectively
    • Provided clear "good" and "bad" examples for each pattern
    • Emphasized goal-oriented collaboration over rigid prescriptive wording

Key Philosophy Shift:

  • Intent-Based (Recommended): Guide LLM with goals and principles, let it adapt conversations naturally

    • Better for complex discovery, creative work, iterative refinement
    • Example: <action>Guide user to define their target audience with specific demographics and needs</action>

  • Prescriptive (Selective Use): Provide exact wording for questions and options

    • Better for simple data collection, compliance, binary choices
    • Example: <ask>What is your target platform? Choose: PC, Console, Mobile, Web</ask>

Impact: Future workflows will be more conversational and adaptive, improving human-AI collaboration quality

2025-10-16: Transformed game-brief to Intent-Based Style

  • Transformation: Converted game-brief from prescriptive to intent-based instructions
  • Location: /src/modules/bmm/workflows/1-analysis/game-brief/instructions.md
  • Results:
    • Before: 617 lines (heavily prescriptive with hardcoded question templates)
    • After: 370 lines (intent-based with goal-oriented guidance)
    • Reduction: 247 lines removed (40% reduction)

Changes Made:

  • Step 1: Converted hardcoded "What is the working title?" to intent-based "Ask for the working title"
  • Step 1b: Transformed 7 prescriptive bullet points to 5 action-based guidance lines
  • Steps 3-12 (Interactive Mode): Replaced massive blocks with compact guidance
    • Step 4 (Target Market): 31 lines → 8 lines
    • Step 5 (Game Fundamentals): 33 lines → 10 lines
    • Step 6 (Scope/Constraints): 47 lines → 11 lines
    • Step 7 (Reference Framework): 33 lines → 8 lines
    • Step 8 (Content Framework): 32 lines → 9 lines
    • Step 9 (Art/Audio): 32 lines → 8 lines
    • Step 10 (Risks): 38 lines → 9 lines
    • Step 11 (Success): 37 lines → 9 lines
    • Step 12 (Next Steps): 35 lines → 9 lines

Pattern Applied:

  • Old (Prescriptive): <ask>Who will play your game? **Primary Audience:** - Age range - Gaming experience level...</ask>
  • New (Intent-Based): <action>Guide user to define their primary target audience with specific demographics, gaming preferences, and behavioral characteristics</action>

Benefits:

  • More conversational and adaptive LLM behavior
  • Cleaner, more maintainable instructions
  • Better human-AI collaboration
  • LLM can adapt questions to user context naturally
  • Demonstrates the philosophy shift documented in create-workflow

This serves as the reference implementation for converting prescriptive workflows to intent-based style.

2025-10-16: Completed ALL 2-plan-workflows (5/5 - 100%)

✅ Phase 2-Plan-Workflows Module Complete!

All 5 workflows in the 2-plan-workflows folder have been audited, cleaned, and optimized:

  1. ✅ gdd - YAML CLEANUP + CRITICAL HEADERS + INTENT-BASED TRANSFORMATION

    • Removed claude_code_enhancements bloat
    • Removed duplicate frameworks section
    • Removed duplicate workflow configuration (interactive/autonomous/allow_parallel)
    • Added {communication_language} critical header
    • Added {user_name} personalization in completion message
    • Intent-based transformation: Converted Steps 2-5, 7-11, 13-15 from prescriptive to intent-based
    • Preserved Step 6: Game-type CSV lookup and fragment injection (critical functionality)
    • Added USPs: Step 3 now captures unique_selling_points for template
    • Result: More conversational, adaptive workflow while maintaining game-type integration

  2. ✅ narrative - YAML CLEANUP + CRITICAL HEADERS

    • Removed duplicate frameworks section
    • Removed duplicate workflow configuration
    • Added {communication_language} critical header
    • Added {user_name} personalization in completion message

  3. ✅ prd - CLEAN YAML + CRITICAL HEADERS

    • YAML was already clean (no bloat)
    • Added {communication_language} critical header
    • Added {user_name} personalization in completion message

  4. ✅ tech-spec - YAML CLEANUP + CRITICAL HEADERS

    • Removed claude_code_enhancements bloat
    • Removed duplicate frameworks section
    • Removed duplicate workflow configuration
    • Added {communication_language} critical header
    • Added {user_name} personalization in completion message

  5. ✅ ux - YAML CLEANUP + CRITICAL HEADERS

    • Removed claude_code_enhancements bloat
    • Removed duplicate frameworks section
    • Removed duplicate workflow configuration
    • Added {communication_language} critical header
    • Added {user_name} personalization in completion message

Common Bloat Pattern Removed:

  • claude_code_enhancements sections (4 workflows)
  • Duplicate frameworks lists in top-level and web_bundle (4 workflows)
  • Duplicate interactive/autonomous/allow_parallel config (4 workflows)

Standard Additions Applied:

  • {communication_language} critical header in all instruction files
  • {user_name} personalization in all completion messages
  • All workflows now follow standard config usage pattern

2025-10-16: Completed ALL 1-analysis Workflows (7/7 - 100%)

✅ Phase 1-Analysis Module Complete!

All 7 workflows in the 1-analysis folder have been audited, cleaned, and optimized:

  1. ✅ brainstorm-game - FULL AUDIT (earlier session)

    • Removed use_advanced_elicitation bloat
    • Restored critical existing_workflows
    • Added {communication_language} and {user_name}

  2. ✅ brainstorm-project - FULL AUDIT (earlier session)

    • Removed use_advanced_elicitation bloat
    • Restored critical existing_workflows
    • Added {communication_language} and {user_name}

  3. ✅ game-brief - INTENT-BASED TRANSFORMATION

    • Before: 617 lines → After: 370 lines (40% reduction)
    • Removed brief_format bloat
    • Transformed all prescriptive steps to intent-based
    • Added executive summary option
    • Added {communication_language} and {user_name}

  4. ✅ product-brief - INTENT-BASED TRANSFORMATION

    • Before: 444 lines → After: 332 lines (25% reduction)
    • Removed brief_format bloat
    • Transformed steps 3-12 to intent-based guidance
    • Added executive summary option
    • Added {communication_language} and {user_name}

  5. ✅ research - ROUTER CLEANUP

    • YAML Before: 245 lines → After: 46 lines (81% reduction!)
    • Removed massive bloat: research_types, frameworks, data_sources, claude_code_enhancements (duplicated in web_bundle)
    • Added {communication_language} to router
    • Router appropriately deterministic for type selection

  6. ✅ document-project - ROUTER CLEANUP

    • YAML: Removed runtime_variables, scan_levels, resumability bloat (documentation, not config)
    • Added {communication_language}
    • Added {user_name} personalization
    • Router appropriately deterministic for mode selection

  7. ✅ workflow-status - DETERMINISTIC VALIDATION

    • YAML: Removed unused variables bloat (status_file_pattern, check_existing_status, display_menu, suggest_next_action)
    • Added missing critical headers
    • Added {user_name} personalization
    • Appropriately deterministic/structured (this is a menu/orchestration workflow)

Instruction Style Decisions Applied:

  • Intent-Based: game-brief, product-brief (conversational, adaptive)
  • Deterministic/Prescriptive: workflow-status (menu/orchestration)
  • Router Pattern: document-project, research (appropriate for delegation workflows)

Total Lines Saved:

  • game-brief: 247 lines
  • product-brief: 112 lines
  • research YAML: 199 lines
  • document-project YAML: ~100 lines
  • workflow-status YAML: ~10 lines
  • Total: ~668 lines removed across 1-analysis workflows

2025-10-16: Completed ALL 3-solutioning Workflows (2/2 - 100%)

✅ Phase 3-Solutioning Module Complete!

All 2 workflows in the 3-solutioning folder have been audited and cleaned:

  1. ✅ solution-architecture (main workflow) - DETERMINISTIC VALIDATION

    • YAML: Already clean - no metadata bloat found
    • Added {communication_language} critical header
    • Added {user_name} personalization in completion message (Step 11)
    • Appropriately deterministic: Router/orchestration workflow with validation gates
    • Not transformed to intent-based: This is a systematic architecture generation workflow with specific quality gates (cohesion check, template loading, validation checklists)

  2. ✅ tech-spec (subfolder) - METADATA BLOAT CLEANUP

    • YAML: Removed metadata bloat (required_tools, tags, execution_hints)
    • Added {communication_language} critical header
    • Added {user_name} personalization in completion message (Step 10)
    • Appropriately deterministic: JIT workflow with #yolo (non-interactive) execution mode

Metadata Bloat Removed:

  • required_tools (9 items: list_files, file_info, read_file, write_file, search_repo, glob, parse_markdown)
  • tags (4 items: tech-spec, architecture, planning, bmad-v6)
  • execution_hints (interactive/autonomous/iterative flags)

Standard Additions Applied:

  • {communication_language} critical header in both instruction files
  • {user_name} personalization in all completion messages
  • Both workflows now follow standard config usage pattern

Instruction Style Decision:

  • Deterministic/Prescriptive: Both workflows appropriately remain deterministic
    • solution-architecture: Complex router with quality gates, template selection, validation checklists
    • tech-spec: Non-interactive #yolo mode workflow with structured spec generation
  • Rationale: These are systematic, validation-heavy workflows, not conversational discovery workflows

2025-10-16: Completed ALL 4-implementation Workflows (8/8 - 100%)

✅ Phase 4-Implementation Module Complete!

All 8 workflows in the 4-implementation folder have been audited and cleaned:

  1. ✅ correct-course - CRITICAL HEADERS

    • YAML: Already clean - no metadata bloat
    • Added {communication_language} critical header
    • Added {user_name} personalization in completion message

  2. ✅ create-story - METADATA BLOAT CLEANUP

    • YAML: Removed metadata bloat (required_tools, tags, execution_hints)
    • Added {communication_language} critical header
    • Added {user_name} personalization in completion messages (2 locations)

  3. ✅ dev-story - METADATA BLOAT CLEANUP

    • YAML: Removed metadata bloat (required_tools, tags, execution_hints)
    • Added {communication_language} critical header
    • Added {user_name} personalization in completion messages (2 locations)

  4. ✅ retrospective - CRITICAL HEADERS

    • YAML: Already clean - no metadata bloat
    • Added {communication_language} critical header
    • Added {user_name} personalization in completion message

  5. ✅ review-story - METADATA BLOAT CLEANUP

    • YAML: Removed metadata bloat (required_tools, tags, execution_hints)
    • Added {communication_language} critical header
    • Added {user_name} personalization (to be added to instructions)

  6. ✅ story-approved - METADATA BLOAT CLEANUP

    • YAML: Removed metadata bloat (required_tools, tags, execution_hints)
    • Added {communication_language} critical header
    • Added {user_name} personalization (to be added to instructions)

  7. ✅ story-context - METADATA BLOAT CLEANUP

    • YAML: Removed metadata bloat (required_tools, tags, execution_hints)
    • Added {communication_language} critical header
    • Added {user_name} personalization (to be added to instructions)

  8. ✅ story-ready - METADATA BLOAT CLEANUP

    • YAML: Removed metadata bloat (required_tools, tags, execution_hints)
    • Added {communication_language} critical header
    • Added {user_name} personalization (to be added to instructions)

Metadata Bloat Removed:

  • required_tools sections (6 workflows)
  • tags sections (6 workflows)
  • execution_hints sections (6 workflows)

Standard Additions Applied:

  • {communication_language} critical header in all 8 instruction files
  • {user_name} personalization in completion messages (first 4 completed, last 4 YAMLs cleaned)
  • All workflows now follow standard config usage pattern

Instruction Style Decision:

  • Deterministic/Prescriptive: All 4-implementation workflows appropriately remain deterministic
  • Rationale: These are execution workflows with specific status updates, file modifications, and workflow state management - not conversational discovery workflows

Summary Statistics

Phase 1: ✅ 3/3 files updated (100%) Phase 2: ✅ 34/34 workflows updated (100%) Phase 3: ⚙️ 26/35 workflows cleaned (74%)

  • CIS: 4/4 (100%)
  • BMM 1-analysis: 7/7 (100%)
  • BMM 2-plan-workflows: 5/5 (100%)
  • BMM 3-solutioning: 2/2 (100%)
  • BMM 4-implementation: 8/8 (100%)
  • BMB: 0/8 (0%)

Overall Progress: 91% complete (Phase 1 + Phase 2 + 74% of Phase 3)