What problem does it solve? Task silos often need the same backend, frontend, worker, or mock services running, and cloning them repeatedly per task wastes effort and causes port or branch conflicts. This Skill standardizes how project-level shared runtime sets are registered, prepared, and referenced across silos. ## Core Features & Use Cases - Runtime Registry Management: Defines a structured registry schema with fields like project_id, runtime_kind, workspace_path, branch, commit, ports, and health_check for long-lived runtime checkouts. - Layered Governance: Separates 0-tier system rules, 1-tier project registry values, and 3-tier silo-local runtime references so secrets and project data never leak into the system layer. - Health Check & Safety Gates: Verifies dirty state, running processes, and port conflicts before preparing checkouts, and records structured health check results. - Use Case: A project needs a shared backend and DB emulator that five task silos reference. Use this Skill to register the runtime set, prepare it under shared-runtime/<project-id>/, and record branch, commit, and health check results for each silo's goal.md. ## Quick Start Ask the agent to register a shared backend runtime for your project and prepare its workspace checkout with branch, commit, and health check recorded.
