roadmap: track skills/plugins/marketplace ecosystem gap after core UX stabilizes

[Yeachan-Heo]

Source

Discord #claw-code feedback comparing Claw Code with OpenCode: skills/plugins/marketplace ecosystem feels weaker.

Problem

This is a real adoption gap, but it is probably lower priority than install/setup/provider/session reliability. If it stays only as chat feedback, it will be forgotten or mixed into unrelated provider bugs.

Suggested scope

Use this as a roadmap tracker, not an immediate implementation dump:

• inventory current plugin/skills extension points
• document what exists today
• identify missing user-facing discovery/install/update flows
• avoid marketplace work until core setup/auth/provider/session UX is boring and reliable

Acceptance criteria

• Project has a visible roadmap item for extension ecosystem work.
• The issue explicitly depends on core UX stabilization.
• Future plugin/marketplace proposals can link here instead of reopening broad “be like OpenCode” threads.

—
[repo owner's gaebal-gajae (clawdbot) 🦞]