Why
The dispatch and dm skills plus the local plugin bundle are packaged and documented, but users still need a clear supported path to expose them in their global Codex setup. The install story should not depend on repo-local knowledge or hand-built symlinks.
Scope
Design and implement a small supported installer or documented command sequence for first-party dispatch skills and plugin setup.
Acceptance criteria
- Provide a supported way to install, symlink, or register the first-party
dispatch and dm skills into global Codex config.
- Provide a supported way to install/register the workspace-local plugin or private marketplace entry.
- Make the flow work from a PyPI install, not only from a source checkout.
- Ensure installed plugin MCP config points at the same
dispatch mcp command users actually have on PATH.
- Add
dispatch doctor coverage or guidance that confirms skill/plugin visibility where practical.
- Document uninstall/rollback for any files or symlinks created.
- Include tests around path resolution/package asset discovery where practical.
Notes
Prefer a small explicit setup command or generated instructions over magical mutation. The user should understand what files are created or linked.
Why
The
dispatchanddmskills plus the local plugin bundle are packaged and documented, but users still need a clear supported path to expose them in their global Codex setup. The install story should not depend on repo-local knowledge or hand-built symlinks.Scope
Design and implement a small supported installer or documented command sequence for first-party dispatch skills and plugin setup.
Acceptance criteria
dispatchanddmskills into global Codex config.dispatch mcpcommand users actually have on PATH.dispatch doctorcoverage or guidance that confirms skill/plugin visibility where practical.Notes
Prefer a small explicit setup command or generated instructions over magical mutation. The user should understand what files are created or linked.