@useorgx/wizard 0.1.11 → 0.1.13

package/README.md

@@ -17,27 +17,27 @@ For local development, use `pnpm dev -- --help`.
 The wizard modifies local tool configuration only. Depending on the command, it can:
 
 - add OrgX MCP server entries to Claude, Cursor, Codex, VS Code, Windsurf, and Zed;
-- install OrgX skills/rules into Cursor and Claude Code;
-- install companion OrgX plugins/rules for Cursor, Claude Code, Codex, and OpenClaw.
+- install standalone OrgX skills/rules into Cursor and Claude Code;
+- install companion OrgX plugins for Cursor, Claude Code, Codex, and OpenClaw so those tools receive OrgX skills, rules, MCP config, commands, hooks, and agent prompts through their plugin systems.
 
 ## Commands
 
-- `setup` adds OrgX MCP configs, skills/rules, and companion plugins/rules to detected AI tools. When OrgX auth is available in an interactive shell, it also guides workspace selection or creation, optional onboarding extras, and optional Cursor rules or companion plugin installs for detected Cursor, Claude Code, Codex, and OpenClaw hosts. The founder preset preplans plugin installs before it writes standalone skills so plugin-backed hosts do not get duplicate standalone Claude assets in the same run.
+- `setup` adds OrgX MCP configs, standalone skills/rules, and companion plugins to detected AI tools. When OrgX auth is available in an interactive shell, it guides workspace selection or creation, can create the user's first live OrgX initiative, creates a starter onboarding task under that initiative, and prints a handoff prompt for the configured AI tool of choice. The founder preset preplans plugin installs before it writes standalone skills so plugin-backed hosts do not get duplicate standalone assets in the same run.
 - `surface list` shows supported surfaces and current status.
 - `surface add <name>` patches a specific surface.
 - `surface remove <name>` removes OrgX-managed config from a specific surface.
 - `mcp add [surface]` and `mcp remove [surface]` manage OrgX MCP entries in Claude, Cursor, Codex, VS Code, Windsurf, and Zed tool configs.
-- `plugins list` shows Cursor rules and companion plugin/rules availability and install status for Cursor, Claude Code, Codex, and OpenClaw.
-- `plugins add [target...]` installs managed Cursor OrgX rules or managed OrgX companion plugins/rules into Claude Code, Codex, and/or OpenClaw. Claude Code and Codex plugins carry their own OrgX skills, so they become the source of truth for those hosts.
-- `plugins remove [target...]` uninstalls managed Cursor OrgX rules or managed OrgX companion plugins/rules from Claude Code, Codex, and/or OpenClaw.
-- `uninstall` removes OrgX-managed tool config, Cursor rules and companion plugins, wizard-local auth, and wizard-local setup state. Use `--keep-auth`, `--keep-state`, `--skip-plugins`, or `--skip-surfaces` to preserve specific pieces.
+- `plugins list` shows companion plugin availability and install status for Cursor, Claude Code, Codex, and OpenClaw.
+- `plugins add [target...]` installs the managed Cursor plugin bundle and managed OrgX companion plugins into Claude Code, Codex, and/or OpenClaw. Cursor, Claude Code, and Codex companion plugins carry their own OrgX skills/rules/MCP config and become the source of truth for those hosts.
+- `plugins remove [target...]` uninstalls the managed Cursor plugin bundle, legacy managed Cursor rules, and managed OrgX companion plugins from Claude Code, Codex, and/or OpenClaw.
+- `uninstall` removes OrgX-managed tool config, companion plugins, legacy managed Cursor rules, wizard-local auth, and wizard-local setup state. Use `--keep-auth`, `--keep-state`, `--skip-plugins`, or `--skip-surfaces` to preserve specific pieces.
 - `doctor` verifies local config, hosted MCP reachability, npm registry readiness, current-workspace connectivity, local OpenClaw health, and optionally the remote setup status API. Hosted MCP tools are OAuth-scoped inside the client connector, so the wizard does not preflight them with `oxk_` API keys. It exits non-zero when blocking connectivity issues remain.
 - `auth status` shows the resolved OrgX API key source and verifies it against `POST /api/client/sync`.
 - `auth login [--base-url <url>]` starts browser pairing against OrgX, waits for approval, saves the returned per-user key to the wizard auth store, and bootstraps OpenClaw auth if OpenClaw is detected. Use `--api-key <oxk_...>` for CI or blocked-browser fallback.
 - `auth set-key <oxk_...> [--base-url <url>]` verifies a per-user OrgX key, saves it to the wizard auth store, and bootstraps OpenClaw auth if OpenClaw is detected.
 - `auth clear` removes the wizard-local saved OrgX API key.
 - `workspace current`, `workspace list`, `workspace create <name>`, and `workspace set-default <id>` inspect and manage OrgX workspaces.
-- `skills add [pack...]` writes OrgX skills/rules into supported local tools: `.cursor/rules/orgx.md`, `.claude/skills/orgx/SKILL.md`, and available OrgX Claude skill packs from `useorgx/skills`. If the Claude Code companion plugin is already installed, the wizard skips those overlapping standalone Claude assets and only installs the remaining standalone pieces.
+- `skills add [pack...]` writes standalone OrgX skills/rules into supported local tools: `.cursor/rules/orgx.md`, `.claude/skills/orgx/SKILL.md`, and available OrgX Claude skill packs from `useorgx/skills`. If a companion plugin already owns a tool's OrgX skills/rules, the wizard skips those overlapping standalone assets and only installs the remaining standalone pieces.
 - `skills sync [pack...]` recomposes generated skill/rule files from the OrgX-managed core plus any enabled local skill extensions.
 - `skills status` shows local extension files and generated skill files tracked for drift protection.
 - `skills extensions add|edit|enable|disable|list` manages user-editable skill extensions without changing the OrgX-managed core skill source.
@@ -60,17 +60,21 @@ The wizard modifies local tool configuration only. Depending on the command, it
 ## Workspace Bootstrap
 
 - `wizard setup` now opens a guided workspace picker in interactive shells, letting you keep the current default workspace, promote another existing workspace, or create a new one and make it active immediately.
+- If the selected workspace has no remembered setup initiative, `wizard setup` offers to create a first initiative, defaulting to `Make OrgX useful on this machine`. It then creates the onboarding workstream and starter task inside that initiative so setup ends with a concrete next action instead of a blank workspace.
+- After the first initiative is ready, setup prints the `/live/<initiative>` URL and a copyable prompt for the user's configured AI tool: continue the initiative, show the next action, and start with the onboarding task.
 - `wizard workspace current` reads the current OrgX workspace from `GET /api/v1/workspaces/current`, with a fallback to workspace listing if that route is unavailable.
 - `wizard workspace list` lists all accessible workspaces.
 - `wizard workspace create "Founders" --description "Initial OrgX workspace"` creates a new workspace through `POST /api/entities`.
 - `wizard workspace set-default <id>` updates the default workspace through the generic entity API.
 
-## Editor Rules And Skills
+## Editor Rules, Skills, And Plugins
 
 - `wizard skills add` writes the OrgX Cursor rule file at `.cursor/rules/orgx.md`.
+- `wizard plugins add cursor` installs the full Cursor local plugin bundle at `.cursor/plugins/local/cursor-plugin`; it includes OrgX skills, rules, MCP config, commands, hooks, and agent prompts.
 - `wizard skills add` also generates a hosted OrgX Claude skill at `.claude/skills/orgx/SKILL.md`.
 - The same command installs available OrgX Claude skill packs by pulling their source files from `useorgx/skills`; pass specific pack names to limit what is installed.
 - `wizard skills add` and `wizard skills sync` both compose generated outputs from OrgX-managed core skills plus any enabled extension files from the wizard skill-extension store.
+- When the Cursor companion plugin is installed, that plugin owns Cursor-side OrgX skills, rules, MCP config, commands, hooks, and agent prompts. In that case `wizard skills add` remains the standalone rules fallback for Cursor installs that are not using the plugin.
 - When the Claude Code companion plugin is installed, that plugin owns Claude-side OrgX skills and skill sync. In that case `wizard skills add` skips overlapping Claude assets instead of writing duplicate copies.
 - The Codex companion plugin also bundles its own OrgX skills, so `wizard skills add` does not try to manage Codex skill files at all.
 - Those generated rules expect artifact proof to use durable sources such as GitHub permalinks, public URLs, or absolute file paths / `file://...`, not OrgX wrapper routes like `/live/...`, `/artifacts/...`, or `/console/...`.
@@ -88,7 +92,7 @@ OrgX core skills are treated as managed upstream content. User behavior lives in
 ## Release Flow
 
 - GitHub Actions publishes to npm on pushes of version tags matching `v*`.
-- The publish workflow installs dependencies with pnpm, runs `pnpm typecheck`, `pnpm test`, and `pnpm build`, then runs `pnpm publish --no-git-checks --provenance`.
+- The publish workflow installs dependencies with pnpm, runs `pnpm typecheck`, `pnpm test`, and `pnpm build`, then runs `pnpm publish --no-git-checks`.
 - The workflow expects an `NPM_TOKEN` repository secret.
 
 ## Troubleshooting