Required sections
Task records include Summary, Files, Work, Verification, and Notes so another person or agent can understand what happened and how it was checked.
What Task Protocol is
Task Protocol is SharkBay's lightweight way to preserve agent work context in the repository being changed. It creates Markdown task records under .sharkbay/tasks so work summaries are not trapped in one terminal transcript or chat session.
Each task record captures the objective, files, meaningful work, verification, and notes for future agents. Completed records can be synced through a Git-backed team context branch.
Local task files
When installed, the protocol writes a .sharkbay harness inside the project. Local task records live under .sharkbay/tasks, while mirrored team context records live under .sharkbay/team-context and should be treated as read-only by agents.
The protocol keeps task files concise. It is not a replacement for commits, pull requests, or code review; it is a durable work log that makes current context easier to inspect.
A task file is created before persistent project-changing work and is updated as changed files, meaningful decisions, and verification become clear.
Commit-aware handoff
Completed tasks can list related commits in chronological order, which helps connect local work records with Git history.
Team context sync
The shared context branch is named sharkbay-team-context. SharkBay fetches that branch into the local read-only mirror and can copy completed local task records into the shared branch when permissions allow.
This keeps collaboration local-first and Git-backed. A teammate or a different agent can open the project later and inspect the same task context without needing the original chat transcript.
Agents should search the read-only team context mirror before overlapping work and mention relevant prior task IDs in the current task notes.
How agents use it
When Task Protocol is installed and a supported agent is launched from SharkBay, the launch prompt tells the agent to read .sharkbay/harness/protocol.md before doing project-changing work.
Agents are expected to create or update task records before edits, keep Files and Work current, fill Verification at the end, and avoid editing the read-only team context mirror.
Completed task records include the final summary, verification results, and any commits produced by the task.
FAQ
Does Task Protocol replace Git commits?
No. Task Protocol records context around the work. Git remains the source of truth for code changes, commits, branches, and review.
Where are SharkBay task files stored?
Local task files are stored under .sharkbay/tasks in the project. Mirrored team records are stored under .sharkbay/team-context and should be treated as read-only.
Can any coding agent participate?
Yes. An agent only needs to read the protocol file, maintain Markdown task records, and record verification. No private SharkBay API is required.