docs: remove deleted template references

Author: tbrandenburg

AGENTS.md

@@ -292,7 +292,7 @@ Agents must NOT:
 
 **Agent Priority: Use templates first when creating workflows**
 
-flowsh includes a comprehensive template system with 14 production-ready workflows. Agents should **always start with templates** rather than creating workflows from scratch.
+flowsh includes a comprehensive template system with 8 production-ready workflows. Agents should **always start with templates** rather than creating workflows from scratch.
 
 **Template Discovery:**
 
@@ -305,12 +305,10 @@ flowsh init --help            # Same as above
 
 - **Enhanced (4)**: Simple, ready-to-use templates
   - `ai-to-telegram-simple`, `data-pipeline-simple`, `ai-to-telegram`, `data-pipeline`
-- **Advanced (10)**: Complex workflows by subcategory
-  - `ai-workflows/`: `ai-chat-memory`, `multi-stage-ai-workflows`
-  - `content-distribution/`: `content-moderation`, `multi-format-distribution`, `scheduled-content-generation`
-  - `data-processing/`: `data-validation-cleanup`, `parallel-processing-aggregation`
-  - `devops-automation/`: `automated-testing-monitoring`
-  - `meta-workflows/`: `interactive-workflow-builder`
+- **Advanced (4)**: Complex workflows by subcategory
+  - `ai-workflows/`: `ai-chat-memory`
+  - `content-distribution/`: `content-moderation`
+  - `data-processing/`: `data-validation-cleanup`
   - `reliability/`: `circuit-breaker`
 
 **Template Usage Pattern for Agents:**

PRPs/FLOWSH_INIT_COMMAND_20250107.md

@@ -60,7 +60,6 @@ class TemplateDiscovery {
     // Support multiple lookup formats:
     // - circuit-breaker-template
     // - circuit-breaker
-    // - automated-testing-monitoring-template
   }
 
   getHierarchicalDisplay(): HierarchicalTemplates {

PRPs/INITIAL_FLOWSH_INIT.md

@@ -83,7 +83,7 @@ flowsh init ai-to-telegram-simple my-bot.yaml
 flowsh init circuit-breaker workflows/resilient-api.yaml
 
 # Create workflow from advanced template
-flowsh init automated-testing-monitoring ci-pipeline.yaml
+flowsh init ai-chat-memory chat-session.yaml
 ```
 
 **Expected Output Format:**
@@ -106,20 +106,12 @@ Available templates:
   advanced:
     ai-workflows:
       - ai-chat-memory-template
-      - multi-stage-ai-workflows-template
     reliability:
       - circuit-breaker-template
-    devops-automation:
-      - automated-testing-monitoring-template
     content-distribution:
       - content-moderation-template
-      - multi-format-distribution-template
-      - scheduled-content-generation-template
     data-processing:
       - data-validation-cleanup-template
-      - parallel-processing-aggregation-template
-    meta-workflows:
-      - interactive-workflow-builder-template
 ```
 
 **Error Handling Examples:**

PRPs/PHASE2_create_advanced_templates.md

@@ -287,156 +287,6 @@ graph:
           **History Size:** ${#updated_history} characters
 ```
 
-### Example 3: Multi-Format Content Distribution Template
-
-```yaml
-# multi-format-distribution-template.yaml
-metadata:
-  template_name: 'Multi-Channel Content Distribution'
-  category: 'content-distribution'
-  intent_keywords:
-    [
-      'multi channel',
-      'content distribution',
-      'social media',
-      'cross platform',
-      'content syndication',
-    ]
-  success_rate: 73
-  deployment_time: '9 minutes'
-  complexity_level: 'advanced'
-
-  skill_guidance:
-    variable_flow_pattern: 'source_content → [format_a, format_b, format_c] → [channel_a, channel_b, channel_c]'
-    parallel_execution: 'format transformations run concurrently'
-    distribution_strategy: 'channel-specific optimization'
-
-workflow:
-  name: 'Multi-Format Content Distribution'
-  description: 'Generate content and distribute across multiple channels with format optimization'
-
-variables:
-  content_topic: 'workflow automation best practices'
-  content_style: 'professional'
-
-graph:
-  nodes:
-    - id: 'generate_source_content'
-      type: 'llm'
-      data:
-        title: 'Generate Source Content'
-        model: { name: 'gpt-4' }
-        prompt: |
-          Create comprehensive content about: ${content_topic}
-
-          Style: ${content_style}
-          Length: 800-1000 words
-          Format: Well-structured with clear sections
-
-          This content will be adapted for multiple channels, so make it informative and engaging.
-
-    # Parallel format transformations
-    - id: 'format_for_twitter'
-      type: 'template-transform'
-      data:
-        title: 'Format for Twitter Thread'
-        template: |
-          🧵 Thread: ${content_topic}
-
-          {{#split llm_content 280}}
-          {{thread_number}}/{{total_threads}} {{content_chunk}}
-
-          {{#if is_last}}#WorkflowAutomation #Productivity{{/if}}
-          {{/split}}
-        output_variable: 'twitter_content'
-
-    - id: 'format_for_linkedin'
-      type: 'template-transform'
-      data:
-        title: 'Format for LinkedIn Post'
-        template: |
-          🚀 **${content_topic}** 
-
-          ${llm_content:0:1200}
-
-          Key takeaways in comments 👇
-
-          #WorkflowAutomation #Productivity #AI #Automation
-        output_variable: 'linkedin_content'
-
-    - id: 'format_for_email'
-      type: 'template-transform'
-      data:
-        title: 'Format for Email Newsletter'
-        template: |
-          Subject: ${content_topic} - Weekly Insights
-
-          <!DOCTYPE html>
-          <html>
-          <body>
-            <h1>${content_topic}</h1>
-            <div>${llm_content}</div>
-            <p>Best regards,<br>Your Automation Team</p>
-          </body>
-          </html>
-        output_variable: 'email_content'
-
-    # Parallel distribution
-    - id: 'distribute_to_telegram'
-      type: 'telegram'
-      data:
-        message: '${twitter_content}'
-        parse_mode: 'HTML'
-
-    - id: 'post_to_webhook'
-      type: 'http-request'
-      data:
-        title: 'Post to LinkedIn via Webhook'
-        url: '${LINKEDIN_WEBHOOK_URL}'
-        method: 'POST'
-        headers:
-          Content-Type: 'application/json'
-        body: |
-          {
-            "platform": "linkedin",
-            "content": "${linkedin_content}",
-            "schedule": "immediate"
-          }
-
-    - id: 'send_email'
-      type: 'http-request'
-      data:
-        title: 'Send Email Newsletter'
-        url: '${EMAIL_API_ENDPOINT}'
-        method: 'POST'
-        headers:
-          Authorization: 'Bearer ${EMAIL_API_TOKEN}'
-        body: |
-          {
-            "to": "${EMAIL_LIST_ID}",
-            "subject": "${content_topic} - Weekly Insights",
-            "html": "${email_content}"
-          }
-
-    - id: 'distribution_summary'
-      type: 'answer'
-      data:
-        title: 'Multi-Channel Distribution Complete'
-        answer: |
-          📢 **Content Distribution Summary**
-
-          **Source Topic:** ${content_topic}
-          **Content Generated:** ${#llm_content} characters
-
-          **Distribution Channels:**
-          ✅ Twitter: ${#twitter_content} characters (thread format)
-          ✅ LinkedIn: ${#linkedin_content} characters (professional format)  
-          ✅ Email: HTML newsletter sent to ${EMAIL_LIST_ID}
-          ✅ Telegram: Posted to channel
-
-          **Distribution Status:** All channels updated successfully
-```
-
 ## DOCUMENTATION:
 
 ### Technical Foundation References

PRPs/fix-template-variable-initialization-systematic.md

@@ -7,8 +7,6 @@
 **Current Failures**:
 
 - `content-moderation-template.yaml`: `PROFANITY_WORDS: unbound variable` (line 553)
-- `multi-format-distribution-template.yaml`: `email_content: unbound variable` (line 1096)
-- `scheduled-content-generation-template.yaml`: `MAIN_CONTENT: unbound variable` (line 582)
 - `circuit-breaker-template.yaml`: `PRIMARY_SUCCESS: unbound variable` (line 479)
 
 **Root Cause**: Templates use extensive `environment_variables` sections that declare variables for template processing, but the actual shell script generation doesn't properly initialize these as global shell variables before they're used in code node bash blocks.
@@ -171,22 +169,6 @@ IMPORTANT: Execute every task in order, top to bottom. Each task is atomic and i
 - **GOTCHA**: Keep template functionality but reduce variable complexity
 - **VALIDATE**: `cd /home/tom/workspace/ai/made/workspace/flowsh && flowsh validate templates/advanced/content-distribution/content-moderation-template.yaml`
 
-### SIMPLIFY templates/advanced/content-distribution/multi-format-distribution-template.yaml
-
-- **IMPLEMENT**: Similar simplification to content-moderation template
-- **PATTERN**: Essential variables only, local variables for single-use cases
-- **REMOVE**: Unnecessary environment variable declarations
-- **GOTCHA**: Maintain template's educational value while reducing complexity
-- **VALIDATE**: `cd /home/tom/workspace/ai/made/workspace/flowsh && flowsh validate templates/advanced/content-distribution/multi-format-distribution-template.yaml`
-
-### SIMPLIFY templates/advanced/content-distribution/scheduled-content-generation-template.yaml
-
-- **IMPLEMENT**: Reduce variable complexity similar to other templates
-- **PATTERN**: Simple environment_variables section with clear defaults
-- **REMOVE**: Over-engineered variable processing
-- **GOTCHA**: Focus on showing node functionality rather than variable processing
-- **VALIDATE**: `cd /home/tom/workspace/ai/made/workspace/flowsh && flowsh validate templates/advanced/content-distribution/scheduled-content-generation-template.yaml`
-
 ### SIMPLIFY templates/advanced/reliability/circuit-breaker-template.yaml
 
 - **IMPLEMENT**: Simplify circuit breaker template variables
@@ -273,17 +255,13 @@ cd /home/tom/workspace/ai/made/workspace/flowsh && npm test -- --grep "shell.*ge
 
 ```bash
 cd /home/tom/workspace/ai/made/workspace/flowsh && flowsh validate templates/advanced/content-distribution/content-moderation-template.yaml
-cd /home/tom/workspace/ai/made/workspace/flowsh && flowsh validate templates/advanced/content-distribution/multi-format-distribution-template.yaml
-cd /home/tom/workspace/ai/made/workspace/flowsh && flowsh validate templates/advanced/content-distribution/scheduled-content-generation-template.yaml
 cd /home/tom/workspace/ai/made/workspace/flowsh && flowsh validate templates/advanced/reliability/circuit-breaker-template.yaml
 ```
 
 ### Level 4: Compilation Testing
 
 ```bash
 cd /home/tom/workspace/ai/made/workspace/flowsh && flowsh compile templates/advanced/content-distribution/content-moderation-template.yaml >/dev/null
-cd /home/tom/workspace/ai/made/workspace/flowsh && flowsh compile templates/advanced/content-distribution/multi-format-distribution-template.yaml >/dev/null
-cd /home/tom/workspace/ai/made/workspace/flowsh && flowsh compile templates/advanced/content-distribution/scheduled-content-generation-template.yaml >/dev/null
 cd /home/tom/workspace/ai/made/workspace/flowsh && flowsh compile templates/advanced/reliability/circuit-breaker-template.yaml >/dev/null
 ```
 
@@ -297,7 +275,7 @@ cd /home/tom/workspace/ai/made/workspace/flowsh && timeout 900 make qa
 
 ## ACCEPTANCE CRITERIA
 
-- [ ] All 4 failing templates now pass compilation and execution
+- [ ] All failing templates now pass compilation and execution
 - [ ] No "unbound variable" errors in any template
 - [ ] Templates are simplified to focus on node functionality rather than variable complexity
 - [ ] All unit tests pass with enhanced variable handling

PRPs/opencode-poem-telegram-template-prp-20250109.md

@@ -32,7 +32,6 @@ Create a new flowsh template called "opencode-poem-telegram" that combines OpenC
 
 1. **`ai-to-telegram-simple.yaml`** - For Telegram integration patterns and environment validation
 2. **`simple-workflow.yaml`** - For opencode agent node usage pattern
-3. **`multi-stage-ai-workflows-template.yaml`** - For creative content generation structure
 
 ### Expected Output Example:
 

README.md

@@ -137,12 +137,10 @@ flowsh init --help
   - `ai-to-telegram` - Production-ready AI content generation
   - `data-pipeline` - Advanced data processing pipeline
 
-- **Advanced (10 templates)** - Complex workflows organized by use case:
-  - **AI Workflows**: `ai-chat-memory`, `multi-stage-ai-workflows`
-  - **Content Distribution**: `content-moderation`, `multi-format-distribution`, `scheduled-content-generation`
-  - **Data Processing**: `data-validation-cleanup`, `parallel-processing-aggregation`
-  - **DevOps**: `automated-testing-monitoring`
-  - **Meta**: `interactive-workflow-builder`
+- **Advanced (4 templates)** - Complex workflows organized by use case:
+  - **AI Workflows**: `ai-chat-memory`
+  - **Content Distribution**: `content-moderation`
+  - **Data Processing**: `data-validation-cleanup`
   - **Reliability**: `circuit-breaker`
 
 ### compile