菜单
Runs synapse-docs, /simplify, sync-plugin-skills, and github-pages-sync in parallel for synapse-a2a development workflows. Use when you need doc updates, code simplification, plugin skill sync, and site-docs sync at the same time.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Synapse A2A agent communication -- sending messages, spawning agents, delegating tasks, sharing memory, managing the LLM wiki, and coordinating file edits. Use this skill when: running synapse send/reply/broadcast/interrupt, spawning agents with synapse spawn or synapse team start, sharing knowledge with synapse memory, managing wiki pages with synapse wiki, locking files with synapse file-safety, checking agent status with synapse list/status, or orchestrating any multi-agent workflow. For AI/programmatic use, prefer synapse list --json, synapse status <target> --json, or the MCP list_agents tool instead of interactive synapse list.
Multi-agent management workflow — task delegation, progress monitoring, quality verification with regression testing, feedback delivery, and cross-review orchestration. Use this skill when coordinating multiple agents on a shared task, monitoring delegated work, ensuring quality across agent outputs, or implementing a multi-phase plan (3+ phases or 10+ file changes).
Bootstrap a new GitHub issue implementation in one command: fetch the issue body, gather cross-references and code hotspots, infer a branch prefix and slug, generate a structured task brief, create a fresh branch from latest main, and (by default) spawn a codex agent to implement it. Triggered by /dev-issue <number>. Use this skill when starting work on a new issue that follows the standard issue → codex spawn → review → PR pipeline.
Fetch dependency source code to give AI agents deeper implementation context. Use when the agent needs to understand how a library works internally, read source code for a package, fetch implementation details for a dependency, or explore how an npm/PyPI/crates.io package is built. Triggers include "fetch source for", "read the source of", "how does X work internally", "get the implementation of", "opensrc path", or any task requiring access to dependency source code beyond types and docs.
Design, review, and improve Claude/Codex skills based on Anthropic's "The Complete Guide to Building Skills for Claude". Use when creating a new skill, rewriting SKILL.md frontmatter and workflows, fixing under-triggering or over-triggering, designing scripts/references/assets, building test cases, or preparing a skill for upload/distribution.
Guide API design for REST, GraphQL, gRPC, and CLI interfaces. Use this skill when designing new APIs, reviewing existing API contracts, or establishing API conventions for a project. Produces consistent, well-documented API specifications.
基于 SOC 职业分类
| name | parallel-docs-simplify-sync |
| license | MIT |
| description | Runs synapse-docs, /simplify, sync-plugin-skills, and github-pages-sync in parallel for synapse-a2a development workflows. Use when you need doc updates, code simplification, plugin skill sync, and site-docs sync at the same time. |
| commands | ["/parallel-docs-simplify-sync"] |
Coordinate four independent skills in parallel using the Task tool.
Dev-focused orchestration skill. The canonical source lives in
plugins/synapse-a2a/skills/and is synced to.agents/skills/and.claude/skills/.
synapse-docs — documentation updates/simplify — Claude Code built-in code simplification (replaces custom code-simplifier)sync-plugin-skills — plugin skill synchronizationgithub-pages-sync — GitHub Pages site synchronizationsite-docs/) needs to reflect code or doc changes.Define one clear objective and divide it:
| Track | Skill | Typical Scope |
|---|---|---|
| Docs | synapse-docs | README.md, guides/, CLAUDE.md |
| Simplify | /simplify (built-in) | Recently changed .py files |
| Sync | sync-plugin-skills | plugins/synapse-a2a/skills/ |
| Pages | github-pages-sync | site-docs/ |
Use the Task tool with four parallel invocations in one response. Each Task call should use the prompt template below.
# Example: four parallel calls (3 Task agents + 1 Skill)
Task(subagent_type="general-purpose", prompt="[synapse-docs prompt]")
Skill("simplify")
Task(subagent_type="general-purpose", prompt="[sync-plugin-skills prompt]")
Task(subagent_type="general-purpose", prompt="[github-pages-sync prompt]")
All four tasks return independently. Collect results before merging.
Apply changes from each track. If conflicts arise, follow the Conflict Resolution Rules below. Run tests after merging.
If any track fails, rerun only that track. Do not re-execute all four.
Use this for each parallel track:
Goal: <shared task goal>
Track: <synapse-docs | simplify | sync-plugin-skills | github-pages-sync>
Scope: <files/areas>
Constraints:
- Keep behavior unchanged unless explicitly requested
- Keep style consistent with repository conventions
- Do NOT touch files outside your track's scope
Deliverable:
- Concise change summary and touched files
synapse-docs and sync-plugin-skills can both modify files under
plugins/synapse-a2a/skills/. When this happens:
sync-plugin-skills output and
verify it against the doc changes from synapse-docs. Manually reconcile
if descriptions diverge./simplify should never conflict because it only touches .py files.github-pages-sync only modifies site-docs/ and mkdocs.yml. If both
synapse-docs and github-pages-sync modify mkdocs.yml,
github-pages-sync takes priority because it owns the site build config.synapse-docs, /simplify, sync-plugin-skills, github-pages-syncpytest passesuv run mkdocs build --strict passes (if Pages track ran)