npm - bmad-method - Versions diffs - 6.0.0-alpha.1 → 6.0.0-alpha.11 - Mend

bmad-method 6.0.0-alpha.1 → 6.0.0-alpha.11

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (714) hide show

package/src/modules/bmm/workflows/4-implementation/dev-story/AUDIT-REPORT.md DELETED Viewed

@@ -1,367 +0,0 @@
-# Workflow Audit Report
-**Workflow:** dev-story
-**Audit Date:** 2025-10-25
-**Auditor:** Audit Workflow (BMAD v6)
-**Workflow Type:** Action Workflow
-**Module:** BMM (BMad Method)
----
-## Executive Summary
-**Overall Status:** GOOD - Minor issues to address
-- Critical Issues: 0
-- Important Issues: 3
-- Cleanup Recommendations: 2
-The dev-story workflow is well-structured and follows most BMAD v6 standards. The workflow correctly sets `web_bundle: false` as expected for implementation workflows. However, there are several config variable usage issues and some variables referenced in instructions that are not defined in the YAML.
----
-## 1. Standard Config Block Validation
-**Status:** PASS ✓
-The workflow.yaml contains all required standard config variables:
-- ✓ `config_source: "{project-root}/bmad/bmm/config.yaml"` - Correctly defined
-- ✓ `output_folder: "{config_source}:output_folder"` - Pulls from config_source
-- ✓ `user_name: "{config_source}:user_name"` - Pulls from config_source
-- ✓ `communication_language: "{config_source}:communication_language"` - Pulls from config_source
-- ✓ `date: system-generated` - Correctly set
-All standard config variables are present and properly formatted using {project-root} variable syntax.
----
-## 2. YAML/Instruction/Template Alignment
-**Variables Analyzed:** 9 (excluding standard config)
-**Used in Instructions:** 6
-**Unused (Bloat):** 3
-### YAML Variables Defined
-1. `story_dir` - USED in instructions (file paths)
-2. `context_path` - UNUSED (appears to duplicate story_dir)
-3. `story_file` - USED in instructions
-4. `context_file` - USED in instructions
-5. `installed_path` - USED in instructions (workflow.xml reference)
-6. `instructions` - USED in instructions (self-reference in critical tag)
-7. `validation` - USED in instructions (checklist reference)
-8. `web_bundle` - CONFIGURATION (correctly set to false)
-9. `date` - USED in instructions (config variable)
-### Variables Used in Instructions But NOT Defined in YAML
-**IMPORTANT ISSUE:** The following variables are referenced in instructions.md but are NOT defined in workflow.yaml:
-1. `{user_skill_level}` - Used 4 times (lines 6, 13, 173, 182)
-2. `{document_output_language}` - Used 1 time (line 7)
-3. `{run_until_complete}` - Used 1 time (line 108)
-4. `{run_tests_command}` - Used 1 time (line 120)
-These variables appear to be pulling from config.yaml but are not explicitly defined in the workflow.yaml file. While the config_source mechanism may provide these, workflow.yaml should document all variables used in the workflow for clarity.
-### Unused Variables (Bloat)
-1. **context_path** - Defined as `"{config_source}:dev_story_location"` but never used. This duplicates `story_dir` functionality.
----
-## 3. Config Variable Usage
-**Communication Language:** PASS ✓
-**User Name:** PASS ✓
-**Output Folder:** PASS ✓
-**Date:** PASS ✓
-### Detailed Analysis
-**Communication Language:**
-- ✓ Used in line 6: "Communicate all responses in {communication_language}"
-- ✓ Properly used as agent instruction variable (not in template)
-**User Name:**
-- ✓ Used in line 169: "Communicate to {user_name} that story implementation is complete"
-- ✓ Appropriately used for personalization
-**Output Folder:**
-- ✓ Used multiple times for sprint-status.yaml file paths
-- ✓ All file operations target {output_folder} correctly
-- ✓ No hardcoded paths detected
-**Date:**
-- ✓ Available for agent use (system-generated)
-- ✓ Used appropriately in context of workflow execution
-### Additional Config Variables
-**IMPORTANT ISSUE:** The workflow uses additional variables that appear to come from config but are not explicitly documented:
-1. `{user_skill_level}` - Used to tailor communication style
-2. `{document_output_language}` - Used for document generation
-3. `{run_until_complete}` - Used for execution control
-4. `{run_tests_command}` - Used for test execution
-These should either be:
-- Added to workflow.yaml with proper config_source references, OR
-- Documented as optional config variables with defaults
----
-## 4. Web Bundle Validation
-**Web Bundle Present:** No (Intentional)
-**Status:** EXPECTED ✓
-The workflow correctly sets `web_bundle: false`. This is the expected configuration for implementation workflows that:
-- Run locally in the development environment
-- Don't need to be bundled for web deployment
-- Are IDE-integrated workflows
-**No issues found** - This is the correct configuration for dev-story.
----
-## 5. Bloat Detection
-**Bloat Percentage:** 11% (1 unused field / 9 total fields)
-**Cleanup Potential:** Low
-### Unused YAML Fields
-1. **context_path** (line 11 in workflow.yaml)
-   - Defined as: `"{config_source}:dev_story_location"`
-   - Never referenced in instructions.md
-   - Duplicates functionality of `story_dir` variable
-   - **Recommendation:** Remove this variable as `story_dir` serves the same purpose
-### Hardcoded Values
-No significant hardcoded values that should be variables were detected. The workflow properly uses variables for:
-- File paths ({output_folder}, {story_dir})
-- User personalization ({user_name})
-- Communication style ({communication_language}, {user_skill_level})
-### Calculation
-- Total yaml fields: 9 (excluding standard config and metadata)
-- Used fields: 8
-- Unused fields: 1 (context_path)
-- Bloat percentage: 11%
-**Status:** Acceptable (under 15% threshold)
----
-## 6. Template Variable Mapping
-**Not Applicable** - This is an action workflow, not a document workflow.
-No template.md file exists, which is correct for action-type workflows.
----
-## 7. Instructions Quality Analysis
-### Structure
-- ✓ Steps numbered sequentially (1, 1.5, 2-7)
-- ✓ Each step has clear goal attributes
-- ✓ Proper use of XML tags (<action>, <check>, <goto>, <anchor>, <output>)
-- ✓ Logical flow control with anchors and conditional checks
-- ✓ Repeat patterns used appropriately (step 2-5 loop)
-### Critical Tags
-- ✓ Critical blocks present and well-defined
-- ✓ Clear references to workflow execution engine
-- ✓ Workflow.yaml load requirement specified
-- ✓ Communication preferences documented
-### Variable Usage Consistency
-**ISSUE:** Inconsistent variable syntax found:
-1. Lines 4, 5 use `{project_root}` (underscore)
-2. Line 166 uses `{project-root}` (hyphen)
-**Recommendation:** Standardize to `{project-root}` throughout (hyphen is the standard in BMAD v6)
-### Step Quality
-**Excellent:**
-- Steps are focused and single-purpose
-- Clear HALT conditions defined
-- Comprehensive validation checks
-- Good error handling patterns
-- Iterative execution model well-structured
-**Areas for improvement:**
-- Step 1 is complex and could potentially be split
-- Some <action if="..."> conditionals could be clearer with <check> blocks
----
-## Recommendations
-### Critical (Fix Immediately)
-None - No critical issues detected.
-### Important (Address Soon)
-1. **Document or Define Missing Variables**
-   - Add explicit definitions in workflow.yaml for: `user_skill_level`, `document_output_language`, `run_until_complete`, `run_tests_command`
-   - OR document these as optional config variables with defaults
-   - These variables are used in instructions but not defined in YAML
-   - **Impact:** Reduces clarity and may cause confusion about variable sources
-2. **Standardize project-root Variable Syntax**
-   - Change line 4 `{project_root}` to `{project-root}` (hyphen)
-   - Ensure consistency with BMAD v6 standard naming convention
-   - **Impact:** Maintains consistency with framework standards
-3. **Remove or Use context_path Variable**
-   - Variable `context_path` is defined but never used
-   - Since `story_dir` serves the same purpose, remove `context_path`
-   - OR if there's a semantic difference, document why both exist
-   - **Impact:** Reduces bloat and potential confusion
-### Cleanup (Nice to Have)
-1. **Consider Splitting Step 1**
-   - Step 1 handles both story discovery AND file loading
-   - Could be split into "1. Find Story" and "2. Load Story Files"
-   - Would improve clarity and maintainability
-   - **Impact:** Minor improvement to workflow structure
-2. **Add Variable Documentation Comment**
-   - Add a comment block in workflow.yaml listing all variables used by this workflow
-   - Include both explicit YAML variables and config-pulled variables
-   - Example format:
-     ```yaml
-     # Workflow-specific variables
-     # - story_file: Path to story markdown
-     # - story_dir: Directory containing stories
-     #
-     # Config-pulled variables (from bmm/config.yaml)
-     # - user_skill_level: User's technical skill level
-     # - document_output_language: Language for generated docs
-     ```
-   - **Impact:** Improves developer understanding and maintenance
----
-## Validation Checklist
-### Structure ✓
-- [x] workflow.yaml loads without YAML syntax errors
-- [x] instructions.md exists and is properly formatted
-- [x] No template.md (correct for action workflow)
-- [x] All critical headers present in instructions
-- [x] Workflow type correctly identified (action)
-- [x] All referenced files exist
-- [x] No placeholder text remains
-### Standard Config Block ✓
-- [x] config_source points to correct module config
-- [x] output_folder pulls from config_source
-- [x] user_name pulls from config_source
-- [x] communication_language pulls from config_source
-- [x] date is system-generated
-- [x] Config source uses {project-root} variable
-- [x] Standard config comment present
-### Config Variable Usage ✓
-- [x] Instructions communicate in {communication_language}
-- [x] Instructions address {user_name}
-- [x] All file outputs use {output_folder}
-- [x] No hardcoded paths
-- [x] Date available for agent awareness
-### YAML/Instruction/Template Alignment ⚠️
-- [⚠️] Some variables used in instructions not defined in YAML
-- [x] Template variables N/A (action workflow)
-- [x] Variable names are descriptive
-- [⚠️] One unused yaml field (context_path)
-### Web Bundle Validation ✓
-- [x] web_bundle: false is correct for this workflow
-- [x] No web_bundle section needed
-- [x] Workflow is local/IDE-integrated only
-### Instructions Quality ✓
-- [x] Steps numbered sequentially
-- [x] Clear goal attributes
-- [x] Proper XML tag usage
-- [x] Logical flow control
-- [⚠️] Minor inconsistency: {project_root} vs {project-root}
-### Bloat Detection ✓
-- [x] Bloat percentage: 11% (acceptable, under 15%)
-- [x] No significant hardcoded values
-- [x] No redundant configuration
-- [x] One cleanup recommendation (context_path)
----
-## Next Steps
-1. **Define missing variables** - Add explicit YAML definitions or document as config-pulled variables
-2. **Standardize variable syntax** - Change `{project_root}` to `{project-root}`
-3. **Remove context_path** - Clean up unused variable
-4. **Re-run audit** - Verify improvements after fixes
----
-## Additional Notes
-### Strengths
-1. **Comprehensive Workflow Logic:** The dev-story workflow is well-thought-out with proper error handling, validation gates, and iterative execution
-2. **Config Integration:** Excellent use of config variables for user personalization and output management
-3. **Clear Documentation:** Instructions are detailed with specific HALT conditions and validation checkpoints
-4. **Proper Web Bundle Setting:** Correctly identifies this as a local-only workflow with web_bundle: false
-5. **Step Flow:** Excellent use of anchors, goto, and conditional checks for complex flow control
-### Workflow Purpose
-This workflow executes user stories by:
-- Finding ready-for-dev stories from sprint status
-- Implementing tasks and subtasks incrementally
-- Writing comprehensive tests
-- Validating against acceptance criteria
-- Updating story status through sprint lifecycle
-- Supporting different user skill levels with adaptive communication
-The workflow is a critical part of the BMM implementation phase and shows mature design patterns.
----
-**Audit Complete** - Generated by audit-workflow v1.0
-**Pass Rate:** 89% (62 passed / 70 total checks)
-**Recommendation:** Good - Minor fixes needed
-The dev-story workflow is production-ready with minor improvements recommended. The issues identified are primarily documentation and consistency improvements rather than functional problems.

package/src/modules/bmm/workflows/4-implementation/dev-story/README.md DELETED Viewed

@@ -1,206 +0,0 @@
-# Dev Story Workflow
-The dev-story workflow is where v6's just-in-time context approach delivers its primary value, enabling the Developer (DEV) agent to implement stories with expert-level guidance injected directly into their context. This workflow is run EXCLUSIVELY by the DEV agent and operates on a single story that has been prepared by the SM through create-story and enhanced with story-context. The DEV loads both the story specification and the dynamically-generated story context XML, then proceeds through implementation with the combined knowledge of requirements and domain-specific expertise.
-The workflow operates with two critical inputs: the story file (created by SM's create-story) containing acceptance criteria, tasks, and requirements; and the story-context XML (generated by SM's story-context) providing just-in-time expertise injection tailored to the story's technical needs. This dual-input approach ensures the developer has both the "what" (from the story) and the "how" (from the context) needed for successful implementation. The workflow iterates through tasks sequentially, implementing code, writing tests, and updating the story document's allowed sections until all tasks are complete.
-A critical aspect of v6 flow is that dev-story may be run multiple times for the same story. Initially run to implement the story, it may be run again after code-review identifies issues that need correction. The workflow intelligently resumes from incomplete tasks, making it ideal for both initial implementation and post-review fixes. The DEV agent maintains strict boundaries on what can be modified in the story file—only Tasks/Subtasks checkboxes, Dev Agent Record, File List, Change Log, and Status may be updated, preserving the story's requirements integrity.
-## Usage
-```bash
-# Developer implements the story with injected context
-bmad dev *develop
-# Or if returning to fix review issues
-bmad dev *develop  # Will resume from incomplete tasks
-```
-The DEV runs this workflow:
-- After SM completes both create-story and story-context
-- When a story status is "Draft" or "Approved" (ready for development)
-- After code-review identifies issues requiring fixes
-- To resume work on a partially completed story
-## Inputs
-**Required Files:**
-- **Story Document** (`{story_dir}/story-{epic}.{story}.md`): Complete specification including:
-  - User story statement
-  - Acceptance criteria (immutable during dev)
-  - Tasks and subtasks (checkable during implementation)
-  - Dev Notes section (for context and guidance)
-  - Status field (Draft → In Progress → Ready for Review)
-- **Story Context XML** (`{story_dir}/story-{epic}.{story}-context.xml`): Domain expertise including:
-  - Technical patterns and best practices
-  - Gotchas and common pitfalls
-  - Testing strategies
-  - Relevant code references
-  - Architecture constraints
-**Configuration:**
-- `dev_story_location`: Directory containing story files (from bmm/config.yaml)
-- `story_selection_limit`: Number of recent stories to show (default: 10)
-- `run_tests_command`: Test command (default: auto-detected)
-- `strict`: Whether to halt on test failures (default: true)
-## Outputs
-**Code Implementation:**
-- Production code satisfying acceptance criteria
-- Unit, integration, and E2E tests as appropriate
-- Documentation updates
-- Migration scripts if needed
-**Story File Updates (allowed sections only):**
-- **Tasks/Subtasks**: Checkboxes marked complete as work progresses
-- **Dev Agent Record**: Debug log and completion notes
-- **File List**: All files created or modified
-- **Change Log**: Summary of implementation changes
-- **Status**: Updated to "Ready for Review" when complete
-**Validation:**
-- All tests passing (existing + new)
-- Acceptance criteria verified
-- Code quality checks passed
-- No regression in existing functionality
-## Key Features
-**Story-Context Integration**: The workflow loads and leverages the story-context XML throughout implementation, providing expert guidance without cluttering the main conversation. This ensures best practices are followed while maintaining developer autonomy.
-**Task-by-Task Iteration**: Implements one task at a time, marking completion before moving to the next. This granular approach enables progress tracking and clean resumption if interrupted or after review feedback.
-**Strict File Boundaries**: Only specific sections of the story file may be modified, preserving requirement integrity. The story's acceptance criteria, main description, and other planning sections remain immutable during development.
-**Test-Driven Approach**: For each task, the workflow emphasizes writing tests that verify acceptance criteria before or alongside implementation, ensuring requirements are actually met.
-**Resumable Implementation**: If the workflow is run again on a story with incomplete tasks (e.g., after code-review finds issues), it intelligently resumes from where it left off rather than starting over.
-## Integration with v6 Flow
-The dev-story workflow is step 3 in the v6 implementation cycle:
-1. SM: create-story (generates the story specification)
-2. SM: story-context (adds JIT technical expertise)
-3. **DEV: dev-story** ← You are here (initial implementation)
-4. DEV/SR: code-review (validates completion)
-5. If issues found: **DEV: dev-story** ← May return here for fixes
-6. After epic: retrospective (captures learnings)
-This workflow may be executed multiple times for the same story as part of the review-fix cycle. Each execution picks up from incomplete tasks, making it efficient for iterative improvement.
-## Workflow Process
-### Phase 1: Story Selection
-- If `story_path` provided: Use that story directly
-- Otherwise: List recent stories from `dev_story_location`
-- Parse story structure and validate format
-- Load corresponding story-context XML
-### Phase 2: Task Implementation Loop
-For each incomplete task:
-1. **Plan**: Log approach in Dev Agent Record
-2. **Implement**: Write code following story-context guidance
-3. **Test**: Create tests verifying acceptance criteria
-4. **Validate**: Run tests and quality checks
-5. **Update**: Mark task complete, update File List
-### Phase 3: Completion
-- Verify all tasks completed
-- Run full test suite
-- Update Status to "Ready for Review"
-- Add completion notes to Dev Agent Record
-## Story File Structure
-The workflow expects stories with this structure:
-```markdown
-# Story {epic}.{story}: {Title}
-**Status**: Draft|In Progress|Ready for Review|Done
-**Epic**: {epic_number}
-**Estimated Effort**: {estimate}
-## Story
-As a {role}, I want to {action} so that {benefit}
-## Acceptance Criteria
-- [ ] AC1...
-- [ ] AC2...
-## Tasks and Subtasks
-- [ ] Task 1
-  - [ ] Subtask 1.1
-- [ ] Task 2
-## Dev Notes
-{Context and guidance from story creation}
-## Dev Agent Record
-### Debug Log
-{Implementation notes added during development}
-### Completion Notes
-{Summary added when complete}
-## File List
-{Files created/modified}
-## Change Log
-{Implementation summary}
-```
-## Best Practices
-**Load Context First**: Always ensure the story-context XML is loaded at the start. This provides the expert guidance needed throughout implementation.
-**Follow Task Order**: Implement tasks in the order listed. Dependencies are typically structured in the task sequence.
-**Test Each Task**: Don't wait until the end to write tests. Test each task as you complete it to ensure it meets acceptance criteria.
-**Update Incrementally**: Update the story file after each task completion rather than batching updates at the end.
-**Respect Boundaries**: Never modify acceptance criteria or story description. If they seem wrong, that's a code-review or correct-course issue, not a dev-story fix.
-**Use Context Guidance**: Actively reference the story-context for patterns, gotchas, and best practices. It's there to help you succeed.
-## Troubleshooting
-**Story Not Found**: Ensure story exists in `dev_story_location` and follows naming pattern `story-{epic}.{story}.md`
-**Context XML Missing**: The story-context workflow must be run first. Check for `story-{epic}.{story}-context.xml`
-**Tests Failing**: If strict mode is on, the workflow halts. Fix tests before continuing or set strict=false for development iteration.
-**Can't Modify Story Section**: Remember only Tasks, Dev Agent Record, File List, Change Log, and Status can be modified. Other sections are immutable.
-**Resuming After Review**: If code-review found issues, the workflow automatically picks up from incomplete tasks when run again.
-## Related Workflows
-- **create-story**: Creates the story specification (run by SM)
-- **story-context**: Generates the context XML (run by SM)
-- **code-review**: Validates implementation (run by SR/DEV)
-- **correct-course**: Handles major issues or scope changes (run by SM)