fix(skills): replace dev team references with Developer agent

No longer a multi-agent development team — just one Developer agent.
Remove residual Scrum Master search patterns from retrospective.

src/bmm-skills/2-plan-workflows/bmad-create-ux-design/steps/step-13-responsive-accessibility.md

@@ -240,7 +240,7 @@ When user selects 'C', append the content directly to the document using the str
 ✅ Appropriate breakpoint strategy established
 ✅ Accessibility requirements determined and documented
 ✅ Comprehensive testing strategy planned
-✅ Implementation guidelines provided for development team
+✅ Implementation guidelines provided for Developer agent
 ✅ A/P/C menu presented and handled correctly
 ✅ Content properly appended to document when C selected
 

src/bmm-skills/3-solutioning/bmad-create-epics-and-stories/workflow.md

@@ -1,6 +1,6 @@
 # Create Epics and Stories
 
-**Goal:** Transform PRD requirements and Architecture decisions into comprehensive stories organized by user value, creating detailed, actionable stories with complete acceptance criteria for development teams.
+**Goal:** Transform PRD requirements and Architecture decisions into comprehensive stories organized by user value, creating detailed, actionable stories with complete acceptance criteria for the Developer agent.
 
 **Your Role:** In addition to your name, communication_style, and persona, you are also a product strategist and technical specifications writer collaborating with a product owner. This is a partnership, not a client-vendor relationship. You bring expertise in requirements decomposition, technical implementation context, and acceptance criteria writing, while the user brings their product vision, user needs, and business requirements. Work together as equals.
 

src/bmm-skills/4-implementation/bmad-correct-course/checklist.md

@@ -217,7 +217,7 @@
 <check-item id="5.5">
 <prompt>Establish agent handoff plan</prompt>
 <action>Identify which roles/agents will execute the changes:</action>
-  - Development team (for implementation)
+  - Developer agent (for implementation)
   - Product Owner / Developer (for backlog changes)
   - Product Manager / Architect (for strategic changes)
 <action>Define responsibilities for each role</action>

src/bmm-skills/4-implementation/bmad-correct-course/workflow.md

@@ -192,7 +192,7 @@ Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
 <action>Section 5: Implementation Handoff</action>
 
 - Categorize change scope:
-  - Minor: Direct implementation by dev team
+  - Minor: Direct implementation by Developer agent
   - Moderate: Backlog reorganization needed (PO/DEV)
   - Major: Fundamental replan required (PM/Architect)
 - Specify handoff recipients and their responsibilities
@@ -219,7 +219,7 @@ Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
   <action>Finalize Sprint Change Proposal document</action>
   <action>Determine change scope classification:</action>
 
-- **Minor**: Can be implemented directly by development team
+- **Minor**: Can be implemented directly by Developer agent
 - **Moderate**: Requires backlog reorganization and PO/DEV coordination
 - **Major**: Needs fundamental replan with PM/Architect involvement
 
@@ -228,7 +228,7 @@ Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
 </check>
 
 <check if="Minor scope">
-  <action>Route to: Development team for direct implementation</action>
+  <action>Route to: Developer agent for direct implementation</action>
   <action>Deliverables: Finalized edit proposals and implementation tasks</action>
 </check>
 
@@ -261,7 +261,7 @@ Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
 - Implementation handoff plan
 
 <action>Report workflow completion to user with personalized message: "Correct Course workflow complete, {user_name}!"</action>
-<action>Remind user of success criteria and next steps for implementation team</action>
+<action>Remind user of success criteria and next steps for Developer agent</action>
 </step>
 
 </workflow>

src/bmm-skills/4-implementation/bmad-retrospective/workflow.md

@@ -219,7 +219,7 @@ Charlie (Senior Dev): "Good idea - those dev notes always have gold in them."
 
 **Review Feedback Patterns:**
 
-- Look for "## Review", "## Code Review", "## Dev Review", "## SM Review", "## Scrum Master Review" sections
+- Look for "## Review", "## Code Review", "## Dev Review" sections
 - Identify recurring feedback themes across stories
 - Note which types of issues came up repeatedly
 - Track quality concerns or architectural misalignments
@@ -577,7 +577,7 @@ Alice (Product Owner): "I'll start. The user authentication flow we delivered ex
 
 Charlie (Senior Dev): "I'll add to that - the caching strategy we implemented in Story {{breakthrough_story_num}} was a game-changer. We cut API calls by 60% and it set the pattern for the rest of the epic."
 
-Dana (QA Engineer): "From my side, testing went smoother than usual. The dev team's documentation was way better this epic - actually usable test plans!"
+Dana (QA Engineer): "From my side, testing went smoother than usual. The Developer's documentation was way better this epic - actually usable test plans!"
 
 Elena (Junior Dev): _smiling_ "That's because Charlie made me document everything after Story 1's code review!"