fix(bmm): add explicit project-context load instructions to workflows

Add Load project_context if exists action to instruction files for
correct-course, retrospective, sprint-status, and sprint-planning.
The workflow.yaml declarations alone do not cause the file to be loaded;
the instruction files must explicitly reference it.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Alex Verkhovsky 2026-02-08 12:42:41 -07:00
parent 4de208ddef
commit 760633b782
4 changed files with 4 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.