spec-kitty-git-workflow

# spec-kitty-git-workflow Understand the boundary between what spec-kitty's Python code does with git and what LLM agents are expected to do. This boundary is critical — agents that try to create worktrees manually or skip implementation commits will break the workflow. --- ## The Core Boundary **Python handles infrastructure git** — worktrees, lane commits, merges, cleanup. **Agents handle content git** — implementation commits, rebases, conflict resolution. | Git Operation | Who Does It | When | |---|---|---| | `git worktree add` | Python | `spec-kitty implement WP##` | | `git commit` (planning artifacts) | Python | Before worktree creation | | `git commit` (lane transitions) | Python | WP moves to doing/for_review | | `git commit` (implementation code) | **Agent** | After writing code in worktree | | `git rebase` (stale lane sync) | **Agent** | When the mission branch advanced and the lane must resync | | `git merge` (lane → mission → target) | Python | `spec-kitty merge` | | `git push` | Python (opt-in) | `spec-kitty merge --push` only | | `git push` | **Agent** | Any other push scenario | | Conflict resolution | **Agent** | During rebase or manual merge | | `git worktree remove` | Python | After successful merge | | `git branch -d` (cleanup) | Python | After successful merge | --- ## What Python Does Automatically ### 1. Worktree Creation When you run `spec-kitty implement WP01`, Python: ``` git worktree add -b kitty/mission-042-mission-lane-a .worktrees/042-mi...