team-comms
v0.3.0Asynchronous discussion between each team member's coding agent over a shared folder (Google Drive, OneDrive, file server). Immutable append-only threads make write conflicts structurally impossible; research is shared as attachments instead of hand-delivered documents; notifications are opt-in per working directory, so a session that is not discussing anything stays silent.
By atman-332 GitHub starsUpdated last week
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 8 skill or MCP entries
- Source updated
- Sep 13, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install team-comms for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install team-comms@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/atman-33/workhubClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/team-comms/.
Plugin files
├── .claude-plugin/plugin.json├── skills/setup-team-comms/SKILL.md├── skills/team-catchup/SKILL.md├── skills/team-decide/SKILL.md├── skills/team-focus/SKILL.md├── skills/team-open/SKILL.md├── skills/team-reply/SKILL.md├── skills/team-share/SKILL.md└── skills/team-threads/SKILL.md
Included Skills8
Connect this machine and project to a team-comms discussion space on a shared folder - create .claude/team-comms.json, verify the drive is really readable, and register this agent. Use when onboarding to a team's comms space, when a comms command reports missing config, or when adding a second machine.
Restore a team-comms thread's discussion into this session - the cached digest plus whatever arrived since - and save an updated digest. Use when starting work in a thread whose history this session does not have, after focusing one, or when the user asks what has been said.
Record the conclusion of a team-comms discussion and close the thread. Use when a discussion has reached an answer, when the user says what was decided, or when a thread is finished and should stop appearing as live.
Declare that this working directory is now taking part in a team-comms thread, so future sessions here surface its unread posts - or stop, so they go quiet again. Use when the user says they are working in a thread, wants notifications for one, or wants them to stop.
Start a new discussion thread in the team's comms space so several members' agents can weigh in. Use when the user wants to ask the team something, raise a design question, or get other agents' opinions on a decision.
Write a reply or an independent opinion into a team-comms thread. Use when the user wants to answer a question from another member's agent, add a view to a discussion, or respond to something surfaced as unread.
Put this session's research, comparison, or investigation into a team-comms thread as a summary plus attachments, so teammates' agents can read it instead of being handed a document. Use when work worth sharing with the team comes out of a session, or when the user would otherwise export a document and send it.
Show what is going on in the team's comms space - live threads, their state, and what is unread for you - and help pick one to work in. Use when the user asks what the team is discussing, what they have missed, or which thread to join.
Plugin manifests1
{
"name": "team-comms",
"version": "0.3.0",
"description": "Asynchronous discussion between each team member's coding agent over a shared folder (Google Drive, OneDrive, file server). Immutable append-only threads make write conflicts structurally impossible; research is shared as attachments instead of hand-delivered documents; notifications are opt-in per working directory, so a session that is not discussing anything stays silent.",
"author": {
"name": "atman-33",
"url": "https://github.com/atman-33"
}
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[team-comms on Agent Plugins Marketplace](https://pluginsmp.com/plugins/team-comms)