bmad-method 6.0.0-alpha.12 → 6.0.0-alpha.14

package/src/modules/bmm/workflows/4-implementation/create-story/instructions.md

@@ -1,256 +0,0 @@
-# Create Story - Workflow Instructions (Spec-compliant, non-interactive by default)
-
-````xml
-<critical>The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml</critical>
-<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
-<critical>Generate all documents in {document_output_language}</critical>
-<critical>This workflow creates or updates the next user story from epics/PRD and architecture context, saving to the configured stories directory and optionally invoking Story Context.</critical>
-<critical>DOCUMENT OUTPUT: Concise, technical, actionable story specifications. Use tables/lists for acceptance criteria and tasks.</critical>
-
-<workflow>
-
-  <step n="1" goal="Load config and initialize">
-    <action>Resolve variables from config_source: story_dir (sprint_artifacts), output_folder, user_name, communication_language. If story_dir missing → ASK user to provide a stories directory and update variable.</action>
-    <action>Create {{story_dir}} if it does not exist</action>
-    <action>Resolve installed component paths from workflow.yaml: template, instructions, validation</action>
-    <action>Load architecture/standards docs: For each file name in {{arch_docs_file_names}} within {{arch_docs_search_dirs}}, read if exists. Collect testing, coding standards, security, and architectural patterns.</action>
-  </step>
-
-  <step n="1.5" goal="Discover and load project documents">
-    <invoke-protocol name="discover_inputs" />
-    <note>After discovery, these content variables are available: {prd_content}, {tech_spec_content}, {architecture_content}, {ux_design_content}, {epics_content}, {document_project_content}</note>
-  </step>
-
-  <step n="2" goal="Discover previous story context">
-    <critical>PREVIOUS STORY CONTINUITY: Essential for maintaining context and learning from prior development</critical>
-
-    <action>Find the previous completed story to extract dev agent learnings and review findings:
-      1. Load {{output_folder}}/sprint-status.yaml COMPLETELY
-      2. Find current {{story_key}} in development_status section
-      3. Identify the story entry IMMEDIATELY ABOVE current story (previous row in file order)
-      4. If previous story exists:
-         - Extract {{previous_story_key}}
-         - Check previous story status (done, in-progress, review, etc.)
-         - If status is "done", "review", or "in-progress" (has some completion):
-           * Construct path: {{story_dir}}/{{previous_story_key}}.md
-           * Load the COMPLETE previous story file
-           * Parse ALL sections comprehensively:
-
-             A) Dev Agent Record → Completion Notes List:
-                - New patterns/services created (to reuse, not recreate)
-                - Architectural deviations or decisions made
-                - Technical debt deferred to future stories
-                - Warnings or recommendations for next story
-                - Interfaces/methods created for reuse
-
-             B) Dev Agent Record → Debug Log References:
-                - Issues encountered and solutions
-                - Gotchas or unexpected challenges
-                - Workarounds applied
-
-             C) Dev Agent Record → File List:
-                - Files created (NEW) - understand new capabilities
-                - Files modified (MODIFIED) - track evolving components
-                - Files deleted (DELETED) - removed functionality
-
-             D) Dev Notes:
-                - Any "future story" notes or TODOs
-                - Patterns established
-                - Constraints discovered
-
-             E) Senior Developer Review (AI) section (if present):
-                - Review outcome (Approve/Changes Requested/Blocked)
-                - Unresolved action items (unchecked [ ] items)
-                - Key findings that might affect this story
-                - Architectural concerns raised
-
-             F) Senior Developer Review → Action Items (if present):
-                - Check for unchecked [ ] items still pending
-                - Note any systemic issues that apply to multiple stories
-
-             G) Review Follow-ups (AI) tasks (if present):
-                - Check for unchecked [ ] review tasks still pending
-                - Determine if they're epic-wide concerns
-
-             H) Story Status:
-                - If "review" or "in-progress" - incomplete, note what's pending
-                - If "done" - confirmed complete
-           * Store ALL findings as {{previous_story_learnings}} with structure:
-             - new_files: [list]
-             - modified_files: [list]
-             - new_services: [list with descriptions]
-             - architectural_decisions: [list]
-             - technical_debt: [list]
-             - warnings_for_next: [list]
-             - review_findings: [list if review exists]
-             - pending_items: [list of unchecked action items]
-         - If status is "backlog" or "drafted":
-           * Set {{previous_story_learnings}} = "Previous story not yet implemented"
-      5. If no previous story exists (first story in epic):
-         - Set {{previous_story_learnings}} = "First story in epic - no predecessor context"
-    </action>
-
-    <action>If {{tech_spec_file}} empty: derive from {{tech_spec_glob_template}} with {{epic_num}} and search {{tech_spec_search_dir}} recursively. If multiple, pick most recent by modified time.</action>
-    <action>Build a prioritized document set for this epic - search and load from {input_file_patterns} list of potential locations:
-      1) tech_spec_file (epic-scoped)
-      2) epics_file (acceptance criteria and breakdown) the specific epic the story will be part of
-      3) prd_file (business requirements and constraints) whole or sharded
-      4) architecture_file (architecture constraints) whole or sharded
-    </action>
-    <action>READ COMPLETE FILES for all items found in the prioritized set. Store content and paths for citation.</action>
-  </step>
-
-  <step n="3" goal="Find next backlog story to draft" tag="sprint-status">
-    <critical>MUST read COMPLETE {sprint_status} file from start to end to preserve order</critical>
-    <action>Read ALL lines from beginning to end - do not skip any content</action>
-    <action>Parse the development_status section completely to understand story order</action>
-
-    <action>Find the FIRST story (by reading in order from top to bottom) where:
-      - Key matches pattern: number-number-name (e.g., "1-2-user-auth")
-      - NOT an epic key (epic-X) or retrospective (epic-X-retrospective)
-      - Status value equals "backlog"
-    </action>
-
-    <check if="no backlog story found">
-      <output>📋 No backlog stories found in sprint-status.yaml
-
-        All stories are either already drafted or completed.
-
-        **Options:**
-        1. Run sprint-planning to refresh story tracking
-        2. Load PM agent and run correct-course to add more stories
-        3. Check if current sprint is complete
-      </output>
-      <action>HALT</action>
-    </check>
-
-    <action>Extract from found story key (e.g., "1-2-user-authentication"):
-      - epic_num: first number before dash (e.g., "1")
-      - story_num: second number after first dash (e.g., "2")
-      - story_title: remainder after second dash (e.g., "user-authentication")
-    </action>
-    <action>Set {{story_id}} = "{{epic_num}}.{{story_num}}"</action>
-    <action>Store story_key for later use (e.g., "1-2-user-authentication")</action>
-
-    <action>Verify story is enumerated in {{epics_file}}. If not found, HALT with message:</action>
-    <action>"Story {{story_key}} not found in epics.md. Please load PM agent and run correct-course to sync epics, then rerun create-story."</action>
-
-    <action>Check if story file already exists at expected path in {{story_dir}}</action>
-    <check if="story file exists">
-      <output>ℹ️ Story file already exists: {{story_file_path}}
-Will update existing story file rather than creating new one.
-      </output>
-      <action>Set update_mode = true</action>
-    </check>
-  </step>
-
-  <step n="4" goal="Extract requirements and derive story statement">
-    <action>From tech_spec_file (preferred) or epics_file: extract epic {{epic_num}} title/summary, acceptance criteria for the next story, and any component references. If not present, fall back to PRD sections mapping to this epic/story.</action>
-    <action>From architecture and architecture docs: extract constraints, patterns, component boundaries, and testing guidance relevant to the extracted ACs. ONLY capture information that directly informs implementation of this story.</action>
-    <action>Derive a clear user story statement (role, action, benefit) grounded strictly in the above sources. If ambiguous and {{non_interactive}} == false → ASK user to clarify. If {{non_interactive}} == true → generate the best grounded statement WITHOUT inventing domain facts.</action>
-    <template-output file="{default_output_file}">requirements_context_summary</template-output>
-  </step>
-
-  <step n="5" goal="Project structure alignment and lessons learned">
-    <action>Review {{previous_story_learnings}} and extract actionable intelligence:
-      - New patterns/services created → Note for reuse (DO NOT recreate)
-      - Architectural deviations → Understand and maintain consistency
-      - Technical debt items → Assess if this story should address them
-      - Files modified → Understand current state of evolving components
-      - Warnings/recommendations → Apply to this story's approach
-      - Review findings → Learn from issues found in previous story
-      - Pending action items → Determine if epic-wide concerns affect this story
-    </action>
-
-    <action>If unified-project-structure.md present: align expected file paths, module names, and component locations; note any potential conflicts.</action>
-
-    <action>Cross-reference {{previous_story_learnings}}.new_files with project structure to understand where new capabilities are located.</action>
-
-    <template-output file="{default_output_file}">structure_alignment_summary</template-output>
-  </step>
-
-  <step n="6" goal="Assemble acceptance criteria and tasks">
-    <action>Assemble acceptance criteria list from tech_spec or epics. If gaps exist, derive minimal, testable criteria from PRD verbatim phrasing (NO invention).</action>
-    <action>Create tasks/subtasks directly mapped to ACs. Include explicit testing subtasks per testing-strategy and existing tests framework. Cite architecture/source documents for any technical mandates.</action>
-    <template-output file="{default_output_file}">acceptance_criteria</template-output>
-    <template-output file="{default_output_file}">tasks_subtasks</template-output>
-  </step>
-
-  <step n="7" goal="Create or update story document">
-    <action>Resolve output path: {default_output_file} using current {{epic_num}} and {{story_num}}. If targeting an existing story for update, use its path.</action>
-    <action>Initialize from template.md if creating a new file; otherwise load existing file for edit.</action>
-    <action>Compute a concise story_title from epic/story context; if missing, synthesize from PRD feature name and epic number.</action>
-    <template-output file="{default_output_file}">story_header</template-output>
-    <template-output file="{default_output_file}">story_body</template-output>
-    <template-output file="{default_output_file}">dev_notes_with_citations</template-output>
-
-    <action>If {{previous_story_learnings}} contains actionable items (not "First story" or "not yet implemented"):
-      - Add "Learnings from Previous Story" subsection to Dev Notes
-      - Include relevant completion notes, new files/patterns, deviations
-      - Cite previous story file as reference [Source: stories/{{previous_story_key}}.md]
-      - Highlight interfaces/services to REUSE (not recreate)
-      - Note any technical debt to address in this story
-      - List pending review items that affect this story (if any)
-      - Reference specific files created: "Use {{file_path}} for {{purpose}}"
-      - Format example:
-        ```
-        ### Learnings from Previous Story
-
-        **From Story {{previous_story_key}} (Status: {{previous_status}})**
-
-        - **New Service Created**: `AuthService` base class available at `src/services/AuthService.js` - use `AuthService.register()` method
-        - **Architectural Change**: Switched from session-based to JWT authentication
-        - **Schema Changes**: User model now includes `passwordHash` field, migration applied
-        - **Technical Debt**: Email verification skipped, should be included in this or subsequent story
-        - **Testing Setup**: Auth test suite initialized at `tests/integration/auth.test.js` - follow patterns established there
-        - **Pending Review Items**: Rate limiting mentioned in review - consider for this story
-
-        [Source: stories/{{previous_story_key}}.md#Dev-Agent-Record]
-        ```
-    </action>
-
-    <template-output file="{default_output_file}">change_log</template-output>
-  </step>
-
-  <step n="8" goal="Validate, save, and mark story drafted" tag="sprint-status">
-    <invoke-task>Validate against checklist at {installed_path}/checklist.md using {bmad_folder}/core/tasks/validate-workflow.xml</invoke-task>
-    <action>Save document unconditionally (non-interactive default). In interactive mode, allow user confirmation.</action>
-
-    <!-- Mark story as drafted in sprint status -->
-    <action>Update {{output_folder}}/sprint-status.yaml</action>
-    <action>Load the FULL file and read all development_status entries</action>
-    <action>Find development_status key matching {{story_key}}</action>
-    <action>Verify current status is "backlog" (expected previous state)</action>
-    <action>Update development_status[{{story_key}}] = "drafted"</action>
-    <action>Save file, preserving ALL comments and structure including STATUS DEFINITIONS</action>
-
-    <check if="story key not found in file">
-      <output>⚠️ Could not update story status: {{story_key}} not found in sprint-status.yaml
-
-Story file was created successfully, but sprint-status.yaml was not updated.
-You may need to run sprint-planning to refresh tracking, or manually set the story row status to `drafted`.
-      </output>
-    </check>
-
-    <action>Report created/updated story path</action>
-    <output>**✅ Story Created Successfully, {user_name}!**
-
-**Story Details:**
-
-- Story ID: {{story_id}}
-- Story Key: {{story_key}}
-- File: {{story_file}}
-- Status: drafted (was backlog)
-
-**⚠️ Important:** The following workflows are context-intensive. It's recommended to clear context and restart the SM agent before running the next command.
-
-**Next Steps:**
-
-1. Review the drafted story in {{story_file}}
-2. **[RECOMMENDED]** Run `story-context` to generate technical context XML and mark story ready for development (combines context + ready in one step)
-3. Or run `story-ready` to manually mark the story ready without generating technical context
-    </output>
-  </step>
-
-</workflow>
-````

package/src/modules/bmm/workflows/4-implementation/dev-story/instructions.md

@@ -1,267 +0,0 @@
-# Develop Story - Workflow Instructions
-
-```xml
-<critical>The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml</critical>
-<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
-<critical>Communicate all responses in {communication_language} and language MUST be tailored to {user_skill_level}</critical>
-<critical>Generate all documents in {document_output_language}</critical>
-<critical>Only modify the story file in these areas: Tasks/Subtasks checkboxes, Dev Agent Record (Debug Log, Completion Notes), File List, Change Log, and Status</critical>
-<critical>Execute ALL steps in exact order; do NOT skip steps</critical>
-<critical>Absolutely DO NOT stop because of "milestones", "significant progress", or "session boundaries". Continue in a single execution until the story is COMPLETE (all ACs satisfied and all tasks/subtasks checked) UNLESS a HALT condition is triggered or the USER gives other instruction.</critical>
-<critical>Do NOT schedule a "next session" or request review pauses unless a HALT condition applies. Only Step 6 decides completion.</critical>
-
-<critical>User skill level ({user_skill_level}) affects conversation style ONLY, not code updates.</critical>
-
-<workflow>
-
-  <step n="1" goal="Find next ready story and load it" tag="sprint-status">
-    <check if="{{story_path}} is provided">
-      <action>Use {{story_path}} directly</action>
-      <action>Read COMPLETE story file</action>
-      <action>Extract story_key from filename or metadata</action>
-      <goto>task_check</goto>
-    </check>
-
-    <critical>MUST read COMPLETE sprint-status.yaml file from start to end to preserve order</critical>
-    <action>Load the FULL file: {{output_folder}}/sprint-status.yaml</action>
-    <action>Read ALL lines from beginning to end - do not skip any content</action>
-    <action>Parse the development_status section completely to understand story order</action>
-
-    <action>Find the FIRST story (by reading in order from top to bottom) where:
-      - Key matches pattern: number-number-name (e.g., "1-2-user-auth")
-      - NOT an epic key (epic-X) or retrospective (epic-X-retrospective)
-      - Status value equals "ready-for-dev"
-    </action>
-
-    <check if="no ready-for-dev or in-progress story found">
-      <output>📋 No ready-for-dev stories found in sprint-status.yaml
-**Options:**
-1. Run `story-context` to generate context file and mark drafted stories as ready
-2. Run `story-ready` to quickly mark drafted stories as ready without generating context
-3. Run `create-story` if no incomplete stories are drafted yet
-4. Check {output_folder}/sprint-status.yaml to see current sprint status
-      </output>
-      <action>HALT</action>
-    </check>
-
-    <action>Store the found story_key (e.g., "1-2-user-authentication") for later status updates</action>
-    <action>Find matching story file in {{story_dir}} using story_key pattern: {{story_key}}.md</action>
-    <action>Read COMPLETE story file from discovered path</action>
-
-    <anchor id="task_check" />
-
-    <action>Parse sections: Story, Acceptance Criteria, Tasks/Subtasks, Dev Notes, Dev Agent Record, File List, Change Log, Status</action>
-
-    <action>Check if context file exists at: {{story_dir}}/{{story_key}}.context.xml</action>
-    <check if="context file exists">
-      <action>Read COMPLETE context file</action>
-      <action>Parse all sections: story details, artifacts (docs, code, dependencies), interfaces, constraints, tests</action>
-      <action>Use this context to inform implementation decisions and approaches</action>
-    </check>
-    <check if="context file does NOT exist">
-      <output>ℹ️ No context file found for {{story_key}}
-
-Proceeding with story file only. For better context, consider running `story-context` workflow first.
-      </output>
-    </check>
-
-    <action>Identify first incomplete task (unchecked [ ]) in Tasks/Subtasks</action>
-
-    <action if="no incomplete tasks"><goto step="6">Completion sequence</goto></action>
-    <action if="story file inaccessible">HALT: "Cannot develop story without access to story file"</action>
-    <action if="incomplete task or subtask requirements ambiguous">ASK user to clarify or HALT</action>
-  </step>
-
-  <step n="0.5" goal="Discover and load project documents">
-    <invoke-protocol name="discover_inputs" />
-    <note>After discovery, these content variables are available: {architecture_content}, {tech_spec_content}, {ux_design_content}, {epics_content} (selective load), {document_project_content}</note>
-  </step>
-
-  <step n="1.5" goal="Detect review continuation and extract review context">
-    <critical>Determine if this is a fresh start or continuation after code review</critical>
-
-    <action>Check if "Senior Developer Review (AI)" section exists in the story file</action>
-    <action>Check if "Review Follow-ups (AI)" subsection exists under Tasks/Subtasks</action>
-
-    <check if="Senior Developer Review section exists">
-      <action>Set review_continuation = true</action>
-      <action>Extract from "Senior Developer Review (AI)" section:
-        - Review outcome (Approve/Changes Requested/Blocked)
-        - Review date
-        - Total action items with checkboxes (count checked vs unchecked)
-        - Severity breakdown (High/Med/Low counts)
-      </action>
-      <action>Count unchecked [ ] review follow-up tasks in "Review Follow-ups (AI)" subsection</action>
-      <action>Store list of unchecked review items as {{pending_review_items}}</action>
-
-      <output>⏯️ **Resuming Story After Code Review** ({{review_date}})
-
-**Review Outcome:** {{review_outcome}}
-**Action Items:** {{unchecked_review_count}} remaining to address
-**Priorities:** {{high_count}} High, {{med_count}} Medium, {{low_count}} Low
-
-**Strategy:** Will prioritize review follow-up tasks (marked [AI-Review]) before continuing with regular tasks.
-      </output>
-    </check>
-
-    <check if="Senior Developer Review section does NOT exist">
-      <action>Set review_continuation = false</action>
-      <action>Set {{pending_review_items}} = empty</action>
-
-      <output>🚀 **Starting Fresh Implementation**
-
-Story: {{story_key}}
-Context file: {{context_available}}
-First incomplete task: {{first_task_description}}
-      </output>
-    </check>
-  </step>
-
-  <step n="1.6" goal="Mark story in-progress" tag="sprint-status">
-    <action>Load the FULL file: {{output_folder}}/sprint-status.yaml</action>
-    <action>Read all development_status entries to find {{story_key}}</action>
-    <action>Get current status value for development_status[{{story_key}}]</action>
-
-    <check if="current status == 'ready-for-dev'">
-      <action>Update the story in the sprint status report to = "in-progress"</action>
-      <output>🚀 Starting work on story {{story_key}}
-Status updated: ready-for-dev → in-progress
-      </output>
-    </check>
-
-    <check if="current status == 'in-progress'">
-      <output>⏯️ Resuming work on story {{story_key}}
-Story is already marked in-progress
-      </output>
-    </check>
-
-    <check if="current status is neither ready-for-dev nor in-progress">
-      <output>⚠️ Unexpected story status: {{current_status}}
-Expected ready-for-dev or in-progress. Continuing anyway...
-      </output>
-    </check>
-  </step>
-
-  <step n="2" goal="Plan and implement task">
-    <action>Review acceptance criteria and dev notes for the selected task</action>
-    <action>Plan implementation steps and edge cases; write down a brief plan in Dev Agent Record → Debug Log</action>
-    <action>Implement the task COMPLETELY including all subtasks, critically following best practices, coding patterns and coding standards in this repo you have learned about from the story and context file or your own critical agent instructions</action>
-    <action>Handle error conditions and edge cases appropriately</action>
-    <action if="new or different than what is documented dependencies are needed">ASK user for approval before adding</action>
-    <action if="3 consecutive implementation failures occur">HALT and request guidance</action>
-    <action if="required configuration is missing">HALT: "Cannot proceed without necessary configuration files"</action>
-    <critical>Do not stop after partial progress; continue iterating tasks until all ACs are satisfied and tested or a HALT condition triggers</critical>
-    <critical>Do NOT propose to pause for review, stand-ups, or validation until Step 6 gates are satisfied</critical>
-  </step>
-
-  <step n="3" goal="Author comprehensive tests">
-    <action>Create unit tests for business logic and core functionality introduced/changed by the task</action>
-    <action>Add integration tests for component interactions where desired by test plan or story notes</action>
-    <action>Include end-to-end tests for critical user flows where desired by test plan or story notes</action>
-    <action>Cover edge cases and error handling scenarios noted in the test plan or story notes</action>
-  </step>
-
-  <step n="4" goal="Run validations and tests">
-    <action>Determine how to run tests for this repo (infer or use {{run_tests_command}} if provided)</action>
-    <action>Run all existing tests to ensure no regressions</action>
-    <action>Run the new tests to verify implementation correctness</action>
-    <action>Run linting and code quality checks if configured</action>
-    <action>Validate implementation meets ALL story acceptance criteria; if ACs include quantitative thresholds (e.g., test pass rate), ensure they are met before marking complete</action>
-    <action if="regression tests fail">STOP and fix before continuing, consider how current changes made broke regression</action>
-    <action if="new tests fail">STOP and fix before continuing</action>
-  </step>
-
-  <step n="5" goal="Mark task complete, track review resolutions, and update story">
-    <critical>If task is a review follow-up, must mark BOTH the task checkbox AND the corresponding action item in the review section</critical>
-
-    <action>Check if completed task has [AI-Review] prefix (indicates review follow-up task)</action>
-
-    <check if="task is review follow-up">
-      <action>Extract review item details (severity, description, related AC/file)</action>
-      <action>Add to resolution tracking list: {{resolved_review_items}}</action>
-
-      <!-- Mark task in Review Follow-ups section -->
-      <action>Mark task checkbox [x] in "Tasks/Subtasks → Review Follow-ups (AI)" section</action>
-
-      <!-- CRITICAL: Also mark corresponding action item in review section -->
-      <action>Find matching action item in "Senior Developer Review (AI) → Action Items" section by matching description</action>
-      <action>Mark that action item checkbox [x] as resolved</action>
-
-      <action>Add to Dev Agent Record → Completion Notes: "✅ Resolved review finding [{{severity}}]: {{description}}"</action>
-    </check>
-
-    <action>ONLY mark the task (and subtasks) checkbox with [x] if ALL tests pass and validation succeeds</action>
-    <action>Update File List section with any new, modified, or deleted files (paths relative to repo root)</action>
-    <action>Add completion notes to Dev Agent Record if significant changes were made (summarize intent, approach, and any follow-ups)</action>
-
-    <check if="review_continuation == true and {{resolved_review_items}} is not empty">
-      <action>Count total resolved review items in this session</action>
-      <action>Add Change Log entry: "Addressed code review findings - {{resolved_count}} items resolved (Date: {{date}})"</action>
-    </check>
-
-    <action>Save the story file</action>
-    <action>Determine if more incomplete tasks remain</action>
-    <action if="more tasks remain"><goto step="2">Next task</goto></action>
-    <action if="no tasks remain"><goto step="6">Completion</goto></action>
-  </step>
-
-  <step n="6" goal="Story completion and mark for review" tag="sprint-status">
-    <action>Verify ALL tasks and subtasks are marked [x] (re-scan the story document now)</action>
-    <action>Run the full regression suite (do not skip)</action>
-    <action>Confirm File List includes every changed file</action>
-    <action>Execute story definition-of-done checklist, if the story includes one</action>
-    <action>Update the story Status to: review</action>
-
-    <!-- Mark story ready for review -->
-    <action>Load the FULL file: {{output_folder}}/sprint-status.yaml</action>
-    <action>Find development_status key matching {{story_key}}</action>
-    <action>Verify current status is "in-progress" (expected previous state)</action>
-    <action>Update development_status[{{story_key}}] = "review"</action>
-    <action>Save file, preserving ALL comments and structure including STATUS DEFINITIONS</action>
-
-    <check if="story key not found in file">
-      <output>⚠️ Story file updated, but sprint-status update failed: {{story_key}} not found
-
-Story is marked Ready for Review in file, but sprint-status.yaml may be out of sync.
-      </output>
-    </check>
-
-    <action if="any task is incomplete">Return to step 1 to complete remaining work (Do NOT finish with partial progress)</action>
-    <action if="regression failures exist">STOP and resolve before completing</action>
-    <action if="File List is incomplete">Update it before completing</action>
-  </step>
-
-  <step n="7" goal="Completion communication and user support">
-    <action>Optionally run the workflow validation task against the story using {project-root}/{bmad_folder}/core/tasks/validate-workflow.xml</action>
-    <action>Prepare a concise summary in Dev Agent Record → Completion Notes</action>
-
-    <action>Communicate to {user_name} that story implementation is complete and ready for review</action>
-    <action>Summarize key accomplishments: story ID, story key, title, key changes made, tests added, files modified</action>
-    <action>Provide the story file path and current status (now "review", was "in-progress")</action>
-
-    <action>Based on {user_skill_level}, ask if user needs any explanations about:
-      - What was implemented and how it works
-      - Why certain technical decisions were made
-      - How to test or verify the changes
-      - Any patterns, libraries, or approaches used
-      - Anything else they'd like clarified
-    </action>
-
-    <check if="user asks for explanations">
-      <action>Provide clear, contextual explanations tailored to {user_skill_level}</action>
-      <action>Use examples and references to specific code when helpful</action>
-    </check>
-
-    <action>Once explanations are complete (or user indicates no questions), suggest logical next steps</action>
-    <action>Common next steps to suggest (but allow user flexibility):
-      - Review the implemented story yourself and test the changes
-      - Verify all acceptance criteria are met
-      - Ensure deployment readiness if applicable
-      - Run `code-review` workflow for peer review
-      - Check sprint-status.yaml to see project progress
-    </action>
-    <action>Remain flexible - allow user to choose their own path or ask for other assistance</action>
-  </step>
-
-</workflow>
-```

package/src/modules/bmm/workflows/4-implementation/epic-tech-context/checklist.md

@@ -1,17 +0,0 @@
-# Tech Spec Validation Checklist
-
-```xml
-<checklist id="{bmad_folder}/bmm/workflows/4-implementation/epic-tech-context/checklist">
-  <item>Overview clearly ties to PRD goals</item>
-  <item>Scope explicitly lists in-scope and out-of-scope</item>
-  <item>Design lists all services/modules with responsibilities</item>
-  <item>Data models include entities, fields, and relationships</item>
-  <item>APIs/interfaces are specified with methods and schemas</item>
-  <item>NFRs: performance, security, reliability, observability addressed</item>
-  <item>Dependencies/integrations enumerated with versions where known</item>
-  <item>Acceptance criteria are atomic and testable</item>
-  <item>Traceability maps AC → Spec → Components → Tests</item>
-  <item>Risks/assumptions/questions listed with mitigation/next steps</item>
-  <item>Test strategy covers all ACs and critical paths</item>
-</checklist>
-```