What problem does it solve? When acting as the central controller of a multi-track parallel Story pipeline, it is easy to misjudge execution carriers, misread manual-track status, skip GATE evidence checks, delay commits, or kill healthy workers. This Skill codifies the behavioral discipline (SOP-1 through SOP-7) that prevents those failures. ## Core Features & Use Cases - Execution Carrier Judgment: Decide whether a card goes to a dispatched worker sub-window or a manual track based on whether it modifies pipeline machinery itself. - Dispatch Loop & GATE Evidence Chain: Run the event-driven five-step dispatch loop and verify the six-item GATE evidence chain (status file, DB lifecycle, tasks, PID exit, red flags, deep checks) before advancing. - Commit Wave Timing & Cross-Window Coordination: Commit per-card immediately after CR passes GATE using pathspec, coordinate freeze windows with manual tracks, and follow a 7-case anomaly handling manual. - Use Case: While orchestrating parallel dev cards, you check the manual track's lifecycle timestamps before dispatching, detect a four-dimension overlap (build/verify/load/self-run) between two cards, and sequence them instead of dispatching in parallel. ## Quick Start Act as the central controller for the multi-track pipeline and plan the dispatch order for these story cards, checking manual-track status and overlap before each dispatch.
