From b7e6bfcde598ee97c7bfd06d4b72c1064fa83f43 Mon Sep 17 00:00:00 2001
From: Brian Madison <brianmadison@Brians-MacBook-Pro.local>
Date: Sat, 25 Oct 2025 23:57:27 -0500
Subject: [PATCH]  a few more instruction cleanup items

---
 .../4-implementation/epic-tech-context/instructions.md        | 4 ++--
 .../4-implementation/epic-tech-context/workflow.yaml          | 3 +++
 .../workflows/4-implementation/review-story/instructions.md   | 2 --
 3 files changed, 5 insertions(+), 4 deletions(-)

diff --git a/src/modules/bmm/workflows/4-implementation/epic-tech-context/instructions.md b/src/modules/bmm/workflows/4-implementation/epic-tech-context/instructions.md
index eb477546..d0b70271 100644
--- a/src/modules/bmm/workflows/4-implementation/epic-tech-context/instructions.md
+++ b/src/modules/bmm/workflows/4-implementation/epic-tech-context/instructions.md
@@ -78,7 +78,7 @@ Continuing to regenerate tech spec...
   </step>
 
   <step n="3" goal="Overview and scope">
-    <action>Read COMPLETE PRD and Architecture files.</action>
+    <action>Read COMPLETE found {recommended_inputs}.</action>
     <template-output file="{default_output_file}">
       Replace {{overview}} with a concise 1-2 paragraph summary referencing PRD context and goals
       Replace {{objectives_scope}} with explicit in-scope and out-of-scope bullets
@@ -87,7 +87,7 @@ Continuing to regenerate tech spec...
   </step>
 
   <step n="4" goal="Detailed design">
-    <action>Derive concrete implementation specifics from Architecture and PRD (CRITICAL: NO invention).</action>
+    <action>Derive concrete implementation specifics from all {recommended_inputs} (CRITICAL: NO invention). If a epic tech spec precedes this one and exists, maintain consistency where appropriate.</action>
     <template-output file="{default_output_file}">
       Replace {{services_modules}} with a table or bullets listing services/modules with responsibilities, inputs/outputs, and owners
       Replace {{data_models}} with normalized data model definitions (entities, fields, types, relationships); include schema snippets where available
diff --git a/src/modules/bmm/workflows/4-implementation/epic-tech-context/workflow.yaml b/src/modules/bmm/workflows/4-implementation/epic-tech-context/workflow.yaml
index 5290a5c0..0a4ab91f 100644
--- a/src/modules/bmm/workflows/4-implementation/epic-tech-context/workflow.yaml
+++ b/src/modules/bmm/workflows/4-implementation/epic-tech-context/workflow.yaml
@@ -16,6 +16,9 @@ recommended_inputs:
   - spec
   - architecture
   - ux_spec
+  - ux-design
+  - if there is an index.md then read the index.md to find other related docs that could be relevant
+  - prior epic tech-specs for model, style and consistency reference
 
 # Workflow components
 installed_path: "{project-root}/bmad/bmm/workflows/4-implementation/epic-tech-context"
diff --git a/src/modules/bmm/workflows/4-implementation/review-story/instructions.md b/src/modules/bmm/workflows/4-implementation/review-story/instructions.md
index 6c6276d7..6d58dae9 100644
--- a/src/modules/bmm/workflows/4-implementation/review-story/instructions.md
+++ b/src/modules/bmm/workflows/4-implementation/review-story/instructions.md
@@ -66,8 +66,6 @@
 
   <step n="3" goal="Detect tech stack and establish best-practice reference set">
     <action>Detect primary ecosystem(s) by scanning for manifests (e.g., package.json, pyproject.toml, go.mod, Dockerfile). Record key frameworks (e.g., Node/Express, React/Vue, Python/FastAPI, etc.).</action>
-    <action>If {{enable_mcp_doc_search}} and MCP servers are available → Use them to search for up-to-date best practices, security advisories, and framework-specific guidance relevant to the detected stack and the story's domain.</action>
-    <action>If MCP is unavailable or insufficient and {{enable_web_fallback}} → Perform targeted web searches and fetch authoritative references (framework docs, OWASP, language style guides). Prefer official documentation and widely-recognized standards.</action>
     <action>Synthesize a concise "Best-Practices and References" note capturing any updates or considerations that should influence the review (cite links and versions if available).</action>
   </step>