Parallel docs simplify sync
Skill s-hiraoku/synapse-a2a/plugins/synapse-a2a/skills/parallel-docs-simplify-sync
npx -y skills add s-hiraoku/synapse-a2a --skill parallel-docs-simplify-syncAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 9 stars9 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
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.
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
3.8 KB, as published. Nobody here has run it
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 synchronization
When To Use
- Code and documentation were changed in the same task.
- Simplification or refactor cleanup is needed while keeping docs in sync.
- Plugin-skill synchronization should happen in the same run.
- GitHub Pages site (
site-docs/) needs to reflect code or doc changes.
Parallel Execution Workflow
Step 1: Split into four independent sub-tasks
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/ |
Step 2: Launch four Task tool calls in a single message
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]")
Step 3: Wait for all four outputs
All four tasks return independently. Collect results before merging.
Step 4: Merge and resolve conflicts
Apply changes from each track. If conflicts arise, follow the Conflict Resolution Rules below. Run tests after merging.
Step 5: Retry failed tracks only
If any track fails, rerun only that track. Do not re-execute all four.
Task Prompt Template
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
Conflict Resolution Rules
synapse-docs and sync-plugin-skills can both modify files under
plugins/synapse-a2a/skills/. When this happens:
- sync-plugin-skills wins for skill SKILL.md content.
- synapse-docs wins for README.md, guides/, and non-skill documentation.
- If both modified the same SKILL.md, take
sync-plugin-skillsoutput and verify it against the doc changes fromsynapse-docs. Manually reconcile if descriptions diverge. /simplifyshould never conflict because it only touches.pyfiles.github-pages-synconly modifiessite-docs/andmkdocs.yml. If bothsynapse-docsandgithub-pages-syncmodifymkdocs.yml,github-pages-synctakes priority because it owns the site build config.
Completion Checklist
- All four tracks completed:
synapse-docs,/simplify,sync-plugin-skills,github-pages-sync - Conflicts resolved per rules above
-
pytestpasses -
uv run mkdocs build --strictpasses (if Pages track ran) - Final diff is coherent and reviewable