Issue-Flow includes metadata for both supported host surfaces:
- Claude Code: ../.claude-plugin/plugin.json
- Claude Code marketplace flow: ./claude-code-marketplace.md
- Codex: ../.codex-plugin/plugin.json
- Codex repo marketplace: ../.agents/plugins/marketplace.json
- Codex marketplace flow: ./codex-marketplace.md
Issue-Flow is distributed using the standard Claude Code marketplace model and the Codex local plugin bundle model recommended by the official Codex plugin docs.
Today, users still need:
- the
superpowersruntime dependency - a host environment that can install or discover plugins
- a small installer script to stage the local
issue-flowCodex marketplace layout
Issue-Flow is intentionally an orchestrator, not a bundled workflow platform. Keeping superpowers separate has a few advantages:
- workflow logic can evolve independently from orchestration logic
- Issue-Flow stays small and easier to reason about
- users who already rely on
superpowersdo not get a duplicated skill tree
- Claude Code can install this repository through
.claude-plugin/marketplace.json - Codex can identify the repository root as an installable plugin package through
.codex-plugin/plugin.json - Codex can expose the plugin in a repo-scoped marketplace through
.agents/plugins/marketplace.json - Installation instructions can point to stable manifest and marketplace locations
scripts/install-codex.shcan stageissue-flowand update the user's personal marketplace plus plugin enablement in one step
- Removal of the
superpowersdependency - Perfectly identical behavior across Claude Code and Codex
Treat Issue-Flow as a focused orchestration plugin with an explicit runtime dependency. For Codex, prefer the documented plugin-bundle flow: install Superpowers from OpenAI Curated, use scripts/install-codex.sh to stage ~/.codex/plugins/issue-flow plus ~/.agents/plugins/marketplace.json, and install from the plugin directory instead of wiring skills/ into ~/.agents/skills/ manually.