init

team-management: Init

Set up team-management for THIS project: enable the plugin on this machine, wire the behavioral guidance into the project's CLAUDE.md via native @-includes (durable across /compact, unlike one-shot SessionStart injection), and optionally enable the LLM Wiki.

Two different sharing models are in play, by design:

• Plugin enablement is per-machine. .claude/ is gitignored wholesale by the SessionStart hook (ensure_claude_dir_gitignored), so .claude/settings.json is NOT committed and does NOT auto-enable the plugin for teammates — each developer runs /team-management:init themselves and puts their own tokens in the per-project .claude/state/provider-tokens.json file.
• The behavioral-guidance files ARE committed. CLAUDE.tm.md, team-management/knowledge/*.md, and the managed @-block in CLAUDE.md live at the project root / under team-management/ (outside the .claude/ ignore), so the whole team gets the same guidance via the committed CLAUDE.md @-includes.

Workflow

0. Windows runtime bootstrap (Windows only — provisions python3)

The plugin's hooks and MCP server launch from static manifests (hooks.json / .mcp.json) that invoke the literal token python3 — correct on macOS/Linux. Windows has no python3.exe (only python.exe / the py launcher), so on Windows those launches fail (python3: command not found) and the plugin is dead until python3 resolves to a real executable. A python3.cmd/.bat shim is NOT enough: Claude Code spawns the MCP command directly, and Windows cannot direct-spawn a .cmd without a shell — only a real .exe is found by every launch path (direct-spawn, bash, cmd, PowerShell). Do this FIRST — before the config_update step below, which needs the runtime up.

1. Detect the platform. On macOS/Linux skip this whole section. Treat as Windows when uname reports MINGW*/MSYS*/CYGWIN*, or %OS% is Windows_NT, or only PowerShell/cmd is available.
2. Is python3 already a real, runnable .exe? Run python3 --version AND where python3 (where.exe python3). Skip the rest ONLY if --version prints 3.x and the first where python3 hit ends in .exe. If it instead resolves to a .cmd/.bat shim (broken for the MCP server per above, even though --version works), opens the Microsoft Store, or errors → do NOT skip; continue and provision a real .exe below.
3. Require the py launcher. Run py --version. If py is missing → STOP and tell the user to install Python from python.org with the py launcher option (or the Microsoft Store build, which already provides a real python3.exe), then re-run /team-management:init. Do not substitute another interpreter.
4. Find the Python install dir (holds python.exe, is on PATH, and — for the python.org installer — precedes %LOCALAPPDATA%\Microsoft\WindowsApps, so the shim is not shadowed by a Store python3.exe app-execution-alias): py -3 -c "import os,sys;print(os.path.dirname(sys.executable))".
5. Create a REAL python3.exe by copying python.exe in that same directory. A copy of python.exe IS a working python3 — it loads the same pythonXX.dll from its own directory — and is directly spawnable by the MCP launcher. Create it only if python3.exe is absent there. Use whichever form works in the agent's shell (the detection commands above are plain program calls and work in any shell; only this copy is shell-specific):
   • PowerShell: Copy-Item "<dir>\python.exe" "<dir>\python3.exe"
   • cmd: copy /Y "<dir>\python.exe" "<dir>\python3.exe" (the /Y keeps it non-interactive — plain copy prompts Overwrite? and would stall the agent shell)
   • Git-bash: cp "<dir>/python.exe" "<dir>/python3.exe"
6. Verify in a fresh process: python3 --version must print a 3.x version and where python3 must point at the python3.exe you just created in the dir from step 4 (NOT a WindowsApps alias). If where python3 finds nothing, that dir is not on PATH (Python was installed without "Add Python to PATH"), so copying the exe there cannot help — tell the user to either re-run the python.org installer with "Add Python to PATH" enabled, OR add the dir to PATH (setx PATH "%PATH%;<dir>", then open a NEW shell), and then re-run /team-management:init. Otherwise print the exact manual copy command and stop.
7. Tell the user to RESTART Claude Code, then continue setup. On a fresh Windows install the hooks (including the config_intent_gate.py hook that authorizes config_update) AND the MCP server were already launched broken this session and only retry on restart — so the wiki/guidance step below CANNOT complete now. After the restart, run /team-management:config to finish it.