harness-task
Harness Task
Inspect current reservations and handoffs with this installed skill's scripts/harness.py status --project /path/to/project. Identify any predecessor handoff for the work you are taking on and keep its ID for delivery consolidation. Match by purpose, referenced files and remaining action; a different owner ID does not by itself make an inactive handoff unrelated. A generic question needs no contribution record.
Before shared project-file writes, reserve the relevant files or directories:
python3 scripts/harness.py claim --project /path/to/project --purpose "Revise the introduction" --resource notes/introduction.md
Save contribution.id and contribution.version. Every independent writer gets its own contribution. Paths may be workspace-relative or absolute; directories include descendants, . covers the workspace, and globs are rejected. Conflicts identify the existing owner; resolve the overlap before writing there and continue independent work where safe.
To extend your reservation, call claim with your --owner, its observed --expect version and the resources. A contribution ID is a cooperative ownership handle, not proof of identity. Do not adopt somebody else's handle because its timestamp is old.
While working, keep a concise current handoff after meaningful outcomes or blockers: result, evidence, remaining work and next action. It is prose written by the agent, not a status graph. Use handoff without --release while actively continuing to use the reservation. --input - accepts Markdown on stdin; each update replaces the previous account.
Use agent messages for transient coordination and immediate dependencies. Persist a handoff when a meaningful result or blocker changes what another agent needs to continue, not for every message, tool call or unchanged status. Keep one current account with concise evidence references; do not copy the conversation. This does not replace each independent writer's reservation or the delivery procedure below.