Summary
The /add-orchestrator install path has no upgrade or divergence detection. Re-running offers overwrite/skip/cancel per skill with no version comparison, no diff, and no detection that a local copy was customized. Reported by corbin (Item 3).
Consequences corbin hit directly:
- The two stranded skills (companion back-port issue) were only found by hand-diffing eight files against the templates — nothing in the flow surfaced
installed > bundled.
- Corbin's
/orchestrate carried a hand-written marketing-hierarchy routing block (operator directive 2026-07-28). A plain "overwrite" would have silently destroyed it; corbin had to re-apply it by hand after copying the new template.
Proposed shape
A --check / doctor mode that, per skill, reports installed vs bundled and flags:
installed < bundled → upgrade availableinstalled > bundled → back-port candidate (the more interesting signal — this is the Item 2 case, a field-hardened local copy the marketplace should pull from)- local edits → diff the installed copy against the bundled template of the installed version so customizations are surfaced before an overwrite, not discovered after
Scope decision (maintainer/Eugene)
The same problem applies to every plugin that installs skill copies into agent repos, so it likely belongs at the plugin-framework level, not inside add-orchestrator. That's a larger call (framework surface, priority) than a bundle patch — routed to Eugene for a build/scope decision per propose-only boundary. Recommend it also feed the back-flow gap in the Item 2 issue (doctor's installed > bundled output is the back-port worklist).
Filed by trinity-pm on behalf of corbin's report. Verdict: adopt as backlog, lower priority; scope (add-orchestrator vs plugin-framework) is a maintainer call.
Summary
The
/add-orchestratorinstall path has no upgrade or divergence detection. Re-running offers overwrite/skip/cancel per skill with no version comparison, no diff, and no detection that a local copy was customized. Reported by corbin (Item 3).Consequences corbin hit directly:
installed > bundled./orchestratecarried a hand-written marketing-hierarchy routing block (operator directive 2026-07-28). A plain "overwrite" would have silently destroyed it; corbin had to re-apply it by hand after copying the new template.Proposed shape
A
--check/ doctor mode that, per skill, reports installed vs bundled and flags:installed < bundled→ upgrade availableinstalled > bundled→ back-port candidate (the more interesting signal — this is the Item 2 case, a field-hardened local copy the marketplace should pull from)Scope decision (maintainer/Eugene)
The same problem applies to every plugin that installs skill copies into agent repos, so it likely belongs at the plugin-framework level, not inside
add-orchestrator. That's a larger call (framework surface, priority) than a bundle patch — routed to Eugene for a build/scope decision per propose-only boundary. Recommend it also feed the back-flow gap in the Item 2 issue (doctor'sinstalled > bundledoutput is the back-port worklist).Filed by trinity-pm on behalf of corbin's report. Verdict: adopt as backlog, lower priority; scope (add-orchestrator vs plugin-framework) is a maintainer call.