---
name: snipara-safe-parallel-work
description: "Coordinate safe parallel work with Snipara Team Sync, collaboration sessions, claims, leases, guard checks, handoffs, and conflict outcomes. Use before editing shared files, taking over work, resuming a dirty workspace, committing, pushing, deploying, or running migrations in a team or multi-agent environment."
---

# Snipara Safe Parallel Work

## Start Or Resume

Before editing in a shared repository, check what changed and whether another human or agent owns the same surface.

```bash
npx -y snipara-companion@latest workflow resume --include-session-context
npx -y snipara-companion@latest team-sync what-changed
npx -y snipara-companion@latest collaboration status
```

For new work, leave a visible breadcrumb:

```bash
npx -y snipara-companion@latest team-sync start-work --summary "<task>" --files <files...>
```

## Guard Before Risk

Run collaboration guards before large edits, commits, pushes, deploys, migrations, schema work, package releases, or work on files likely to be touched by others.

```bash
npx -y snipara-companion@latest collaboration guard --files <files...>
npx -y snipara-companion@latest collaboration guard --profile pre-commit --enforce
npx -y snipara-companion@latest collaboration guard --profile pre-push --enforce
npx -y snipara-companion@latest collaboration guard --profile pre-deploy --enforce
```

Treat outcomes as follows:

- `CLEAR`: proceed.
- `WATCH`: proceed, but leave a handoff and watch the surface.
- `REQUIRES_ACK` or `REVIEW_REQUIRED`: coordinate explicitly before proceeding.
- `BLOCKED`: stop until the conflict, lease, or ownership issue is resolved.

## Claims And Leases

Use exclusive claims only for genuinely risky surfaces such as schema, migrations, deployment scripts, auth, billing, package publication, or production data handling. Release claims when work finishes or becomes blocked.

## Handoff

End multi-agent work with a concise handoff:

```bash
npx -y snipara-companion@latest team-sync handoff --summary "<changed>" --next "<recommended next action>" --files <files...> --attention watch
```

Do not treat stale local warnings as final truth. Verify hosted active sessions and leases before blocking useful work.