orcakit

# orcakit Thin glue between two systems that each own half of "take an issue from ready to landed": a GitHub issue tracker (labels say *what* is workable) and [Orca](https://orca.computer) worktrees (an isolated branch + workspace is *where* it gets worked). orcakit doesn't add tracker or worktree behavior — it **sequences** the two at the two moments they meet: `start <n>` and `finish <n>`. It leans on two companion skills where they exist — **issuekit** for the GitHub lifecycle and **orca-cli** for worktree operations — but hard-depends on neither: everything runs through the `gh` and `orca` CLIs directly, so orcakit works with just those installed. ## When this fires The user wants to move an issue between "ready to work" and "landed": - **start** — "start issue #12", "spin up a worktree for #12", "begin #12", "orcakit start 12". - **finish** — "finish #12", "wrap up #12 now the PR merged", "tear down #12's worktree", "orcakit finish 12". If they name neither action explicitly but reference an issue and a worktree, ask which. orcakit never *implements* — it only prepares or tears down the workspace; writing code inside the worktree is a separate step. ## Preflight Confirm both CLIs are ready before mutating anything: ```sh gh --version && gh auth status # GitHub CLI installed + authenticated gh repo view --json nameWithOwner -q .nameWithOwner # inside a repo ``` - If `gh` is missing or unauthenticated, say so and point to `https://cli.github.com` / `gh...