cfn-loop-orchestration-v2-legacy-skill

Migration from Bash orchestration to TypeScript-based CFN Loop involves transitioning container spawning, Redis context management, and consensus logic to the newer implementation. This Skill provides historical reference and migration guidance for teams moving away from the legacy Bash path. Consult the migration documentation included in this archive for step-by-step transition planning.

A Bash orchestrator manages task analysis, Redis-backed context storage, Docker container spawning across Loop implementers and validators, progress monitoring, confidence scoring, and consensus-driven decision gates for Product Owner workflows. This legacy version is archived; new deployments should use the TypeScript-based orchestrator.

The Bash-based orchestrator is archived and marked for legacy reference only. New deployments should use the TypeScript-based orchestrator instead. This Skill is valuable as a historical reference and for teams planning migration paths from existing Bash implementations.

The orchestrator requires Docker for container management and Redis for context state persistence across agent spawning and consensus collection. These dependencies enable the distributed agent ecosystem spanning Loop 3 implementers, Loop 2 validators, and Loop 4 decision flows.

Consensus gating collects confidence scores from validator agents, applies gate-driven decision logic, and triggers Product Owner workflows when thresholds are met. The Bash implementation manages this through progress monitoring and consensus aggregation before advancing to downstream decision stages.