ss-create-branchlisted

# Create Development Branch Create a named development branch from the latest remote default branch, decide whether to develop in an isolated git worktree (explicit request > repository default > ask the user), push the branch immediately, and set up upstream tracking. ## Inputs - A branch name, a requirement link (issue/ticket/doc URL), or a plain-language description of the work. If none is given, ask. - Optional: `--from <branch>` to branch off something other than the remote default. - Optional: an explicit worktree preference (isolated worktree vs. develop in place) — if not given, follow Step 4's priority order below. - Optional: `--verify-baseline` to run the full test suite once after the worktree is ready, to confirm the baseline. Skipped by default because the branch starts as a zero-diff cut of the remote base, so its baseline already equals whatever CI last confirmed. ## Step 1 — Determine the branch slug Derive the slug (the name portion after the type prefix) from the input: | Input | Example | Slug | |-------|---------|------| | Plain text | "add payment", "login fix 123" | Lowercase, spaces → hyphens | | A requirement/ticket link | `https://tracker.example.com/issues/10442755` | If a numeric ID is visible in the URL, use it directly; otherwise fetch and summarize | | A document link | any URL to a spec/PRD | Fetch its content with your document-reading tool and summarize to a 2–4 word English slug | | Pasted markdown/text | `# Add User API\n...` | Extrac