Roadmap: Public dispatch module registry

[MehmetSecgin]

Vision

A public registry for dispatch modules — think npm but agent-native. Anyone can publish a module, anyone's agent can discover and use it.

Why this matters

Right now modules are local to a project. The missing piece is a distribution channel that makes the ecosystem composable:

• Community builds modules for GitHub, Stripe, Linear, etc.
• Anyone runs dispatch module install stripe and gets the runtime + agent instructions
• SKILL.md ships with every module so agents know how to use it without README hunting

Resolution hierarchy (full picture)

local (./modules/)        ← development / override
user registry             ← personal modules
org registry              ← company-shared (configured per project)
public dispatch registry  ← community modules  ← this issue

The public registry is the top-level default — the layer everything else builds on.

What it needs

• Hosted registry (npm-compatible or custom)
• dispatch module publish command
• dispatch module install <name> command
• SKILL.md as a first-class field in module.json or alongside it
• Registry browsing / search: dispatch module search <keyword>

Deferred until

Private/personal/org registry layer is proven first. This is explicitly a later phase.

Related

• Private org registry (dispatch config registry.url)
• User-level registry (~/.dispatch/registry)
• SKILL.md convention