What problem does it solve? Setting up an isolated git worktree for parallel feature development normally requires manual steps: creating the branch, installing dependencies, copying environment files, and provisioning a backend deployment. This Skill automates that entire setup in one command. ## Core Features & Use Cases - Three Input Modes: Invoke with no arguments (prompts for scope), a ticket markdown file (derives branch name from its type and title), or free-text requirements (infers prefix from intent). - Branch Naming Conventions: Enforces kebab-case slugs with prefixes like feature-, fix-, refactor-, docs-, chore-, or improvements-, capped at 40 characters. - Full Environment Provisioning: Runs pnpm install, copies apps/mirror/.env.local, provisions an expiring per-worktree Convex dev deployment, syncs secrets, pushes code, seeds demo data, and allowlists the owner's git email. - Use Case: You receive a bug ticket fix-nav-transition.md and want to work on it without disturbing your current checkout. Run the Skill with the ticket path and get a ready-to-use worktree at .worktrees/fix-nav-transition-bug with its own Convex backend. ## Quick Start Ask the AI to create a new worktree for your ticket file or requirement, for example by invoking /new-worktree with a ticket markdown path or a short description of the work.
