You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Feature]: First-class OpenCode support for WinUI skills #149
The winui plugin exposes its capabilities primarily to GitHub Copilot CLI (agents via .agent.md, skills via the plugin manifest), with separate adapters for Claude Code and Codex. OpenCode users currently have no first-class path: they can't link the shared skills, parse OpenCode sessions in winui-session-report, or run the winui-dev orchestrator agent. A developer who has standardized on OpenCode therefore can't get the same end-to-end WinUI 3 build flow that Copilot CLI provides.
Proposed solution
Add first-class OpenCode support to the winui plugin, delivered as three independent, independently mergeable changes (each targeting staging):
Orchestrator agent — expose winui-dev to OpenCode (opencode run --agent winui-dev), loading winui-dev-workflow and winui-design on demand. → Add OpenCode winui-dev orchestrator agent #148
Each PR is self-contained and can be reviewed/merged on its own; together they give OpenCode the same discover → analyze → orchestrate loop the other harnesses already have.
Alternatives considered
Single mega-PR — rejected: too large to review in a slow-review repo; a defect in one area would block the whole feature.
Sequential stacked PRs — rejected: each layer waits on the previous review, multiplying the already-slow latency.
Skill-only, no orchestrator agent — rejected: OpenCode can map skills, but without an agent the "do the build yourself" flow the winui-dev agent encodes is lost.
Activity