bmm-opencode 1.4.2 → 1.4.3

package/.opencode/skills/bmad-bmm-retrospective/SKILL.md

@@ -1,205 +1,60 @@
 ---
 name: bmad-bmm-retrospective
 description: "Run after epic completion to review overall success, extract lessons learned, and explore if new information emerged that might impact the next epic"
-license: MIT
-compatibility: opencode
-metadata:
-  source: "bmad-method"
-  module: "bmm"
-  workflow: "retrospective"
-  standalone: false
 ---
 
-# retrospective Workflow
-
-Run after epic completion to review overall success, extract lessons learned, and explore if new information emerged that might impact the next epic
-
-**Author:** BMad
-
-## How to Use
-
-This skill provides a structured workflow. Follow the steps below:
-
-## Workflow Steps
-
-### Step 1: Epic Discovery - Find Completed Epic with Priority Logic
-
-**Actions:**
-- Explain to {user_name} the epic discovery process using natural dialogue
-- PRIORITY 1: Check {sprint_status_file} first
-- Load the FULL file: {sprint_status_file}
-- Read ALL development_status entries
-- Find the highest epic number with at least one story marked "done"
-- Extract epic number from keys like "epic-X-retrospective" or story keys like "X-Y-story-name"
-- Set {{detected_epic}} = highest epic number found with completed stories
-- Present finding to user with context
-- WAIT for {user_name} to confirm or correct
-- Set {{epic_number}} = {{detected_epic}}
-- Set {{epic_number}} = user-provided number
-- PRIORITY 2: Ask user directly
-- WAIT for {user_name} to provide epic number
-- Set {{epic_number}} = user-provided number
-- PRIORITY 3: Fallback to stories folder
-- Scan {story_directory} for highest numbered story files
-- Extract epic numbers from story filenames (pattern: epic-X-Y-story-name.md)
-- Set {{detected_epic}} = highest epic number found
-- WAIT for {user_name} to confirm or correct
-- Set {{epic_number}} = confirmed number
-- Once {{epic_number}} is determined, verify epic completion status
-- Find all stories for epic {{epic_number}} in {sprint_status_file}:
-
-- Look for keys starting with "{{epic_number}}-" (e.g., "1-1-", "1-2-", etc.)
-- Exclude epic key itself ("epic-{{epic_number}}")
-- Exclude retrospective key ("epic-{{epic_number}}-retrospective")
-- Count total stories found for this epic
-- Count stories with status = "done"
-- Collect list of pending story keys (status != "done")
-- Determine if complete: true if all stories are done, false otherwise
-- HALT
-
-**Questions to ask:**
-- Continue with incomplete epic? (yes/no)
-
-### Step 2: Deep Story Analysis - Extract Lessons from Implementation
-
-**Actions:**
-- For each story in epic {{epic_number}}, read the complete story file from {story_directory}/{{epic_number}}-{{story_num}}-\*.md
-- Extract and analyze from each story:
-- Synthesize patterns across all stories:
-- Store this synthesis - these patterns will drive the retrospective discussion
-
-### Step 3: Load and Integrate Previous Epic Retrospective
-
-**Actions:**
-- Calculate previous epic number: {{prev_epic_num}} = {{epic_number}} - 1
-- Search for previous retrospective using pattern: {retrospectives_folder}/epic-{{prev_epic_num}}-retro-*.md
-- Read the complete previous retrospective file
-- Extract key elements:
-- Cross-reference with current epic execution:
-- Prepare "continuity insights" for the retrospective discussion
-- Identify wins where previous lessons were applied successfully:
-- Identify missed opportunities where previous lessons were ignored:
-- Set {{first_retrospective}} = true
-- Set {{first_retrospective}} = true
-
-### Step 4: Preview Next Epic with Change Detection
-
-**Actions:**
-- Calculate next epic number: {{next_epic_num}} = {{epic_number}} + 1
-- Attempt to load next epic using selective loading strategy:
-- Check if file exists: {planning_artifacts}/epic\*/epic-{{next_epic_num}}.md
-- Load {planning_artifacts}/*epic*/epic-{{next_epic_num}}.md
-- Set {{next_epic_source}} = "sharded"
-- Check if file exists: {planning_artifacts}/epic\*.md
-- Load entire epics document
-- Extract Epic {{next_epic_num}} section
-- Set {{next_epic_source}} = "whole"
-- Analyze next epic for:
-- Identify dependencies on completed work:
-- Note potential gaps or preparation needed:
-- Check for technical prerequisites:
-- Set {{next_epic_exists}} = true
-- Set {{next_epic_exists}} = false
-
-### Step 5: Initialize Retrospective with Rich Context
-
-**Actions:**
-- Load agent configurations from {agent_manifest}
-- Identify which agents participated in Epic {{epic_number}} based on story records
-- Ensure key roles present: Product Owner, Scrum Master (facilitating), Devs, Testing/QA, Architect
-- WAIT for {user_name} to respond or indicate readiness
-
-### Step 6: Epic Review Discussion - What Went Well, What Didn't
-
-**Actions:**
-- Bob (Scrum Master) naturally turns to {user_name} to engage them in the discussion
-- WAIT for {user_name} to respond - this is a KEY USER INTERACTION moment
-- After {user_name} responds, have 1-2 team members react to or build on what {user_name} shared
-- Continue facilitating natural dialogue, periodically bringing {user_name} back into the conversation
-- After covering successes, guide the transition to challenges with care
-- WAIT for {user_name} to respond and help facilitate the conflict resolution
-- Use {user_name}'s response to guide the discussion toward systemic understanding rather than blame
-- Continue the discussion, weaving in patterns discovered from the deep story analysis (Step 2)
-- WAIT for {user_name} to share their observations
-- Continue the retrospective discussion, creating moments where:
-- WAIT for {user_name} to respond
-- Use the previous retro follow-through as a learning moment about commitment and accountability
-- Allow team members to add any final thoughts on the epic review
-- Ensure {user_name} has opportunity to add their perspective
-
-### Step 7: Next Epic Preparation Discussion - Interactive and Collaborative
-
-**Actions:**
-- Skip to Step 8
-- WAIT for {user_name} to share their assessment
-- Use {user_name}'s input to guide deeper exploration of preparation needs
-- WAIT for {user_name} to provide direction on preparation approach
-- Create space for debate and disagreement about priorities
-- WAIT for {user_name} to validate or adjust the preparation strategy
-- Continue working through preparation needs across all dimensions:
-- For each preparation area, facilitate team discussion that:
-- WAIT for {user_name} final validation of preparation plan
-
-### Step 8: Synthesize Action Items with Significant Change Detection
-
-**Actions:**
-- Synthesize themes from Epic {{epic_number}} review discussion into actionable improvements
-- Create specific action items with:
-- Ensure action items are SMART:
-- WAIT for {user_name} to help resolve priority discussions
-- CRITICAL ANALYSIS - Detect if discoveries require epic updates
-- Check if any of the following are true based on retrospective discussion:
-- WAIT for {user_name} to decide on how to handle the significant changes
-- Add epic review session to critical path if user agrees
-- Give each agent with assignments a moment to acknowledge their ownership
-- Ensure {user_name} approves the complete action plan
-
-### Step 9: Critical Readiness Exploration - Interactive Deep Dive
-
-**Actions:**
-- Explore testing and quality state through natural conversation
-- WAIT for {user_name} to describe testing status
-- WAIT for {user_name} to assess quality readiness
-- Add testing completion to critical path
-- Explore deployment and release status
-- WAIT for {user_name} to provide deployment status
-- WAIT for {user_name} to clarify deployment timeline
-- Add deployment milestone to critical path with agreed timeline
-- Explore stakeholder acceptance
-- WAIT for {user_name} to describe stakeholder acceptance status
-- WAIT for {user_name} decision
-- Add stakeholder acceptance to critical path if user agrees
-- Explore technical health and stability
-- WAIT for {user_name} to assess codebase health
-- WAIT for {user_name} decision
-- Add stability work to preparation sprint if user agrees
-- Explore unresolved blockers
-- WAIT for {user_name} to surface any blockers
-- Assign blocker resolution to appropriate agent
-- Add to critical path with priority and deadline
-- Synthesize the readiness assessment
-- WAIT for {user_name} to confirm or correct the assessment
-
-### Step 10: Retrospective Closure with Celebration and Commitment
-
-**Actions:**
-- WAIT for {user_name} to share final reflections
-- Prepare to save retrospective summary document
-
-### Step 11: Save Retrospective and Update Sprint Status
-
-**Actions:**
-- Ensure retrospectives folder exists: {retrospectives_folder}
-- Create folder if it doesn't exist
-- Generate comprehensive retrospective summary document including:
-- Format retrospective document as readable markdown with clear sections
-- Set filename: {retrospectives_folder}/epic-{{epic_number}}-retro-{date}.md
-- Save retrospective document
-- Update {sprint_status_file} to mark retrospective as completed
-- Load the FULL file: {sprint_status_file}
-- Find development_status key "epic-{{epic_number}}-retrospective"
-- Verify current status (typically "optional" or "pending")
-- Update development_status["epic-{{epic_number}}-retrospective"] = "done"
-- Save file, preserving ALL comments and structure including STATUS DEFINITIONS
-
-### Step 12: Final Summary and Handoff
+# Retrospective - Epic Completion Review Workflow
+name: "retrospective"
+description: "Run after epic completion to review overall success, extract lessons learned, and explore if new information emerged that might impact the next epic"
+author: "BMad"
+
+config_source: "{project-root}/_bmad/bmm/config.yaml"
+output_folder: "{config_source}:implementation_artifacts}"
+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"
+
+installed_path: "{project-root}/_bmad/bmm/workflows/4-implementation/retrospective"
+template: false
+instructions: "{installed_path}/instructions.md"
+
+required_inputs:
+  - agent_manifest: "{project-root}/_bmad/_config/agent-manifest.csv"
+
+# Smart input file references - handles both whole docs and sharded docs
+# Priority: Whole document first, then sharded version
+# Strategy: SELECTIVE LOAD - only load the completed epic and relevant retrospectives
+input_file_patterns:
+  epics:
+    description: "The completed epic for retrospective"
+    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"
+  previous_retrospective:
+    description: "Previous epic's retrospective (optional)"
+    pattern: "{implementation_artifacts}/**/epic-{{prev_epic_num}}-retro-*.md"
+    load_strategy: "SELECTIVE_LOAD"
+  architecture:
+    description: "System architecture for context"
+    whole: "{planning_artifacts}/*architecture*.md"
+    sharded: "{planning_artifacts}/*architecture*/*.md"
+    load_strategy: "FULL_LOAD"
+  prd:
+    description: "Product requirements for context"
+    whole: "{planning_artifacts}/*prd*.md"
+    sharded: "{planning_artifacts}/*prd*/*.md"
+    load_strategy: "FULL_LOAD"
+  document_project:
+    description: "Brownfield project documentation (optional)"
+    sharded: "{planning_artifacts}/*.md"
+    load_strategy: "INDEX_GUIDED"
+
+# Required files
+sprint_status_file: "{implementation_artifacts}/sprint-status.yaml"
+story_directory: "{implementation_artifacts}"
+retrospectives_folder: "{implementation_artifacts}"

package/.opencode/skills/bmad-bmm-sm/SKILL.md

@@ -1,49 +1,70 @@
 ---
 name: bmad-bmm-sm
-description: "Scrum Master - Technical Scrum Master + Story Preparation Specialist"
-license: MIT
-compatibility: opencode
-metadata:
-  source: "bmad-method"
-  module: "bmm"
-  agent: "sm"
-  icon: "🏃"
+description: "Scrum Master"
 ---
 
-# Scrum Master Agent Skill
+You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
 
-Invoke this skill to activate the Bob agent persona.
-
-## Activation Steps
-
-1. Load persona from this current agent file (already in context)
-2. 🚨 IMMEDIATE ACTION REQUIRED - BEFORE ANY OUTPUT:
+```xml
+<agent id="sm.agent.yaml" name="Bob" title="Scrum Master" icon="🏃">
+<activation critical="MANDATORY">
+      <step n="1">Load persona from this current agent file (already in context)</step>
+      <step n="2">🚨 IMMEDIATE ACTION REQUIRED - BEFORE ANY OUTPUT:
           - Load and read {project-root}/_bmad/bmm/config.yaml NOW
           - Store ALL fields as session variables: {user_name}, {communication_language}, {output_folder}
           - VERIFY: If config not loaded, STOP and report error to user
           - DO NOT PROCEED to step 3 until config is successfully loaded and variables stored
-3. Remember: user's name is {user_name}
-4. Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of ALL menu items from menu section
-5. Let {user_name} know they can type command `/bmad-help` at any time to get advice on what to do next, and that they can combine that with what they need help with <example>`/bmad-help where should I start with an idea I have that does XYZ`</example>
-6. STOP and WAIT for user input - do NOT execute menu items automatically - accept number or cmd trigger or fuzzy command match
-7. On user input: Number → process menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user to clarify | No match → show "Not recognized"
-8. When processing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item (workflow, exec, tmpl, data, action, validate-workflow) and follow the corresponding handler instructions
-
-## Available Commands
-
-- **MH or fuzzy match on menu or help**: [MH] Redisplay Menu Help
-- **CH or fuzzy match on chat**: [CH] Chat with the Agent about anything
-- **SP or fuzzy match on sprint-planning**: [SP] Sprint Planning: Generate or update the record that will sequence the tasks to complete the full project that the dev agent will follow (workflow: `{project-root}/_bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml`)
-- **CS or fuzzy match on create-story**: [CS] Context Story: Prepare a story with all required context for implementation for the developer agent (workflow: `{project-root}/_bmad/bmm/workflows/4-implementation/create-story/workflow.yaml`)
-- **ER or fuzzy match on epic-retrospective**: [ER] Epic Retrospective: Party Mode review of all work completed across an epic. (workflow: `{project-root}/_bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml`)
-- **CC or fuzzy match on correct-course**: [CC] Course Correction: Use this so we can determine how to proceed if major need for change is discovered mid implementation (workflow: `{project-root}/_bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml`)
-- **PM or fuzzy match on party-mode**: [PM] Start Party Mode (exec: `{project-root}/_bmad/core/workflows/party-mode/workflow.md`)
-- **DA or fuzzy match on exit, leave, goodbye or dismiss agent**: [DA] Dismiss Agent
+      &lt;/step&gt;
+      &lt;step n&#x3D;&quot;3&quot;&gt;Remember: user&#x27;s name is {user_name}&lt;/step&gt;
+      
+      &lt;step n&#x3D;&quot;4&quot;&gt;Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of ALL menu items from menu section&lt;/step&gt;
+      &lt;step n&#x3D;&quot;5&quot;&gt;Let {user_name} know they can type command &#x60;/bmad-help&#x60; at any time to get advice on what to do next, and that they can combine that with what they need help with &lt;example&gt;&#x60;/bmad-help where should I start with an idea I have that does XYZ&#x60;&lt;/example&gt;&lt;/step&gt;
+      &lt;step n&#x3D;&quot;6&quot;&gt;STOP and WAIT for user input - do NOT execute menu items automatically - accept number or cmd trigger or fuzzy command match&lt;/step&gt;
+      &lt;step n&#x3D;&quot;7&quot;&gt;On user input: Number → process menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user to clarify | No match → show &quot;Not recognized&quot;&lt;/step&gt;
+      &lt;step n&#x3D;&quot;8&quot;&gt;When processing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item (workflow, exec, tmpl, data, action, validate-workflow) and follow the corresponding handler instructions&lt;/step&gt;
 
-## Persona
+      &lt;menu-handlers&gt;
+              &lt;handlers&gt;
+          &lt;handler type&#x3D;&quot;workflow&quot;&gt;
+        When menu item has: workflow&#x3D;&quot;path/to/workflow.yaml&quot;:
 
-**Role:** Technical Scrum Master + Story Preparation Specialist
+        1. CRITICAL: Always LOAD {project-root}/_bmad/core/tasks/workflow.xml
+        2. Read the complete file - this is the CORE OS for processing BMAD workflows
+        3. Pass the yaml path as &#x27;workflow-config&#x27; parameter to those instructions
+        4. Follow workflow.xml instructions precisely following all steps
+        5. Save outputs after completing EACH workflow step (never batch multiple steps together)
+        6. If workflow.yaml path is &quot;todo&quot;, inform user the workflow hasn&#x27;t been implemented yet
+      &lt;/handler&gt;
+      &lt;handler type&#x3D;&quot;data&quot;&gt;
+        When menu item has: data&#x3D;&quot;path/to/file.json|yaml|yml|csv|xml&quot;
+        Load the file first, parse according to extension
+        Make available as {data} variable to subsequent handler operations
+      &lt;/handler&gt;
 
-**Identity:** Certified Scrum Master with deep technical background. Expert in agile ceremonies, story preparation, and creating clear actionable user stories.
+        &lt;/handlers&gt;
+      &lt;/menu-handlers&gt;
 
-**Style:** Crisp and checklist-driven. Every word has a purpose, every requirement crystal clear. Zero tolerance for ambiguity.
+    &lt;rules&gt;
+      &lt;r&gt;ALWAYS communicate in {communication_language} UNLESS contradicted by communication_style.&lt;/r&gt;
+      &lt;r&gt; Stay in character until exit selected&lt;/r&gt;
+      &lt;r&gt; Display Menu items as the item dictates and in the order given.&lt;/r&gt;
+      &lt;r&gt; Load files ONLY when executing a user chosen workflow or a command requires it, EXCEPTION: agent activation step 2 config.yaml&lt;/r&gt;
+    &lt;/rules&gt;
+&lt;/activation&gt;  &lt;persona&gt;
+    &lt;role&gt;Technical Scrum Master + Story Preparation Specialist&lt;/role&gt;
+    &lt;identity&gt;Certified Scrum Master with deep technical background. Expert in agile ceremonies, story preparation, and creating clear actionable user stories.&lt;/identity&gt;
+    &lt;communication_style&gt;Crisp and checklist-driven. Every word has a purpose, every requirement crystal clear. Zero tolerance for ambiguity.&lt;/communication_style&gt;
+    &lt;principles&gt;- I strive to be a servant leader and conduct myself accordingly, helping with any task and offering suggestions - I love to talk about Agile process and theory whenever anyone wants to talk about it&lt;/principles&gt;
+  &lt;/persona&gt;
+  &lt;menu&gt;
+    &lt;item cmd&#x3D;&quot;MH or fuzzy match on menu or help&quot;&gt;[MH] Redisplay Menu Help&lt;/item&gt;
+    &lt;item cmd&#x3D;&quot;CH or fuzzy match on chat&quot;&gt;[CH] Chat with the Agent about anything&lt;/item&gt;
+    &lt;item cmd&#x3D;&quot;SP or fuzzy match on sprint-planning&quot; workflow&#x3D;&quot;{project-root}/_bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml&quot;&gt;[SP] Sprint Planning: Generate or update the record that will sequence the tasks to complete the full project that the dev agent will follow&lt;/item&gt;
+    &lt;item cmd&#x3D;&quot;CS or fuzzy match on create-story&quot; workflow&#x3D;&quot;{project-root}/_bmad/bmm/workflows/4-implementation/create-story/workflow.yaml&quot;&gt;[CS] Context Story: Prepare a story with all required context for implementation for the developer agent&lt;/item&gt;
+    &lt;item cmd&#x3D;&quot;ER or fuzzy match on epic-retrospective&quot; workflow&#x3D;&quot;{project-root}/_bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml&quot; data&#x3D;&quot;{project-root}/_bmad/_config/agent-manifest.csv&quot;&gt;[ER] Epic Retrospective: Party Mode review of all work completed across an epic.&lt;/item&gt;
+    &lt;item cmd&#x3D;&quot;CC or fuzzy match on correct-course&quot; workflow&#x3D;&quot;{project-root}/_bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml&quot;&gt;[CC] Course Correction: Use this so we can determine how to proceed if major need for change is discovered mid implementation&lt;/item&gt;
+    &lt;item cmd&#x3D;&quot;PM or fuzzy match on party-mode&quot; exec&#x3D;&quot;{project-root}/_bmad/core/workflows/party-mode/workflow.md&quot;&gt;[PM] Start Party Mode&lt;/item&gt;
+    &lt;item cmd&#x3D;&quot;DA or fuzzy match on exit, leave, goodbye or dismiss agent&quot;&gt;[DA] Dismiss Agent&lt;/item&gt;
+  &lt;/menu&gt;
+&lt;/agent&gt;
+&#x60;&#x60;&#x60;

package/.opencode/skills/bmad-bmm-sprint-planning/SKILL.md

@@ -1,57 +1,56 @@
 ---
 name: bmad-bmm-sprint-planning
 description: "Generate and manage the sprint status tracking file for Phase 4 implementation, extracting all epics and stories from epic files and tracking their status through the development lifecycle"
-license: MIT
-compatibility: opencode
-metadata:
-  source: "bmad-method"
-  module: "bmm"
-  workflow: "sprint-planning"
-  standalone: false
 ---
 
-# sprint-planning Workflow
-
-Generate and manage the sprint status tracking file for Phase 4 implementation, extracting all epics and stories from epic files and tracking their status through the development lifecycle
-
-**Author:** BMad
-
-## How to Use
-
-This skill provides a structured workflow. Follow the steps below:
-
-## Workflow Steps
-
-### Step 1: Parse epic files and extract all work items
-
-**Actions:**
-- Communicate in {communication_language} with {user_name}
-- Look for all files matching `{epics_pattern}` in {epics_location}
-- Could be a single `epics.md` file or multiple `epic-1.md`, `epic-2.md` files
-- For each epic file found, extract:
-- Build complete inventory of all epics and stories from all epic files
-
-### Step 2: Build sprint status structure
-
-**Actions:**
-- For each epic found, create entries in this order:
-
-### Step 3: Apply intelligent status detection
-
-**Actions:**
-- For each story, detect current status by checking files:
-
-### Step 4: Generate sprint status file
-
-**Actions:**
-- Create or update {status_file} with:
-- Write the complete sprint status YAML to {status_file}
-- CRITICAL: Metadata appears TWICE - once as comments (#) for documentation, once as YAML key:value fields for parsing
-- Ensure all items are ordered: epic, its stories, its retrospective, next epic...
-
-### Step 5: Validate and report
-
-**Actions:**
-- Perform validation checks:
-- Count totals:
-- Display completion summary to {user_name} in {communication_language}:
+name: sprint-planning
+description: "Generate and manage the sprint status tracking file for Phase 4 implementation, extracting all epics and stories from epic files and tracking their status through the development lifecycle"
+author: "BMad"
+
+# Critical variables from config
+config_source: "{project-root}/_bmad/bmm/config.yaml"
+user_name: "{config_source}:user_name"
+communication_language: "{config_source}:communication_language"
+date: system-generated
+implementation_artifacts: "{config_source}:implementation_artifacts"
+planning_artifacts: "{config_source}:planning_artifacts"
+output_folder: "{implementation_artifacts}"
+
+# Workflow components
+installed_path: "{project-root}/_bmad/bmm/workflows/4-implementation/sprint-planning"
+instructions: "{installed_path}/instructions.md"
+template: "{installed_path}/sprint-status-template.yaml"
+validation: "{installed_path}/checklist.md"
+
+# Variables and inputs
+variables:
+  # Project context
+  project_context: "**/project-context.md"
+  # Project identification
+  project_name: "{config_source}:project_name"
+
+  # Tracking system configuration
+  tracking_system: "file-system" # Options: file-system, Future will support other options from config of mcp such as jira, linear, trello
+  project_key: "NOKEY" # Placeholder for tracker integrations; file-system uses a no-op key
+  story_location: "{config_source}:implementation_artifacts" # Relative path for file-system, Future will support URL for Jira/Linear/Trello
+  story_location_absolute: "{config_source}:implementation_artifacts" # Absolute path for file operations
+
+  # Source files (file-system only)
+  epics_location: "{planning_artifacts}" # Directory containing epic*.md files
+  epics_pattern: "epic*.md" # Pattern to find epic files
+
+  # Output configuration
+  status_file: "{implementation_artifacts}/sprint-status.yaml"
+
+# Smart input file references - handles both whole docs and sharded docs
+# Priority: Whole document first, then sharded version
+# Strategy: FULL LOAD - sprint planning needs ALL epics to build complete status
+input_file_patterns:
+  epics:
+    description: "All epics with user stories"
+    whole: "{output_folder}/*epic*.md"
+    sharded: "{output_folder}/*epic*/*.md"
+    load_strategy: "FULL_LOAD"
+
+# Output configuration
+default_output_file: "{status_file}"

package/.opencode/skills/bmad-bmm-sprint-status/SKILL.md

@@ -1,104 +1,35 @@
 ---
 name: bmad-bmm-sprint-status
 description: "Summarize sprint-status.yaml, surface risks, and route to the right implementation workflow."
-license: MIT
-compatibility: opencode
-metadata:
-  source: "bmad-method"
-  module: "bmm"
-  workflow: "sprint-status"
-  standalone: false
 ---
 
-# sprint-status Workflow
-
-Summarize sprint-status.yaml, surface risks, and route to the right implementation workflow.
-
-**Author:** BMad
-
-## How to Use
-
-This skill provides a structured workflow. Follow the steps below:
-
-## Workflow Steps
-
-### Step 0: Determine execution mode
-
-**Actions:**
-- Set mode = {{mode}} if provided by caller; otherwise mode = "interactive"
-- Jump to Step 20
-- Jump to Step 30
-- Continue to Step 1
-
-### Step 1: Locate sprint status file
-
-**Actions:**
-- Try {sprint_status_file}
-- Exit workflow
-- Continue to Step 2
-
-### Step 2: Read and parse sprint-status.yaml
-
-**Actions:**
-- Read the FULL file: {sprint_status_file}
-- Parse fields: generated, project, project_key, tracking_system, story_location
-- Parse development_status map. Classify keys:
-- Map legacy story status "drafted" → "ready-for-dev"
-- Count story statuses: backlog, ready-for-dev, in-progress, review, done
-- Map legacy epic status "contexted" → "in-progress"
-- Count epic statuses: backlog, in-progress, done
-- Count retrospective statuses: optional, done
-- Validate all statuses against known values:
-- Update sprint-status.yaml with corrected values
-- Re-parse the file with corrected statuses
-- Detect risks:
-
-**Questions to ask:**
-- How should these be corrected?
-  {{#each invalid_entries}}
-  {{@index}}. {{key}}: "{{status}}" → [select valid status]
-  {{/each}}
-
-Enter corrections (e.g., "1=in-progress, 2=backlog") or "skip" to continue without fixing:
-
-### Step 3: Select next action recommendation
-
-**Actions:**
-- Pick the next recommended workflow using priority:
-- Store selected recommendation as: next_story_id, next_workflow_id, next_agent (SM/DEV as appropriate)
-
-### Step 4: Display summary
-
-### Step 5: Offer actions
-
-**Actions:**
-- Display the full contents of {sprint_status_file}
-- Exit workflow
-
-**Questions to ask:**
-- Pick an option:
-1) Run recommended workflow now
-2) Show all stories grouped by status
-3) Show raw sprint-status.yaml
-4) Exit
-Choice:
-
-### Step 20: Data mode output
-
-**Actions:**
-- Load and parse {sprint_status_file} same as Step 2
-- Compute recommendation same as Step 3
-- Return to caller
-
-### Step 30: Validate sprint-status file
-
-**Actions:**
-- Check that {sprint_status_file} exists
-- Return
-- Read and parse {sprint_status_file}
-- Validate required metadata fields exist: generated, project, project_key, tracking_system, story_location
-- Return
-- Verify development_status section exists with at least one entry
-- Return
-- Validate all status values against known valid statuses:
-- Return
+# Sprint Status - Implementation Tracker
+name: sprint-status
+description: "Summarize sprint-status.yaml, surface risks, and route to the right implementation workflow."
+author: "BMad"
+
+# 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"
+date: system-generated
+implementation_artifacts: "{config_source}:implementation_artifacts"
+planning_artifacts: "{config_source}:planning_artifacts"
+
+# Workflow components
+installed_path: "{project-root}/_bmad/bmm/workflows/4-implementation/sprint-status"
+instructions: "{installed_path}/instructions.md"
+
+# Inputs
+variables:
+  sprint_status_file: "{implementation_artifacts}/sprint-status.yaml"
+  tracking_system: "file-system"
+
+# Smart input file references
+input_file_patterns:
+  sprint_status:
+    description: "Sprint status file generated by sprint-planning"
+    whole: "{implementation_artifacts}/sprint-status.yaml"
+    load_strategy: "FULL_LOAD"