Merge remote-tracking branch 'upstream/main' into phase1-md-workflows-clean

# Conflicts:
#	src/bmm/workflows/4-implementation/correct-course/workflow.yaml
#	src/bmm/workflows/4-implementation/retrospective/workflow.yaml
#	src/bmm/workflows/4-implementation/sprint-status/workflow.yaml
This commit is contained in:
Dicky Moore 2026-02-10 17:43:42 +00:00
commit 4409df7c0f
5 changed files with 5 additions and 0 deletions

View File

@ -10,6 +10,7 @@
<workflow> <workflow>
<step n="1" goal="Initialize Change Navigation"> <step n="1" goal="Initialize Change Navigation">
<action>Load {project_context} for coding standards and project-wide patterns (if exists)</action>
<action>Confirm change trigger and gather user description of the issue</action> <action>Confirm change trigger and gather user description of the issue</action>
<action>Ask: "What specific issue or change has been identified that requires navigation?"</action> <action>Ask: "What specific issue or change has been identified that requires navigation?"</action>
<action>Verify access to required project documents:</action> <action>Verify access to required project documents:</action>

View File

@ -31,6 +31,7 @@ PARTY MODE PROTOCOL:
<step n="1" goal="Epic Discovery - Find Completed Epic with Priority Logic"> <step n="1" goal="Epic Discovery - Find Completed Epic with Priority Logic">
<action>Load {project_context} for project-wide patterns and conventions (if exists)</action>
<action>Explain to {user_name} the epic discovery process using natural dialogue</action> <action>Explain to {user_name} the epic discovery process using natural dialogue</action>
<output> <output>

View File

@ -23,6 +23,7 @@
<workflow> <workflow>
<step n="1" goal="Parse epic files and extract all work items"> <step n="1" goal="Parse epic files and extract all work items">
<action>Load {project_context} for project-wide patterns and conventions (if exists)</action>
<action>Communicate in {communication_language} with {user_name}</action> <action>Communicate in {communication_language} with {user_name}</action>
<action>Look for all files matching `{epics_pattern}` in {epics_location}</action> <action>Look for all files matching `{epics_pattern}` in {epics_location}</action>
<action>Could be a single `epics.md` file or multiple `epic-1.md`, `epic-2.md` files</action> <action>Could be a single `epics.md` file or multiple `epic-1.md`, `epic-2.md` files</action>

View File

@ -24,6 +24,7 @@
</step> </step>
<step n="1" goal="Locate sprint status file"> <step n="1" goal="Locate sprint status file">
<action>Load {project_context} for project-wide patterns and conventions (if exists)</action>
<action>Try {sprint_status_file}</action> <action>Try {sprint_status_file}</action>
<check if="file not found"> <check if="file not found">
<output>❌ sprint-status.yaml not found. <output>❌ sprint-status.yaml not found.

View File

@ -71,6 +71,7 @@ Load and read full config from `{main_config}` and resolve:
- `project_name`, `output_folder`, `planning_artifacts`, `implementation_artifacts`, `user_name` - `project_name`, `output_folder`, `planning_artifacts`, `implementation_artifacts`, `user_name`
- `communication_language`, `document_output_language`, `user_skill_level` - `communication_language`, `document_output_language`, `user_skill_level`
- `date` as system-generated current datetime - `date` as system-generated current datetime
- `project_context` = `**/project-context.md` (load if exists)
- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}` - ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
### 2. First Step Execution ### 2. First Step Execution