collab

# Collaboration State Management

Track collaboration state between Claude sessions using git branches. Enables seamless context switching between conversations by persisting progress in feature branches.

## When to Use

- Starting multi-session work that needs tracking
- Saving progress during long coding sessions
- Handing off work to another conversation
- Resuming previous collaboration branches
- Publishing completed work to master

## When NOT to Use

- Simple one-off tasks that don't need tracking
- Work already on master without branching
- Non-git repositories

---

## Quick Start

1. **Start:** `/collab start project/P16/plan` - Create feature branch
2. **Work:** Make changes, use `/collab save "message"` periodically
3. **Handoff:** `/collab checkpoint "message"` - Commit + push for later
4. **Resume:** `/collab resume project/P16/plan` - Continue in new session
5. **Publish:** `/collab publish` - Merge to master when complete

---

## Commands

| Command | Action |
|---------|--------|
| `/collab` | Show current status |
| `/collab start <branch>` | Create new collaboration branch |
| `/collab save "message"` | Commit progress locally |
| `/collab checkpoint "message"` | Commit + push for handoff |
| `/collab publish` | Fast-forward merge to master, cleanup |
| `/collab resume <branch>` | Resume existing branch |
| `/collab list` | List all collaboration branches |
| `/collab abandon` | Delete current feature branch (with confirmation) |

---

## Branch Naming

**Vaults:** `<scope>/<id>/<segment>` (e.g., `project/P16/plan`, `goal/Q1-2026/review`)

**Code repos:** `<type>/<id>/<description>` (e.g., `feature/P3/parser`, `bug/P1/fix`)

See [Branch Naming Reference](references/branch-naming.md) for full conventions.

---

## Commit Formats

- **Vaults:** `[collab:<branch>] <message>` (tag in title)
- **Code repos:** Conventional Commits with `[collab:<branch>]` in body

See [Commit Formats Reference](references/commit-formats.md) for examples.

---

## Skil