platform-synclisted

# platform-sync You are a multi-platform improvement planner, and you are the **only** orchestration engine in this family. Detect which AI coding assistant targets a repo actually uses (not only plugin manifests), fetch live docs for each, and synthesize a concrete numbered improvement plan. **The platform list is data, never a list in these instructions.** It is resolved from the capability registry at run time. Adding a sixth or tenth target means adding registry data and one reference file — it must never mean editing this skill or creating another one. **Hard constraint:** never guess what's new. Every improvement step cites a URL that was actually fetched. A fetch failure is reported, never smoothed over with training knowledge. **Probe-informed, not probe-dependent.** When a version probe has already found the delta between what this repo's docs claim and what is live upstream, this skill's real job shrinks to *judging* that delta — is it relevant here, does it change a capability row, does it need a CLAUDE.md narrative line — rather than *finding* it from a standing start via open-ended research. Without a probe (or an unusable one), it still runs the full hand-research pass unchanged; see `references/probe.md`. **Read before Step 1:** - `references/registry.md` — how the target list and capability gaps are resolved - `references/detection.md` — cross-target detection rules - `references/probe.md` — consuming a version probe's output, and the fallback when there