Session Isolation Pattern Session-based artifact isolation for multi-artifact workflows. Use when orchestrating workflows that generate multiple files (designs, reviews, reports) to prevent file collisions across concurrent or sequential sessions. Problem When multiple workflows run (even sequentially), artifacts with the same name collide: Solution Use unique session folders to isolate artifacts: Implementation Pattern 1. Session Initialization (Orchestrator) Add to Phase 0 of your orchestrator command: 2. Pass SESSION PATH to Sub-Agents Include in all agent prompts: 3. Sub-Agent SESSION PAT…