A full URL or a local checkout path works as the marketplace source too — or run bare /plugin and install from the picker. On first use the plugin's MCP server cold-starts: it builds its own isolated venv under Claude Code's managed plugin-data directory — no system Python packages — and the tools appear once it connects, usually the next turn. Once per version.

Requirements: Claude Code, Python 3.10+ on your PATH, and git.

Run it inside the project you want managed. It merges enabledPlugins into the project's .claude/settings.json — commit that file, and every teammate auto-enables the plugin when they open the project. No secrets are written there.

Windows: this step is required, not optional — it provisions the python3 runtime the hooks and MCP server launch with (via the py launcher). Run it once, then fully quit and reopen Claude Code.

Non-secret settings — developer identity, DAIC options, issue tracking (GitLab / Jira / GitHub / Gitea), AI providers — via /team-management:config, which writes team-management/config.json. Provider tokens live in the per-project .claude/state/provider-tokens.json — git-ignored, owner-only (0600), and unreadable by Claude. It's auto-created with blank keys; open it in your editor and fill in only the tokens you use — never in config.json, never in the transcript.

Claude discusses the approach with you first (it cannot edit code until you align), then starts a protocol that manages the branch, the task file, and the workflow from there. See the protocols overview for what runs next.

Run /plugin and uninstall team-management— the plugin's venv and caches live under Claude Code's managed plugin-data directory and are cleaned up with it. To disable it for one project instead, remove its entries from .claude/settings.json.

Never delete team-management/ — that directory holds your task history, config.json, and custom protocols. Uninstalling leaves it in place; a reinstall picks it right back up. Full source and issues on GitHub.