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

package/src/modules/bmm/docs/workflows-implementation.md

@@ -70,7 +70,7 @@ For a visual representation of the complete workflow, see: [workflow-method-gree
 Stories move through these states in the sprint status file:
 
 1. **TODO** - Story identified but not started
-2. **IN PROGRESS** - Story being implemented (create-story → story-context → dev-story)
+2. **IN PROGRESS** - Story being implemented (create-story → dev-story)
 3. **READY FOR REVIEW** - Implementation complete, awaiting code review
 4. **DONE** - Accepted and complete
 
@@ -108,7 +108,8 @@ Stories move through these states in the sprint status file:
 
 **As Needed:**
 
-- Run `workflow-status` anytime to check progress
+- Run `sprint-status` anytime in Phase 4 to inspect sprint-status.yaml and get the next implementation command
+- Run `workflow-status` for cross-phase routing and project-level paths
 - Run `correct-course` if significant changes needed
 
 ---
@@ -132,6 +133,7 @@ The `sprint-status.yaml` file is the single source of truth for all implementati
 ### (BMad Method / Enterprise)
 
 ```
+<<<<<<< Updated upstream
 PRD (PM) → Architecture (Architect)
   → create-epics-and-stories (PM)  ← V6: After architecture!
   → implementation-readiness (Architect)
@@ -140,6 +142,144 @@ PRD (PM) → Architecture (Architect)
       → story loop (SM/DEV)
       → retrospective (SM)
   → [Next Epic]
+=======
+Current Phase: 4 (Implementation)
+Current Epic: Epic 1 (Authentication)
+Current Sprint: Sprint 1
+
+Next Story: Story 1.3 (Email Verification)
+Status: TODO
+Dependencies: Story 1.2 (DONE) ✅
+
+**Recommendation:** Run `create-story` to generate Story 1.3
+
+After create-story:
+1. Run story-context
+2. Run dev-story
+3. Run code-review
+4. Run story-done
+```
+
+See: [workflow-status instructions](../workflows/workflow-status/instructions.md)
+
+---
+
+### document-project
+
+**Purpose:** Analyze and document brownfield projects by scanning codebase, architecture, and patterns.
+
+**Agent:** Analyst
+**Duration:** 1-3 hours
+**When to Use:** Brownfield projects without documentation
+
+**How It Works:**
+
+1. Scans codebase structure
+2. Identifies architecture patterns
+3. Documents technology stack
+4. Creates reference documentation
+5. Generates PRD-like document from existing code
+
+**Output:** `project-documentation-{date}.md`
+
+**When to Run:**
+
+- Before starting work on legacy project
+- When inheriting undocumented codebase
+- Creating onboarding documentation
+
+See: [document-project reference](./workflow-document-project-reference.md)
+
+---
+
+## Story Lifecycle Visualization
+
+```
+┌─────────────────────────────────────────────────────────────┐
+│ PHASE 4: IMPLEMENTATION (Iterative Story Lifecycle)        │
+└─────────────────────────────────────────────────────────────┘
+
+┌─────────────────┐
+│ Sprint Planning │  → Creates sprint-status.yaml
+└────────┬────────┘     Defines story queue
+         │
+         ├──────────────────────────────────────────┐
+         │                                          │
+         ▼                                          │
+┌─────────────────────┐                            │
+│ Epic Tech Context   │  → Optional per epic       │
+│ (Once per epic)     │     Provides technical     │
+└─────────────────────┘     guidance              │
+         │                                          │
+         ▼                                          │
+┌─────────────────────────────────────────────────┤
+│ FOR EACH STORY IN QUEUE:                        │
+├─────────────────────────────────────────────────┤
+         │                                          │
+         ▼                                          │
+┌─────────────────┐                                │
+│ Create Story    │  → Generates story file        │
+│ (TODO → IN PROGRESS)                            │
+└────────┬────────┘                                │
+         │                                          │
+         ▼                                          │
+┌─────────────────┐                                │
+│ Story Context   │  → Assembles focused context   │
+└────────┬────────┘                                │
+         │                                          │
+         ▼                                          │
+┌─────────────────┐                                │
+│ Dev Story       │  → Implements + tests           │
+│ (IN PROGRESS)   │                                │
+└────────┬────────┘                                │
+         │                                          │
+         ▼                                          │
+┌─────────────────┐                                │
+│ Code Review     │  → Senior dev review            │
+│ (IN PROGRESS →  │                                │
+│  READY FOR REVIEW)                               │
+└────────┬────────┘                                │
+         │                                          │
+    ┌────┴────┐                                    │
+    │ Result? │                                    │
+    └────┬────┘                                    │
+         │                                          │
+    ┌────┼────────────────────┐                   │
+    │    │                    │                   │
+    ▼    ▼                    ▼                   │
+APPROVED  APPROVED           REQUEST              │
+          WITH COMMENTS      CHANGES              │
+    │         │                   │                │
+    └─────────┴───────────────────┘               │
+              │                                    │
+              ▼                                    │
+    ┌─────────────────┐                           │
+    │ Story Done      │  → READY FOR REVIEW → DONE│
+    └────────┬────────┘                           │
+             │                                     │
+             ├─────────────────────────────────────┘
+             │ More stories?
+             │
+             ▼
+    ┌────────────────┐
+    │ Epic Complete? │
+    └────────┬───────┘
+             │
+        ┌────┼────┐
+        │         │
+       Yes       No
+        │         └──> Continue to next story
+        │
+        ▼
+┌─────────────────┐
+│ Retrospective   │  → Review epic, lessons learned
+└─────────────────┘
+        │
+        ▼
+    All epics done?
+        │
+       Yes → PROJECT COMPLETE
+>>>>>>> Stashed changes
 ```
 
 ---
@@ -155,7 +295,7 @@ PRD (PM) → Architecture (Architect)
 ## Troubleshooting
 
 **Q: Which workflow should I run next?**
-A: Run `workflow-status` - it reads the sprint status file and tells you exactly what to do.
+A: Run `workflow-status` - it reads the sprint status file and tells you exactly what to do. During implementation (Phase 4) run `sprint-status` (fast check against sprint-status.yaml).
 
 **Q: Story needs significant changes mid-implementation?**
 A: Run `correct-course` to analyze impact and route appropriately.

package/src/modules/bmm/docs/workflows-solutioning.md

@@ -424,13 +424,13 @@ Architecture documents are living. Update them as you learn during implementatio
 
 - **Planning:** prd (PM) - creates FRs/NFRs only, NOT epics
 - **Solutioning:** Optional UX → architecture (Architect) → create-epics-and-stories (PM) → implementation-readiness (Architect)
-- **Implementation:** sprint-planning → epic-tech-context → dev-story
+- **Implementation:** sprint-planning → create-story → dev-story
 
 ### Enterprise
 
 - **Planning:** prd (PM) - creates FRs/NFRs only (same as BMad Method)
 - **Solutioning:** Optional UX → architecture (Architect) → Optional extended workflows (security-architecture, devops-strategy) → create-epics-and-stories (PM) → implementation-readiness (Architect)
-- **Implementation:** sprint-planning → epic-tech-context → dev-story
+- **Implementation:** sprint-planning → create-story → dev-story
 
 **Key Difference:** Enterprise adds optional extended workflows AFTER architecture but BEFORE create-epics-and-stories. Everything else is identical to BMad Method.
 

package/src/modules/bmm/tasks/daily-standup.xml

@@ -0,0 +1,85 @@
+<task id="bmad/bmm/tasks/daily-standup.xml" name="Daily Standup">
+  <llm critical="true">
+    <i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>
+    <i>DO NOT skip steps or change the sequence</i>
+    <i>HALT immediately when halt-conditions are met</i>
+    <i>Each action tag within a step tag is a REQUIRED action to complete that step</i>
+    <i>Sections outside flow (validation, output, critical-context) provide essential context - review and apply throughout execution</i>
+  </llm>
+  <flow>
+    <step n="1" title="Project Context Discovery">
+      <action>Check for stories folder at {project-root}{output_folder}/stories/</action>
+      <action>Find current story by identifying highest numbered story file</action>
+      <action>Read story status (In Progress, Ready for Review, etc.)</action>
+      <action>Extract agent notes from Dev Agent Record, TEA Results, PO Notes sections</action>
+      <action>Check for next story references from epics</action>
+      <action>Identify blockers from story sections</action>
+    </step>
+
+    <step n="2" title="Initialize Standup with Context">
+      <output>
+        🏃 DAILY STANDUP - Story-{{number}}: {{title}}
+
+        Current Sprint Status:
+        - Active Story: story-{{number}} ({{status}} - {{percentage}}% complete)
+        - Next in Queue: story-{{next-number}}: {{next-title}}
+        - Blockers: {{blockers-from-story}}
+
+        Team assembled based on story participants:
+        {{ List Agents from {project-root}/bmad/_cfg/agent-manifest.csv }}
+      </output>
+    </step>
+
+    <step n="3" title="Structured Standup Discussion">
+      <action>Each agent provides three items referencing real story data</action>
+      <action>What I see: Their perspective on current work, citing story sections (1-2 sentences)</action>
+      <action>What concerns me: Issues from their domain or story blockers (1-2 sentences)</action>
+      <action>What I suggest: Actionable recommendations for progress (1-2 sentences)</action>
+    </step>
+
+    <step n="4" title="Create Standup Summary">
+      <output>
+        📋 STANDUP SUMMARY:
+        Key Items from Story File:
+        - {{completion-percentage}}% complete ({{tasks-complete}}/{{total-tasks}} tasks)
+        - Blocker: {{main-blocker}}
+        - Next: {{next-story-reference}}
+
+        Action Items:
+        - {{agent}}: {{action-item}}
+        - {{agent}}: {{action-item}}
+        - {{agent}}: {{action-item}}
+
+        Need extended discussion? Use *party-mode for detailed breakout.
+      </output>
+    </step>
+  </flow>
+
+  <agent-selection>
+    <context type="prd-review">
+      <i>Primary: Sarah (PO), Mary (Analyst), Winston (Architect)</i>
+      <i>Secondary: Murat (TEA), James (Dev)</i>
+    </context>
+    <context type="story-planning">
+      <i>Primary: Sarah (PO), Bob (SM), James (Dev)</i>
+      <i>Secondary: Murat (TEA)</i>
+    </context>
+    <context type="validate-architecture">
+      <i>Primary: Winston (Architect), James (Dev), Murat (TEA)</i>
+      <i>Secondary: Sarah (PO)</i>
+    </context>
+    <context type="implementation">
+      <i>Primary: James (Dev), Murat (TEA), Winston (Architect)</i>
+      <i>Secondary: Sarah (PO)</i>
+    </context>
+  </agent-selection>
+
+  <llm critical="true">
+    <i>This task extends party-mode with agile-specific structure</i>
+    <i>Time-box responses (standup = brief)</i>
+    <i>Focus on actionable items from real story data when available</i>
+    <i>End with clear next steps</i>
+    <i>No deep dives (suggest breakout if needed)</i>
+    <i>If no stories folder detected, run general standup format</i>
+  </llm>
+</task>

package/src/modules/bmm/testarch/knowledge/ci-burn-in.md

@@ -662,7 +662,7 @@ Before deploying your CI pipeline, verify:
 - [ ] **Artifact retention**: 30 days for reports, 7 days for failure artifacts
 - [ ] **Parallelization**: Matrix strategy uses fail-fast: false
 - [ ] **Burn-in enabled**: Changed specs run 5-10x before merge
-- [ ] **wait-on app startup**: CI waits for app (wait-on: 'http://localhost:3000')
+- [ ] **wait-on app startup**: CI waits for app (wait-on: '<http://localhost:3000>')
 - [ ] **Secrets documented**: README lists required secrets (API keys, tokens)
 - [ ] **Local parity**: CI scripts runnable locally (npm run test:ci)
 

package/src/modules/bmm/testarch/knowledge/overview.md

@@ -262,7 +262,7 @@ import { apiRequest } from '@seontechnologies/playwright-utils/api-request'; //
 
 The official `@seontechnologies/playwright-utils` repository provides working examples of all patterns described in these fragments.
 
-**Repository:** https://github.com/seontechnologies/playwright-utils
+**Repository:** <https://github.com/seontechnologies/playwright-utils>
 
 **Key resources:**
 

package/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-02-vision.md

@@ -12,8 +12,8 @@ workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/analysis/product-brief-{{project_name}}-{{date}}.md'
 
 # Task References
-advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
-partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
+advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml'
+partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md'
 ---
 
 # Step 2: Product Vision Discovery

package/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-03-users.md

@@ -12,8 +12,8 @@ workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/analysis/product-brief-{{project_name}}-{{date}}.md'
 
 # Task References
-advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
-partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
+advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml'
+partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md'
 ---
 
 # Step 3: Target Users Discovery

package/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-04-metrics.md

@@ -12,8 +12,8 @@ workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/analysis/product-brief-{{project_name}}-{{date}}.md'
 
 # Task References
-advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
-partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
+advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml'
+partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md'
 ---
 
 # Step 4: Success Metrics Definition

package/src/modules/bmm/workflows/1-analysis/product-brief/steps/step-05-scope.md

@@ -12,8 +12,8 @@ workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{output_folder}/analysis/product-brief-{{project_name}}-{{date}}.md'
 
 # Task References
-advancedElicitationTask: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
-partyModeWorkflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.md'
+advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml'
+partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md'
 ---
 
 # Step 5: MVP Scope Definition

package/src/modules/bmm/workflows/1-analysis/product-brief/workflow.md

@@ -1,5 +1,5 @@
 ---
-name: Product Brief Workflow
+name: create-product-brief
 description: Create comprehensive product briefs through collaborative step-by-step discovery as creative Business Analyst working with the user as peers.
 web_bundle: true
 ---

package/src/modules/bmm/workflows/1-analysis/research/domain-steps/step-01-init.md

@@ -25,7 +25,7 @@
 - **Research topic = "{{research_topic}}"** - discovered from initial discussion
 - **Research goals = "{{research_goals}}"** - captured from initial discussion
 - Focus on industry/domain analysis with web research
-- Web search capabilities with {{current_year}} data are enabled
+- Web search is required to verify and supplement your knowledge with current facts
 
 ## YOUR TASK:
 
@@ -48,7 +48,7 @@ Start with domain scope understanding:
 
 **Research Approach:**
 
-- Current {{current_year}} web data with rigorous source verification
+- All claims verified against current public sources
 - Multi-source validation for critical domain claims
 - Confidence levels for uncertain domain information
 - Comprehensive domain coverage with industry-specific insights
@@ -66,7 +66,7 @@ For **{{research_topic}}**, I will research:
 ✅ **Economic Factors** - market size, growth projections, economic impact
 ✅ **Supply Chain Analysis** - value chain, ecosystem, partnerships
 
-**All using current {{current_year}} web data with source verification.**
+**All claims verified against current public sources.**
 
 **Does this domain research scope and approach align with your goals?**
 [C] Continue - Begin domain research with this scope
@@ -77,7 +77,7 @@ For **{{research_topic}}**, I will research:
 
 - Document scope confirmation in research file
 - Update frontmatter: `stepsCompleted: [1]`
-- Load: `./step-02-industry-analysis.md`
+- Load: `./step-02-domain-analysis.md`
 
 ## APPEND TO DOCUMENT:
 
@@ -99,7 +99,7 @@ When user selects 'C', append scope confirmation:
 
 **Research Methodology:**
 
-- Current {{current_year}} web data with rigorous source verification
+- All claims verified against current public sources
 - Multi-source validation for critical domain claims
 - Confidence level framework for uncertain information
 - Comprehensive domain coverage with industry-specific insights
@@ -111,7 +111,7 @@ When user selects 'C', append scope confirmation:
 
 ✅ Domain research scope clearly confirmed with user
 ✅ All domain analysis areas identified and explained
-✅ Research methodology with {{current_year}} data emphasized
+✅ Research methodology emphasized
 ✅ [C] continue option presented and handled correctly
 ✅ Scope confirmation documented when user proceeds
 ✅ Proper routing to next domain research step
@@ -120,7 +120,7 @@ When user selects 'C', append scope confirmation:
 
 ❌ Not clearly confirming domain research scope with user
 ❌ Missing critical domain analysis areas
-❌ Not emphasizing {{current_year}} web data requirement
+❌ Not explaining that web search is required for current facts
 ❌ Not presenting [C] continue option
 ❌ Proceeding without user scope confirmation
 ❌ Not routing to next domain research step
@@ -131,6 +131,6 @@ When user selects 'C', append scope confirmation:
 
 ## NEXT STEP:
 
-After user selects 'C', load `./step-02-industry-analysis.md` to begin industry analysis with current {{current_year}} web data.
+After user selects 'C', load `./step-02-domain-analysis.md` to begin industry analysis.
 
 Remember: This is SCOPE CONFIRMATION ONLY - no actual domain research yet, just confirming the research approach and scope!

package/src/modules/bmm/workflows/1-analysis/research/domain-steps/step-02-domain-analysis.md

@@ -6,10 +6,10 @@
 
 - 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
 - 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
-- ✅ ALWAYS use {{current_year}} web searches for current industry data
+- ✅ Search the web to verify and supplement your knowledge with current facts
 - 📋 YOU ARE AN INDUSTRY ANALYST, not content generator
 - 💬 FOCUS on market size, growth, and industry dynamics
-- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
+- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
 - 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
 
 ## EXECUTION PROTOCOLS:
@@ -31,7 +31,7 @@
 
 ## YOUR TASK:
 
-Conduct industry analysis focusing on market size, growth, and industry dynamics using current {{current_year}} web data with rigorous source verification.
+Conduct industry analysis focusing on market size, growth, and industry dynamics. Search the web to verify and supplement current facts.
 
 ## INDUSTRY ANALYSIS SEQUENCE:
 
@@ -40,7 +40,7 @@ Conduct industry analysis focusing on market size, growth, and industry dynamics
 **UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different industry areas simultaneously and thoroughly.
 
 Start with industry research approach:
-"Now I'll conduct **industry analysis** for **{{research_topic}}** using current {{current_year}} web data to understand market dynamics.
+"Now I'll conduct **industry analysis** for **{{research_topic}}** to understand market dynamics.
 
 **Industry Analysis Focus:**
 
@@ -56,10 +56,10 @@ Start with industry research approach:
 
 **Execute multiple web searches simultaneously:**
 
-`WebSearch: "{{research_topic}} market size value {{current_year}}"`
-`WebSearch: "{{research_topic}} market growth rate dynamics {{current_year}}"`
-`WebSearch: "{{research_topic}} market segmentation structure {{current_year}}"`
-`WebSearch: "{{research_topic}} industry trends evolution {{current_year}}"`
+Search the web: "{{research_topic}} market size value"
+Search the web: "{{research_topic}} market growth rate dynamics"
+Search the web: "{{research_topic}} market segmentation structure"
+Search the web: "{{research_topic}} industry trends evolution"
 
 **Analysis approach:**
 
@@ -104,11 +104,11 @@ When saving to document, append these Level 2 and Level 3 sections:
 ### Market Size and Valuation
 
 [Market size analysis with source citations]
-_Total Market Size: [Current market valuation with {{current_year}} data]_
+_Total Market Size: [Current market valuation]_
 _Growth Rate: [CAGR and market growth projections]_
 _Market Segments: [Size and value of key market segments]_
 _Economic Impact: [Economic contribution and value creation]_
-_Source: [URL with {{current_year}} market size data]_
+_Source: [URL]_
 
 ### Market Dynamics and Growth
 
@@ -117,7 +117,7 @@ _Growth Drivers: [Key factors driving market growth]_
 _Growth Barriers: [Factors limiting market expansion]_
 _Cyclical Patterns: [Industry seasonality and cycles]_
 _Market Maturity: [Life cycle stage and development phase]_
-_Source: [URL with {{current_year}} market dynamics data]_
+_Source: [URL]_
 
 ### Market Structure and Segmentation
 
@@ -126,7 +126,7 @@ _Primary Segments: [Key market segments and their characteristics]_
 _Sub-segment Analysis: [Detailed breakdown of market sub-segments]_
 _Geographic Distribution: [Regional market variations and concentrations]_
 _Vertical Integration: [Supply chain and value chain structure]_
-_Source: [URL with {{current_year}} market structure data]_
+_Source: [URL]_
 
 ### Industry Trends and Evolution
 
@@ -135,7 +135,7 @@ _Emerging Trends: [Current industry developments and transformations]_
 _Historical Evolution: [Industry development over recent years]_
 _Technology Integration: [How technology is changing the industry]_
 _Future Outlook: [Projected industry developments and changes]_
-_Source: [URL with {{current_year}} industry trends data]_
+_Source: [URL]_
 
 ### Competitive Dynamics
 
@@ -144,14 +144,14 @@ _Market Concentration: [Level of market consolidation and competition]_
 _Competitive Intensity: [Degree of competition and rivalry]_
 _Barriers to Entry: [Obstacles for new market entrants]_
 _Innovation Pressure: [Rate of innovation and change]_
-_Source: [URL with {{current_year}} competitive dynamics data]_
+_Source: [URL]_
 ```
 
 ### 5. Present Analysis and Continue Option
 
 **Show analysis and present continue option:**
 
-"I've completed **industry analysis** using current {{current_year}} data to understand market dynamics for {{research_topic}}.
+"I've completed **industry analysis** for {{research_topic}}.
 
 **Key Industry Findings:**
 
@@ -190,7 +190,7 @@ Content is already written to document when generated in step 4. No additional a
 
 ## FAILURE MODES:
 
-❌ Not using {{current_year}} in industry web searches
+❌ Relying on training data instead of web search for current facts
 ❌ Missing critical market size or growth data
 ❌ Incomplete market structure analysis
 ❌ Not identifying key industry trends
@@ -208,7 +208,7 @@ Content is already written to document when generated in step 4. No additional a
 - Use authoritative sources (market research firms, industry associations)
 - Analyze market size, growth rates, and segmentation data
 - Study industry trends and evolution patterns
-- Focus on current {{current_year}} industry data
+- Search the web to verify facts
 - Present conflicting information when sources disagree
 - Apply confidence levels appropriately
 
@@ -225,4 +225,4 @@ Content is already written to document when generated in step 4. No additional a
 
 After user selects 'C', load `./step-03-competitive-landscape.md` to analyze competitive landscape, key players, and ecosystem analysis for {{research_topic}}.
 
-Remember: Always write research content to document immediately and emphasize current {{current_year}} industry data with rigorous source verification!
+Remember: Always write research content to document immediately and search the web to verify facts!