.claude/skills/finalize-step-sync-plugin-cache/SKILL.md
Finalize-phase wrapper that syncs marketplace bundles to the Claude plugin cache by delegating to the sync-plugin-cache skill
npx skillsauth add cuioss/plan-marshall finalize-step-sync-plugin-cacheInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Keep ~/.claude/plugins/cache/plan-marshall/ in sync with the merged state of marketplace/bundles/ after a plan finalizes. Without this step, Claude Code plugins silently load stale bundle code after a finalize completes, producing behavior that diverges from the freshly merged source tree until the cache is manually re-synced.
Invoked by plan-marshall:phase-6-finalize for projects that include project:finalize-step-sync-plugin-cache in their phase-6-finalize.steps list.
Accepts the standard finalize-step arguments:
--plan-id — plan identifier (ignored; rsync is stateless)--iteration — finalize iteration counter (ignored; rsync is idempotent)Both arguments are accepted for discovery-contract compliance but have no effect on execution. The underlying rsync operation is fully idempotent and can be re-run safely.
Load and run the underlying sync skill:
Skill: project:sync-plugin-cache
The project: prefix matches the notation used by phase-6-finalize when dispatching project-local skills (see marketplace/bundles/plan-marshall/skills/phase-6-finalize/SKILL.md line 88), and is consistent with how this wrapper itself is referenced as project:finalize-step-sync-plugin-cache in phase-6-finalize.steps.
That skill performs parallel rsync of every bundle under marketplace/bundles/ into ~/.claude/plugins/cache/plan-marshall/ with --delete semantics.
rsync failures are non-fatal. Log the failure and continue — finalize must not block on a cache mismatch, because the cache can always be re-synced manually via the /sync-plugin-cache command after the plan is merged.
development
Domain-owned OpenRewrite log-line finding parser for the java-cui domain — parses the
development
Domain-owned OpenRewrite marker detection for the java-cui domain — scans Java/Kotlin sources for cui-rewrite TODO markers, categorizes them by recipe, and fails the gate on any detected marker
development
Operator control surface for the marshalld build server — enrol/drop a project in the machine-global registry (the opt-in enable signal and anti-laundering wall), manage the daemon lifecycle (start, stop, drain, status, install, upgrade) version-pinned to the verified bundle copy, and inspect the daemon's per-project interaction-audit log (read-only)
tools
The tiny build-consumption client for the marshalld build server — submit a build job, bounded long-poll for its result, ping the daemon identity, and preflight registry-plus-liveness in one call; consumption only, never provisioning or enrolment