workflow-team

name	workflow-team
description	Coordinate solo vs team development on a shared harness backlog — claim, branch, per-assignee WIP=1, PR integration gate, handoff, and features.json conflict resolution. Use when: multiple people/agents share one backlog, deciding solo vs team mode, claiming/branching a US, resolving a features.json claim conflict, or handing off a half-done US.

One-Liner

The git-tracked backlog is the only coordination layer: a claim is real once pushed, integration goes through a PR review gate, and the first committer wins every features.json conflict — so no two people silently work the same US.

The backlog (.harness/features.json, git-tracked) is the coordination layer — not chat, not a spreadsheet. This skill defines how solo and team runs differ; everything else (the phase chain, gates) is shared with workflow-feature.

Solo vs team

	solo (default)	team
WIP	global WIP=1	WIP=1 per assignee
Claim	none	./harness start <id> --assignee <name> --branch
Integration	checkpoint on current branch	feature branch → PR review gate → merge
Auto-advance	allowed (esp. Non-Technical)	off — each assignee holds one US

Record the choice in the task-state Collab: field (set at workflow-intake Phase 3).

Gate: the run's mode (solo/team) is recorded and everyone follows the matching WIP rule.

Team loop (per developer)

git pull                                          # 1. features.json current
./harness start <id> --assignee <you> --branch    # 2. claim + branch
git commit -am "claim <id>" && git push           #    claim is real only once pushed
# … 3. standard phase chain on your branch (review + tests + verify) …
# 4. open PR → check-pr-review gate must pass before merge
git commit -am "<id> passing" && git push         # 5. publish status to teammates

1. Pull first — git pull before claiming, so features.json is current.
2. Claim & start — ./harness start <id> --assignee <you> --branch; commit + push the features.json change immediately (claim is only real once pushed).
3. Work the standard phase chain on your branch — including an independent role-based review (scripts/role-resolver.sh --phase review + harness review open/record provenance) — plus the required tests + verify.
4. Integrate — open a PR; the review gate (check-pr-review) must pass before merge.
5. Push status — when verify marks the US passing, commit features.json and push so teammates see it on git pull.

Gate: your claim is pushed before you start work, and the US is merged only after check-pr-review passes and the passing status is pushed.

Handoff (mid-US)

./harness session stop writes docs/session-handoff.md. Commit it with plan.md + evidence.md

• features.json. The incoming developer reads all three before ./harness start <id> --force (re-assign), then pushes immediately.

Gate: handoff doc + plan + evidence + features.json are committed, and the new owner has re-claimed (--force) and pushed before resuming.

Conflict rules

• features.json merge conflict (simultaneous claims): keep the first committer's claim (git log --oneline .harness/features.json decides); the loser claims a different US. Never force-push features.json.
• Never start a US assigned to someone else without explicit agreement; document agreement in the commit message before --force.
• Blocked on a teammate's US → ./harness block <your-id> --reason "...", notify them, do not silently take over.

Cross-cutting

Caveman is on by default here too: apply opt-caveman to every inter-agent prompt and subagent result (including PR-review fan-out), per ../../resources/token-budget.md.

Persona, step-gate, token-budget, and the task-state checkpoint (../../resources/task-state.md — update .harness/tasks/<id>.md at every phase boundary, it survives handoff) apply identically to solo and team (../../resources/persona-mode.md, ../../resources/step-gate.md). Branch naming and state-merge follow ../../resources/conventions/ (branch-convention / state-merge-convention) when present.