What problem does it solve? Starting a development phase without checking readiness leads to half-opened work: branches cut from dirty trees, wrong base branches, or stories that were never refined. This Skill enforces a hard entry gate before any phase begins, so every phase starts from a clean, verified state. ## Core Features & Use Cases - Explicit scope resolution: Resolves a phase, chat, or epic target into a concrete story list and echoes it for review before anything is created. - Three-part entry gate: Verifies a clean working tree, that the current branch is main, and that every story carries a ready status, aborting with a specific gap list if any check fails. - Safe branch creation: Surfaces a copy-pasteable git switch command to cut the phase branch off main, never force-creating or overwriting an existing branch. - Board synchronization: Records the phase opening in MONITOR.md and ACTIVE.md and regenerates the dashboard in one atomic step. - Use Case: Before running an execute-batch on chat CHAT-01, invoke this Skill to confirm all stories are ready, cut the phase/chat-01 branch, and update the project board. ## Quick Start Ask the assistant to start phase CHAT-01 so it verifies the entry gate, cuts the phase branch off main, and records the opening on the board.