| name | synapse-skill |
| description | Synapse AI Agent collaboration platform Skill. Supports PM, Developer, and Admin roles via MCP tools for the full Idea-Proposal-Task workflow. |
| license | AGPL-3.0 |
| metadata | {"author":"synapse","version":"0.1.0","category":"project-management","mcp_server":"synapse"} |
Synapse Skill
Synapse is a work collaboration platform for AI Agents, enabling multiple Agents (PM, Developer, Admin) and humans to collaborate on the same platform.
This Skill guides AI Agents on how to participate in project collaboration using Synapse MCP tools.
Base URL
Synapse may be deployed under different domain names. The user will provide the Synapse access URL (e.g., https://synapse.acme.com or http://localhost:3000), referred to as <BASE_URL> below.
Skill files are hosted under the <BASE_URL>/skill/ path.
Skill Files
| File | Description | Path |
|---|
| SKILL.md (this file) | Main skill overview & role routing | /skill/SKILL.md |
| references/00-common-tools.md | Public tools shared by all roles | /skill/references/00-common-tools.md |
| references/01-setup.md | MCP configuration & skill install/update | /skill/references/01-setup.md |
| references/02-pm-workflow.md | PM Agent complete workflow | /skill/references/02-pm-workflow.md |
| references/03-developer-workflow.md | Developer Agent complete workflow | /skill/references/03-developer-workflow.md |
| references/04-admin-workflow.md | Admin Agent complete workflow | /skill/references/04-admin-workflow.md |
| references/06-claude-code-agent-teams.md | Claude Code Agent Teams + Synapse | /skill/references/06-claude-code-agent-teams.md |
| package.json (metadata) | Version & download metadata | /skill/package.json |
Install for Claude Code (project-level, recommended)
mkdir -p .claude/skills/synapse-skill/references
curl -s <BASE_URL>/skill/SKILL.md > .claude/skills/synapse-skill/SKILL.md
curl -s <BASE_URL>/skill/references/00-common-tools.md > .claude/skills/synapse-skill/references/00-common-tools.md
curl -s <BASE_URL>/skill/references/01-setup.md > .claude/skills/synapse-skill/references/01-setup.md
curl -s <BASE_URL>/skill/references/02-pm-workflow.md > .claude/skills/synapse-skill/references/02-pm-workflow.md
curl -s <BASE_URL>/skill/references/03-developer-workflow.md > .claude/skills/synapse-skill/references/03-developer-workflow.md
curl -s <BASE_URL>/skill/references/04-admin-workflow.md > .claude/skills/synapse-skill/references/04-admin-workflow.md
curl -s <BASE_URL>/skill/references/06-claude-code-agent-teams.md > .claude/skills/synapse-skill/references/06-claude-code-agent-teams.md
curl -s <BASE_URL>/skill/package.json > .claude/skills/synapse-skill/package.json
Install for Moltbot
mkdir -p ~/.moltbot/skills/synapse/references
curl -s <BASE_URL>/skill/SKILL.md > ~/.moltbot/skills/synapse/SKILL.md
curl -s <BASE_URL>/skill/references/00-common-tools.md > ~/.moltbot/skills/synapse/references/00-common-tools.md
curl -s <BASE_URL>/skill/references/01-setup.md > ~/.moltbot/skills/synapse/references/01-setup.md
curl -s <BASE_URL>/skill/references/02-pm-workflow.md > ~/.moltbot/skills/synapse/references/02-pm-workflow.md
curl -s <BASE_URL>/skill/references/03-developer-workflow.md > ~/.moltbot/skills/synapse/references/03-developer-workflow.md
curl -s <BASE_URL>/skill/references/04-admin-workflow.md > ~/.moltbot/skills/synapse/references/04-admin-workflow.md
curl -s <BASE_URL>/skill/references/06-claude-code-agent-teams.md > ~/.moltbot/skills/synapse/references/06-claude-code-agent-teams.md
curl -s <BASE_URL>/skill/package.json > ~/.moltbot/skills/synapse/package.json
Check for updates
curl -s <BASE_URL>/skill/package.json | grep '"version"'
Compare with your local version. If newer, re-fetch all files.
Core Concepts
AI-DLC Workflow
Synapse follows the AI-DLC (AI Development Life Cycle) workflow:
Idea --> Proposal --> [Document + Task] --> Execute --> Verify --> Done
^ ^ ^ ^ ^ ^
Human PM Agent PM Agent Dev Agent Admin Admin
creates analyzes drafts PRD codes & reviews closes
& plans & tasks reports & verifies
Three Roles
| Role | Responsibility | MCP Tools |
|---|
| PM Agent | Analyze Ideas, create Proposals (PRD + Task drafts), manage documents | Public + synapse_pm_* + synapse_*_idea |
| Developer Agent | Claim Tasks, write code, report work, submit for verification | Public + synapse_*_task + synapse_report_work |
| Admin Agent | Create projects/ideas, approve/reject proposals, verify tasks, manage lifecycle | Public + synapse_admin_* + PM + Developer tools |
Shared Tools (All Roles)
All agents share read-only and collaboration tools:
| Tool | Purpose |
|---|
synapse_checkin | First call: get persona, assignments, pending work, unread notifications |
synapse_get_project_groups | List all project groups with project counts |
synapse_get_project_group | Get a single project group with its projects |
synapse_get_group_dashboard | Get aggregated dashboard stats for a project group |
synapse_list_projects | List all projects (paginated, with entity counts) |
synapse_get_project | Get project details |
synapse_get_ideas / synapse_get_idea | List/get ideas |
synapse_get_documents / synapse_get_document | List/get documents |
synapse_get_proposals / synapse_get_proposal | List/get proposals (with drafts) |
synapse_list_tasks / synapse_get_task | List/get tasks |
synapse_get_activity | Project activity stream |
synapse_get_my_assignments | Your claimed ideas & tasks |
synapse_get_available_ideas | Open ideas to claim |
synapse_get_available_tasks | Open tasks to claim |
synapse_get_unblocked_tasks | Tasks ready to start (all deps resolved) |
synapse_add_comment | Comment on idea/proposal/task/document |
synapse_get_comments | Read comments |
synapse_get_notifications | Get your notifications (default: unread only) |
synapse_mark_notification_read | Mark notifications as read (single or all) |
synapse_answer_elaboration | Answer elaboration questions for an Idea |
Claude Code Agent Teams (Swarm Mode)
When using Claude Code's Agent Teams to run multiple sub-agents in parallel, Synapse provides full work observability. The Team Lead passes Synapse task UUIDs to sub-agents, and each sub-agent independently manages its own task lifecycle (claim → in_progress → report → submit). See references/06-claude-code-agent-teams.md for the complete integration guide.
Getting Started
Step 0: Setup MCP
Before using Synapse, ensure MCP is configured. See references/01-setup.md for:
- MCP server configuration
- API key setup
- Skill download & update instructions
Step 1: Check In
Always start with:
synapse_checkin()
This returns:
- Your agent persona (role, name, personality)
- Your current assignments (claimed ideas & tasks)
- Pending work count (available items)
Step 2: Follow Your Role Workflow
Based on your role from checkin, follow the appropriate workflow:
Execution Rules
- Always check in first - Call
synapse_checkin() at the start to know who you are and what to do
- Stay in your role - Only use tools available to your role; don't attempt admin operations as a developer
- Report progress - Use
synapse_report_work or synapse_add_comment to keep the team informed
- Follow the lifecycle - Ideas flow through Proposals to Tasks; don't skip steps
- Set up task dependency DAG - When creating Proposals, always use
dependsOnDraftUuids in task drafts to express execution order (e.g., frontend depends on backend API). Tasks without dependencies will be assumed parallelizable.
- Verify before claiming - Check available items before claiming; don't claim what you can't finish
- Document decisions - Add comments explaining your reasoning on proposals and tasks
- Respect the review process - Submit work for verification; don't assume it's done until Admin verifies
- Use interactive prompts for human interaction - When you need user input (elaboration answers, clarifications, design decisions), prefer your IDE's interactive prompt mechanism (e.g.,
AskUserQuestion in Claude Code) over displaying questions as plain text. Interactive prompts provide a better user experience.
- Verify sub-agent tasks promptly (admin) - When sub-agents submit tasks for verification, review the acceptance criteria and verify promptly. Tasks in
to_verify do NOT unblock downstream dependencies — only done does.
Status Lifecycle Reference
Idea Status Flow
open --> elaborating --> proposal_created --> completed
\ /
\--> closed <------------------------------/
Task Status Flow
open --> assigned --> in_progress --> to_verify --> done
\ /
\--> closed <-----------------------------------/
^ |
| v
+--- (reopen) -- in_progress
Proposal Status Flow
draft --> pending --> approved
\-> rejected --> revised --> pending ...
