fix: correct retrospective workflow handoff

[Jrakru]

Summary

• align every workflow-status path so epic retrospectives hand off to the Scrum Master, matching documentation and actual SM ownership
• update the story-approved workflow's next-step guidance so completed epics are routed to the SM for retrospectives
• keeps workflow-status recommendations and exported prompts consistent with the process teams follow after an epic closes

Testing

• manual: rebuilt BMAD agents and regenerated Codex prompts to verify the SM ownership propagates

[Copilot]

Pull Request Overview

Align retrospective ownership to the Scrum Master across workflows and guidance, matching documented process.

• Switch retrospective step agent from pm to sm in multiple workflow-status paths
• Update story-approved instructions to direct users to run the retrospective with the SM agent

Reviewed Changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
src/modules/bmm/workflows/workflow-status/paths/greenfield-level-4.yaml	Set retrospective step agent to sm for epic completion
src/modules/bmm/workflows/workflow-status/paths/greenfield-level-3.yaml	Set retrospective step agent to sm for epic completion
src/modules/bmm/workflows/workflow-status/paths/greenfield-level-2.yaml	Set retrospective step agent to sm for epic completion
src/modules/bmm/workflows/workflow-status/paths/game-design.yaml	Set retrospective step agent to sm for retrospective in feature flow
src/modules/bmm/workflows/workflow-status/paths/brownfield-level-4.yaml	Set retrospective step agent to sm for epic completion
src/modules/bmm/workflows/workflow-status/paths/brownfield-level-3.yaml	Set retrospective step agent to sm for epic completion
src/modules/bmm/workflows/4-implementation/story-approved/instructions.md	Update next-step guidance to use SM agent for retrospective

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

[nitpick] Consider expanding the acronym for clarity: 'Run retrospective workflow with Scrum Master (SM) agent to review the project' to make this instruction self-explanatory for new contributors.

Suggested change

	1. Run `retrospective` workflow with SM agent to review the project
	1. Run `retrospective` workflow with Scrum Master (SM) agent to review the project

[Copilot]

[nitpick] The retrospective step definition is duplicated across multiple path files. Consider extracting a shared YAML anchor or central include for the epic_completion.retrospective step (with agent: 'sm') to keep all paths consistent and reduce future drift.

[alexeyv]

I have reviewed and tested this. Looks good.

• Rebased on latest v6-alpha (2a6eb71)
• Installed BMAD to test environment and verified all generated files show correct SM ownership
• No conflicts, clean rebase
• All workflow-status YAML files install correctly with `agent: "sm"`

[alexeyv]

@Jrakru thank you!

[bmadcode]

Thanks for catching this @Jrakru !