dos-setuplisted

# dos-setup — confirm the plugin is wired, then point at the next move > **The plugin ships JSON + markdown; the brains ship as a pip package.** The > bundled hooks shell `python -m dos.cli …` and the bundled MCP server runs > `python -m dos_mcp.server` — both need the `dos-kernel` package importable in the > SAME Python that Claude Code launches. This skill verifies that one prerequisite > and shows you what the plugin gave you. It is the only DOS skill that names the > pip package; the rest are domain-free. ## Step 1 — Is the kernel importable? (the one prerequisite) ```bash python -c "import dos, dos_mcp; print('dos', dos.__version__)" ``` - **Prints a version** → the package is installed and importable. Go to Step 2. - **`ModuleNotFoundError: dos`** → the plugin's hooks/MCP cannot work yet. Install the package (the `[mcp]` extra pulls the MCP server framework the bundled server needs): ```bash pip install "dos-kernel[mcp]" ``` Install it into the SAME interpreter Claude Code runs (the one `python` resolves to here). Then re-run Step 1. If `python` is the wrong interpreter, the hooks will silently no-op (they fail safe, by design) and the MCP server will print an install hint in `/mcp`. - **`ModuleNotFoundError: dos_mcp`** → the core installed but not the MCP extra; re-run the `pip install "dos-kernel[mcp]"` line above. ## Step 2 — Does the kernel see this workspace? (confirm wiring) ```bash python -m dos.cli doctor --workspace . --json ``` A J