bmm-opencode 1.4.2 → 1.4.3

package/.opencode/skills/bmad-bmm-code-review/SKILL.md

@@ -1,21 +1,53 @@
 ---
 name: bmad-bmm-code-review
-description: "Perform an ADVERSARIAL Senior Developer code review that finds 3-10 specific problems in every story. Challenges everything: code quality, test coverage, architecture compliance, security, performance. NEVER accepts `looks good` - must find minimum issues and can auto-fix with user approval."
-license: MIT
-compatibility: opencode
-metadata:
-  source: "bmad-method"
-  module: "bmm"
-  workflow: "code-review"
-  standalone: false
+description: "Perform an ADVERSARIAL Senior Developer code review that finds 3-10 specific problems in every story. Challenges everything: code quality, test coverage, architecture compliance, security, performance. NEVER accepts `looks good` - must find minimum issues and can auto-fix with user approval."
 ---
 
-# code-review Workflow
+# Review Story Workflow
+name: code-review
+description: "Perform an ADVERSARIAL Senior Developer code review that finds 3-10 specific problems in every story. Challenges everything: code quality, test coverage, architecture compliance, security, performance. NEVER accepts `looks good` - must find minimum issues and can auto-fix with user approval."
+author: "BMad"
 
-Perform an ADVERSARIAL Senior Developer code review that finds 3-10 specific problems in every story. Challenges everything: code quality, test coverage, architecture compliance, security, performance. NEVER accepts `looks good` - must find minimum issues and can auto-fix with user approval.
+# Critical variables from config
+config_source: "{project-root}/_bmad/bmm/config.yaml"
+user_name: "{config_source}:user_name"
+communication_language: "{config_source}:communication_language"
+user_skill_level: "{config_source}:user_skill_level"
+document_output_language: "{config_source}:document_output_language"
+date: system-generated
+planning_artifacts: "{config_source}:planning_artifacts"
+implementation_artifacts: "{config_source}:implementation_artifacts"
+output_folder: "{implementation_artifacts}"
+sprint_status: "{implementation_artifacts}/sprint-status.yaml"
 
-**Author:** BMad
+# Workflow components
+installed_path: "{project-root}/_bmad/bmm/workflows/4-implementation/code-review"
+instructions: "{installed_path}/instructions.xml"
+validation: "{installed_path}/checklist.md"
+template: false
 
-## How to Use
+variables:
+  # Project context
+  project_context: "**/project-context.md"
+  story_dir: "{implementation_artifacts}"
 
-This skill provides a structured workflow. Follow the steps below:
+# Smart input file references - handles both whole docs and sharded docs
+# Priority: Whole document first, then sharded version
+# Strategy: SELECTIVE LOAD - only load the specific epic needed for this story review
+input_file_patterns:
+  architecture:
+    description: "System architecture for review context"
+    whole: "{planning_artifacts}/*architecture*.md"
+    sharded: "{planning_artifacts}/*architecture*/*.md"
+    load_strategy: "FULL_LOAD"
+  ux_design:
+    description: "UX design specification (if UI review)"
+    whole: "{planning_artifacts}/*ux*.md"
+    sharded: "{planning_artifacts}/*ux*/*.md"
+    load_strategy: "FULL_LOAD"
+  epics:
+    description: "Epic containing story being reviewed"
+    whole: "{planning_artifacts}/*epic*.md"
+    sharded_index: "{planning_artifacts}/*epic*/index.md"
+    sharded_single: "{planning_artifacts}/*epic*/epic-{{epic_num}}.md"
+    load_strategy: "SELECTIVE_LOAD"

package/.opencode/skills/bmad-bmm-correct-course/SKILL.md

@@ -1,99 +1,61 @@
 ---
 name: bmad-bmm-correct-course
 description: "Navigate significant changes during sprint execution by analyzing impact, proposing solutions, and routing for implementation"
-license: MIT
-compatibility: opencode
-metadata:
-  source: "bmad-method"
-  module: "bmm"
-  workflow: "correct-course"
-  standalone: false
 ---
 
-# correct-course Workflow
-
-Navigate significant changes during sprint execution by analyzing impact, proposing solutions, and routing for implementation
-
-**Author:** BMad Method
-
-## How to Use
-
-This skill provides a structured workflow. Follow the steps below:
-
-## Workflow Steps
-
-### Step 1: Initialize Change Navigation
-
-**Actions:**
-- Confirm change trigger and gather user description of the issue
-- Ask: "What specific issue or change has been identified that requires navigation?"
-- Verify access to required project documents:
-- Ask user for mode preference:
-- Store mode selection for use throughout workflow
-
-### Step 2: Execute Change Analysis Checklist
-
-**Actions:**
-- Read fully and follow the systematic analysis from: {checklist}
-- Work through each checklist section interactively with the user
-- Record status for each checklist item:
-- Maintain running notes of findings and impacts discovered
-- Present checklist progress after each major section
-
-### Step 3: Draft Specific Change Proposals
-
-**Actions:**
-- Based on checklist findings, create explicit edit proposals for each identified artifact
-- For Story changes:
-- For PRD modifications:
-- For Architecture changes:
-- For UI/UX specification updates:
-- Present each edit proposal individually
-- Iterate on each proposal based on user feedback
-
-**Questions to ask:**
-- Review and refine this change? Options: Approve [a], Edit [e], Skip [s]
-
-### Step 4: Generate Sprint Change Proposal
-
-**Actions:**
-- Compile comprehensive Sprint Change Proposal document with following sections:
-- Section 1: Issue Summary
-- Section 2: Impact Analysis
-- Section 3: Recommended Approach
-- Section 4: Detailed Change Proposals
-- Section 5: Implementation Handoff
-- Present complete Sprint Change Proposal to user
-- Write Sprint Change Proposal document to {default_output_file}
-
-**Questions to ask:**
-- Review complete proposal. Continue [c] or Edit [e]?
-
-### Step 5: Finalize and Route for Implementation
-
-**Actions:**
-- Get explicit user approval for complete proposal
-- Gather specific feedback on what needs adjustment
-- Return to appropriate step to address concerns
-- Finalize Sprint Change Proposal document
-- Determine change scope classification:
-- Provide appropriate handoff based on scope:
-- Route to: Development team for direct implementation
-- Deliverables: Finalized edit proposals and implementation tasks
-- Route to: Product Owner / Scrum Master agents
-- Deliverables: Sprint Change Proposal + backlog reorganization plan
-- Route to: Product Manager / Solution Architect
-- Deliverables: Complete Sprint Change Proposal + escalation notice
-- Confirm handoff completion and next steps with user
-- Document handoff in workflow execution log
-
-**Questions to ask:**
-- Do you approve this Sprint Change Proposal for implementation? (yes/no/revise)
-
-### Step 6: Workflow Completion
-
-**Actions:**
-- Summarize workflow execution:
-- Confirm all deliverables produced:
-- Report workflow completion to user with personalized message: "✅ Correct Course workflow complete, {user_name}!"
-- Remind user of success criteria and next steps for implementation team
+# Correct Course - Sprint Change Management Workflow
+name: "correct-course"
+description: "Navigate significant changes during sprint execution by analyzing impact, proposing solutions, and routing for implementation"
+author: "BMad Method"
+
+config_source: "{project-root}/_bmad/bmm/config.yaml"
+user_name: "{config_source}:user_name"
+communication_language: "{config_source}:communication_language"
+user_skill_level: "{config_source}:user_skill_level"
+document_output_language: "{config_source}:document_output_language"
+date: system-generated
+implementation_artifacts: "{config_source}:implementation_artifacts"
+planning_artifacts: "{config_source}:planning_artifacts"
+project_knowledge: "{config_source}:project_knowledge"
+output_folder: "{implementation_artifacts}"
+sprint_status: "{implementation_artifacts}/sprint-status.yaml"
+
+# Smart input file references - handles both whole docs and sharded docs
+# Priority: Whole document first, then sharded version
+# Strategy: Load project context for impact analysis
+input_file_patterns:
+  prd:
+    description: "Product requirements for impact analysis"
+    whole: "{planning_artifacts}/*prd*.md"
+    sharded: "{planning_artifacts}/*prd*/*.md"
+    load_strategy: "FULL_LOAD"
+  epics:
+    description: "All epics to analyze change impact"
+    whole: "{planning_artifacts}/*epic*.md"
+    sharded: "{planning_artifacts}/*epic*/*.md"
+    load_strategy: "FULL_LOAD"
+  architecture:
+    description: "System architecture and decisions"
+    whole: "{planning_artifacts}/*architecture*.md"
+    sharded: "{planning_artifacts}/*architecture*/*.md"
+    load_strategy: "FULL_LOAD"
+  ux_design:
+    description: "UX design specification (if UI impacts)"
+    whole: "{planning_artifacts}/*ux*.md"
+    sharded: "{planning_artifacts}/*ux*/*.md"
+    load_strategy: "FULL_LOAD"
+  tech_spec:
+    description: "Technical specification"
+    whole: "{planning_artifacts}/*tech-spec*.md"
+    load_strategy: "FULL_LOAD"
+  document_project:
+    description: "Brownfield project documentation (optional)"
+    sharded: "{project_knowledge}/index.md"
+    load_strategy: "INDEX_GUIDED"
+
+installed_path: "{project-root}/_bmad/bmm/workflows/4-implementation/correct-course"
+template: false
+instructions: "{installed_path}/instructions.md"
+validation: "{installed_path}/checklist.md"
+checklist: "{installed_path}/checklist.md"
+default_output_file: "{planning_artifacts}/sprint-change-proposal-{date}.md"