What problem does it solve? Prototype work across multiple tickets often collides in shared checkouts, loses track of accepted baselines, or leaves orphaned branches and running dev servers. This Skill enforces a disciplined repository lifecycle so every prototype request gets an isolated branch and worktree, a recorded ticket identity, and a clean commit, integration, and cleanup sequence. ## Core Features & Use Cases - Repository and Worktree Isolation: Resolves or initializes a canonical prototype repository and creates one dedicated branch and Git worktree per ticket, preventing collisions between concurrent requests. - Baseline and Bootstrap Boundary: Coordinates a fixed handoff payload to a bootstrapper for current-experience baselines, then reviews, accepts, and integrates the baseline before future-state work begins. - Commit, Integration, and Cleanup: Commits accepted results, integrates ticket branches into the canonical base under repository policy, promotes approved previews to the default entry point, and safely removes worktrees after evidence is durable. - Use Case: A product prototyper receives a new requirements ticket; the Skill creates prototype/<ticket-id> branch and worktree, records runtime port ownership, and after approval commits and merges the result while moving the ticket from tickets/in-progress/ to tickets/done/. ## Quick Start Set up an isolated ticket branch and worktree in the prototype repository for this new requirements request and record its ticket state.
