/context-load-temporal

allowed-tools: WebFetch, Read, Write, Bash(curl:*), Bash(jq:*), Bash(gdate:*), Task
name: "Context Load Temporal"
description: "Load comprehensive Temporal workflow orchestration context with adaptive research and enterprise-grade implementation patterns"
author: "wcygan"
tags: ["context","web"]
version: "1.0.0"
created_at: "2025-07-14T00:00:00Z"
updated_at: "2025-07-14T00:00:00Z"

Context

• Session ID: !`gdate +%s%N`
• Current directory: !`pwd`
• Target technology: Temporal Workflow Orchestration
• Documentation base: https://docs.temporal.io/
• Project type detection: !`fd "(go\.mod|Cargo\.toml|package\.json|pom\.xml|requirements\.txt)" . -d 2 | head -3 || echo "No project files detected"`
• Existing Temporal usage: !`rg "temporal" . --type go --type rust --type java --type typescript --type python -i | head -5 || echo "No Temporal usage detected"`
• Documentation availability: !`curl -s --head https://docs.temporal.io/ | head -1 || echo "Documentation unavailable"`
• Context loading strategy: comprehensive_parallel_research

Your Task

STEP 1: Initialize Temporal context loading session

• CREATE session state file: `/tmp/temporal-context-$SESSION_ID.json`
• SET initial state:

  {
    "sessionId": "$SESSION_ID",
    "target": "temporal-workflow-orchestration",
    "phase": "initialization",
    "project_context": "auto-detect",
    "documentation_sources": [],
    "research_domains": [
      "core-concepts",
      "workflow-patterns",
      "activity-patterns",
      "testing-strategies",
      "deployment-patterns",
      "monitoring-observability",
      "performance-optimization",
      "enterprise-patterns"
    ],
    "loaded_contexts": {},
    "implementation_examples": [],
    "best_practices": [],
    "checkpoints": []
  }

• INITIALIZE comprehensive documentation loading workspace

STEP 2: Project-specific context detection and research strategy

Think hard about the optimal context loading strategy based on detected project characteristics and existing Temporal usage patterns.

Think deeper about enterprise-grade implementation requirements, performance optimization strategies, and production deployment considerations for Temporal workflows.

• ANALYZE project context from detection commands
• DETERMINE primary development language and framework
• IDENTIFY existing Temporal integration patterns
• ASSESS documentation complexity and scope requirements

IF existing Temporal usage detected:

• SET research_focus = "enhancement_and_optimization"
• PRIORITIZE advanced patterns, performance tuning, and enterprise features
• FOCUS on integration patterns with existing codebase

ELSE IF project files detected:

• SET research_focus = "implementation_planning"
• PRIORITIZE getting-started guides, basic patterns, and language-specific examples
• FOCUS on setup, configuration, and foundational concepts

ELSE:

• SET research_focus = "comprehensive_overview"
• LOAD complete Temporal ecosystem knowledge
• FOCUS on architectural understanding and technology evaluation

STEP 3: Parallel documentation loading with comprehensive coverage

TRY:

IF research_focus == "comprehensive_overview":

• USE Task tool to delegate parallel documentation loading with 5 specialized agents:

1. **Core Concepts Agent**: Load fundamental Temporal concepts

• WebFetch: `https://docs.temporal.io/concepts`
• FOCUS: workflows, activities, workers, task queues, durable execution
• SAVE findings: `/tmp/temporal-context-$SESSION_ID/core-concepts.json`

2. **Architecture & Deployment Agent**: Load system architecture and deployment patterns

• WebFetch: `https://docs.temporal.io/production-deployment`
• FOCUS: cluster setup, scaling, security, high availability
• SAVE findings: `/tmp/temporal-context-$SESSION_ID/architecture.json`

3. **Development Patterns Agent**: Load development guides and best practices

• WebFetch: `https://docs.temporal.io/dev-guide`
• FOCUS: workflow development, testing, debugging, versioning
• SAVE findings: `/tmp/temporal-context-$SESSION_ID/development.json`

4. **Language Integration Agent**: Load language-specific implementations

• WebFetch: `https://docs.temporal.io/dev-guide/sdks`
• FOCUS: Go, Java, TypeScript, Python, .NET SDKs
• SAVE findings: `/tmp/temporal-context-$SESSION_ID/language-sdks.json`

5. **Enterprise Features Agent**: Load enterprise-grade features and patterns

• WebFetch: `https://docs.temporal.io/security`
• FOCUS: security, compliance, multi-tenancy, governance
• SAVE findings: `/tmp/temporal-context-$SESSION_ID/enterprise.json`

ELSE IF research_focus == "implementation_planning":

• EXECUTE focused context loading based on detected project type:
• WebFetch primary documentation areas relevant to detected language
• PRIORITIZE quick-start guides and basic implementation patterns
• LOAD configuration and setup documentation
• GATHER testing and debugging strategies

ELSE:

• PERFORM targeted context enhancement:
• WebFetch advanced topics and optimization guides
• FOCUS on performance tuning and enterprise patterns
• LOAD troubleshooting and operational guides
• GATHER monitoring and observability best practices

CATCH (documentation_unavailable):

• LOG unavailable sources to session state
• CONTINUE with available documentation sources
• PROVIDE offline documentation recommendations
• INCLUDE alternative learning resources and community content

STEP 4: Comprehensive Temporal knowledge synthesis

• ORGANIZE loaded context by implementation priority:
• Foundation: Core concepts and architecture understanding
• Setup: Installation, configuration, and basic workflow creation
• Development: Advanced patterns, testing, and debugging
• Production: Deployment, monitoring, and enterprise features
• Optimization: Performance tuning and scalability patterns

• SYNTHESIZE project-specific guidance:
• Integration strategies for detected te