Merge upstream origin/main into local fork

163 upstream commits merged. All local skills, agents, and commands preserved. Metadata recalculated: 30 agents, 56 skills, 7 commands. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-03-16 10:46:52 -05:00
parent 24d77808c0 eb96e32c58
commit 6aec16b9cc
180 changed files with 18263 additions and 10848 deletions
--- a/.claude-plugin/marketplace.json
+++ b/.claude-plugin/marketplace.json
@@ -1,5 +1,5 @@
 {
-  "name": "every-marketplace",
+  "name": "compound-engineering-plugin",
  "owner": {
    "name": "Kieran Klaassen",
    "url": "https://github.com/kieranklaassen"
@@ -11,15 +11,15 @@
  "plugins": [
    {
      "name": "compound-engineering",
-      "description": "AI-powered development tools that get smarter with every use. Make each unit of engineering work easier than the last. Includes 25 specialized agents, 25 commands, and 24 skills.",
-      "version": "2.39.0",
+      "description": "AI-powered development tools that get smarter with every use. Make each unit of engineering work easier than the last. Includes 30 specialized agents, 56 skills, and 7 commands.",
+      "version": "2.40.0",
      "author": {
        "name": "Kieran Klaassen",
        "url": "https://github.com/kieranklaassen",
        "email": "kieran@every.to"
      },
      "homepage": "https://github.com/EveryInc/compound-engineering-plugin",
-      "tags": ["ai-powered", "compound-engineering", "workflow-automation", "code-review", "fastapi", "python", "knowledge-management"],
+      "tags": ["ai-powered", "compound-engineering", "workflow-automation", "code-review", "quality", "knowledge-management", "image-generation"],
      "source": "./plugins/compound-engineering"
    },
    {
--- a/.cursor-plugin/marketplace.json
+++ b/.cursor-plugin/marketplace.json
@@ -0,0 +1,25 @@
+{
+  "name": "compound-engineering",
+  "owner": {
+    "name": "Kieran Klaassen",
+    "email": "kieran@every.to",
+    "url": "https://github.com/kieranklaassen"
+  },
+  "metadata": {
+    "description": "Cursor plugin marketplace for Every Inc plugins",
+    "version": "1.0.0",
+    "pluginRoot": "plugins"
+  },
+  "plugins": [
+    {
+      "name": "compound-engineering",
+      "source": "compound-engineering",
+      "description": "AI-powered development tools that get smarter with every use. Includes specialized agents, commands, skills, and Context7 MCP."
+    },
+    {
+      "name": "coding-tutor",
+      "source": "coding-tutor",
+      "description": "Personalized coding tutorials with spaced repetition quizzes using your real codebase."
+    }
+  ]
+}
--- a/.github/workflows/publish.yml
+++ b/.github/workflows/publish.yml
@@ -1,18 +1,27 @@
 name: Publish to npm

 on:
-  release:
-    types: [published]
+  push:
+    branches: [main]
+  workflow_dispatch:

 jobs:
  publish:
    runs-on: ubuntu-latest
    permissions:
-      contents: read
+      contents: write
      id-token: write
+      issues: write
+      pull-requests: write
+
+    concurrency:
+      group: publish-${{ github.ref }}
+      cancel-in-progress: false

    steps:
      - uses: actions/checkout@v6
+        with:
+          fetch-depth: 0

      - name: Setup Bun
        uses: oven-sh/setup-bun@v2
@@ -20,18 +29,19 @@ jobs:
          bun-version: latest

      - name: Install dependencies
-        run: bun install
+        run: bun install --frozen-lockfile

      - name: Run tests
        run: bun test

-      - name: Setup Node.js for npm publish
+      - name: Setup Node.js for release
        uses: actions/setup-node@v4
        with:
-          node-version: "20"
-          registry-url: "https://registry.npmjs.org"
+          # npm trusted publishing requires Node 22.14.0+.
+          node-version: "24"

-      - name: Publish to npm
-        run: npm publish --provenance --access public
+      - name: Release
        env:
-          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
+        run: npx semantic-release
--- a/.gitignore
+++ b/.gitignore
@@ -3,3 +3,4 @@
 node_modules/
 .codex/
 todos/
+.worktrees
--- a/.releaserc.json
+++ b/.releaserc.json
@@ -0,0 +1,36 @@
+{
+  "branches": [
+    "main"
+  ],
+  "tagFormat": "v${version}",
+  "plugins": [
+    "@semantic-release/commit-analyzer",
+    "@semantic-release/release-notes-generator",
+    [
+      "@semantic-release/changelog",
+      {
+        "changelogTitle": "# Changelog\n\nAll notable changes to the `@every-env/compound-plugin` CLI tool will be documented in this file.\n\nThe format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),\nand this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).\n\nRelease numbering now follows the repository `v*` tag line. Starting at `v2.34.0`, the root CLI package and this changelog stay on that shared version stream. Older entries below retain the previous `0.x` CLI numbering."
+      }
+    ],
+    "@semantic-release/npm",
+    [
+      "@semantic-release/git",
+      {
+        "assets": [
+          "CHANGELOG.md",
+          "package.json"
+        ],
+        "message": "chore(release): ${nextRelease.version} [skip ci]"
+      }
+    ],
+    [
+      "@semantic-release/github",
+      {
+        "successComment": false,
+        "failCommentCondition": false,
+        "labels": false,
+        "releasedLabels": false
+      }
+    ]
+  ]
+}
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -7,7 +7,8 @@ This repository contains a Bun/TypeScript CLI that converts Claude Code plugins
 - **Branching:** Create a feature branch for any non-trivial change. If already on the correct branch for the task, keep using it; do not create additional branches or worktrees unless explicitly requested.
 - **Safety:** Do not delete or overwrite user data. Avoid destructive commands.
 - **Testing:** Run `bun test` after changes that affect parsing, conversion, or output.
- **Output Paths:** Keep OpenCode output at `opencode.json` and `.opencode/{agents,skills,plugins}`.
+- **Release versioning:** The root CLI package (`package.json`, root `CHANGELOG.md`, and repo `v*` tags) uses one shared release line managed by semantic-release on `main`. Do not start or maintain a separate root CLI version stream. Use conventional commits and let release automation write the next root package version. Keep the root changelog header block in sync with `.releaserc.json` `changelogTitle` so generated release entries stay under the header. Embedded marketplace plugin metadata (`plugins/compound-engineering/.claude-plugin/plugin.json` and `.claude-plugin/marketplace.json`) is a separate version surface and may differ, but contributors should not guess or hand-bump release versions for it in normal PRs. The automated release process decides the next plugin/marketplace releases and changelog entries after deciding which merged changes ship together.
+- **Output Paths:** Keep OpenCode output at `opencode.json` and `.opencode/{agents,skills,plugins}`. For OpenCode, command go to `~/.config/opencode/commands/<name>.md`; `opencode.json` is deep-merged (never overwritten wholesale).
 - **ASCII-first:** Use ASCII unless the file already contains Unicode.

 ## Adding a New Target Provider (e.g., Codex)
@@ -46,3 +47,17 @@ Add a new provider when at least one of these is true:
 - You can write fixtures + tests that validate the mapping.

 Avoid adding a provider if the target spec is unstable or undocumented.
+
+## Agent References in Skills
+
+When referencing agents from within skill SKILL.md files (e.g., via the `Agent` or `Task` tool), always use the **fully-qualified namespace**: `compound-engineering:<category>:<agent-name>`. Never use the short agent name alone.
+
+Example:
+- `compound-engineering:research:learnings-researcher` (correct)
+- `learnings-researcher` (wrong - will fail to resolve at runtime)
+
+This prevents resolution failures when the plugin is installed alongside other plugins that may define agents with the same short name.
+
+## Repository Docs Convention
+
+- **Plans** live in `docs/plans/` and track implementation progress.
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -5,6 +5,214 @@ All notable changes to the `@every-env/compound-plugin` CLI tool will be documen
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

+Release numbering now follows the repository `v*` tag line. Starting at `v2.34.0`, the root CLI package and this changelog stay on that shared version stream. Older entries below retain the previous `0.x` CLI numbering.
+
+## [2.37.1](https://github.com/EveryInc/compound-engineering-plugin/compare/v2.37.0...v2.37.1) (2026-03-16)
+
+
+### Bug Fixes
+
+* **compound:** remove overly defensive context budget precheck ([#278](https://github.com/EveryInc/compound-engineering-plugin/issues/278)) ([#279](https://github.com/EveryInc/compound-engineering-plugin/issues/279)) ([84ca52e](https://github.com/EveryInc/compound-engineering-plugin/commit/84ca52efdb198c7c8ae6c94ca06fc02d2c3ef648))
+
+# [2.37.0](https://github.com/EveryInc/compound-engineering-plugin/compare/v2.36.5...v2.37.0) (2026-03-15)
+
+
+### Features
+
+* sync agent-browser skill with upstream vercel-labs/agent-browser ([24860ec](https://github.com/EveryInc/compound-engineering-plugin/commit/24860ec3f1f1e7bfdee0f4408636ada1a3bb8f75))
+
+## [2.36.5](https://github.com/EveryInc/compound-engineering-plugin/compare/v2.36.4...v2.36.5) (2026-03-15)
+
+
+### Bug Fixes
+
+* **create-agent-skills:** remove literal dynamic context directives that break skill loading ([4b4d1ae](https://github.com/EveryInc/compound-engineering-plugin/commit/4b4d1ae2707895d6d4fd2e60a64d83ca50f094a6)), closes [anthropics/claude-code#27149](https://github.com/anthropics/claude-code/issues/27149) [#13655](https://github.com/EveryInc/compound-engineering-plugin/issues/13655)
+
+## [2.36.4](https://github.com/EveryInc/compound-engineering-plugin/compare/v2.36.3...v2.36.4) (2026-03-14)
+
+
+### Bug Fixes
+
+* **skills:** use fully-qualified agent namespace in Task invocations ([026602e](https://github.com/EveryInc/compound-engineering-plugin/commit/026602e6247d63a83502b80e72cd318232a06af7)), closes [#251](https://github.com/EveryInc/compound-engineering-plugin/issues/251)
+
+## [2.36.3](https://github.com/EveryInc/compound-engineering-plugin/compare/v2.36.2...v2.36.3) (2026-03-13)
+
+
+### Bug Fixes
+
+* **targets:** nest colon-separated command names into directories ([a84682c](https://github.com/EveryInc/compound-engineering-plugin/commit/a84682cd35e94b0408f6c6a990af0732c2acf03f)), closes [#226](https://github.com/EveryInc/compound-engineering-plugin/issues/226)
+
+## [2.36.2](https://github.com/EveryInc/compound-engineering-plugin/compare/v2.36.1...v2.36.2) (2026-03-13)
+
+
+### Bug Fixes
+
+* **plan:** remove deprecated /technical_review references ([0ab9184](https://github.com/EveryInc/compound-engineering-plugin/commit/0ab91847f278efba45477462d8e93db5f068e058)), closes [#244](https://github.com/EveryInc/compound-engineering-plugin/issues/244)
+
+## [2.36.1](https://github.com/EveryInc/compound-engineering-plugin/compare/v2.36.0...v2.36.1) (2026-03-13)
+
+
+### Bug Fixes
+
+* **agents:** update learnings-researcher model from haiku to inherit ([30852b7](https://github.com/EveryInc/compound-engineering-plugin/commit/30852b72937091b0a85c22b7c8c45d513ab49fd1)), closes [#249](https://github.com/EveryInc/compound-engineering-plugin/issues/249)
+
+# [2.36.0](https://github.com/EveryInc/compound-engineering-plugin/compare/v2.35.0...v2.36.0) (2026-03-11)
+
+
+### Bug Fixes
+
+* **hooks:** wrap PreToolUse handlers in try-catch to prevent parallel tool call crashes ([598222e](https://github.com/EveryInc/compound-engineering-plugin/commit/598222e11cb2206a2e3347cb5dd38cacdc3830df)), closes [#85](https://github.com/EveryInc/compound-engineering-plugin/issues/85)
+* **install:** merge config instead of overwriting on opencode target ([1db7680](https://github.com/EveryInc/compound-engineering-plugin/commit/1db76800f91fefcc1bb9c1798ef273ddd0b65f5c)), closes [#125](https://github.com/EveryInc/compound-engineering-plugin/issues/125)
+* **review:** add serial mode to prevent context limit crashes ([d96671b](https://github.com/EveryInc/compound-engineering-plugin/commit/d96671b9e9ecbe417568b2ce7f7fa4d379c2bec2)), closes [#166](https://github.com/EveryInc/compound-engineering-plugin/issues/166)
+
+
+### Features
+
+* **compound:** add context budget precheck and compact-safe mode ([c4b1358](https://github.com/EveryInc/compound-engineering-plugin/commit/c4b13584312058cb8db3ad0f25674805bbb91b2d)), closes [#198](https://github.com/EveryInc/compound-engineering-plugin/issues/198)
+* **plan:** add daily sequence number to plan filenames ([e94ca04](https://github.com/EveryInc/compound-engineering-plugin/commit/e94ca0409671efcfa2d4a8fcb2d60b79a848fd85)), closes [#135](https://github.com/EveryInc/compound-engineering-plugin/issues/135)
+* **plugin:** release v2.39.0 with community contributions ([d2ab6c0](https://github.com/EveryInc/compound-engineering-plugin/commit/d2ab6c076882a4dacaa787c0a6f3c9d555d38af0))
+
+# [2.35.0](https://github.com/EveryInc/compound-engineering-plugin/compare/v2.34.7...v2.35.0) (2026-03-10)
+
+
+### Bug Fixes
+
+* **test-browser:** detect dev server port from project config ([94aedd5](https://github.com/EveryInc/compound-engineering-plugin/commit/94aedd5a7b6da4ce48de994b5a137953c0fd21c3)), closes [#164](https://github.com/EveryInc/compound-engineering-plugin/issues/164)
+
+
+### Features
+
+* **compound:** add context budget precheck and compact-safe mode ([7266062](https://github.com/EveryInc/compound-engineering-plugin/commit/726606286873c4059261a8c5f1b75c20fe11ac77)), closes [#198](https://github.com/EveryInc/compound-engineering-plugin/issues/198)
+* **plan:** add daily sequence number to plan filenames ([4fc6ddc](https://github.com/EveryInc/compound-engineering-plugin/commit/4fc6ddc5db3e2b4b398c0ffa0c156e1177b35d05)), closes [#135](https://github.com/EveryInc/compound-engineering-plugin/issues/135)
+
+## [2.34.7](https://github.com/EveryInc/compound-engineering-plugin/compare/v2.34.6...v2.34.7) (2026-03-10)
+
+
+### Bug Fixes
+
+* **test-browser:** detect dev server port from project config ([50cb89e](https://github.com/EveryInc/compound-engineering-plugin/commit/50cb89efde7cee7d6dcd42008e6060e1bec44fcc)), closes [#164](https://github.com/EveryInc/compound-engineering-plugin/issues/164)
+
+## [2.34.6](https://github.com/EveryInc/compound-engineering-plugin/compare/v2.34.5...v2.34.6) (2026-03-10)
+
+
+### Bug Fixes
+
+* **mcp:** add API key auth support for Context7 server ([c649cfc](https://github.com/EveryInc/compound-engineering-plugin/commit/c649cfc17f895b58babf737dfdec2f6cc391e40a)), closes [#153](https://github.com/EveryInc/compound-engineering-plugin/issues/153)
+
+## [2.34.5](https://github.com/EveryInc/compound-engineering-plugin/compare/v2.34.4...v2.34.5) (2026-03-10)
+
+
+### Bug Fixes
+
+* **lfg:** enforce plan phase with explicit step gating ([b07f43d](https://github.com/EveryInc/compound-engineering-plugin/commit/b07f43ddf59cd7f2fe54b2e0a00d2b5b508b7f11)), closes [#227](https://github.com/EveryInc/compound-engineering-plugin/issues/227)
+
+## [2.34.4](https://github.com/EveryInc/compound-engineering-plugin/compare/v2.34.3...v2.34.4) (2026-03-04)
+
+
+### Bug Fixes
+
+* **openclaw:** emit empty configSchema in plugin manifests ([4e9899f](https://github.com/EveryInc/compound-engineering-plugin/commit/4e9899f34693711b8997cf73eaa337f0da2321d6)), closes [#224](https://github.com/EveryInc/compound-engineering-plugin/issues/224)
+
+## [2.34.3](https://github.com/EveryInc/compound-engineering-plugin/compare/v2.34.2...v2.34.3) (2026-03-03)
+
+
+### Bug Fixes
+
+* **release:** keep changelog header stable ([2fd29ff](https://github.com/EveryInc/compound-engineering-plugin/commit/2fd29ff6ed99583a8539b7a1e876194df5b18dd6))
+
+## [2.34.2](https://github.com/EveryInc/compound-engineering-plugin/compare/v2.34.1...v2.34.2) (2026-03-03)
+
+### Bug Fixes
+
+* **release:** add package repository metadata ([eab77bc](https://github.com/EveryInc/compound-engineering-plugin/commit/eab77bc5b5361dc73e2ec8aa4678c8bb6114f6e7))
+
+## [2.34.1](https://github.com/EveryInc/compound-engineering-plugin/compare/v2.34.0...v2.34.1) (2026-03-03)
+
+### Bug Fixes
+
+* **release:** align cli versioning with repo tags ([7c58eee](https://github.com/EveryInc/compound-engineering-plugin/commit/7c58eeeec6cf33675cbe2b9639c7d69b92ecef60))
+
+## [2.34.0] - 2026-03-03
+
+### Added
+
+- **Sync parity across supported providers** — `sync` now uses a shared target registry and supports MCP sync for Codex, Droid, Gemini, Copilot, Pi, Windsurf, Kiro, and Qwen, with OpenClaw kept validation-gated for skills-only sync.
+- **Personal command sync** — Personal Claude commands from `~/.claude/commands/` now sync into provider-native command surfaces, including Codex prompts and generated skills, Gemini TOML commands, OpenCode command markdown, Windsurf workflows, and converted skills where that is the closest available equivalent.
+
+### Changed
+
+- **Global user config targets** — Copilot sync now writes to `~/.copilot/` and Gemini sync writes to `~/.gemini/`, matching current documented user-level config locations.
+- **Gemini skill deduplication** — Gemini sync now avoids mirroring skills that Gemini already resolves from `~/.agents/skills`, preventing duplicate skill conflict warnings after sync.
+
+### Fixed
+
+- **Safe skill sync replacement** — When a real directory already exists at a symlink target (for example `~/.config/opencode/skills/proof`), sync now logs a warning and skips instead of throwing an error.
+
+---
+
+## [0.12.0] - 2026-03-01
+
+### Added
+
+- **Auto-detect install targets** — `install --to all` and `convert --to all` auto-detect installed AI coding tools and install to all of them in one command
+- **Gemini sync** — `sync --target gemini` symlinks personal skills to `.gemini/skills/` and merges MCP servers into `.gemini/settings.json`
+- **Sync all targets** — `sync --target all` syncs personal config to all detected tools
+- **Tool detection utility** — Checks config directories for OpenCode, Codex, Droid, Cursor, Pi, and Gemini
+
+---
+
+## [0.11.0] - 2026-03-01
+
+### Added
+
+- **OpenClaw target** — `--to openclaw` converts plugins to OpenClaw format. Agents become `.md` files, commands become `.md` files, pass-through skills copy unchanged, and MCP servers are written to `openclaw-extension.json`. Output goes to `~/.openclaw/extensions/<plugin-name>/` by default. Use `--openclaw-home` to override. ([#217](https://github.com/EveryInc/compound-engineering-plugin/pull/217)) — thanks [@TrendpilotAI](https://github.com/TrendpilotAI)!
+- **Qwen Code target** — `--to qwen` converts plugins to Qwen Code extension format. Agents become `.yaml` files with Qwen-compatible fields, commands become `.md` files, MCP servers write to `qwen-extension.json`, and a `QWEN.md` context file is generated. Output goes to `~/.qwen/extensions/<plugin-name>/` by default. Use `--qwen-home` to override. ([#220](https://github.com/EveryInc/compound-engineering-plugin/pull/220)) — thanks [@rlam3](https://github.com/rlam3)!
+- **Windsurf target** — `--to windsurf` converts plugins to Windsurf format. Claude agents become Windsurf skills (`skills/{name}/SKILL.md`), commands become flat workflows (`global_workflows/{name}.md` for global scope, `workflows/{name}.md` for workspace), and pass-through skills copy unchanged. MCP servers write to `mcp_config.json` (machine-readable, merged with existing config). ([#202](https://github.com/EveryInc/compound-engineering-plugin/pull/202)) — thanks [@rburnham52](https://github.com/rburnham52)!
+- **Global scope support** — New `--scope global|workspace` flag (generic, Windsurf as first adopter). `--to windsurf` defaults to global scope (`~/.codeium/windsurf/`), making installed skills, workflows, and MCP servers available across all projects. Use `--scope workspace` for project-level `.windsurf/` output.
+- **`mcp_config.json` integration** — Windsurf converter writes proper machine-readable MCP config supporting stdio, Streamable HTTP, and SSE transports. Merges with existing config (user entries preserved, plugin entries take precedence). Written with `0o600` permissions.
+- **Shared utilities** — Extracted `resolveTargetOutputRoot` to `src/utils/resolve-output.ts` and `hasPotentialSecrets` to `src/utils/secrets.ts` to eliminate duplication.
+
+### Fixed
+
+- **OpenClaw code injection** — `generateEntryPoint` now uses `JSON.stringify()` for all string interpolation (was escaping only `"`, leaving `\n`/`\\` unguarded).
+- **Qwen `plugin.manifest.name`** — context file header was `# undefined` due to using `plugin.name` (which doesn't exist on `ClaudePlugin`); fixed to `plugin.manifest.name`.
+- **Qwen remote MCP servers** — curl fallback removed; HTTP/SSE servers are now skipped with a warning (Qwen only supports stdio transport).
+- **`--openclaw-home` / `--qwen-home` CLI flags** — wired through to `resolveTargetOutputRoot` so custom home directories are respected.
+
+---
+
+## [0.9.1] - 2026-02-20
+
+### Changed
+
+- **Remove docs/reports and docs/decisions directories** — only `docs/plans/` is retained as living documents that track implementation progress
+- **OpenCode commands as Markdown** — commands are now `.md` files with deep-merged config, permissions default to none ([#201](https://github.com/EveryInc/compound-engineering-plugin/pull/201)) — thanks [@0ut5ider](https://github.com/0ut5ider)!
+- **Fix changelog GitHub link** ([#215](https://github.com/EveryInc/compound-engineering-plugin/pull/215)) — thanks [@XSAM](https://github.com/XSAM)!
+- **Update Claude Code install command in README** ([#218](https://github.com/EveryInc/compound-engineering-plugin/pull/218)) — thanks [@ianguelman](https://github.com/ianguelman)!
+
+---
+
+## [0.9.0] - 2026-02-17
+
+### Added
+
+- **Kiro CLI target** — `--to kiro` converts plugins to `.kiro/` format with custom agent JSON configs, prompt files, skills, steering files, and `mcp.json`. Only stdio MCP servers are supported ([#196](https://github.com/EveryInc/compound-engineering-plugin/pull/196)) — thanks [@krthr](https://github.com/krthr)!
+
+---
+
+## [0.8.0] - 2026-02-17
+
+### Added
+
+- **GitHub Copilot target** — `--to copilot` converts plugins to `.github/` format with `.agent.md` files, `SKILL.md` skills, and `copilot-mcp-config.json`. Also supports `sync --target copilot` ([#192](https://github.com/EveryInc/compound-engineering-plugin/pull/192)) — thanks [@brayanjuls](https://github.com/brayanjuls)!
+- **Native Cursor plugin support** — Cursor now installs via `/add-plugin compound-engineering` using Cursor's native plugin system instead of CLI conversion ([#184](https://github.com/EveryInc/compound-engineering-plugin/pull/184)) — thanks [@ericzakariasson](https://github.com/ericzakariasson)!
+
+### Removed
+
+- Cursor CLI conversion target (`--to cursor`) — replaced by native Cursor plugin install
+
+---
+
 ## [0.6.0] - 2026-02-12

 ### Added
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -1,11 +1,11 @@
-# Every Marketplace - Claude Code Plugin Marketplace
+# compound-engineering-plugin - Claude Code Plugin Marketplace

 This repository is a Claude Code plugin marketplace that distributes the `compound-engineering` plugin to developers building with AI-powered tools.

 ## Repository Structure

 ```
-every-marketplace/
+compound-engineering-plugin/
 ├── .claude-plugin/
 │   └── marketplace.json          # Marketplace catalog (lists available plugins)
 ├── docs/                         # Documentation site (GitHub Pages)
@@ -38,6 +38,20 @@ When working on this repository, follow the compounding engineering process:

 ## Working with This Repository

+## CLI Release Versioning
+
+The repository has two separate version surfaces:
+
+1. **Root CLI package** — `package.json`, root `CHANGELOG.md`, and repo `v*` tags all share one release line managed by semantic-release on `main`.
+2. **Embedded marketplace plugin metadata** — `plugins/compound-engineering/.claude-plugin/plugin.json` and `.claude-plugin/marketplace.json` track the distributed Claude plugin metadata and can differ from the root CLI package version.
+
+Rules:
+
+- Do not start a separate root CLI version stream. The root CLI follows the repo tag line.
+- Do not hand-bump the root CLI `package.json` or root `CHANGELOG.md` for routine feature work. Use conventional commits and let semantic-release write the released root version back to git.
+- Keep the root `CHANGELOG.md` header block aligned with `.releaserc.json` `changelogTitle`. If they drift, semantic-release will prepend release notes above the header.
+- Do not guess or hand-bump embedded plugin release versions in routine PRs. The automated release process decides the next plugin/marketplace version and generate release changelog entries after choosing which merged changes ship together.
+
 ### Adding a New Plugin

 1. Create plugin directory: `plugins/new-plugin-name/`
@@ -79,17 +93,17 @@ The description appears in multiple places and must match everywhere:

 Format: `"Includes X specialized agents, Y commands, and Z skill(s)."`

-#### 3. Update version numbers
+#### 3. Do not pre-cut release versions

-When adding new functionality, bump the version in:
+Contributors should not guess the next released plugin version in a normal PR:

- [ ] `plugins/compound-engineering/.claude-plugin/plugin.json` → `version`
- [ ] `.claude-plugin/marketplace.json` → plugin `version`
+- [ ] No manual bump in `plugins/compound-engineering/.claude-plugin/plugin.json` → `version`
+- [ ] No manual bump in `.claude-plugin/marketplace.json` → plugin `version`

 #### 4. Update documentation

 - [ ] `plugins/compound-engineering/README.md` → list all components
- [ ] `plugins/compound-engineering/CHANGELOG.md` → document changes
+- [ ] Do not cut a release section in `plugins/compound-engineering/CHANGELOG.md` for a normal feature PR
 - [ ] `CLAUDE.md` → update structure diagram if needed

 #### 5. Rebuild documentation site
@@ -261,7 +275,7 @@ python -m http.server 8000
 1. Install the marketplace locally:

   ```bash
-   claude /plugin marketplace add /Users/yourusername/every-marketplace
+   claude /plugin marketplace add /Users/yourusername/compound-engineering-plugin
   ```

 2. Install the plugin:
--- a/PRIVACY.md
+++ b/PRIVACY.md
@@ -0,0 +1,38 @@
+# Privacy & Data Handling
+
+This repository contains:
+- a plugin package (`plugins/compound-engineering`) made of markdown/config content
+- a CLI (`@every-env/compound-plugin`) that converts and installs plugin content for different AI coding tools
+
+## Summary
+
+- The plugin package does not include telemetry or analytics code.
+- The plugin package does not run a background service that uploads repository/workspace contents automatically.
+- Data leaves your machine only when your host/tooling or an explicitly invoked integration performs a network request.
+
+## What May Send Data
+
+1. AI host/model providers
+
+If you run the plugin in tools like Claude Code, Cursor, Gemini CLI, Copilot, Kiro, Windsurf, etc., those tools may send prompts/context/code to their configured model providers. This behavior is controlled by those tools and providers, not by this plugin repository.
+
+2. Optional integrations and tools
+
+The plugin includes optional capabilities that can call external services when explicitly used, for example:
+- Context7 MCP (`https://mcp.context7.com/mcp`) for documentation lookup
+- Proof (`https://www.proofeditor.ai`) when using share/edit flows
+- Other opt-in skills (for example image generation or cloud upload workflows) that call their own external APIs/services
+
+If you do not invoke these integrations, they do not transmit your project data.
+
+3. Package/installer infrastructure
+
+Installing dependencies or packages (for example `npm`, `bunx`) communicates with package registries/CDNs according to your package manager configuration.
+
+## Data Ownership and Retention
+
+This repository does not operate a backend service for collecting or storing your project/workspace data. Data retention and processing for model prompts or optional integrations are governed by the external services you use.
+
+## Security Reporting
+
+If you identify a security issue in this repository, follow the disclosure process in [SECURITY.md](SECURITY.md).
--- a/README.md
+++ b/README.md
@@ -8,13 +8,19 @@ A Claude Code plugin marketplace featuring the **Compound Engineering Plugin**
 ## Claude Code Install

 ```bash
-/plugin marketplace add https://github.com/EveryInc/compound-engineering-plugin
+/plugin marketplace add EveryInc/compound-engineering-plugin
 /plugin install compound-engineering
 ```

-## OpenCode, Codex, Droid, Cursor, Pi & Gemini (experimental) Install
+## Cursor Install

-This repo includes a Bun/TypeScript CLI that converts Claude Code plugins to OpenCode, Codex, Factory Droid, Cursor, Pi, and Gemini CLI.
+```text
+/add-plugin compound-engineering
+```
+
+## OpenCode, Codex, Droid, Pi, Gemini, Copilot, Kiro, Windsurf, OpenClaw & Qwen (experimental) Install
+
+This repo includes a Bun/TypeScript CLI that converts Claude Code plugins to OpenCode, Codex, Factory Droid, Pi, Gemini CLI, GitHub Copilot, Kiro CLI, Windsurf, OpenClaw, and Qwen Code.

 ```bash
 # convert the compound-engineering plugin into OpenCode format
@@ -26,36 +32,93 @@ bunx @every-env/compound-plugin install compound-engineering --to codex
 # convert to Factory Droid format
 bunx @every-env/compound-plugin install compound-engineering --to droid

-# convert to Cursor format
-bunx @every-env/compound-plugin install compound-engineering --to cursor
-
 # convert to Pi format
 bunx @every-env/compound-plugin install compound-engineering --to pi

 # convert to Gemini CLI format
 bunx @every-env/compound-plugin install compound-engineering --to gemini
+
+# convert to GitHub Copilot format
+bunx @every-env/compound-plugin install compound-engineering --to copilot
+
+# convert to Kiro CLI format
+bunx @every-env/compound-plugin install compound-engineering --to kiro
+
+# convert to OpenClaw format
+bunx @every-env/compound-plugin install compound-engineering --to openclaw
+
+# convert to Windsurf format (global scope by default)
+bunx @every-env/compound-plugin install compound-engineering --to windsurf
+
+# convert to Windsurf workspace scope
+bunx @every-env/compound-plugin install compound-engineering --to windsurf --scope workspace
+
+# convert to Qwen Code format
+bunx @every-env/compound-plugin install compound-engineering --to qwen
+
+# auto-detect installed tools and install to all
+bunx @every-env/compound-plugin install compound-engineering --to all
 ```

-Local dev:
+### Local Development
+
+When developing and testing local changes to the plugin:
+
+**Claude Code** — add a shell alias so your local copy loads alongside your normal plugins:
+
+```bash
+# add to ~/.zshrc or ~/.bashrc
+alias claude-dev-ce='claude --plugin-dir ~/code/compound-engineering-plugin/plugins/compound-engineering'
+```
+
+One-liner to append it:
+
+```bash
+echo "alias claude-dev-ce='claude --plugin-dir ~/code/compound-engineering-plugin/plugins/compound-engineering'" >> ~/.zshrc
+```
+
+Then run `claude-dev-ce` instead of `claude` to test your changes. Your production install stays untouched.
+
+**Codex** — point the install command at your local path:
+
+```bash
+bunx @every-env/compound-plugin install ./plugins/compound-engineering --to codex
+```
+
+**Other targets** — same pattern, swap the target:

 ```bash
 bun run src/index.ts install ./plugins/compound-engineering --to opencode
 ```

-OpenCode output is written to `~/.config/opencode` by default, with `opencode.json` at the root and `agents/`, `skills/`, and `plugins/` alongside it.
-Codex output is written to `~/.codex/prompts` and `~/.codex/skills`, with each Claude command converted into both a prompt and a skill (the prompt instructs Codex to load the corresponding skill). Generated Codex skill descriptions are truncated to 1024 characters (Codex limit).
-Droid output is written to `~/.factory/` with commands, droids (agents), and skills. Claude tool names are mapped to Factory equivalents (`Bash` → `Execute`, `Write` → `Create`, etc.) and namespace prefixes are stripped from commands.
-Cursor output is written to `.cursor/` with rules (`.mdc`), commands, skills, and `mcp.json`. Agents become "Agent Requested" rules (`alwaysApply: false`) so Cursor's AI activates them on demand. Works with both the Cursor IDE and Cursor CLI (`cursor-agent`) — they share the same `.cursor/` config directory.
-Pi output is written to `~/.pi/agent/` by default with prompts, skills, extensions, and `compound-engineering/mcporter.json` for MCPorter interoperability.
-Gemini output is written to `.gemini/` with skills (from agents), commands (`.toml`), and `settings.json` (MCP servers). Namespaced commands create directory structure (`workflows:plan` → `commands/workflows/plan.toml`). Skills use the identical SKILL.md standard and pass through unchanged.
+<details>
+<summary>Output format details per target</summary>
+
+| Target | Output path | Notes |
+|--------|------------|-------|
+| `opencode` | `~/.config/opencode/` | Commands as `.md` files; `opencode.json` MCP config deep-merged; backups made before overwriting |
+| `codex` | `~/.codex/prompts` + `~/.codex/skills` | Each command becomes a prompt + skill pair; descriptions truncated to 1024 chars |
+| `droid` | `~/.factory/` | Tool names mapped (`Bash`→`Execute`, `Write`→`Create`); namespace prefixes stripped |
+| `pi` | `~/.pi/agent/` | Prompts, skills, extensions, and `mcporter.json` for MCPorter interoperability |
+| `gemini` | `.gemini/` | Skills from agents; commands as `.toml`; namespaced commands become directories (`workflows:plan` → `commands/workflows/plan.toml`) |
+| `copilot` | `.github/` | Agents as `.agent.md` with Copilot frontmatter; MCP env vars prefixed with `COPILOT_MCP_` |
+| `kiro` | `.kiro/` | Agents as JSON configs + prompt `.md` files; only stdio MCP servers supported |
+| `openclaw` | `~/.openclaw/extensions/<plugin>/` | Entry-point TypeScript skill file; `openclaw-extension.json` for MCP servers |
+| `windsurf` | `~/.codeium/windsurf/` (global) or `.windsurf/` (workspace) | Agents become skills; commands become flat workflows; `mcp_config.json` merged |
+| `qwen` | `~/.qwen/extensions/<plugin>/` | Agents as `.yaml`; env vars with placeholders extracted as settings; colon separator for nested commands |

 All provider targets are experimental and may change as the formats evolve.

+</details>
+
 ## Sync Personal Config

-Sync your personal Claude Code config (`~/.claude/`) to other AI coding tools:
+Sync your personal Claude Code config (`~/.claude/`) to other AI coding tools. Omit `--target` to sync to all detected supported tools automatically:

 ```bash
+# Sync to all detected tools (default)
+bunx @every-env/compound-plugin sync
+
 # Sync skills and MCP servers to OpenCode
 bunx @every-env/compound-plugin sync --target opencode

@@ -65,33 +128,75 @@ bunx @every-env/compound-plugin sync --target codex
 # Sync to Pi
 bunx @every-env/compound-plugin sync --target pi

-# Sync to Droid (skills only)
+# Sync to Droid
 bunx @every-env/compound-plugin sync --target droid

-# Sync to Cursor (skills + MCP servers)
-bunx @every-env/compound-plugin sync --target cursor
+# Sync to GitHub Copilot (skills + MCP servers)
+bunx @every-env/compound-plugin sync --target copilot
+
+# Sync to Gemini (skills + MCP servers)
+bunx @every-env/compound-plugin sync --target gemini
+
+# Sync to Windsurf
+bunx @every-env/compound-plugin sync --target windsurf
+
+# Sync to Kiro
+bunx @every-env/compound-plugin sync --target kiro
+
+# Sync to Qwen
+bunx @every-env/compound-plugin sync --target qwen
+
+# Sync to OpenClaw (skills only; MCP is validation-gated)
+bunx @every-env/compound-plugin sync --target openclaw
+
+# Sync to all detected tools
+bunx @every-env/compound-plugin sync --target all
 ```

 This syncs:
 - Personal skills from `~/.claude/skills/` (as symlinks)
+- Personal slash commands from `~/.claude/commands/` (as provider-native prompts, workflows, or converted skills where supported)
 - MCP servers from `~/.claude/settings.json`

 Skills are symlinked (not copied) so changes in Claude Code are reflected immediately.

+Supported sync targets:
+- `opencode`
+- `codex`
+- `pi`
+- `droid`
+- `copilot`
+- `gemini`
+- `windsurf`
+- `kiro`
+- `qwen`
+- `openclaw`
+
+Notes:
+- Codex sync preserves non-managed `config.toml` content and now includes remote MCP servers.
+- Command sync reuses each provider's existing Claude command conversion, so some targets receive prompts or workflows while others receive converted skills.
+- Copilot sync writes personal skills to `~/.copilot/skills/` and MCP config to `~/.copilot/mcp-config.json`.
+- Gemini sync writes MCP config to `~/.gemini/` and avoids mirroring skills that Gemini already discovers from `~/.agents/skills`, which prevents duplicate-skill warnings.
+- Droid, Windsurf, Kiro, and Qwen sync merge MCP servers into the provider's documented user config.
+- OpenClaw currently syncs skills only. Personal command sync is skipped because this repo does not yet have a documented user-level OpenClaw command surface, and MCP sync is skipped because the current official OpenClaw docs do not clearly document an MCP server config contract.
+
 ## Workflow

 ```
-Plan → Work → Review → Compound → Repeat
+Brainstorm → Plan → Work → Review → Compound → Repeat
 ```

 | Command | Purpose |
 |---------|---------|
-| `/workflows:plan` | Turn feature ideas into detailed implementation plans |
-| `/workflows:work` | Execute plans with worktrees and task tracking |
-| `/workflows:review` | Multi-agent code review before merging |
-| `/workflows:compound` | Document learnings to make future work easier |
+| `/ce:brainstorm` | Explore requirements and approaches before planning |
+| `/ce:plan` | Turn feature ideas into detailed implementation plans |
+| `/ce:work` | Execute plans with worktrees and task tracking |
+| `/ce:review` | Multi-agent code review before merging |
+| `/ce:compound` | Document learnings to make future work easier |

-Each cycle compounds: plans inform future plans, reviews catch more issues, patterns get documented.
+The `brainstorming` skill supports `/ce:brainstorm` with collaborative dialogue to clarify requirements and compare approaches before committing to a plan.
+
+Each cycle compounds: brainstorms sharpen plans, plans inform future plans, reviews catch more issues, patterns get documented.

 ## Philosophy

--- a/SECURITY.md
+++ b/SECURITY.md
@@ -0,0 +1,29 @@
+# Security Policy
+
+## Supported Versions
+
+Security fixes are applied to the latest version on `main`.
+
+## Reporting a Vulnerability
+
+Please do not open a public issue for undisclosed vulnerabilities.
+
+Instead, report privately by emailing:
+- `kieran@every.to`
+
+Include:
+- A clear description of the issue
+- Reproduction steps or proof of concept
+- Impact assessment (what an attacker can do)
+- Any suggested mitigation
+
+We will acknowledge receipt as soon as possible and work with you on validation, remediation, and coordinated disclosure timing.
+
+## Scope Notes
+
+This repository primarily contains plugin instructions/configuration plus a conversion/install CLI.
+
+- Plugin instruction content itself does not run as a server process.
+- Security/privacy behavior also depends on the host AI tool and any external integrations you explicitly invoke.
+
+For data-handling details, see [PRIVACY.md](PRIVACY.md).
--- a/bun.lock
+++ b/bun.lock
--- a/docs/brainstorms/2026-02-14-copilot-converter-target-brainstorm.md
+++ b/docs/brainstorms/2026-02-14-copilot-converter-target-brainstorm.md
@@ -0,0 +1,117 @@
+---
+date: 2026-02-14
+topic: copilot-converter-target
+---
+
+# Add GitHub Copilot Converter Target
+
+## What We're Building
+
+A new converter target that transforms the compound-engineering Claude Code plugin into GitHub Copilot's native format. This follows the same established pattern as the existing converters (Cursor, Codex, OpenCode, Droid, Pi) and outputs files that Copilot can consume directly from `.github/` (repo-level) or `~/.copilot/` (user-wide).
+
+Copilot's customization system (as of early 2026) supports: custom agents (`.agent.md`), agent skills (`SKILL.md`), prompt files (`.prompt.md`), custom instructions (`copilot-instructions.md`), and MCP servers (via repo settings).
+
+## Why This Approach
+
+The repository already has a robust multi-target converter infrastructure with a consistent `TargetHandler` pattern. Adding Copilot as a new target follows this proven pattern rather than inventing something new. Copilot's format is close enough to Claude Code's that the conversion is straightforward, and the SKILL.md format is already cross-compatible.
+
+### Approaches Considered
+
+1. **Full converter target (chosen)** — Follow the existing pattern with types, converter, writer, and target registration. Most consistent with codebase conventions.
+2. **Minimal agent-only converter** — Only convert agents, skip commands/skills. Too limited; users would lose most of the plugin's value.
+3. **Documentation-only approach** — Just document how to manually set up Copilot. Doesn't compound — every user would repeat the work.
+
+## Key Decisions
+
+### Component Mapping
+
+| Claude Code Component | Copilot Equivalent | Notes |
+|----------------------|-------------------|-------|
+| **Agents** (`.md`) | **Custom Agents** (`.agent.md`) | Full frontmatter mapping: description, tools, target, infer |
+| **Commands** (`.md`) | **Agent Skills** (`SKILL.md`) | Commands become skills since Copilot has no direct command equivalent. `allowed-tools` dropped silently. |
+| **Skills** (`SKILL.md`) | **Agent Skills** (`SKILL.md`) | Copy as-is — format is already cross-compatible |
+| **MCP Servers** | **Repo settings JSON** | Generate a `copilot-mcp-config.json` users paste into GitHub repo settings |
+| **Hooks** | **Skipped with warning** | Copilot doesn't have a hooks equivalent |
+
+### Agent Frontmatter Mapping
+
+| Claude Field | Copilot Field | Mapping |
+|-------------|--------------|---------|
+| `name` | `name` | Direct pass-through |
+| `description` | `description` (required) | Direct pass-through, generate fallback if missing |
+| `capabilities` | Body text | Fold into body as "## Capabilities" section (like Cursor) |
+| `model` | `model` | Pass through (works in IDE, may be ignored on github.com) |
+| — | `tools` | Default to `["*"]` (all tools). Claude agents have unrestricted tool access, so Copilot agents should too. |
+| — | `target` | Omit (defaults to `both` — IDE + github.com) |
+| — | `infer` | Set to `true` (auto-selection enabled) |
+
+### Output Directories
+
+- **Repository-level (default):** `.github/agents/`, `.github/skills/`
+- **User-wide (with --personal flag):** `~/.copilot/skills/` (only skills supported at this level)
+
+### Content Transformation
+
+Apply transformations similar to Cursor converter:
+
+1. **Task agent calls:** `Task agent-name(args)` → `Use the agent-name skill to: args`
+2. **Slash commands:** `/workflows:plan` → `/plan` (flatten namespace)
+3. **Path rewriting:** `.claude/` → `.github/` (Copilot's repo-level config path)
+4. **Agent references:** `@agent-name` → `the agent-name agent`
+
+### MCP Server Handling
+
+Generate a `copilot-mcp-config.json` file with the structure Copilot expects:
+
+```json
+{
+  "mcpServers": {
+    "server-name": {
+      "type": "local",
+      "command": "npx",
+      "args": ["package"],
+      "tools": ["*"],
+      "env": {
+        "KEY": "COPILOT_MCP_KEY"
+      }
+    }
+  }
+}
+```
+
+Note: Copilot requires env vars to use the `COPILOT_MCP_` prefix. The converter should transform env var names accordingly and include a comment/note about this.
+
+## Files to Create/Modify
+
+### New Files
+
+- `src/types/copilot.ts` — Type definitions (CopilotAgent, CopilotSkill, CopilotBundle, etc.)
+- `src/converters/claude-to-copilot.ts` — Converter with `transformContentForCopilot()`
+- `src/targets/copilot.ts` — Writer with `writeCopilotBundle()`
+- `docs/specs/copilot.md` — Format specification document
+
+### Modified Files
+
+- `src/targets/index.ts` — Register copilot target handler
+- `src/commands/sync.ts` — Add "copilot" to valid sync targets
+
+### Test Files
+
+- `tests/copilot-converter.test.ts` — Converter tests following existing patterns
+
+### Character Limit
+
+Copilot imposes a 30,000 character limit on agent body content. If an agent body exceeds this after folding in capabilities, the converter should truncate with a warning to stderr.
+
+### Agent File Extension
+
+Use `.agent.md` (not plain `.md`). This is the canonical Copilot convention and makes agent files immediately identifiable.
+
+## Open Questions
+
+- Should the converter generate a `copilot-setup-steps.yml` workflow file for MCP servers that need special dependencies (e.g., `uv`, `pipx`)?
+- Should `.github/copilot-instructions.md` be generated with any base instructions from the plugin?
+
+## Next Steps
+
+→ `/workflows:plan` for implementation details
--- a/docs/brainstorms/2026-02-17-copilot-skill-naming-brainstorm.md
+++ b/docs/brainstorms/2026-02-17-copilot-skill-naming-brainstorm.md
@@ -0,0 +1,30 @@
+---
+date: 2026-02-17
+topic: copilot-skill-naming
+---
+
+# Copilot Skill Naming: Preserve Namespace
+
+## What We're Building
+
+Change the Copilot converter to preserve command namespaces when converting commands to skills. Currently `workflows:plan` flattens to `plan`, which is too generic and clashes with Copilot's own features in the chat suggestion UI.
+
+## Why This Approach
+
+The `flattenCommandName` function strips everything before the last colon, producing names like `plan`, `review`, `work` that are too generic for Copilot's skill discovery UI. Replacing colons with hyphens (`workflows:plan` -> `workflows-plan`) preserves context while staying within valid filename characters.
+
+## Key Decisions
+
+- **Replace colons with hyphens** instead of stripping the prefix: `workflows:plan` -> `workflows-plan`
+- **Copilot only** — other converters (Cursor, Droid, etc.) keep their current flattening behavior
+- **Content transformation too** — slash command references in body text also use hyphens: `/workflows:plan` -> `/workflows-plan`
+
+## Changes Required
+
+1. `src/converters/claude-to-copilot.ts` — change `flattenCommandName` to replace colons with hyphens
+2. `src/converters/claude-to-copilot.ts` — update `transformContentForCopilot` slash command rewriting
+3. `tests/copilot-converter.test.ts` — update affected tests
+
+## Next Steps
+
+-> Implement directly (small, well-scoped change)
--- a/docs/css/docs.css
+++ b/docs/css/docs.css
@@ -1,675 +0,0 @@
-/* Documentation-specific styles */
-
-/* ============================================
-   Documentation Layout
-   ============================================ */
-
-.docs-layout {
-  display: grid;
-  grid-template-columns: 1fr;
-  min-height: 100vh;
-}
-
-@media (min-width: 1024px) {
-  .docs-layout {
-    grid-template-columns: 280px 1fr;
-  }
-}
-
-/* ============================================
-   Sidebar
-   ============================================ */
-
-.docs-sidebar {
-  position: fixed;
-  top: 0;
-  left: -300px;
-  width: 280px;
-  height: 100vh;
-  background-color: var(--color-background);
-  border-right: 1px solid var(--color-border);
-  overflow-y: auto;
-  transition: left 0.3s ease;
-  z-index: 100;
-}
-
-.docs-sidebar.open {
-  left: 0;
-}
-
-@media (min-width: 1024px) {
-  .docs-sidebar {
-    position: sticky;
-    left: 0;
-  }
-}
-
-.sidebar-header {
-  padding: var(--space-l);
-  border-bottom: 1px solid var(--color-border);
-}
-
-.sidebar-header .nav-brand {
-  display: flex;
-  align-items: center;
-  gap: var(--space-s);
-  text-decoration: none;
-  color: var(--color-text-primary);
-  font-weight: 600;
-}
-
-.sidebar-header .logo-icon {
-  color: var(--color-accent);
-  font-size: var(--font-size-l);
-}
-
-.sidebar-header .logo-text {
-  display: inline;
-}
-
-.sidebar-nav {
-  padding: var(--space-l);
-}
-
-.nav-section {
-  margin-bottom: var(--space-xl);
-}
-
-.nav-section h3 {
-  font-size: var(--font-size-xs);
-  font-weight: 600;
-  text-transform: uppercase;
-  letter-spacing: 0.05em;
-  color: var(--color-text-tertiary);
-  margin: 0 0 var(--space-m) 0;
-}
-
-.nav-section ul {
-  list-style: none;
-  margin: 0;
-  padding: 0;
-}
-
-.nav-section li {
-  margin: 0;
-}
-
-.nav-section a {
-  display: block;
-  padding: var(--space-s) var(--space-m);
-  color: var(--color-text-secondary);
-  text-decoration: none;
-  font-size: var(--font-size-s);
-  border-radius: var(--radius-s);
-  transition: all 0.2s ease;
-}
-
-.nav-section a:hover {
-  color: var(--color-text-primary);
-  background-color: var(--color-surface);
-}
-
-.nav-section a.active {
-  color: var(--color-accent);
-  background-color: var(--color-accent-light);
-}
-
-/* ============================================
-   Main Content
-   ============================================ */
-
-.docs-content {
-  padding: var(--space-xl);
-  max-width: 900px;
-}
-
-@media (min-width: 1024px) {
-  .docs-content {
-    padding: var(--space-xxl);
-  }
-}
-
-.docs-header {
-  display: flex;
-  align-items: center;
-  justify-content: space-between;
-  margin-bottom: var(--space-xl);
-}
-
-.breadcrumb {
-  display: flex;
-  align-items: center;
-  gap: var(--space-s);
-  font-size: var(--font-size-s);
-  color: var(--color-text-tertiary);
-}
-
-.breadcrumb a {
-  color: var(--color-text-secondary);
-  text-decoration: none;
-}
-
-.breadcrumb a:hover {
-  color: var(--color-accent);
-}
-
-.mobile-menu-toggle {
-  display: flex;
-  align-items: center;
-  justify-content: center;
-  width: 40px;
-  height: 40px;
-  background: none;
-  border: 1px solid var(--color-border);
-  border-radius: var(--radius-s);
-  color: var(--color-text-secondary);
-  cursor: pointer;
-}
-
-@media (min-width: 1024px) {
-  .mobile-menu-toggle {
-    display: none;
-  }
-}
-
-/* ============================================
-   Article Styles
-   ============================================ */
-
-.docs-article {
-  line-height: 1.7;
-}
-
-.docs-article h1 {
-  font-size: var(--font-size-xl);
-  margin-bottom: var(--space-l);
-}
-
-.docs-article h2 {
-  font-size: var(--font-size-l);
-  margin-top: var(--space-xxl);
-  margin-bottom: var(--space-l);
-  padding-bottom: var(--space-s);
-  border-bottom: 1px solid var(--color-border);
-  display: flex;
-  align-items: center;
-  gap: var(--space-s);
-}
-
-.docs-article h2 i {
-  color: var(--color-accent);
-}
-
-.docs-article h3 {
-  font-size: var(--font-size-m);
-  margin-top: var(--space-xl);
-  margin-bottom: var(--space-m);
-}
-
-.docs-article h4 {
-  font-size: var(--font-size-s);
-  margin-top: var(--space-l);
-  margin-bottom: var(--space-s);
-}
-
-.docs-article p {
-  margin-bottom: var(--space-l);
-}
-
-.docs-article .lead {
-  font-size: var(--font-size-l);
-  color: var(--color-text-secondary);
-  margin-bottom: var(--space-xl);
-}
-
-.docs-article ul,
-.docs-article ol {
-  margin-bottom: var(--space-l);
-  padding-left: var(--space-xl);
-}
-
-.docs-article li {
-  margin-bottom: var(--space-s);
-}
-
-/* ============================================
-   Code Blocks in Docs
-   ============================================ */
-
-.docs-article .card-code-block {
-  margin: var(--space-l) 0;
-}
-
-.docs-article code {
-  font-family: var(--font-mono);
-  font-size: 0.9em;
-  background-color: var(--color-surface);
-  padding: 2px 6px;
-  border-radius: var(--radius-xs);
-  color: var(--color-accent);
-}
-
-.docs-article pre code {
-  background: none;
-  padding: 0;
-  color: var(--color-code-text);
-}
-
-/* ============================================
-   Tables
-   ============================================ */
-
-.docs-table {
-  width: 100%;
-  border-collapse: collapse;
-  margin: var(--space-l) 0;
-  font-size: var(--font-size-s);
-}
-
-.docs-table th,
-.docs-table td {
-  padding: var(--space-m);
-  text-align: left;
-  border-bottom: 1px solid var(--color-border);
-}
-
-.docs-table th {
-  font-weight: 600;
-  color: var(--color-text-primary);
-  background-color: var(--color-surface);
-}
-
-.docs-table td {
-  color: var(--color-text-secondary);
-}
-
-.docs-table code {
-  font-size: 0.85em;
-}
-
-/* ============================================
-   Callouts
-   ============================================ */
-
-.callout {
-  display: flex;
-  gap: var(--space-m);
-  padding: var(--space-l);
-  border-radius: var(--radius-m);
-  margin: var(--space-l) 0;
-}
-
-.callout-icon {
-  font-size: var(--font-size-l);
-  flex-shrink: 0;
-}
-
-.callout-content h4 {
-  margin: 0 0 var(--space-s) 0;
-  font-size: var(--font-size-s);
-}
-
-.callout-content p {
-  margin: 0;
-  font-size: var(--font-size-s);
-}
-
-.callout-info {
-  background-color: rgba(99, 102, 241, 0.1);
-  border: 1px solid rgba(99, 102, 241, 0.2);
-}
-
-.callout-info .callout-icon {
-  color: var(--color-accent);
-}
-
-.callout-info .callout-content h4 {
-  color: var(--color-accent);
-}
-
-.callout-tip {
-  background-color: rgba(16, 185, 129, 0.1);
-  border: 1px solid rgba(16, 185, 129, 0.2);
-}
-
-.callout-tip .callout-icon {
-  color: var(--color-success);
-}
-
-.callout-tip .callout-content h4 {
-  color: var(--color-success);
-}
-
-.callout-warning {
-  background-color: rgba(245, 158, 11, 0.1);
-  border: 1px solid rgba(245, 158, 11, 0.2);
-}
-
-.callout-warning .callout-icon {
-  color: var(--color-warning);
-}
-
-.callout-warning .callout-content h4 {
-  color: var(--color-warning);
-}
-
-/* ============================================
-   Badges
-   ============================================ */
-
-.badge {
-  display: inline-block;
-  padding: 2px 8px;
-  font-size: var(--font-size-xs);
-  font-weight: 600;
-  border-radius: var(--radius-s);
-  text-transform: uppercase;
-  letter-spacing: 0.03em;
-}
-
-.badge-critical {
-  background-color: rgba(239, 68, 68, 0.15);
-  color: var(--color-error);
-}
-
-.badge-important {
-  background-color: rgba(245, 158, 11, 0.15);
-  color: var(--color-warning);
-}
-
-.badge-nice {
-  background-color: rgba(99, 102, 241, 0.15);
-  color: var(--color-accent);
-}
-
-/* ============================================
-   Philosophy Grid
-   ============================================ */
-
-.philosophy-grid {
-  display: grid;
-  grid-template-columns: repeat(1, 1fr);
-  gap: var(--space-l);
-  margin: var(--space-xl) 0;
-}
-
-@media (min-width: 640px) {
-  .philosophy-grid {
-    grid-template-columns: repeat(2, 1fr);
-  }
-}
-
-.philosophy-card {
-  padding: var(--space-xl);
-  background-color: var(--color-surface);
-  border-radius: var(--radius-m);
-  border: 1px solid var(--color-border);
-}
-
-.philosophy-icon {
-  font-size: var(--font-size-xl);
-  color: var(--color-accent);
-  margin-bottom: var(--space-m);
-}
-
-.philosophy-card h4 {
-  margin: 0 0 var(--space-s) 0;
-  color: var(--color-text-primary);
-}
-
-.philosophy-card p {
-  margin: 0;
-  font-size: var(--font-size-s);
-  color: var(--color-text-secondary);
-}
-
-/* ============================================
-   Blockquotes
-   ============================================ */
-
-.highlight-quote {
-  font-size: var(--font-size-l);
-  font-style: italic;
-  color: var(--color-accent);
-  padding: var(--space-xl);
-  margin: var(--space-xl) 0;
-  background: linear-gradient(135deg, var(--color-accent-lighter), transparent);
-  border-left: 4px solid var(--color-accent);
-  border-radius: var(--radius-m);
-}
-
-/* ============================================
-   Navigation Footer
-   ============================================ */
-
-.docs-nav-footer {
-  display: flex;
-  justify-content: space-between;
-  gap: var(--space-l);
-  margin-top: var(--space-xxl);
-  padding-top: var(--space-xl);
-  border-top: 1px solid var(--color-border);
-}
-
-.nav-prev,
-.nav-next {
-  display: flex;
-  flex-direction: column;
-  gap: var(--space-xs);
-  padding: var(--space-l);
-  background-color: var(--color-surface);
-  border-radius: var(--radius-m);
-  text-decoration: none;
-  transition: all 0.2s ease;
-  flex: 1;
-  max-width: 300px;
-}
-
-.nav-prev:hover,
-.nav-next:hover {
-  background-color: var(--color-surface-hover);
-  border-color: var(--color-accent);
-}
-
-.nav-next {
-  text-align: right;
-  margin-left: auto;
-}
-
-.nav-label {
-  font-size: var(--font-size-xs);
-  color: var(--color-text-tertiary);
-  text-transform: uppercase;
-  letter-spacing: 0.05em;
-}
-
-.nav-title {
-  font-weight: 600;
-  color: var(--color-accent);
-  display: flex;
-  align-items: center;
-  gap: var(--space-s);
-}
-
-.nav-next .nav-title {
-  justify-content: flex-end;
-}
-
-/* ============================================
-   Mobile Sidebar Overlay
-   ============================================ */
-
-@media (max-width: 1023px) {
-  .docs-sidebar.open::before {
-    content: '';
-    position: fixed;
-    top: 0;
-    left: 0;
-    right: 0;
-    bottom: 0;
-    background-color: rgba(0, 0, 0, 0.5);
-    z-index: -1;
-  }
-}
-
-/* ============================================
-   Changelog Styles
-   ============================================ */
-
-.version-section {
-  margin-bottom: var(--space-xxl);
-  padding-bottom: var(--space-xl);
-  border-bottom: 1px solid var(--color-border);
-}
-
-.version-section:last-child {
-  border-bottom: none;
-}
-
-.version-header {
-  display: flex;
-  align-items: center;
-  gap: var(--space-m);
-  margin-bottom: var(--space-l);
-  flex-wrap: wrap;
-}
-
-.version-header h2 {
-  margin: 0;
-  padding: 0;
-  border: none;
-  font-size: var(--font-size-xl);
-  color: var(--color-text-primary);
-}
-
-.version-date {
-  font-size: var(--font-size-s);
-  color: var(--color-text-tertiary);
-  background-color: var(--color-surface);
-  padding: var(--space-xs) var(--space-m);
-  border-radius: var(--radius-s);
-}
-
-.version-badge {
-  font-size: var(--font-size-xs);
-  font-weight: 600;
-  padding: var(--space-xs) var(--space-m);
-  border-radius: var(--radius-s);
-  background-color: var(--color-accent);
-  color: white;
-}
-
-.version-badge.major {
-  background-color: var(--color-warning);
-}
-
-.version-description {
-  font-size: var(--font-size-m);
-  color: var(--color-text-secondary);
-  margin-bottom: var(--space-l);
-  font-style: italic;
-}
-
-.changelog-category {
-  margin-bottom: var(--space-l);
-  padding: var(--space-l);
-  background-color: var(--color-surface);
-  border-radius: var(--radius-m);
-  border-left: 4px solid var(--color-border);
-}
-
-.changelog-category h3 {
-  margin: 0 0 var(--space-m) 0;
-  font-size: var(--font-size-m);
-  display: flex;
-  align-items: center;
-  gap: var(--space-s);
-}
-
-.changelog-category h3 i {
-  font-size: var(--font-size-s);
-}
-
-.changelog-category h4 {
-  margin: var(--space-l) 0 var(--space-s) 0;
-  font-size: var(--font-size-s);
-  color: var(--color-text-secondary);
-}
-
-.changelog-category ul {
-  margin: 0;
-  padding-left: var(--space-xl);
-}
-
-.changelog-category li {
-  margin-bottom: var(--space-s);
-}
-
-.changelog-category.added {
-  border-left-color: var(--color-success);
-}
-
-.changelog-category.added h3 {
-  color: var(--color-success);
-}
-
-.changelog-category.improved {
-  border-left-color: var(--color-accent);
-}
-
-.changelog-category.improved h3 {
-  color: var(--color-accent);
-}
-
-.changelog-category.changed {
-  border-left-color: var(--color-warning);
-}
-
-.changelog-category.changed h3 {
-  color: var(--color-warning);
-}
-
-.changelog-category.fixed {
-  border-left-color: var(--color-error);
-}
-
-.changelog-category.fixed h3 {
-  color: var(--color-error);
-}
-
-.version-summary {
-  margin-top: var(--space-l);
-}
-
-.version-summary h4 {
-  margin-bottom: var(--space-m);
-}
-
-.version-summary table {
-  width: 100%;
-  max-width: 400px;
-  border-collapse: collapse;
-  font-size: var(--font-size-s);
-}
-
-.version-summary th,
-.version-summary td {
-  padding: var(--space-s) var(--space-m);
-  text-align: left;
-  border-bottom: 1px solid var(--color-border);
-}
-
-.version-summary th {
-  font-weight: 600;
-  background-color: var(--color-surface);
-}
-
-.version-summary .positive {
-  color: var(--color-success);
-  font-weight: 600;
-}
-
-.version-summary .negative {
-  color: var(--color-error);
-  font-weight: 600;
-}
--- a/docs/css/style.css
+++ b/docs/css/style.css
--- a/docs/index.html
+++ b/docs/index.html
--- a/docs/js/main.js
+++ b/docs/js/main.js
@@ -1,225 +0,0 @@
-/**
- * Compounding Engineering Documentation
- * Main JavaScript functionality
- */
-
-document.addEventListener('DOMContentLoaded', () => {
-  initMobileNav();
-  initSmoothScroll();
-  initCopyCode();
-  initThemeToggle();
-});
-
-/**
- * Mobile Navigation Toggle
- */
-function initMobileNav() {
-  const mobileToggle = document.querySelector('[data-mobile-toggle]');
-  const navigation = document.querySelector('[data-navigation]');
-
-  if (!mobileToggle || !navigation) return;
-
-  mobileToggle.addEventListener('click', () => {
-    navigation.classList.toggle('open');
-    mobileToggle.classList.toggle('active');
-
-    // Update aria-expanded
-    const isOpen = navigation.classList.contains('open');
-    mobileToggle.setAttribute('aria-expanded', isOpen);
-  });
-
-  // Close menu when clicking outside
-  document.addEventListener('click', (event) => {
-    if (!mobileToggle.contains(event.target) && !navigation.contains(event.target)) {
-      navigation.classList.remove('open');
-      mobileToggle.classList.remove('active');
-      mobileToggle.setAttribute('aria-expanded', 'false');
-    }
-  });
-
-  // Close menu when clicking a nav link
-  navigation.querySelectorAll('.nav-link').forEach(link => {
-    link.addEventListener('click', () => {
-      navigation.classList.remove('open');
-      mobileToggle.classList.remove('active');
-      mobileToggle.setAttribute('aria-expanded', 'false');
-    });
-  });
-}
-
-/**
- * Smooth Scroll for Anchor Links
- */
-function initSmoothScroll() {
-  document.querySelectorAll('a[href^="#"]').forEach(anchor => {
-    anchor.addEventListener('click', function(e) {
-      const targetId = this.getAttribute('href');
-      if (targetId === '#') return;
-
-      const targetElement = document.querySelector(targetId);
-      if (!targetElement) return;
-
-      e.preventDefault();
-
-      const navHeight = document.querySelector('.nav-container')?.offsetHeight || 0;
-      const targetPosition = targetElement.getBoundingClientRect().top + window.pageYOffset - navHeight - 24;
-
-      window.scrollTo({
-        top: targetPosition,
-        behavior: 'smooth'
-      });
-
-      // Update URL without jumping
-      history.pushState(null, null, targetId);
-    });
-  });
-}
-
-/**
- * Copy Code Functionality
- */
-function initCopyCode() {
-  document.querySelectorAll('.card-code-block').forEach(block => {
-    // Create copy button
-    const copyBtn = document.createElement('button');
-    copyBtn.className = 'copy-btn';
-    copyBtn.innerHTML = '<i class="fa-regular fa-copy"></i>';
-    copyBtn.setAttribute('aria-label', 'Copy code');
-    copyBtn.setAttribute('title', 'Copy to clipboard');
-
-    // Style the button
-    copyBtn.style.cssText = `
-      position: absolute;
-      top: 8px;
-      right: 8px;
-      padding: 6px 10px;
-      background: rgba(255, 255, 255, 0.1);
-      border: none;
-      border-radius: 6px;
-      color: #94a3b8;
-      cursor: pointer;
-      opacity: 0;
-      transition: all 0.2s ease;
-      font-size: 14px;
-    `;
-
-    // Make parent relative for positioning
-    block.style.position = 'relative';
-    block.appendChild(copyBtn);
-
-    // Show/hide on hover
-    block.addEventListener('mouseenter', () => {
-      copyBtn.style.opacity = '1';
-    });
-
-    block.addEventListener('mouseleave', () => {
-      copyBtn.style.opacity = '0';
-    });
-
-    // Copy functionality
-    copyBtn.addEventListener('click', async () => {
-      const code = block.querySelector('code');
-      if (!code) return;
-
-      try {
-        await navigator.clipboard.writeText(code.textContent);
-        copyBtn.innerHTML = '<i class="fa-solid fa-check"></i>';
-        copyBtn.style.color = '#34d399';
-
-        setTimeout(() => {
-          copyBtn.innerHTML = '<i class="fa-regular fa-copy"></i>';
-          copyBtn.style.color = '#94a3b8';
-        }, 2000);
-      } catch (err) {
-        console.error('Failed to copy:', err);
-        copyBtn.innerHTML = '<i class="fa-solid fa-xmark"></i>';
-        copyBtn.style.color = '#f87171';
-
-        setTimeout(() => {
-          copyBtn.innerHTML = '<i class="fa-regular fa-copy"></i>';
-          copyBtn.style.color = '#94a3b8';
-        }, 2000);
-      }
-    });
-  });
-}
-
-/**
- * Theme Toggle (Light/Dark)
- */
-function initThemeToggle() {
-  // Check for saved theme preference or default to dark
-  const savedTheme = localStorage.getItem('theme') || 'dark';
-  document.documentElement.className = `theme-${savedTheme}`;
-
-  // Create theme toggle button if it doesn't exist
-  const existingToggle = document.querySelector('[data-theme-toggle]');
-  if (existingToggle) {
-    existingToggle.addEventListener('click', toggleTheme);
-    updateThemeToggleIcon(existingToggle, savedTheme);
-  }
-}
-
-function toggleTheme() {
-  const html = document.documentElement;
-  const currentTheme = html.classList.contains('theme-dark') ? 'dark' : 'light';
-  const newTheme = currentTheme === 'dark' ? 'light' : 'dark';
-
-  html.className = `theme-${newTheme}`;
-  localStorage.setItem('theme', newTheme);
-
-  const toggle = document.querySelector('[data-theme-toggle]');
-  if (toggle) {
-    updateThemeToggleIcon(toggle, newTheme);
-  }
-}
-
-function updateThemeToggleIcon(toggle, theme) {
-  const icon = toggle.querySelector('i');
-  if (icon) {
-    icon.className = theme === 'dark' ? 'fa-solid fa-sun' : 'fa-solid fa-moon';
-  }
-}
-
-/**
- * Intersection Observer for Animation on Scroll
- */
-function initScrollAnimations() {
-  const observerOptions = {
-    threshold: 0.1,
-    rootMargin: '0px 0px -50px 0px'
-  };
-
-  const observer = new IntersectionObserver((entries) => {
-    entries.forEach(entry => {
-      if (entry.isIntersecting) {
-        entry.target.classList.add('visible');
-        observer.unobserve(entry.target);
-      }
-    });
-  }, observerOptions);
-
-  document.querySelectorAll('.agent-card, .command-card, .skill-card, .mcp-card, .stat-card').forEach(card => {
-    card.style.opacity = '0';
-    card.style.transform = 'translateY(20px)';
-    card.style.transition = 'opacity 0.5s ease, transform 0.5s ease';
-    observer.observe(card);
-  });
-}
-
-// Add visible class styles
-const style = document.createElement('style');
-style.textContent = `
-  .agent-card.visible,
-  .command-card.visible,
-  .skill-card.visible,
-  .mcp-card.visible,
-  .stat-card.visible {
-    opacity: 1 !important;
-    transform: translateY(0) !important;
-  }
-`;
-document.head.appendChild(style);
-
-// Initialize scroll animations after a short delay
-setTimeout(initScrollAnimations, 100);
--- a/docs/pages/agents.html
+++ b/docs/pages/agents.html
@@ -1,649 +0,0 @@
-<!DOCTYPE html>
-<html lang="en" class="theme-dark">
-
-<head>
-  <meta charset="utf-8" />
-  <title>Agent Reference - Compounding Engineering</title>
-  <meta content="Complete reference for all 23 specialized AI agents in the Compounding Engineering plugin." name="description" />
-  <meta content="width=device-width, initial-scale=1" name="viewport" />
-
-  <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/6.5.1/css/all.min.css" />
-  <link href="../css/style.css" rel="stylesheet" type="text/css" />
-  <link href="../css/docs.css" rel="stylesheet" type="text/css" />
-  <script src="../js/main.js" type="text/javascript" defer></script>
-</head>
-
-<body>
-  <div class="background-gradient"></div>
-  <div class="docs-layout">
-    <aside class="docs-sidebar">
-      <div class="sidebar-header">
-        <a href="../index.html" class="nav-brand">
-          <span class="logo-icon"><i class="fa-solid fa-layer-group"></i></span>
-          <span class="logo-text">CE Docs</span>
-        </a>
-      </div>
-      <nav class="sidebar-nav">
-        <div class="nav-section">
-          <h3>Getting Started</h3>
-          <ul>
-            <li><a href="getting-started.html">Installation</a></li>
-          </ul>
-        </div>
-        <div class="nav-section">
-          <h3>Reference</h3>
-          <ul>
-            <li><a href="agents.html" class="active">Agents (23)</a></li>
-            <li><a href="commands.html">Commands (13)</a></li>
-            <li><a href="skills.html">Skills (11)</a></li>
-            <li><a href="mcp-servers.html">MCP Servers (2)</a></li>
-          </ul>
-        </div>
-        <div class="nav-section">
-          <h3>Resources</h3>
-          <ul>
-            <li><a href="changelog.html">Changelog</a></li>
-          </ul>
-        </div>
-        <div class="nav-section">
-          <h3>On This Page</h3>
-          <ul>
-            <li><a href="#review-agents">Review (10)</a></li>
-            <li><a href="#research-agents">Research (4)</a></li>
-            <li><a href="#workflow-agents">Workflow (5)</a></li>
-            <li><a href="#design-agents">Design (3)</a></li>
-            <li><a href="#docs-agents">Docs (1)</a></li>
-          </ul>
-        </div>
-      </nav>
-    </aside>
-
-    <main class="docs-content">
-      <div class="docs-header">
-        <nav class="breadcrumb">
-          <a href="../index.html">Home</a>
-          <span>/</span>
-          <a href="getting-started.html">Docs</a>
-          <span>/</span>
-          <span>Agents</span>
-        </nav>
-        <button class="mobile-menu-toggle" data-sidebar-toggle>
-          <i class="fa-solid fa-bars"></i>
-        </button>
-      </div>
-
-      <article class="docs-article">
-        <h1><i class="fa-solid fa-users-gear color-accent"></i> Agent Reference</h1>
-        <p class="lead">
-          Think of agents as your expert teammates who never sleep. You've got 23 specialists here—each one obsessed with a single domain. Call them individually when you need focused expertise, or orchestrate them together for multi-angle analysis. They're opinionated, they're fast, and they remember your codebase better than you do.
-        </p>
-
-        <div class="usage-box">
-          <h3>How to Use Agents</h3>
-          <div class="card-code-block">
-            <pre><code># Basic invocation
-claude agent [agent-name]
-
-# With a specific message
-claude agent [agent-name] "Your message here"
-
-# Examples
-claude agent kieran-rails-reviewer
-claude agent security-sentinel "Audit the payment flow"</code></pre>
-          </div>
-        </div>
-
-        <!-- Review Agents -->
-        <section id="review-agents">
-          <h2><i class="fa-solid fa-code-pull-request"></i> Review Agents (10)</h2>
-          <p>Your code review dream team. These agents catch what humans miss at 2am—security holes, performance cliffs, architectural drift, and those "it works but I hate it" moments. They're picky. They disagree with each other. That's the point.</p>
-
-          <div class="agent-detail" id="kieran-rails-reviewer">
-            <div class="agent-detail-header">
-              <h3>kieran-rails-reviewer</h3>
-              <span class="agent-badge">Rails</span>
-            </div>
-            <p class="agent-detail-description">
-              Your senior Rails developer who's seen too many "clever" solutions fail in production. Obsessed with code that's boring, predictable, and maintainable. Strict on existing code (because touching it risks everything), pragmatic on new isolated features (because shipping matters). If you've ever thought "this works but feels wrong," this reviewer will tell you why.
-            </p>
-            <h4>Key Principles</h4>
-            <ul>
-              <li><strong>Existing Code Modifications</strong> - Very strict. Added complexity needs strong justification.</li>
-              <li><strong>New Code</strong> - Pragmatic. If it's isolated and works, it's acceptable.</li>
-              <li><strong>Turbo Streams</strong> - Simple turbo streams MUST be inline arrays in controllers.</li>
-              <li><strong>Testing as Quality</strong> - Hard-to-test code = poor structure that needs refactoring.</li>
-              <li><strong>Naming (5-Second Rule)</strong> - Must understand what a view/component does in 5 seconds from its name.</li>
-              <li><strong>Namespacing</strong> - Always use <code>class Module::ClassName</code> pattern.</li>
-              <li><strong>Duplication > Complexity</strong> - Simple duplicated code is better than complex DRY abstractions.</li>
-            </ul>
-            <div class="card-code-block">
-              <pre><code>claude agent kieran-rails-reviewer "Review the UserController"</code></pre>
-            </div>
-          </div>
-
-          <div class="agent-detail" id="dhh-rails-reviewer">
-            <div class="agent-detail-header">
-              <h3>dhh-rails-reviewer</h3>
-              <span class="agent-badge">Rails</span>
-            </div>
-            <p class="agent-detail-description">
-              What if DHH reviewed your Rails PR? He'd ask why you're building React inside Rails, why you need six layers of abstraction for a form, and whether you've forgotten that Rails already solved this problem. This agent channels that energy—blunt, opinionated, allergic to complexity.
-            </p>
-            <h4>Key Focus Areas</h4>
-            <ul>
-              <li>Identifies deviations from Rails conventions</li>
-              <li>Spots JavaScript framework patterns infiltrating Rails</li>
-              <li>Tears apart unnecessary abstractions</li>
-              <li>Challenges overengineering and microservices mentality</li>
-            </ul>
-            <div class="card-code-block">
-              <pre><code>claude agent dhh-rails-reviewer</code></pre>
-            </div>
-          </div>
-
-          <div class="agent-detail" id="kieran-python-reviewer">
-            <div class="agent-detail-header">
-              <h3>kieran-python-reviewer</h3>
-              <span class="agent-badge">Python</span>
-            </div>
-            <p class="agent-detail-description">
-              Your Pythonic perfectionist who believes type hints aren't optional and <code>dict.get()</code> beats try/except KeyError. Expects modern Python 3.10+ patterns—no legacy syntax, no <code>typing.List</code> when <code>list</code> works natively. If your code looks like Java translated to Python, prepare for rewrites.
-            </p>
-            <h4>Key Focus Areas</h4>
-            <ul>
-              <li>Type hints for all functions</li>
-              <li>Pythonic patterns and idioms</li>
-              <li>Modern Python syntax</li>
-              <li>Import organization</li>
-              <li>Module extraction signals</li>
-            </ul>
-            <div class="card-code-block">
-              <pre><code>claude agent kieran-python-reviewer</code></pre>
-            </div>
-          </div>
-
-          <div class="agent-detail" id="kieran-typescript-reviewer">
-            <div class="agent-detail-header">
-              <h3>kieran-typescript-reviewer</h3>
-              <span class="agent-badge">TypeScript</span>
-            </div>
-            <p class="agent-detail-description">
-              TypeScript's type system is a gift—don't throw it away with <code>any</code>. This reviewer treats <code>any</code> like a code smell that needs justification. Expects proper types, clean imports, and code that doesn't need comments because the types explain everything. You added TypeScript for safety; this agent makes sure you actually get it.
-            </p>
-            <h4>Key Focus Areas</h4>
-            <ul>
-              <li>No <code>any</code> without justification</li>
-              <li>Component/module extraction signals</li>
-              <li>Import organization</li>
-              <li>Modern TypeScript patterns</li>
-              <li>Testability assessment</li>
-            </ul>
-            <div class="card-code-block">
-              <pre><code>claude agent kieran-typescript-reviewer</code></pre>
-            </div>
-          </div>
-
-          <div class="agent-detail" id="security-sentinel">
-            <div class="agent-detail-header">
-              <h3>security-sentinel</h3>
-              <span class="agent-badge critical">Security</span>
-            </div>
-            <p class="agent-detail-description">
-              Security vulnerabilities hide in boring code—the "just grab the user ID from params" line that ships a privilege escalation bug to production. This agent thinks like an attacker: SQL injection, XSS, auth bypass, leaked secrets. Run it before touching authentication, payments, or anything with PII. Your users' data depends on paranoia.
-            </p>
-            <h4>Security Checks</h4>
-            <ul>
-              <li>Input validation analysis</li>
-              <li>SQL injection risk assessment</li>
-              <li>XSS vulnerability detection</li>
-              <li>Authentication/authorization audit</li>
-              <li>Sensitive data exposure scanning</li>
-              <li>OWASP Top 10 compliance</li>
-              <li>Hardcoded secrets search</li>
-            </ul>
-            <div class="card-code-block">
-              <pre><code>claude agent security-sentinel "Audit the payment flow"</code></pre>
-            </div>
-          </div>
-
-          <div class="agent-detail" id="performance-oracle">
-            <div class="agent-detail-header">
-              <h3>performance-oracle</h3>
-              <span class="agent-badge">Performance</span>
-            </div>
-            <p class="agent-detail-description">
-              Your code works fine with 10 users. What happens at 10,000? This agent time-travels to your future scaling problems—N+1 queries that murder your database, O(n²) algorithms hiding in loops, missing indexes, memory leaks. It thinks in Big O notation and asks uncomfortable questions about what breaks first when traffic spikes.
-            </p>
-            <h4>Analysis Areas</h4>
-            <ul>
-              <li>Algorithmic complexity (Big O notation)</li>
-              <li>N+1 query pattern detection</li>
-              <li>Proper index usage verification</li>
-              <li>Memory management review</li>
-              <li>Caching opportunity identification</li>
-              <li>Network usage optimization</li>
-              <li>Frontend bundle impact</li>
-            </ul>
-            <div class="card-code-block">
-              <pre><code>claude agent performance-oracle</code></pre>
-            </div>
-          </div>
-
-          <div class="agent-detail" id="architecture-strategist">
-            <div class="agent-detail-header">
-              <h3>architecture-strategist</h3>
-              <span class="agent-badge">Architecture</span>
-            </div>
-            <p class="agent-detail-description">
-              Every "small change" either reinforces your architecture or starts eroding it. This agent zooms out to see if your fix actually fits the system's design—or if you're bolting duct tape onto a crumbling foundation. It speaks SOLID principles, microservice boundaries, and API contracts. Call it when you're about to make a change that "feels weird."
-            </p>
-            <h4>Analysis Areas</h4>
-            <ul>
-              <li>Overall system structure understanding</li>
-              <li>Change context within architecture</li>
-              <li>Architectural violation identification</li>
-              <li>SOLID principles compliance</li>
-              <li>Microservice boundary assessment</li>
-              <li>API contract evaluation</li>
-            </ul>
-            <div class="card-code-block">
-              <pre><code>claude agent architecture-strategist</code></pre>
-            </div>
-          </div>
-
-          <div class="agent-detail" id="data-integrity-guardian">
-            <div class="agent-detail-header">
-              <h3>data-integrity-guardian</h3>
-              <span class="agent-badge critical">Data</span>
-            </div>
-            <p class="agent-detail-description">
-              Migrations can't be rolled back once they're run on production. This agent is your last line of defense before you accidentally drop a column with user data, create a race condition in transactions, or violate GDPR. It obsesses over referential integrity, rollback safety, and data constraints. Your database is forever; migrations should be paranoid.
-            </p>
-            <h4>Review Areas</h4>
-            <ul>
-              <li>Migration safety and reversibility</li>
-              <li>Data constraint validation</li>
-              <li>Transaction boundary review</li>
-              <li>Referential integrity preservation</li>
-              <li>Privacy compliance (GDPR, CCPA)</li>
-              <li>Data corruption scenario checking</li>
-            </ul>
-            <div class="card-code-block">
-              <pre><code>claude agent data-integrity-guardian</code></pre>
-            </div>
-          </div>
-
-          <div class="agent-detail" id="pattern-recognition-specialist">
-            <div class="agent-detail-header">
-              <h3>pattern-recognition-specialist</h3>
-              <span class="agent-badge">Patterns</span>
-            </div>
-            <p class="agent-detail-description">
-              Patterns tell stories—Factory, Observer, God Object, Copy-Paste Programming. This agent reads your code like an archaeologist reading artifacts. It spots the good patterns (intentional design), the anti-patterns (accumulated tech debt), and the duplicated blocks you swore you'd refactor later. Runs tools like jscpd because humans miss repetition that machines catch instantly.
-            </p>
-            <h4>Detection Areas</h4>
-            <ul>
-              <li>Design patterns (Factory, Singleton, Observer, etc.)</li>
-              <li>Anti-patterns and code smells</li>
-              <li>TODO/FIXME comments</li>
-              <li>God objects and circular dependencies</li>
-              <li>Naming consistency</li>
-              <li>Code duplication</li>
-            </ul>
-            <div class="card-code-block">
-              <pre><code>claude agent pattern-recognition-specialist</code></pre>
-            </div>
-          </div>
-
-          <div class="agent-detail" id="code-simplicity-reviewer">
-            <div class="agent-detail-header">
-              <h3>code-simplicity-reviewer</h3>
-              <span class="agent-badge">Quality</span>
-            </div>
-            <p class="agent-detail-description">
-              Simplicity is violent discipline. This agent asks "do you actually need this?" about every line, every abstraction, every dependency. YAGNI isn't a suggestion—it's the law. Your 200-line feature with three layers of indirection? This agent will show you the 50-line version that does the same thing. Complexity is a liability; simplicity compounds.
-            </p>
-            <h4>Simplification Checks</h4>
-            <ul>
-              <li>Analyze every line for necessity</li>
-              <li>Simplify complex logic</li>
-              <li>Remove redundancy and duplication</li>
-              <li>Challenge abstractions</li>
-              <li>Optimize for readability</li>
-              <li>Eliminate premature generalization</li>
-            </ul>
-            <div class="card-code-block">
-              <pre><code>claude agent code-simplicity-reviewer</code></pre>
-            </div>
-          </div>
-        </section>
-
-        <!-- Research Agents -->
-        <section id="research-agents">
-          <h2><i class="fa-solid fa-microscope"></i> Research Agents (4)</h2>
-          <p>Stop guessing. These agents dig through documentation, GitHub repos, git history, and real-world examples to give you answers backed by evidence. They read faster than you, remember more than you, and synthesize patterns you'd miss. Perfect for "how should I actually do this?" questions.</p>
-
-          <div class="agent-detail" id="framework-docs-researcher">
-            <div class="agent-detail-header">
-              <h3>framework-docs-researcher</h3>
-              <span class="agent-badge">Research</span>
-            </div>
-            <p class="agent-detail-description">
-              Official docs are scattered. GitHub examples are inconsistent. Deprecations hide in changelogs. This agent pulls it all together—docs, source code, version constraints, real-world examples. Ask "how do I use Hotwire Turbo?" and get back patterns that actually work in production, not toy tutorials.
-            </p>
-            <h4>Capabilities</h4>
-            <ul>
-              <li>Fetch official framework and library documentation</li>
-              <li>Identify version-specific constraints and deprecations</li>
-              <li>Search GitHub for real-world usage examples</li>
-              <li>Analyze gem/library source code using <code>bundle show</code></li>
-              <li>Synthesize findings with practical examples</li>
-            </ul>
-            <div class="card-code-block">
-              <pre><code>claude agent framework-docs-researcher "Research Hotwire Turbo patterns"</code></pre>
-            </div>
-          </div>
-
-          <div class="agent-detail" id="best-practices-researcher">
-            <div class="agent-detail-header">
-              <h3>best-practices-researcher</h3>
-              <span class="agent-badge">Research</span>
-            </div>
-            <p class="agent-detail-description">
-              "Best practices" are everywhere and contradictory. This agent cuts through the noise by evaluating sources (official docs, trusted blogs, real GitHub repos), checking recency, and synthesizing actionable guidance. You get code templates, patterns that scale, and answers you can trust—not StackOverflow copy-paste roulette.
-            </p>
-            <h4>Capabilities</h4>
-            <ul>
-              <li>Leverage multiple sources (Context7 MCP, web search, GitHub)</li>
-              <li>Evaluate information quality and recency</li>
-              <li>Synthesize into actionable guidance</li>
-              <li>Provide code examples and templates</li>
-              <li>Research issue templates and community engagement</li>
-            </ul>
-            <div class="card-code-block">
-              <pre><code>claude agent best-practices-researcher "Find pagination patterns"</code></pre>
-            </div>
-          </div>
-
-          <div class="agent-detail" id="git-history-analyzer">
-            <div class="agent-detail-header">
-              <h3>git-history-analyzer</h3>
-              <span class="agent-badge">Git</span>
-            </div>
-            <p class="agent-detail-description">
-              Your codebase has a history—decisions, patterns, mistakes. This agent does archaeology with git tools: file evolution, blame analysis, contributor expertise mapping. Ask "why does this code exist?" and get the commit that explains it. Spot patterns in how bugs appear. Understand the design decisions buried in history.
-            </p>
-            <h4>Analysis Techniques</h4>
-            <ul>
-              <li>Trace file evolution using <code>git log --follow</code></li>
-              <li>Determine code origins using <code>git blame -w -C -C -C</code></li>
-              <li>Identify patterns from commit history</li>
-              <li>Map key contributors and expertise areas</li>
-              <li>Extract historical patterns of issues and fixes</li>
-            </ul>
-            <div class="card-code-block">
-              <pre><code>claude agent git-history-analyzer "Analyze changes to User model"</code></pre>
-            </div>
-          </div>
-
-          <div class="agent-detail" id="repo-research-analyst">
-            <div class="agent-detail-header">
-              <h3>repo-research-analyst</h3>
-              <span class="agent-badge">Research</span>
-            </div>
-            <p class="agent-detail-description">
-              Every repo has conventions—some documented, most tribal knowledge. This agent reads ARCHITECTURE.md, issue templates, PR patterns, and actual code to reverse-engineer the standards. Perfect for joining a new project or ensuring your PR matches the team's implicit style. Finds the rules nobody wrote down.
-            </p>
-            <h4>Analysis Areas</h4>
-            <ul>
-              <li>Architecture and documentation files (ARCHITECTURE.md, README.md, CLAUDE.md)</li>
-              <li>GitHub issues for patterns and conventions</li>
-              <li>Issue/PR templates and guidelines</li>
-              <li>Implementation patterns using ast-grep or rg</li>
-              <li>Project-specific conventions</li>
-            </ul>
-            <div class="card-code-block">
-              <pre><code>claude agent repo-research-analyst</code></pre>
-            </div>
-          </div>
-        </section>
-
-        <!-- Workflow Agents -->
-        <section id="workflow-agents">
-          <h2><i class="fa-solid fa-gears"></i> Workflow Agents (5)</h2>
-          <p>Tedious work you hate doing. These agents handle the grind—reproducing bugs, resolving PR comments, running linters, analyzing specs. They're fast, they don't complain, and they free you up to solve interesting problems instead of mechanical ones.</p>
-
-          <div class="agent-detail" id="bug-reproduction-validator">
-            <div class="agent-detail-header">
-              <h3>bug-reproduction-validator</h3>
-              <span class="agent-badge">Bugs</span>
-            </div>
-            <p class="agent-detail-description">
-              Half of bug reports aren't bugs—they're user errors, environment issues, or misunderstood features. This agent systematically reproduces the reported behavior, classifies what it finds (Confirmed, Can't Reproduce, Not a Bug, etc.), and assesses severity. Saves you from chasing ghosts or missing real issues.
-            </p>
-            <h4>Classification Types</h4>
-            <ul>
-              <li><strong>Confirmed</strong> - Bug reproduced successfully</li>
-              <li><strong>Cannot Reproduce</strong> - Unable to reproduce</li>
-              <li><strong>Not a Bug</strong> - Expected behavior</li>
-              <li><strong>Environmental</strong> - Environment-specific issue</li>
-              <li><strong>Data</strong> - Data-related issue</li>
-              <li><strong>User Error</strong> - User misunderstanding</li>
-            </ul>
-            <div class="card-code-block">
-              <pre><code>claude agent bug-reproduction-validator</code></pre>
-            </div>
-          </div>
-
-          <div class="agent-detail" id="pr-comment-resolver">
-            <div class="agent-detail-header">
-              <h3>pr-comment-resolver</h3>
-              <span class="agent-badge">PR</span>
-            </div>
-            <p class="agent-detail-description">
-              Code review comments pile up. This agent reads them, plans fixes, implements changes, and reports back what it did. It doesn't argue with reviewers or skip hard feedback—it just resolves the work systematically. Great for burning through a dozen "change this variable name" comments in seconds.
-            </p>
-            <h4>Workflow</h4>
-            <ul>
-              <li>Analyze code review comments</li>
-              <li>Plan the resolution before implementation</li>
-              <li>Implement requested modifications</li>
-              <li>Verify resolution doesn't break functionality</li>
-              <li>Provide clear resolution reports</li>
-            </ul>
-            <div class="card-code-block">
-              <pre><code>claude agent pr-comment-resolver</code></pre>
-            </div>
-          </div>
-
-          <div class="agent-detail" id="lint">
-            <div class="agent-detail-header">
-              <h3>lint</h3>
-              <span class="agent-badge">Quality</span>
-            </div>
-            <p class="agent-detail-description">
-              Linters are pedantic robots that enforce consistency. This agent runs StandardRB, ERBLint, and Brakeman for you—checking Ruby style, ERB templates, and security issues. It's fast (uses the Haiku model) and catches the formatting noise before CI does.
-            </p>
-            <h4>Tools Run</h4>
-            <ul>
-              <li><code>bundle exec standardrb</code> - Ruby file checking/fixing</li>
-              <li><code>bundle exec erblint --lint-all</code> - ERB templates</li>
-              <li><code>bin/brakeman</code> - Security scanning</li>
-            </ul>
-            <div class="card-code-block">
-              <pre><code>claude agent lint</code></pre>
-            </div>
-          </div>
-
-          <div class="agent-detail" id="spec-flow-analyzer">
-            <div class="agent-detail-header">
-              <h3>spec-flow-analyzer</h3>
-              <span class="agent-badge">Testing</span>
-            </div>
-            <p class="agent-detail-description">
-              Specs always have gaps—edge cases nobody thought about, ambiguous requirements, missing error states. This agent maps all possible user flows, identifies what's unclear or missing, and generates the questions you need to ask stakeholders. Runs before you code to avoid building the wrong thing.
-            </p>
-            <h4>Analysis Areas</h4>
-            <ul>
-              <li>Map all possible user flows and permutations</li>
-              <li>Identify gaps, ambiguities, and missing specifications</li>
-              <li>Consider different user types, roles, permissions</li>
-              <li>Analyze error states and edge cases</li>
-              <li>Generate critical questions requiring clarification</li>
-            </ul>
-            <div class="card-code-block">
-              <pre><code>claude agent spec-flow-analyzer</code></pre>
-            </div>
-          </div>
-
-          <div class="agent-detail" id="every-style-editor">
-            <div class="agent-detail-header">
-              <h3>every-style-editor</h3>
-              <span class="agent-badge">Content</span>
-            </div>
-            <p class="agent-detail-description">
-              Style guides are arbitrary rules that make writing consistent. This agent enforces Every's particular quirks—title case in headlines, no overused filler words ("actually," "very"), active voice, Oxford commas. It's a line-by-line grammar cop for content that needs to match the brand.
-            </p>
-            <h4>Style Checks</h4>
-            <ul>
-              <li>Title case in headlines, sentence case elsewhere</li>
-              <li>Company singular/plural usage</li>
-              <li>Remove overused words (actually, very, just)</li>
-              <li>Enforce active voice</li>
-              <li>Apply formatting rules (Oxford commas, em dashes)</li>
-            </ul>
-            <div class="card-code-block">
-              <pre><code>claude agent every-style-editor</code></pre>
-            </div>
-          </div>
-        </section>
-
-        <!-- Design Agents -->
-        <section id="design-agents">
-          <h2><i class="fa-solid fa-palette"></i> Design Agents (3)</h2>
-          <p>Design is iteration. These agents take screenshots, compare them to Figma, make targeted improvements, and repeat. They fix spacing, alignment, colors, typography—the visual details that compound into polish. Perfect for closing the gap between "it works" and "it looks right."</p>
-
-          <div class="agent-detail" id="design-iterator">
-            <div class="agent-detail-header">
-              <h3>design-iterator</h3>
-              <span class="agent-badge">Design</span>
-            </div>
-            <p class="agent-detail-description">
-              Design doesn't happen in one pass. This agent runs a loop: screenshot the UI, analyze what's off (spacing, colors, alignment), implement 3-5 targeted fixes, repeat. Run it for 10 iterations and watch rough interfaces transform into polished designs through systematic refinement.
-            </p>
-            <h4>Process</h4>
-            <ul>
-              <li>Take focused screenshots of target elements</li>
-              <li>Analyze current state and identify 3-5 improvements</li>
-              <li>Implement targeted CSS/design changes</li>
-              <li>Document changes made</li>
-              <li>Repeat for specified iterations (default 10)</li>
-            </ul>
-            <div class="card-code-block">
-              <pre><code>claude agent design-iterator</code></pre>
-            </div>
-          </div>
-
-          <div class="agent-detail" id="figma-design-sync">
-            <div class="agent-detail-header">
-              <h3>figma-design-sync</h3>
-              <span class="agent-badge">Figma</span>
-            </div>
-            <p class="agent-detail-description">
-              Designers hand you a Figma file. You build it. Then: "the spacing is wrong, the font is off, the colors don't match." This agent compares your implementation to the Figma spec, identifies every visual discrepancy, and fixes them automatically. Designers stay happy. You stay sane.
-            </p>
-            <h4>Workflow</h4>
-            <ul>
-              <li>Extract design specifications from Figma</li>
-              <li>Capture implementation screenshots</li>
-              <li>Conduct systematic visual comparison</li>
-              <li>Make precise code changes to fix discrepancies</li>
-              <li>Verify implementation matches design</li>
-            </ul>
-            <div class="card-code-block">
-              <pre><code>claude agent figma-design-sync</code></pre>
-            </div>
-          </div>
-
-          <div class="agent-detail" id="design-implementation-reviewer">
-            <div class="agent-detail-header">
-              <h3>design-implementation-reviewer</h3>
-              <span class="agent-badge">Review</span>
-            </div>
-            <p class="agent-detail-description">
-              Before you ship UI changes, run this agent. It compares your implementation against Figma at a pixel level—layouts, typography, colors, spacing, responsive behavior. Uses the Opus model for detailed visual analysis. Catches the "close enough" mistakes that users notice but you don't.
-            </p>
-            <h4>Comparison Areas</h4>
-            <ul>
-              <li>Layouts and structure</li>
-              <li>Typography (fonts, sizes, weights)</li>
-              <li>Colors and themes</li>
-              <li>Spacing and alignment</li>
-              <li>Different viewport sizes</li>
-            </ul>
-            <div class="card-code-block">
-              <pre><code>claude agent design-implementation-reviewer</code></pre>
-            </div>
-          </div>
-        </section>
-
-        <!-- Docs Agents -->
-        <section id="docs-agents">
-          <h2><i class="fa-solid fa-file-lines"></i> Documentation Agent (1)</h2>
-
-          <div class="agent-detail" id="ankane-readme-writer">
-            <div class="agent-detail-header">
-              <h3>ankane-readme-writer</h3>
-              <span class="agent-badge">Docs</span>
-            </div>
-            <p class="agent-detail-description">
-              Andrew Kane writes READMEs that are models of clarity—concise, scannable, zero fluff. This agent generates gem documentation in that style: 15 words max per sentence, imperative voice, single-purpose code examples. If your README rambles, this agent will fix it.
-            </p>
-            <h4>Section Order</h4>
-            <ol>
-              <li>Header (title + description)</li>
-              <li>Installation</li>
-              <li>Quick Start</li>
-              <li>Usage</li>
-              <li>Options</li>
-              <li>Upgrading</li>
-              <li>Contributing</li>
-              <li>License</li>
-            </ol>
-            <h4>Style Guidelines</h4>
-            <ul>
-              <li>Imperative voice throughout</li>
-              <li>15 words max per sentence</li>
-              <li>Single-purpose code fences</li>
-              <li>Up to 4 badges maximum</li>
-              <li>No HTML comments</li>
-            </ul>
-            <div class="card-code-block">
-              <pre><code>claude agent ankane-readme-writer</code></pre>
-            </div>
-          </div>
-        </section>
-
-        <!-- Navigation -->
-        <nav class="docs-nav-footer">
-          <a href="getting-started.html" class="nav-prev">
-            <span class="nav-label">Previous</span>
-            <span class="nav-title"><i class="fa-solid fa-arrow-left"></i> Getting Started</span>
-          </a>
-          <a href="commands.html" class="nav-next">
-            <span class="nav-label">Next</span>
-            <span class="nav-title">Commands <i class="fa-solid fa-arrow-right"></i></span>
-          </a>
-        </nav>
-      </article>
-    </main>
-  </div>
-
-  <script>
-    document.querySelector('[data-sidebar-toggle]')?.addEventListener('click', () => {
-      document.querySelector('.docs-sidebar').classList.toggle('open');
-    });
-  </script>
-</body>
-
-</html>
--- a/docs/pages/changelog.html
+++ b/docs/pages/changelog.html
@@ -1,534 +0,0 @@
-<!DOCTYPE html>
-<html lang="en" class="theme-dark">
-
-<head>
-  <meta charset="utf-8" />
-  <title>Changelog - Compounding Engineering</title>
-  <meta content="Version history and release notes for the Compounding Engineering plugin." name="description" />
-  <meta content="width=device-width, initial-scale=1" name="viewport" />
-
-  <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/6.5.1/css/all.min.css" />
-  <link href="../css/style.css" rel="stylesheet" type="text/css" />
-  <link href="../css/docs.css" rel="stylesheet" type="text/css" />
-  <script src="../js/main.js" type="text/javascript" defer></script>
-</head>
-
-<body>
-  <div class="background-gradient"></div>
-  <div class="docs-layout">
-    <aside class="docs-sidebar">
-      <div class="sidebar-header">
-        <a href="../index.html" class="nav-brand">
-          <span class="logo-icon"><i class="fa-solid fa-layer-group"></i></span>
-          <span class="logo-text">CE Docs</span>
-        </a>
-      </div>
-      <nav class="sidebar-nav">
-        <div class="nav-section">
-          <h3>Getting Started</h3>
-          <ul>
-            <li><a href="getting-started.html">Installation</a></li>
-          </ul>
-        </div>
-        <div class="nav-section">
-          <h3>Reference</h3>
-          <ul>
-            <li><a href="agents.html">Agents (23)</a></li>
-            <li><a href="commands.html">Commands (13)</a></li>
-            <li><a href="skills.html">Skills (11)</a></li>
-            <li><a href="mcp-servers.html">MCP Servers (two)</a></li>
-          </ul>
-        </div>
-        <div class="nav-section">
-          <h3>Resources</h3>
-          <ul>
-            <li><a href="changelog.html" class="active">Changelog</a></li>
-          </ul>
-        </div>
-        <div class="nav-section">
-          <h3>On This Page</h3>
-          <ul>
-            <li><a href="#v2.32.2">v2.32.2</a></li>
-            <li><a href="#v2.32.1">v2.32.1</a></li>
-            <li><a href="#v2.6.0">v2.6.0</a></li>
-            <li><a href="#v2.5.0">v2.5.0</a></li>
-            <li><a href="#v2.4.1">v2.4.1</a></li>
-            <li><a href="#v2.4.0">v2.4.0</a></li>
-            <li><a href="#v2.3.0">v2.3.0</a></li>
-            <li><a href="#v2.2.1">v2.2.1</a></li>
-            <li><a href="#v2.2.0">v2.2.0</a></li>
-            <li><a href="#v2.1.0">v2.1.0</a></li>
-            <li><a href="#v2.0.0">v2.0.0</a></li>
-            <li><a href="#v1.1.0">v1.1.0</a></li>
-            <li><a href="#v1.0.0">v1.0.0</a></li>
-          </ul>
-        </div>
-      </nav>
-    </aside>
-
-    <main class="docs-content">
-      <div class="docs-header">
-        <nav class="breadcrumb">
-          <a href="../index.html">Home</a>
-          <span>/</span>
-          <a href="getting-started.html">Docs</a>
-          <span>/</span>
-          <span>Changelog</span>
-        </nav>
-        <button class="mobile-menu-toggle" data-sidebar-toggle>
-          <i class="fa-solid fa-bars"></i>
-        </button>
-      </div>
-
-      <article class="docs-article">
-        <h1><i class="fa-solid fa-clock-rotate-left color-accent"></i> Changelog</h1>
-        <p class="lead">
-          All notable changes to the compound-engineering plugin. This project follows
-          <a href="https://semver.org/">Semantic Versioning</a> and
-          <a href="https://keepachangelog.com/">Keep a Changelog</a> conventions.
-        </p>
-
-        <!-- Version 2.32.2 -->
-        <section id="v2.32.2" class="version-section">
-          <div class="version-header">
-            <h2>v2.32.2</h2>
-            <span class="version-date">2026-02-12</span>
-          </div>
-
-          <div class="changelog-category changed">
-            <h3><i class="fa-solid fa-arrows-rotate"></i> Changed</h3>
-            <ul>
-              <li>
-                <strong><code>/release-docs</code> command moved from plugin to local <code>.claude/commands/</code></strong> -
-                This is a repository maintenance command and should not be distributed to users. Command count reduced from 24 to 23.
-              </li>
-            </ul>
-          </div>
-        </section>
-
-        <!-- Version 2.32.1 -->
-        <section id="v2.32.1" class="version-section">
-          <div class="version-header">
-            <h2>v2.32.1</h2>
-            <span class="version-date">2026-02-12</span>
-          </div>
-
-          <div class="changelog-category changed">
-            <h3><i class="fa-solid fa-arrows-rotate"></i> Changed</h3>
-            <ul>
-              <li>
-                <strong><code>/workflows:review</code> command</strong> - Added <code>learnings-researcher</code>
-                agent to the parallel review phase. The review now searches <code>docs/solutions/</code> for past
-                issues related to the PR's modules and patterns, surfacing "Known Pattern" findings during synthesis.
-              </li>
-            </ul>
-          </div>
-        </section>
-
-        <!-- Version 2.6.0 -->
-        <section id="v2.6.0" class="version-section">
-          <div class="version-header">
-            <h2>v2.6.0</h2>
-            <span class="version-date">2024-11-26</span>
-          </div>
-
-          <div class="changelog-category removed">
-            <h3><i class="fa-solid fa-minus"></i> Removed</h3>
-            <ul>
-              <li>
-                <strong><code>feedback-codifier</code> agent</strong> - Removed from workflow agents.
-                Agent count reduced from 24 to 23.
-              </li>
-            </ul>
-          </div>
-        </section>
-
-        <!-- Version 2.5.0 -->
-        <section id="v2.5.0" class="version-section">
-          <div class="version-header">
-            <h2>v2.5.0</h2>
-            <span class="version-date">2024-11-25</span>
-          </div>
-
-          <div class="changelog-category added">
-            <h3><i class="fa-solid fa-plus"></i> Added</h3>
-            <ul>
-              <li>
-                <strong><code>/report-bug</code> command</strong> - New slash command for reporting bugs in the
-                compound-engineering plugin. Provides a structured workflow that gathers bug information
-                through guided questions, collects environment details automatically, and creates a GitHub
-                issue in the EveryInc/compound-engineering-plugin repository.
-              </li>
-            </ul>
-          </div>
-        </section>
-
-        <!-- Version 2.4.1 -->
-        <section id="v2.4.1" class="version-section">
-          <div class="version-header">
-            <h2>v2.4.1</h2>
-            <span class="version-date">2024-11-24</span>
-          </div>
-
-          <div class="changelog-category improved">
-            <h3><i class="fa-solid fa-arrow-up"></i> Improved</h3>
-            <ul>
-              <li>
-                <strong>design-iterator agent</strong> - Added focused screenshot guidance: always capture
-                only the target element/area instead of full page screenshots. Includes browser_resize
-                recommendations, element-targeted screenshot workflow using browser_snapshot refs, and
-                explicit instruction to never use fullPage mode.
-              </li>
-            </ul>
-          </div>
-        </section>
-
-        <!-- Version 2.4.0 -->
-        <section id="v2.4.0" class="version-section">
-          <div class="version-header">
-            <h2>v2.4.0</h2>
-            <span class="version-date">2024-11-24</span>
-          </div>
-
-          <div class="changelog-category fixed">
-            <h3><i class="fa-solid fa-bug"></i> Fixed</h3>
-            <ul>
-              <li>
-                <strong>MCP Configuration</strong> - Moved MCP servers back to <code>plugin.json</code>
-                following working examples from anthropics/life-sciences plugins.
-              </li>
-              <li>
-                <strong>Context7 URL</strong> - Updated to use HTTP type with correct endpoint URL.
-              </li>
-            </ul>
-          </div>
-        </section>
-
-        <!-- Version 2.3.0 -->
-        <section id="v2.3.0" class="version-section">
-          <div class="version-header">
-            <h2>v2.3.0</h2>
-            <span class="version-date">2024-11-24</span>
-          </div>
-
-          <div class="changelog-category changed">
-            <h3><i class="fa-solid fa-arrows-rotate"></i> Changed</h3>
-            <ul>
-              <li>
-                <strong>MCP Configuration</strong> - Moved MCP servers from inline <code>plugin.json</code>
-                to separate <code>.mcp.json</code> file per Claude Code best practices.
-              </li>
-            </ul>
-          </div>
-        </section>
-
-        <!-- Version 2.2.1 -->
-        <section id="v2.2.1" class="version-section">
-          <div class="version-header">
-            <h2>v2.2.1</h2>
-            <span class="version-date">2024-11-24</span>
-          </div>
-
-          <div class="changelog-category fixed">
-            <h3><i class="fa-solid fa-bug"></i> Fixed</h3>
-            <ul>
-              <li>
-                <strong>Playwright MCP Server</strong> - Added missing <code>"type": "stdio"</code> field
-                required for MCP server configuration to load properly.
-              </li>
-            </ul>
-          </div>
-        </section>
-
-        <!-- Version 2.2.0 -->
-        <section id="v2.2.0" class="version-section">
-          <div class="version-header">
-            <h2>v2.2.0</h2>
-            <span class="version-date">2024-11-24</span>
-          </div>
-
-          <div class="changelog-category added">
-            <h3><i class="fa-solid fa-plus"></i> Added</h3>
-            <ul>
-              <li>
-                <strong>Context7 MCP Server</strong> - Bundled Context7 for instant framework documentation
-                lookup. Provides up-to-date docs for Rails, React, Next.js, and more than 100 other frameworks.
-              </li>
-            </ul>
-          </div>
-        </section>
-
-        <!-- Version 2.1.0 -->
-        <section id="v2.1.0" class="version-section">
-          <div class="version-header">
-            <h2>v2.1.0</h2>
-            <span class="version-date">2024-11-24</span>
-          </div>
-
-          <div class="changelog-category added">
-            <h3><i class="fa-solid fa-plus"></i> Added</h3>
-            <ul>
-              <li>
-                <strong>Playwright MCP Server</strong> - Bundled <code>@playwright/mcp</code> for browser
-                automation across all projects. Provides screenshot, navigation, click, fill, and evaluate tools.
-              </li>
-            </ul>
-          </div>
-
-          <div class="changelog-category changed">
-            <h3><i class="fa-solid fa-arrows-rotate"></i> Changed</h3>
-            <ul>
-              <li>Replaced all Puppeteer references with Playwright across agents and commands:
-                <ul>
-                  <li><code>bug-reproduction-validator</code> agent</li>
-                  <li><code>design-iterator</code> agent</li>
-                  <li><code>design-implementation-reviewer</code> agent</li>
-                  <li><code>figma-design-sync</code> agent</li>
-                  <li><code>generate_command</code> command</li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-        </section>
-
-        <!-- Version 2.0.2 -->
-        <section id="v2.0.2" class="version-section">
-          <div class="version-header">
-            <h2>v2.0.2</h2>
-            <span class="version-date">2024-11-24</span>
-          </div>
-
-          <div class="changelog-category changed">
-            <h3><i class="fa-solid fa-arrows-rotate"></i> Changed</h3>
-            <ul>
-              <li>
-                <strong>design-iterator agent</strong> - Updated description to emphasize proactive usage
-                when design work isn't coming together on first attempt.
-              </li>
-            </ul>
-          </div>
-        </section>
-
-        <!-- Version 2.0.1 -->
-        <section id="v2.0.1" class="version-section">
-          <div class="version-header">
-            <h2>v2.0.1</h2>
-            <span class="version-date">2024-11-24</span>
-          </div>
-
-          <div class="changelog-category added">
-            <h3><i class="fa-solid fa-plus"></i> Added</h3>
-            <ul>
-              <li><strong>CLAUDE.md</strong> - Project instructions with versioning requirements</li>
-              <li><strong>docs/solutions/plugin-versioning-requirements.md</strong> - Workflow documentation</li>
-            </ul>
-          </div>
-        </section>
-
-        <!-- Version 2.0.0 -->
-        <section id="v2.0.0" class="version-section">
-          <div class="version-header">
-            <h2>v2.0.0</h2>
-            <span class="version-date">2024-11-24</span>
-            <span class="version-badge major">Major Release</span>
-          </div>
-
-          <p class="version-description">
-            Major reorganization consolidating agents, commands, and skills from multiple sources into
-            a single, well-organized plugin.
-          </p>
-
-          <div class="changelog-category added">
-            <h3><i class="fa-solid fa-plus"></i> Added</h3>
-
-            <h4>New Agents (seven)</h4>
-            <ul>
-              <li><code>design-iterator</code> - Iteratively refine UI components through systematic design iterations</li>
-              <li><code>design-implementation-reviewer</code> - Verify UI implementations match Figma design specifications</li>
-              <li><code>figma-design-sync</code> - Synchronize web implementations with Figma designs</li>
-              <li><code>bug-reproduction-validator</code> - Systematically reproduce and validate bug reports</li>
-              <li><code>spec-flow-analyzer</code> - Analyze user flows and identify gaps in specifications</li>
-              <li><code>lint</code> - Run linting and code quality checks on Ruby and ERB files</li>
-              <li><code>ankane-readme-writer</code> - Create READMEs following Ankane-style template for Ruby gems</li>
-            </ul>
-
-            <h4>New Commands (nine)</h4>
-            <ul>
-              <li><code>/changelog</code> - Create engaging changelogs for recent merges</li>
-              <li><code>/plan_review</code> - Multi-agent plan review in parallel</li>
-              <li><code>/resolve_parallel</code> - Resolve TODO comments in parallel</li>
-              <li><code>/resolve_pr_parallel</code> - Resolve PR comments in parallel</li>
-              <li><code>/reproduce-bug</code> - Reproduce bugs using logs and console</li>
-              <li><code>/prime</code> - Prime/setup command</li>
-              <li><code>/create-agent-skill</code> - Create or edit Claude Code skills</li>
-              <li><code>/heal-skill</code> - Fix skill documentation issues</li>
-              <li><code>/codify</code> - Document solved problems for knowledge base</li>
-            </ul>
-
-            <h4>New Skills (10)</h4>
-            <ul>
-              <li><code>andrew-kane-gem-writer</code> - Write Ruby gems following Andrew Kane's patterns</li>
-              <li><code>codify-docs</code> - Capture solved problems as categorized documentation</li>
-              <li><code>create-agent-skills</code> - Expert guidance for creating Claude Code skills</li>
-              <li><code>dhh-ruby-style</code> - Write Ruby/Rails code in DHH's 37signals style</li>
-              <li><code>dspy-ruby</code> - Build type-safe LLM applications with DSPy.rb</li>
-              <li><code>every-style-editor</code> - Review copy for Every's style guide compliance</li>
-              <li><code>file-todos</code> - File-based todo tracking system</li>
-              <li><code>frontend-design</code> - Create production-grade frontend interfaces</li>
-              <li><code>git-worktree</code> - Manage Git worktrees for parallel development</li>
-              <li><code>skill-creator</code> - Guide for creating effective Claude Code skills</li>
-            </ul>
-          </div>
-
-          <div class="changelog-category changed">
-            <h3><i class="fa-solid fa-arrows-rotate"></i> Changed</h3>
-            <h4>Agents Reorganized by Category</h4>
-            <ul>
-              <li><code>review/</code> (10 agents) - Code quality, security, performance reviewers</li>
-              <li><code>research/</code> (four agents) - Documentation, patterns, history analysis</li>
-              <li><code>design/</code> (three agents) - UI/design review and iteration</li>
-              <li><code>workflow/</code> (six agents) - PR resolution, bug validation, linting</li>
-              <li><code>docs/</code> (one agent) - README generation</li>
-            </ul>
-          </div>
-
-          <div class="version-summary">
-            <h4>Summary</h4>
-            <table>
-              <thead>
-                <tr>
-                  <th>Component</th>
-                  <th>v1.1.0</th>
-                  <th>v2.0.0</th>
-                  <th>Change</th>
-                </tr>
-              </thead>
-              <tbody>
-                <tr>
-                  <td>Agents</td>
-                  <td>17</td>
-                  <td>24</td>
-                  <td class="positive">+7</td>
-                </tr>
-                <tr>
-                  <td>Commands</td>
-                  <td>6</td>
-                  <td>15</td>
-                  <td class="positive">+9</td>
-                </tr>
-                <tr>
-                  <td>Skills</td>
-                  <td>1</td>
-                  <td>11</td>
-                  <td class="positive">+10</td>
-                </tr>
-              </tbody>
-            </table>
-          </div>
-        </section>
-
-        <!-- Version 1.1.0 -->
-        <section id="v1.1.0" class="version-section">
-          <div class="version-header">
-            <h2>v1.1.0</h2>
-            <span class="version-date">2024-11-22</span>
-          </div>
-
-          <div class="changelog-category added">
-            <h3><i class="fa-solid fa-plus"></i> Added</h3>
-            <ul>
-              <li>
-                <strong>gemini-imagegen Skill</strong>
-                <ul>
-                  <li>Text-to-image generation with Google's Gemini API</li>
-                  <li>Image editing and manipulation</li>
-                  <li>Multi-turn refinement via chat interface</li>
-                  <li>Multiple reference image composition (up to 14 images)</li>
-                  <li>Model support: <code>gemini-2.5-flash-image</code> and <code>gemini-3-pro-image-preview</code></li>
-                </ul>
-              </li>
-            </ul>
-          </div>
-
-          <div class="changelog-category fixed">
-            <h3><i class="fa-solid fa-bug"></i> Fixed</h3>
-            <ul>
-              <li>Corrected component counts in documentation (17 agents, not 15)</li>
-            </ul>
-          </div>
-        </section>
-
-        <!-- Version 1.0.0 -->
-        <section id="v1.0.0" class="version-section">
-          <div class="version-header">
-            <h2>v1.0.0</h2>
-            <span class="version-date">2024-10-09</span>
-            <span class="version-badge">Initial Release</span>
-          </div>
-
-          <p class="version-description">
-            Initial release of the compound-engineering plugin.
-          </p>
-
-          <div class="changelog-category added">
-            <h3><i class="fa-solid fa-plus"></i> Added</h3>
-
-            <h4>17 Specialized Agents</h4>
-
-            <p><strong>Code Review (five)</strong></p>
-            <ul>
-              <li><code>kieran-rails-reviewer</code> - Rails code review with strict conventions</li>
-              <li><code>kieran-python-reviewer</code> - Python code review with quality standards</li>
-              <li><code>kieran-typescript-reviewer</code> - TypeScript code review</li>
-              <li><code>dhh-rails-reviewer</code> - Rails review from DHH's perspective</li>
-              <li><code>code-simplicity-reviewer</code> - Final pass for simplicity and minimalism</li>
-            </ul>
-
-            <p><strong>Analysis & Architecture (four)</strong></p>
-            <ul>
-              <li><code>architecture-strategist</code> - Architectural decisions and compliance</li>
-              <li><code>pattern-recognition-specialist</code> - Design pattern analysis</li>
-              <li><code>security-sentinel</code> - Security audits and vulnerability assessments</li>
-              <li><code>performance-oracle</code> - Performance analysis and optimization</li>
-            </ul>
-
-            <p><strong>Research (four)</strong></p>
-            <ul>
-              <li><code>framework-docs-researcher</code> - Framework documentation research</li>
-              <li><code>best-practices-researcher</code> - External best practices gathering</li>
-              <li><code>git-history-analyzer</code> - Git history and code evolution analysis</li>
-              <li><code>repo-research-analyst</code> - Repository structure and conventions</li>
-            </ul>
-
-            <p><strong>Workflow (three)</strong></p>
-            <ul>
-              <li><code>every-style-editor</code> - Every's style guide compliance</li>
-              <li><code>pr-comment-resolver</code> - PR comment resolution</li>
-              <li><code>feedback-codifier</code> - Feedback pattern codification</li>
-            </ul>
-
-            <h4>Six Slash Commands</h4>
-            <ul>
-              <li><code>/plan</code> - Create implementation plans</li>
-              <li><code>/review</code> - Comprehensive code reviews</li>
-              <li><code>/work</code> - Execute work items systematically</li>
-              <li><code>/triage</code> - Triage and prioritize issues</li>
-              <li><code>/resolve_todo_parallel</code> - Resolve TODOs in parallel</li>
-              <li><code>/generate_command</code> - Generate new slash commands</li>
-            </ul>
-
-            <h4>Infrastructure</h4>
-            <ul>
-              <li>MIT license</li>
-              <li>Plugin manifest (<code>plugin.json</code>)</li>
-              <li>Pre-configured permissions for Rails development</li>
-            </ul>
-          </div>
-        </section>
-
-      </article>
-    </main>
-  </div>
-</body>
-
-</html>
--- a/docs/pages/commands.html
+++ b/docs/pages/commands.html
@@ -1,523 +0,0 @@
-<!DOCTYPE html>
-<html lang="en" class="theme-dark">
-
-<head>
-  <meta charset="utf-8" />
-  <title>Command Reference - Compounding Engineering</title>
-  <meta content="Complete reference for all 16 slash commands in the Compounding Engineering plugin." name="description" />
-  <meta content="width=device-width, initial-scale=1" name="viewport" />
-
-  <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/6.5.1/css/all.min.css" />
-  <link href="../css/style.css" rel="stylesheet" type="text/css" />
-  <link href="../css/docs.css" rel="stylesheet" type="text/css" />
-  <script src="../js/main.js" type="text/javascript" defer></script>
-</head>
-
-<body>
-  <div class="background-gradient"></div>
-  <div class="docs-layout">
-    <aside class="docs-sidebar">
-      <div class="sidebar-header">
-        <a href="../index.html" class="nav-brand">
-          <span class="logo-icon"><i class="fa-solid fa-layer-group"></i></span>
-          <span class="logo-text">CE Docs</span>
-        </a>
-      </div>
-      <nav class="sidebar-nav">
-        <div class="nav-section">
-          <h3>Getting Started</h3>
-          <ul>
-            <li><a href="getting-started.html">Installation</a></li>
-          </ul>
-        </div>
-        <div class="nav-section">
-          <h3>Reference</h3>
-          <ul>
-            <li><a href="agents.html">Agents (23)</a></li>
-            <li><a href="commands.html" class="active">Commands (13)</a></li>
-            <li><a href="skills.html">Skills (11)</a></li>
-            <li><a href="mcp-servers.html">MCP Servers (two)</a></li>
-          </ul>
-        </div>
-        <div class="nav-section">
-          <h3>Resources</h3>
-          <ul>
-            <li><a href="changelog.html">Changelog</a></li>
-          </ul>
-        </div>
-        <div class="nav-section">
-          <h3>On This Page</h3>
-          <ul>
-            <li><a href="#workflow-commands">Workflow (four)</a></li>
-            <li><a href="#utility-commands">Utility (12)</a></li>
-          </ul>
-        </div>
-      </nav>
-    </aside>
-
-    <main class="docs-content">
-      <div class="docs-header">
-        <nav class="breadcrumb">
-          <a href="../index.html">Home</a>
-          <span>/</span>
-          <a href="getting-started.html">Docs</a>
-          <span>/</span>
-          <span>Commands</span>
-        </nav>
-        <button class="mobile-menu-toggle" data-sidebar-toggle>
-          <i class="fa-solid fa-bars"></i>
-        </button>
-      </div>
-
-      <article class="docs-article">
-        <h1><i class="fa-solid fa-terminal color-accent"></i> Command Reference</h1>
-        <p class="lead">
-          Here's the thing about slash commands: they're workflows you'd spend 20 minutes doing manually, compressed into one line. Type <code>/plan</code> and watch three agents launch in parallel to research your codebase while you grab coffee. That's the point—automation that actually saves time, not busywork dressed up as productivity.
-        </p>
-
-        <!-- Workflow Commands -->
-        <section id="workflow-commands">
-          <h2><i class="fa-solid fa-arrows-spin"></i> Workflow Commands (four)</h2>
-          <p>These are the big four: Plan your feature, Review your code, Work through the implementation, and Codify what you learned. Every professional developer does this cycle—these commands just make you faster at it.</p>
-
-          <div class="command-detail" id="workflows-plan">
-            <div class="command-detail-header">
-              <code class="command-detail-name">/plan</code>
-            </div>
-            <p class="command-detail-description">
-              You've got a feature request and a blank page. This command turns "we need OAuth" into a structured plan that actually tells you what to build—researched, reviewed, and ready to execute.
-            </p>
-            <h4>Arguments</h4>
-            <p><code>[feature description, bug report, or improvement idea]</code></p>
-            <h4>Workflow</h4>
-            <ol>
-              <li><strong>Repository Research (Parallel)</strong> - Launch three agents simultaneously:
-                <ul>
-                  <li><code>repo-research-analyst</code> - Project patterns</li>
-                  <li><code>best-practices-researcher</code> - Industry standards</li>
-                  <li><code>framework-docs-researcher</code> - Framework documentation</li>
-                </ul>
-              </li>
-              <li><strong>SpecFlow Analysis</strong> - Run <code>spec-flow-analyzer</code> for user flows</li>
-              <li><strong>Choose Detail Level</strong>:
-                <ul>
-                  <li><strong>MINIMAL</strong> - Simple bugs/small improvements</li>
-                  <li><strong>MORE</strong> - Standard features</li>
-                  <li><strong>A LOT</strong> - Major features with phases</li>
-                </ul>
-              </li>
-              <li><strong>Write Plan</strong> - Save as <code>plans/&lt;issue_title&gt;.md</code></li>
-              <li><strong>Review</strong> - Call <code>/plan_review</code> for multi-agent feedback</li>
-            </ol>
-            <div class="callout callout-info">
-              <div class="callout-icon"><i class="fa-solid fa-circle-info"></i></div>
-              <div class="callout-content">
-                <p>This command does NOT write code. It only researches and creates the plan.</p>
-              </div>
-            </div>
-            <div class="card-code-block">
-              <pre><code>/plan Add OAuth integration for third-party auth
-/plan Fix N+1 query in user dashboard</code></pre>
-            </div>
-          </div>
-
-          <div class="command-detail" id="workflows-review">
-            <div class="command-detail-header">
-              <code class="command-detail-name">/review</code>
-            </div>
-            <p class="command-detail-description">
-              Twelve specialized reviewers examine your PR in parallel—security, performance, architecture, patterns. It's like code review by committee, except the committee finishes in two minutes instead of two days.
-            </p>
-            <h4>Arguments</h4>
-            <p><code>[PR number, GitHub URL, branch name, or "latest"]</code></p>
-            <h4>Workflow</h4>
-            <ol>
-              <li><strong>Setup</strong> - Detect review target, optionally use git-worktree for isolation</li>
-              <li><strong>Launch 12 Parallel Review Agents</strong>:
-                <ul>
-                  <li><code>kieran-rails-reviewer</code>, <code>dhh-rails-reviewer</code></li>
-                  <li><code>security-sentinel</code>, <code>performance-oracle</code></li>
-                  <li><code>architecture-strategist</code>, <code>data-integrity-guardian</code></li>
-                  <li><code>pattern-recognition-specialist</code>, <code>git-history-analyzer</code></li>
-                  <li>And more...</li>
-                </ul>
-              </li>
-              <li><strong>Ultra-Thinking Analysis</strong> - Stakeholder perspectives, scenario exploration</li>
-              <li><strong>Simplification Review</strong> - Run <code>code-simplicity-reviewer</code></li>
-              <li><strong>Synthesize Findings</strong> - Categorize by severity (P1/P2/P3)</li>
-              <li><strong>Create Todo Files</strong> - Using file-todos skill for all findings</li>
-            </ol>
-            <div class="callout callout-warning">
-              <div class="callout-icon"><i class="fa-solid fa-triangle-exclamation"></i></div>
-              <div class="callout-content">
-                <p><strong>P1 (Critical) findings BLOCK MERGE.</strong> Address these before merging.</p>
-              </div>
-            </div>
-            <div class="card-code-block">
-              <pre><code>/review 42
-/review https://github.com/owner/repo/pull/42
-/review feature-branch-name
-/review latest</code></pre>
-            </div>
-          </div>
-
-          <div class="command-detail" id="workflows-work">
-            <div class="command-detail-header">
-              <code class="command-detail-name">/work</code>
-            </div>
-            <p class="command-detail-description">
-              Point this at a plan file and watch it execute—reading requirements, setting up environment, running tests, creating commits, opening PRs. It's the "just build the thing" button you wish you always had.
-            </p>
-            <h4>Arguments</h4>
-            <p><code>[plan file, specification, or todo file path]</code></p>
-            <h4>Phases</h4>
-            <ol>
-              <li><strong>Quick Start</strong>
-                <ul>
-                  <li>Read plan & clarify requirements</li>
-                  <li>Setup environment (live or worktree)</li>
-                  <li>Create TodoWrite task list</li>
-                </ul>
-              </li>
-              <li><strong>Execute</strong>
-                <ul>
-                  <li>Task execution loop with progress tracking</li>
-                  <li>Follow existing patterns</li>
-                  <li>Test continuously</li>
-                  <li>Figma sync if applicable</li>
-                </ul>
-              </li>
-              <li><strong>Quality Check</strong>
-                <ul>
-                  <li>Run test suite</li>
-                  <li>Run linting</li>
-                  <li>Optional reviewer agents for complex changes</li>
-                </ul>
-              </li>
-              <li><strong>Ship It</strong>
-                <ul>
-                  <li>Create commit with conventional format</li>
-                  <li>Create pull request</li>
-                  <li>Notify with summary</li>
-                </ul>
-              </li>
-            </ol>
-            <div class="card-code-block">
-              <pre><code>/work plans/user-authentication.md
-/work todos/042-ready-p1-performance-issue.md</code></pre>
-            </div>
-          </div>
-
-          <div class="command-detail" id="workflows-compound">
-            <div class="command-detail-header">
-              <code class="command-detail-name">/compound</code>
-            </div>
-            <p class="command-detail-description">
-              Just fixed a gnarly bug? This captures the solution before you forget it. Seven agents analyze what you did, why it worked, and how to prevent it next time. Each documented solution compounds your team's knowledge.
-            </p>
-            <h4>Arguments</h4>
-            <p><code>[optional: brief context about the fix]</code></p>
-            <h4>Workflow</h4>
-            <ol>
-              <li><strong>Preconditions</strong> - Verify problem is solved and verified working</li>
-              <li><strong>Launch seven parallel subagents</strong>:
-                <ul>
-                  <li>Context Analyzer - Extract YAML frontmatter skeleton</li>
-                  <li>Solution Extractor - Identify root cause and solution</li>
-                  <li>Related Docs Finder - Find cross-references</li>
-                  <li>Prevention Strategist - Develop prevention strategies</li>
-                  <li>Category Classifier - Determine docs category</li>
-                  <li>Documentation Writer - Create the file</li>
-                  <li>Optional Specialized Agent - Based on problem type</li>
-                </ul>
-              </li>
-              <li><strong>Create Documentation</strong> - File in <code>docs/solutions/[category]/</code></li>
-            </ol>
-            <h4>Auto-Triggers</h4>
-            <p>Phrases: "that worked", "it's fixed", "working now", "problem solved"</p>
-            <div class="card-code-block">
-              <pre><code>/compound
-/compound N+1 query optimization</code></pre>
-            </div>
-          </div>
-        </section>
-
-        <!-- Utility Commands -->
-        <section id="utility-commands">
-          <h2><i class="fa-solid fa-wrench"></i> Utility Commands (12)</h2>
-          <p>The supporting cast—commands that do one specific thing really well. Generate changelogs, resolve todos in parallel, triage findings, create new commands. The utilities you reach for daily.</p>
-
-          <div class="command-detail" id="changelog">
-            <div class="command-detail-header">
-              <code class="command-detail-name">/changelog</code>
-            </div>
-            <p class="command-detail-description">
-              Turn your git history into a changelog people actually want to read. Breaking changes at the top, fun facts at the bottom, everything organized by what matters to your users.
-            </p>
-            <h4>Arguments</h4>
-            <p><code>[optional: daily|weekly, or time period in days]</code></p>
-            <h4>Output Sections</h4>
-            <ul>
-              <li>Breaking Changes (top priority)</li>
-              <li>New Features</li>
-              <li>Bug Fixes</li>
-              <li>Other Improvements</li>
-              <li>Shoutouts</li>
-              <li>Fun Fact</li>
-            </ul>
-            <div class="card-code-block">
-              <pre><code>/changelog daily
-/changelog weekly
-/changelog 7</code></pre>
-            </div>
-          </div>
-
-          <div class="command-detail" id="create-agent-skill">
-            <div class="command-detail-header">
-              <code class="command-detail-name">/create-agent-skill</code>
-            </div>
-            <p class="command-detail-description">
-              Need a new skill? This walks you through creating one that actually works—proper frontmatter, clear documentation, all the conventions baked in. Think of it as scaffolding for skills.
-            </p>
-            <h4>Arguments</h4>
-            <p><code>[skill description or requirements]</code></p>
-            <div class="card-code-block">
-              <pre><code>/create-agent-skill PDF processing for document analysis
-/create-agent-skill Web scraping with error handling</code></pre>
-            </div>
-          </div>
-
-          <div class="command-detail" id="generate-command">
-            <div class="command-detail-header">
-              <code class="command-detail-name">/generate_command</code>
-            </div>
-            <p class="command-detail-description">
-              Same idea, but for commands instead of skills. Tell it what workflow you're tired of doing manually, and it generates a proper slash command with all the right patterns.
-            </p>
-            <h4>Arguments</h4>
-            <p><code>[command purpose and requirements]</code></p>
-            <div class="card-code-block">
-              <pre><code>/generate_command Security audit for codebase
-/generate_command Automated performance testing</code></pre>
-            </div>
-          </div>
-
-          <div class="command-detail" id="heal-skill">
-            <div class="command-detail-header">
-              <code class="command-detail-name">/heal-skill</code>
-            </div>
-            <p class="command-detail-description">
-              Skills drift—APIs change, URLs break, parameters get renamed. When a skill stops working, this figures out what's wrong and fixes the documentation. You approve the changes before anything commits.
-            </p>
-            <h4>Arguments</h4>
-            <p><code>[optional: specific issue to fix]</code></p>
-            <h4>Approval Options</h4>
-            <ol>
-              <li>Apply and commit</li>
-              <li>Apply without commit</li>
-              <li>Revise changes</li>
-              <li>Cancel</li>
-            </ol>
-            <div class="card-code-block">
-              <pre><code>/heal-skill API endpoint URL changed
-/heal-skill parameter validation error</code></pre>
-            </div>
-          </div>
-
-          <div class="command-detail" id="plan-review">
-            <div class="command-detail-header">
-              <code class="command-detail-name">/plan_review</code>
-            </div>
-            <p class="command-detail-description">
-              Before you execute a plan, have three reviewers tear it apart—Rails conventions, best practices, simplicity. Better to find the problems in the plan than in production.
-            </p>
-            <h4>Arguments</h4>
-            <p><code>[plan file path or plan content]</code></p>
-            <h4>Review Agents</h4>
-            <ul>
-              <li><code>dhh-rails-reviewer</code> - Rails conventions</li>
-              <li><code>kieran-rails-reviewer</code> - Rails best practices</li>
-              <li><code>code-simplicity-reviewer</code> - Simplicity and clarity</li>
-            </ul>
-            <div class="card-code-block">
-              <pre><code>/plan_review plans/user-authentication.md</code></pre>
-            </div>
-          </div>
-
-          <div class="command-detail" id="report-bug">
-            <div class="command-detail-header">
-              <code class="command-detail-name">/report-bug</code>
-            </div>
-            <p class="command-detail-description">
-              Something broken? This collects all the context—what broke, what you expected, error messages, environment—and files a proper bug report. No more "it doesn't work" issues.
-            </p>
-            <h4>Arguments</h4>
-            <p><code>[optional: brief description of the bug]</code></p>
-            <h4>Information Collected</h4>
-            <ul>
-              <li>Bug category (Agent/Command/Skill/MCP/Installation)</li>
-              <li>Specific component name</li>
-              <li>Actual vs expected behavior</li>
-              <li>Steps to reproduce</li>
-              <li>Error messages</li>
-              <li>Environment info (auto-gathered)</li>
-            </ul>
-            <div class="card-code-block">
-              <pre><code>/report-bug Agent not working
-/report-bug Command failing with timeout</code></pre>
-            </div>
-          </div>
-
-          <div class="command-detail" id="reproduce-bug">
-            <div class="command-detail-header">
-              <code class="command-detail-name">/reproduce-bug</code>
-            </div>
-            <p class="command-detail-description">
-              Give it a GitHub issue number and it tries to actually reproduce the bug—reading the issue, analyzing code paths, iterating until it finds the root cause. Then it posts findings back to the issue.
-            </p>
-            <h4>Arguments</h4>
-            <p><code>[GitHub issue number]</code></p>
-            <h4>Investigation Process</h4>
-            <ol>
-              <li>Read GitHub issue details</li>
-              <li>Launch parallel investigation agents</li>
-              <li>Analyze code for failure points</li>
-              <li>Iterate until root cause found</li>
-              <li>Post findings to GitHub issue</li>
-            </ol>
-            <div class="card-code-block">
-              <pre><code>/reproduce-bug 142</code></pre>
-            </div>
-          </div>
-
-          <div class="command-detail" id="triage">
-            <div class="command-detail-header">
-              <code class="command-detail-name">/triage</code>
-            </div>
-            <p class="command-detail-description">
-              Got a pile of code review findings or security audit results? This turns them into actionable todos—one at a time, you decide: create the todo, skip it, or modify and re-present.
-            </p>
-            <h4>Arguments</h4>
-            <p><code>[findings list or source type]</code></p>
-            <h4>User Decisions</h4>
-            <ul>
-              <li><strong>"yes"</strong> - Create/update todo file, change status to ready</li>
-              <li><strong>"next"</strong> - Skip and delete from todos</li>
-              <li><strong>"custom"</strong> - Modify and re-present</li>
-            </ul>
-            <div class="callout callout-info">
-              <div class="callout-icon"><i class="fa-solid fa-circle-info"></i></div>
-              <div class="callout-content">
-                <p>This command does NOT write code. It only categorizes and creates todo files.</p>
-              </div>
-            </div>
-            <div class="card-code-block">
-              <pre><code>/triage code-review-findings.txt
-/triage security-audit-results</code></pre>
-            </div>
-          </div>
-
-          <div class="command-detail" id="resolve-parallel">
-            <div class="command-detail-header">
-              <code class="command-detail-name">/resolve_parallel</code>
-            </div>
-            <p class="command-detail-description">
-              All those TODO comments scattered through your codebase? This finds them, builds a dependency graph, and spawns parallel agents to resolve them all at once. Clears the backlog in minutes.
-            </p>
-            <h4>Arguments</h4>
-            <p><code>[optional: specific TODO pattern or file]</code></p>
-            <h4>Process</h4>
-            <ol>
-              <li>Analyze TODO comments from codebase</li>
-              <li>Create dependency graph (mermaid diagram)</li>
-              <li>Spawn parallel <code>pr-comment-resolver</code> agents</li>
-              <li>Commit and push after completion</li>
-            </ol>
-            <div class="card-code-block">
-              <pre><code>/resolve_parallel
-/resolve_parallel authentication
-/resolve_parallel src/auth/</code></pre>
-            </div>
-          </div>
-
-          <div class="command-detail" id="resolve-pr-parallel">
-            <div class="command-detail-header">
-              <code class="command-detail-name">/resolve_pr_parallel</code>
-            </div>
-            <p class="command-detail-description">
-              Same deal, but for PR review comments. Fetch unresolved threads, spawn parallel resolver agents, commit the fixes, and mark threads as resolved. Your reviewers will wonder how you're so fast.
-            </p>
-            <h4>Arguments</h4>
-            <p><code>[optional: PR number or current PR]</code></p>
-            <h4>Process</h4>
-            <ol>
-              <li>Get all unresolved PR comments</li>
-              <li>Create TodoWrite list</li>
-              <li>Launch parallel <code>pr-comment-resolver</code> agents</li>
-              <li>Commit, resolve threads, and push</li>
-            </ol>
-            <div class="card-code-block">
-              <pre><code>/resolve_pr_parallel
-/resolve_pr_parallel 123</code></pre>
-            </div>
-          </div>
-
-          <div class="command-detail" id="resolve-todo-parallel">
-            <div class="command-detail-header">
-              <code class="command-detail-name">/resolve_todo_parallel</code>
-            </div>
-            <p class="command-detail-description">
-              Those todo files in your <code>/todos</code> directory? Point this at them and watch parallel agents knock them out—analyzing dependencies, executing in the right order, marking resolved as they finish.
-            </p>
-            <h4>Arguments</h4>
-            <p><code>[optional: specific todo ID or pattern]</code></p>
-            <h4>Process</h4>
-            <ol>
-              <li>Get unresolved TODOs from <code>/todos/*.md</code></li>
-              <li>Analyze dependencies</li>
-              <li>Spawn parallel agents</li>
-              <li>Commit, mark as resolved, push</li>
-            </ol>
-            <div class="card-code-block">
-              <pre><code>/resolve_todo_parallel
-/resolve_todo_parallel 042
-/resolve_todo_parallel p1</code></pre>
-            </div>
-          </div>
-
-          <div class="command-detail" id="prime">
-            <div class="command-detail-header">
-              <code class="command-detail-name">/prime</code>
-            </div>
-            <p class="command-detail-description">
-              Your project initialization command. What exactly it does depends on your project setup—think of it as the "get everything ready" button before you start coding.
-            </p>
-            <div class="card-code-block">
-              <pre><code>/prime</code></pre>
-            </div>
-          </div>
-        </section>
-
-        <!-- Navigation -->
-        <nav class="docs-nav-footer">
-          <a href="agents.html" class="nav-prev">
-            <span class="nav-label">Previous</span>
-            <span class="nav-title"><i class="fa-solid fa-arrow-left"></i> Agents</span>
-          </a>
-          <a href="skills.html" class="nav-next">
-            <span class="nav-label">Next</span>
-            <span class="nav-title">Skills <i class="fa-solid fa-arrow-right"></i></span>
-          </a>
-        </nav>
-      </article>
-    </main>
-  </div>
-
-  <script>
-    document.querySelector('[data-sidebar-toggle]')?.addEventListener('click', () => {
-      document.querySelector('.docs-sidebar').classList.toggle('open');
-    });
-  </script>
-</body>
-
-</html>
--- a/docs/pages/getting-started.html
+++ b/docs/pages/getting-started.html
@@ -1,582 +0,0 @@
-<!DOCTYPE html>
-<html lang="en" class="theme-dark">
-
-<head>
-  <meta charset="utf-8" />
-  <title>Getting Started - Compounding Engineering</title>
-  <meta content="Complete guide to installing and using the Compounding Engineering plugin for Claude Code." name="description" />
-  <meta content="width=device-width, initial-scale=1" name="viewport" />
-
-  <!-- Styles -->
-  <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/6.5.1/css/all.min.css" />
-  <link href="../css/style.css" rel="stylesheet" type="text/css" />
-  <link href="../css/docs.css" rel="stylesheet" type="text/css" />
-  <script src="../js/main.js" type="text/javascript" defer></script>
-</head>
-
-<body>
-  <div class="background-gradient"></div>
-  <div class="docs-layout">
-    <!-- Sidebar -->
-    <aside class="docs-sidebar">
-      <div class="sidebar-header">
-        <a href="../index.html" class="nav-brand">
-          <span class="logo-icon"><i class="fa-solid fa-layer-group"></i></span>
-          <span class="logo-text">CE Docs</span>
-        </a>
-      </div>
-      <nav class="sidebar-nav">
-        <div class="nav-section">
-          <h3>Getting Started</h3>
-          <ul>
-            <li><a href="#installation" class="active">Installation</a></li>
-            <li><a href="#quick-start">Quick Start</a></li>
-            <li><a href="#configuration">Configuration</a></li>
-          </ul>
-        </div>
-        <div class="nav-section">
-          <h3>Core Concepts</h3>
-          <ul>
-            <li><a href="#philosophy">Philosophy</a></li>
-            <li><a href="#agents">Using Agents</a></li>
-            <li><a href="#commands">Using Commands</a></li>
-            <li><a href="#skills">Using Skills</a></li>
-          </ul>
-        </div>
-        <div class="nav-section">
-          <h3>Guides</h3>
-          <ul>
-            <li><a href="#code-review">Code Review Workflow</a></li>
-            <li><a href="#creating-agents">Creating Custom Agents</a></li>
-            <li><a href="#creating-skills">Creating Custom Skills</a></li>
-          </ul>
-        </div>
-        <div class="nav-section">
-          <h3>Reference</h3>
-          <ul>
-            <li><a href="agents.html">Agent Reference</a></li>
-            <li><a href="commands.html">Command Reference</a></li>
-            <li><a href="skills.html">Skill Reference</a></li>
-            <li><a href="mcp-servers.html">MCP Servers</a></li>
-            <li><a href="changelog.html">Changelog</a></li>
-          </ul>
-        </div>
-      </nav>
-    </aside>
-
-    <!-- Main Content -->
-    <main class="docs-content">
-      <div class="docs-header">
-        <nav class="breadcrumb">
-          <a href="../index.html">Home</a>
-          <span>/</span>
-          <span>Getting Started</span>
-        </nav>
-        <button class="mobile-menu-toggle" data-sidebar-toggle>
-          <i class="fa-solid fa-bars"></i>
-        </button>
-      </div>
-
-      <article class="docs-article">
-        <h1>Getting Started with Compounding Engineering</h1>
-        <p class="lead">
-          Five minutes from now, you'll run a single command that spins up 10 AI agents—each with a different specialty—to review your pull request in parallel. Security, performance, architecture, accessibility, all happening at once. That's the plugin. Let's get you set up.
-        </p>
-
-        <!-- Installation Section -->
-        <section id="installation">
-          <h2><i class="fa-solid fa-download"></i> Installation</h2>
-
-          <h3>Prerequisites</h3>
-          <ul>
-            <li><a href="https://claude.ai/claude-code" target="_blank">Claude Code</a> installed and configured</li>
-            <li>A GitHub account (for marketplace access)</li>
-            <li>Node.js 18+ (for MCP servers)</li>
-          </ul>
-
-          <h3>Step 1: Add the Marketplace</h3>
-          <p>Think of the marketplace as an app store. You're adding it to Claude Code's list of places to look for plugins:</p>
-          <div class="card-code-block">
-            <pre><code>claude /plugin marketplace add https://github.com/EveryInc/compound-engineering-plugin</code></pre>
-          </div>
-
-          <h3>Step 2: Install the Plugin</h3>
-          <p>Now grab the plugin itself:</p>
-          <div class="card-code-block">
-            <pre><code>claude /plugin install compound-engineering</code></pre>
-          </div>
-
-          <h3>Step 3: Verify Installation</h3>
-          <p>Check that it worked:</p>
-          <div class="card-code-block">
-            <pre><code>claude /plugin list</code></pre>
-          </div>
-          <p>You'll see <code>compound-engineering</code> in the list. If you do, you're ready.</p>
-
-          <div class="callout callout-info">
-            <div class="callout-icon"><i class="fa-solid fa-circle-info"></i></div>
-            <div class="callout-content">
-              <h4>Known Issue: MCP Servers</h4>
-              <p>
-                The bundled MCP servers (Playwright for browser automation, Context7 for docs) don't always auto-load. If you need them, there's a manual config step below. Otherwise, ignore this—everything else works fine.
-              </p>
-            </div>
-          </div>
-        </section>
-
-        <!-- Quick Start Section -->
-        <section id="quick-start">
-          <h2><i class="fa-solid fa-rocket"></i> Quick Start</h2>
-
-          <p>Let's see what this thing can actually do. I'll show you three workflows you'll use constantly:</p>
-
-          <h3>Run a Code Review</h3>
-          <p>This is the big one. Type <code>/review</code> and watch it spawn 10+ specialized reviewers:</p>
-          <div class="card-code-block">
-            <pre><code># Review a PR by number
-/review 123
-
-# Review the current branch
-/review
-
-# Review a specific branch
-/review feature/my-feature</code></pre>
-          </div>
-
-          <h3>Use a Specialized Agent</h3>
-          <p>Sometimes you just need one expert. Call them directly:</p>
-          <div class="card-code-block">
-            <pre><code># Rails code review with Kieran's conventions
-claude agent kieran-rails-reviewer "Review the UserController"
-
-# Security audit
-claude agent security-sentinel "Audit authentication flow"
-
-# Research best practices
-claude agent best-practices-researcher "Find pagination patterns for Rails"</code></pre>
-          </div>
-
-          <h3>Invoke a Skill</h3>
-          <p>Skills are like loading a reference book into Claude's brain. When you need deep knowledge in a specific domain:</p>
-          <div class="card-code-block">
-            <pre><code># Generate images with Gemini
-skill: gemini-imagegen
-
-# Write Ruby in DHH's style
-skill: dhh-ruby-style
-
-# Create a new Claude Code skill
-skill: create-agent-skills</code></pre>
-          </div>
-        </section>
-
-        <!-- Configuration Section -->
-        <section id="configuration">
-          <h2><i class="fa-solid fa-gear"></i> Configuration</h2>
-
-          <h3 id="mcp-configuration">MCP Server Configuration</h3>
-          <p>
-            If the MCP servers didn't load automatically, paste this into <code>.claude/settings.json</code>:
-          </p>
-          <div class="card-code-block">
-            <pre><code>{
-  "mcpServers": {
-    "playwright": {
-      "type": "stdio",
-      "command": "npx",
-      "args": ["-y", "@playwright/mcp@latest"],
-      "env": {}
-    },
-    "context7": {
-      "type": "http",
-      "url": "https://mcp.context7.com/mcp"
-    }
-  }
-}</code></pre>
-          </div>
-
-          <h3>Environment Variables</h3>
-          <p>Right now, only one skill needs an API key. If you use Gemini's image generation:</p>
-          <table class="docs-table">
-            <thead>
-              <tr>
-                <th>Variable</th>
-                <th>Required For</th>
-                <th>Description</th>
-              </tr>
-            </thead>
-            <tbody>
-              <tr>
-                <td><code>GEMINI_API_KEY</code></td>
-                <td>gemini-imagegen</td>
-                <td>Google Gemini API key for image generation</td>
-              </tr>
-            </tbody>
-          </table>
-        </section>
-
-        <!-- Philosophy Section -->
-        <section id="philosophy">
-          <h2><i class="fa-solid fa-lightbulb"></i> The Compounding Engineering Philosophy</h2>
-
-          <blockquote class="highlight-quote">
-            Every unit of engineering work should make subsequent units of work easier&mdash;not harder.
-          </blockquote>
-
-          <p>Here's how it works in practice—the four-step loop you'll run over and over:</p>
-
-          <div class="philosophy-grid">
-            <div class="philosophy-card">
-              <div class="philosophy-icon"><i class="fa-solid fa-brain"></i></div>
-              <h4>1. Plan</h4>
-              <p>
-                Before you write a single line, figure out what you're building and why. Use research agents to gather examples, patterns, and context. Think of it as Google Search meets expert consultation.
-              </p>
-            </div>
-            <div class="philosophy-card">
-              <div class="philosophy-icon"><i class="fa-solid fa-robot"></i></div>
-              <h4>2. Delegate</h4>
-              <p>
-                Now build it—with help. Each agent specializes in something (Rails, security, design). You stay in the driver's seat, but you've got a team of specialists riding shotgun.
-              </p>
-            </div>
-            <div class="philosophy-card">
-              <div class="philosophy-icon"><i class="fa-solid fa-magnifying-glass"></i></div>
-              <h4>3. Assess</h4>
-              <p>
-                Before you ship, run the gauntlet. Security agent checks for vulnerabilities. Performance agent flags N+1 queries. Architecture agent questions your design choices. All at once, all in parallel.
-              </p>
-            </div>
-            <div class="philosophy-card">
-              <div class="philosophy-icon"><i class="fa-solid fa-book"></i></div>
-              <h4>4. Codify</h4>
-              <p>
-                You just solved a problem. Write it down. Next time you (or your teammate) face this, you'll have a runbook. That's the "compounding" part—each solution makes the next one faster.
-              </p>
-            </div>
-          </div>
-        </section>
-
-        <!-- Using Agents Section -->
-        <section id="agents">
-          <h2><i class="fa-solid fa-users-gear"></i> Using Agents</h2>
-
-          <p>
-            Think of agents as coworkers with different job titles. You wouldn't ask your security engineer to design your UI, right? Same concept here—each agent has a specialty, and you call the one you need.
-          </p>
-
-          <h3>Invoking Agents</h3>
-          <div class="card-code-block">
-            <pre><code># Basic syntax
-claude agent [agent-name] "[optional message]"
-
-# Examples
-claude agent kieran-rails-reviewer
-claude agent security-sentinel "Audit the payment flow"
-claude agent git-history-analyzer "Show changes to user model"</code></pre>
-          </div>
-
-          <h3>Agent Categories</h3>
-          <table class="docs-table">
-            <thead>
-              <tr>
-                <th>Category</th>
-                <th>Count</th>
-                <th>Purpose</th>
-              </tr>
-            </thead>
-            <tbody>
-              <tr>
-                <td>Review</td>
-                <td>10</td>
-                <td>Code review, security audits, performance analysis</td>
-              </tr>
-              <tr>
-                <td>Research</td>
-                <td>four</td>
-                <td>Best practices, documentation, git history</td>
-              </tr>
-              <tr>
-                <td>Design</td>
-                <td>three</td>
-                <td>UI iteration, Figma sync, design review</td>
-              </tr>
-              <tr>
-                <td>Workflow</td>
-                <td>five</td>
-                <td>Bug reproduction, PR resolution, linting</td>
-              </tr>
-              <tr>
-                <td>Docs</td>
-                <td>one</td>
-                <td>README generation</td>
-              </tr>
-            </tbody>
-          </table>
-
-          <p>
-            <a href="agents.html" class="button secondary">
-              <i class="fa-solid fa-arrow-right"></i> View All Agents
-            </a>
-          </p>
-        </section>
-
-        <!-- Using Commands Section -->
-        <section id="commands">
-          <h2><i class="fa-solid fa-terminal"></i> Using Commands</h2>
-
-          <p>
-            Commands are macros that run entire workflows for you. One command can spin up a dozen agents, coordinate their work, collect results, and hand you a summary. It's automation all the way down.
-          </p>
-
-          <h3>Running Commands</h3>
-          <div class="card-code-block">
-            <pre><code># Workflow commands
-/plan
-/review 123
-/work
-/compound
-
-# Utility commands
-/changelog
-/triage
-/reproduce-bug</code></pre>
-          </div>
-
-          <h3>The Review Workflow</h3>
-          <p>Let me show you what happens when you run <code>/review</code>. Here's the sequence:</p>
-          <ol>
-            <li><strong>Detection</strong> - Figures out what you want reviewed (PR number, branch name, or current changes)</li>
-            <li><strong>Isolation</strong> - Spins up a git worktree so the review doesn't mess with your working directory</li>
-            <li><strong>Parallel execution</strong> - Launches 10+ agents simultaneously (security, performance, architecture, accessibility...)</li>
-            <li><strong>Synthesis</strong> - Sorts findings by severity (P1 = blocks merge, P2 = should fix, P3 = nice-to-have)</li>
-            <li><strong>Persistence</strong> - Creates todo files so you don't lose track of issues</li>
-            <li><strong>Summary</strong> - Hands you a readable report with action items</li>
-          </ol>
-
-          <p>
-            <a href="commands.html" class="button secondary">
-              <i class="fa-solid fa-arrow-right"></i> View All Commands
-            </a>
-          </p>
-        </section>
-
-        <!-- Using Skills Section -->
-        <section id="skills">
-          <h2><i class="fa-solid fa-wand-magic-sparkles"></i> Using Skills</h2>
-
-          <p>
-            Here's the difference: agents are <em>who</em> does the work, skills are <em>what they know</em>. When you invoke a skill, you're loading a reference library into Claude's context—patterns, templates, examples, workflows. It's like handing Claude a technical manual.
-          </p>
-
-          <h3>Invoking Skills</h3>
-          <div class="card-code-block">
-            <pre><code># In your prompt, reference the skill
-skill: gemini-imagegen
-
-# Or ask Claude to use it
-"Use the dhh-ruby-style skill to refactor this code"</code></pre>
-          </div>
-
-          <h3>Skill Structure</h3>
-          <p>Peek inside a skill directory and you'll usually find:</p>
-          <ul>
-            <li><strong>SKILL.md</strong> - The main instructions (what Claude reads first)</li>
-            <li><strong>references/</strong> - Deep dives on concepts and patterns</li>
-            <li><strong>templates/</strong> - Copy-paste code snippets</li>
-            <li><strong>workflows/</strong> - Step-by-step "how to" guides</li>
-            <li><strong>scripts/</strong> - Actual executable code (when words aren't enough)</li>
-          </ul>
-
-          <p>
-            <a href="skills.html" class="button secondary">
-              <i class="fa-solid fa-arrow-right"></i> View All Skills
-            </a>
-          </p>
-        </section>
-
-        <!-- Code Review Workflow Guide -->
-        <section id="code-review">
-          <h2><i class="fa-solid fa-code-pull-request"></i> Code Review Workflow Guide</h2>
-
-          <p>
-            You'll spend most of your time here. This workflow is why the plugin exists—to turn code review from a bottleneck into a superpower.
-          </p>
-
-          <h3>Basic Review</h3>
-          <div class="card-code-block">
-            <pre><code># Review a PR
-/review 123
-
-# Review current branch
-/review</code></pre>
-          </div>
-
-          <h3>Understanding Findings</h3>
-          <p>Every finding gets a priority label. Here's what they mean:</p>
-          <ul>
-            <li><span class="badge badge-critical">P1 Critical</span> - Don't merge until this is fixed. Think: SQL injection, data loss, crashes in production.</li>
-            <li><span class="badge badge-important">P2 Important</span> - Fix before shipping. Performance regressions, N+1 queries, shaky architecture.</li>
-            <li><span class="badge badge-nice">P3 Nice-to-Have</span> - Would be better, but ship without it if you need to. Documentation, minor cleanup, style issues.</li>
-          </ul>
-
-          <h3>Working with Todo Files</h3>
-          <p>After a review, you'll have a <code>todos/</code> directory full of markdown files. Each one is a single issue to fix:</p>
-          <div class="card-code-block">
-            <pre><code># List all pending todos
-ls todos/*-pending-*.md
-
-# Triage findings
-/triage
-
-# Resolve todos in parallel
-/resolve_todo_parallel</code></pre>
-          </div>
-        </section>
-
-        <!-- Creating Custom Agents -->
-        <section id="creating-agents">
-          <h2><i class="fa-solid fa-plus"></i> Creating Custom Agents</h2>
-
-          <p>
-            The built-in agents cover a lot of ground, but every team has unique needs. Maybe you want a "rails-api-reviewer" that enforces your company's API standards. That's 10 minutes of work.
-          </p>
-
-          <h3>Agent File Structure</h3>
-          <div class="card-code-block">
-            <pre><code>---
-name: my-custom-agent
-description: Brief description of what this agent does
---
-
-# Agent Instructions
-
-You are [role description].
-
-## Your Responsibilities
-1. First responsibility
-2. Second responsibility
-
-## Guidelines
- Guideline one
- Guideline two</code></pre>
-          </div>
-
-          <h3>Agent Location</h3>
-          <p>Drop your agent file in one of these directories:</p>
-          <ul>
-            <li><code>.claude/agents/</code> - Just for this project (committed to git)</li>
-            <li><code>~/.claude/agents/</code> - Available in all your projects (stays on your machine)</li>
-          </ul>
-
-          <div class="callout callout-tip">
-            <div class="callout-icon"><i class="fa-solid fa-lightbulb"></i></div>
-            <div class="callout-content">
-              <h4>The Easy Way</h4>
-              <p>
-                Don't write the YAML by hand. Just run <code>/create-agent-skill</code> and answer a few questions. The command generates the file, validates the format, and puts it in the right place.
-              </p>
-            </div>
-          </div>
-        </section>
-
-        <!-- Creating Custom Skills -->
-        <section id="creating-skills">
-          <h2><i class="fa-solid fa-plus"></i> Creating Custom Skills</h2>
-
-          <p>
-            Skills are heavier than agents—they're knowledge bases, not just prompts. You're building a mini library that Claude can reference. Worth the effort for things you do repeatedly.
-          </p>
-
-          <h3>Skill Directory Structure</h3>
-          <div class="card-code-block">
-            <pre><code>my-skill/
-  SKILL.md           # Main skill file (required)
-  references/        # Supporting documentation
-    concept-one.md
-    concept-two.md
-  templates/         # Code templates
-    basic-template.md
-  workflows/         # Step-by-step procedures
-    workflow-one.md
-  scripts/           # Executable scripts
-    helper.py</code></pre>
-          </div>
-
-          <h3>SKILL.md Format</h3>
-          <div class="card-code-block">
-            <pre><code>---
-name: my-skill
-description: Brief description shown when skill is invoked
---
-
-# Skill Title
-
-Detailed instructions for using this skill.
-
-## Quick Start
-...
-
-## Reference Materials
-The skill includes references in the `references/` directory.
-
-## Templates
-Use templates from the `templates/` directory.</code></pre>
-          </div>
-
-          <div class="callout callout-tip">
-            <div class="callout-icon"><i class="fa-solid fa-lightbulb"></i></div>
-            <div class="callout-content">
-              <h4>Get Help Building Skills</h4>
-              <p>
-                Type <code>skill: create-agent-skills</code> and Claude loads expert guidance on skill architecture, best practices, file organization, and validation. It's like having a senior engineer walk you through it.
-              </p>
-            </div>
-          </div>
-        </section>
-
-        <!-- Navigation -->
-        <nav class="docs-nav-footer">
-          <a href="../index.html" class="nav-prev">
-            <span class="nav-label">Previous</span>
-            <span class="nav-title"><i class="fa-solid fa-arrow-left"></i> Home</span>
-          </a>
-          <a href="agents.html" class="nav-next">
-            <span class="nav-label">Next</span>
-            <span class="nav-title">Agent Reference <i class="fa-solid fa-arrow-right"></i></span>
-          </a>
-        </nav>
-      </article>
-    </main>
-  </div>
-
-  <script>
-    // Sidebar toggle for mobile
-    document.querySelector('[data-sidebar-toggle]')?.addEventListener('click', () => {
-      document.querySelector('.docs-sidebar').classList.toggle('open');
-    });
-
-    // Active link highlighting
-    const sections = document.querySelectorAll('section[id]');
-    const navLinks = document.querySelectorAll('.sidebar-nav a');
-
-    window.addEventListener('scroll', () => {
-      let current = '';
-      sections.forEach(section => {
-        const sectionTop = section.offsetTop;
-        if (pageYOffset >= sectionTop - 100) {
-          current = section.getAttribute('id');
-        }
-      });
-
-      navLinks.forEach(link => {
-        link.classList.remove('active');
-        if (link.getAttribute('href') === `#${current}`) {
-          link.classList.add('active');
-        }
-      });
-    });
-  </script>
-</body>
-
-</html>
--- a/docs/pages/mcp-servers.html
+++ b/docs/pages/mcp-servers.html
@@ -1,409 +0,0 @@
-<!DOCTYPE html>
-<html lang="en" class="theme-dark">
-
-<head>
-  <meta charset="utf-8" />
-  <title>MCP Servers Reference - Compounding Engineering</title>
-  <meta content="Complete reference for the two MCP servers in the Compounding Engineering plugin." name="description" />
-  <meta content="width=device-width, initial-scale=1" name="viewport" />
-
-  <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/6.5.1/css/all.min.css" />
-  <link href="../css/style.css" rel="stylesheet" type="text/css" />
-  <link href="../css/docs.css" rel="stylesheet" type="text/css" />
-  <script src="../js/main.js" type="text/javascript" defer></script>
-</head>
-
-<body>
-  <div class="background-gradient"></div>
-  <div class="docs-layout">
-    <aside class="docs-sidebar">
-      <div class="sidebar-header">
-        <a href="../index.html" class="nav-brand">
-          <span class="logo-icon"><i class="fa-solid fa-layer-group"></i></span>
-          <span class="logo-text">CE Docs</span>
-        </a>
-      </div>
-      <nav class="sidebar-nav">
-        <div class="nav-section">
-          <h3>Getting Started</h3>
-          <ul>
-            <li><a href="getting-started.html">Installation</a></li>
-          </ul>
-        </div>
-        <div class="nav-section">
-          <h3>Reference</h3>
-          <ul>
-            <li><a href="agents.html">Agents (23)</a></li>
-            <li><a href="commands.html">Commands (13)</a></li>
-            <li><a href="skills.html">Skills (11)</a></li>
-            <li><a href="mcp-servers.html" class="active">MCP Servers (two)</a></li>
-          </ul>
-        </div>
-        <div class="nav-section">
-          <h3>Resources</h3>
-          <ul>
-            <li><a href="changelog.html">Changelog</a></li>
-          </ul>
-        </div>
-        <div class="nav-section">
-          <h3>On This Page</h3>
-          <ul>
-            <li><a href="#playwright">Playwright</a></li>
-            <li><a href="#context7">Context7</a></li>
-            <li><a href="#manual-config">Manual Configuration</a></li>
-          </ul>
-        </div>
-      </nav>
-    </aside>
-
-    <main class="docs-content">
-      <div class="docs-header">
-        <nav class="breadcrumb">
-          <a href="../index.html">Home</a>
-          <span>/</span>
-          <a href="getting-started.html">Docs</a>
-          <span>/</span>
-          <span>MCP Servers</span>
-        </nav>
-        <button class="mobile-menu-toggle" data-sidebar-toggle>
-          <i class="fa-solid fa-bars"></i>
-        </button>
-      </div>
-
-      <article class="docs-article">
-        <h1><i class="fa-solid fa-server color-accent"></i> MCP Servers Reference</h1>
-        <p class="lead">
-          Think of MCP servers as power tools that plug into Claude Code. Want Claude to actually <em>open a browser</em> and click around your app? That's Playwright. Need the latest Rails docs without leaving your terminal? That's Context7. The plugin bundles both servers—they just work when you install.
-        </p>
-
-        <div class="callout callout-warning">
-          <div class="callout-icon"><i class="fa-solid fa-triangle-exclamation"></i></div>
-          <div class="callout-content">
-            <h4>Known Issue: Auto-Loading</h4>
-            <p>
-              Sometimes MCP servers don't wake up automatically. If Claude can't take screenshots or look up docs, you'll need to add them manually. See <a href="#manual-config">Manual Configuration</a> for the fix.
-            </p>
-          </div>
-        </div>
-
-        <!-- Playwright -->
-        <section id="playwright">
-          <h2><i class="fa-brands fa-chrome"></i> Playwright</h2>
-          <p>
-            You know how you can tell a junior developer "open Chrome and click the login button"? Now you can tell Claude the same thing. Playwright gives Claude hands to control a real browser—clicking buttons, filling forms, taking screenshots, running JavaScript. It's like pair programming with someone who has a browser open next to you.
-          </p>
-
-          <h3>Tools Provided</h3>
-          <table class="docs-table">
-            <thead>
-              <tr>
-                <th>Tool</th>
-                <th>Description</th>
-              </tr>
-            </thead>
-            <tbody>
-              <tr>
-                <td><code>browser_navigate</code></td>
-                <td>Go to any URL—your localhost dev server, production, staging, that competitor's site you're studying</td>
-              </tr>
-              <tr>
-                <td><code>browser_take_screenshot</code></td>
-                <td>Capture what you're seeing right now. Perfect for "does this look right?" design reviews</td>
-              </tr>
-              <tr>
-                <td><code>browser_click</code></td>
-                <td>Click buttons, links, whatever. Claude finds it by text or CSS selector, just like you would</td>
-              </tr>
-              <tr>
-                <td><code>browser_fill_form</code></td>
-                <td>Type into forms faster than you can. Great for testing signup flows without manual clicking</td>
-              </tr>
-              <tr>
-                <td><code>browser_snapshot</code></td>
-                <td>Get the page's accessibility tree—how screen readers see it. Useful for understanding structure without HTML noise</td>
-              </tr>
-              <tr>
-                <td><code>browser_evaluate</code></td>
-                <td>Run any JavaScript in the page. Check localStorage, trigger functions, read variables—full console access</td>
-              </tr>
-            </tbody>
-          </table>
-
-          <h3>When You'll Use This</h3>
-          <ul>
-            <li><strong>Design reviews without leaving the terminal</strong> - "Take a screenshot of the new navbar on mobile" gets you a PNG in seconds</li>
-            <li><strong>Testing signup flows while you code</strong> - "Fill in the registration form with test@example.com and click submit" runs the test for you</li>
-            <li><strong>Debugging production issues</strong> - "Navigate to the error page and show me what's in localStorage" gives you the state without opening DevTools</li>
-            <li><strong>Competitive research</strong> - "Go to competitor.com and screenshot their pricing page" builds your swipe file automatically</li>
-          </ul>
-
-          <h3>Example Usage</h3>
-          <div class="card-code-block">
-            <pre><code># Just talk to Claude naturally—it knows when to use Playwright
-
-# Design review
-"Take a screenshot of the login page"
-
-# Testing a form
-"Navigate to /signup and fill in the email field with test@example.com"
-
-# Debug JavaScript state
-"Go to localhost:3000 and run console.log(window.currentUser)"
-
-# The browser runs in the background. You'll get results without switching windows.</code></pre>
-          </div>
-
-          <h3>Configuration</h3>
-          <div class="card-code-block">
-            <pre><code>{
-  "playwright": {
-    "type": "stdio",
-    "command": "npx",
-    "args": ["-y", "@playwright/mcp@latest"],
-    "env": {}
-  }
-}</code></pre>
-          </div>
-        </section>
-
-        <!-- Context7 -->
-        <section id="context7">
-          <h2><i class="fa-solid fa-book-open"></i> Context7</h2>
-          <p>
-            Ever ask Claude about a framework and get an answer from 2023? Context7 fixes that. It's a documentation service that keeps Claude current with 100+ frameworks—Rails, React, Next.js, Django, whatever you're using. Think of it as having the official docs piped directly into Claude's brain.
-          </p>
-
-          <h3>Tools Provided</h3>
-          <table class="docs-table">
-            <thead>
-              <tr>
-                <th>Tool</th>
-                <th>Description</th>
-              </tr>
-            </thead>
-            <tbody>
-              <tr>
-                <td><code>resolve-library-id</code></td>
-                <td>Maps "Rails" to the actual library identifier Context7 uses. You don't call this—Claude does it automatically</td>
-              </tr>
-              <tr>
-                <td><code>get-library-docs</code></td>
-                <td>Fetches the actual documentation pages. Ask "How does useEffect work?" and this grabs the latest React docs</td>
-              </tr>
-            </tbody>
-          </table>
-
-          <h3>What's Covered</h3>
-          <p>Over 100 frameworks and libraries. Here's a taste of what you can look up:</p>
-          <div class="framework-grid">
-            <div class="framework-category">
-              <h4>Backend</h4>
-              <ul>
-                <li>Ruby on Rails</li>
-                <li>Django</li>
-                <li>Laravel</li>
-                <li>Express</li>
-                <li>FastAPI</li>
-                <li>Spring Boot</li>
-              </ul>
-            </div>
-            <div class="framework-category">
-              <h4>Frontend</h4>
-              <ul>
-                <li>React</li>
-                <li>Vue.js</li>
-                <li>Angular</li>
-                <li>Svelte</li>
-                <li>Next.js</li>
-                <li>Nuxt</li>
-              </ul>
-            </div>
-            <div class="framework-category">
-              <h4>Mobile</h4>
-              <ul>
-                <li>React Native</li>
-                <li>Flutter</li>
-                <li>SwiftUI</li>
-                <li>Kotlin</li>
-              </ul>
-            </div>
-            <div class="framework-category">
-              <h4>Tools & Libraries</h4>
-              <ul>
-                <li>Tailwind CSS</li>
-                <li>PostgreSQL</li>
-                <li>Redis</li>
-                <li>GraphQL</li>
-                <li>Prisma</li>
-                <li>And many more...</li>
-              </ul>
-            </div>
-          </div>
-
-          <h3>Example Usage</h3>
-          <div class="card-code-block">
-            <pre><code># Just ask about the framework—Claude fetches current docs automatically
-
-"Look up the Rails ActionCable documentation"
-
-"How does the useEffect hook work in React?"
-
-"What are the best practices for PostgreSQL indexes?"
-
-# You get answers based on the latest docs, not Claude's training cutoff</code></pre>
-          </div>
-
-          <h3>Configuration</h3>
-          <div class="card-code-block">
-            <pre><code>{
-  "context7": {
-    "type": "http",
-    "url": "https://mcp.context7.com/mcp"
-  }
-}</code></pre>
-          </div>
-        </section>
-
-        <!-- Manual Configuration -->
-        <section id="manual-config">
-          <h2><i class="fa-solid fa-gear"></i> Manual Configuration</h2>
-          <p>
-            If the servers don't load automatically (you'll know because Claude can't take screenshots or fetch docs), you need to wire them up yourself. It's a two-minute copy-paste job.
-          </p>
-
-          <h3>Project-Level Configuration</h3>
-          <p>To enable for just this project, add this to <code>.claude/settings.json</code> in your project root:</p>
-          <div class="card-code-block">
-            <pre><code>{
-  "mcpServers": {
-    "playwright": {
-      "type": "stdio",
-      "command": "npx",
-      "args": ["-y", "@playwright/mcp@latest"],
-      "env": {}
-    },
-    "context7": {
-      "type": "http",
-      "url": "https://mcp.context7.com/mcp"
-    }
-  }
-}</code></pre>
-          </div>
-
-          <h3>Global Configuration</h3>
-          <p>Or enable everywhere—every project on your machine gets these servers. Add to <code>~/.claude/settings.json</code>:</p>
-          <div class="card-code-block">
-            <pre><code>{
-  "mcpServers": {
-    "playwright": {
-      "type": "stdio",
-      "command": "npx",
-      "args": ["-y", "@playwright/mcp@latest"],
-      "env": {}
-    },
-    "context7": {
-      "type": "http",
-      "url": "https://mcp.context7.com/mcp"
-    }
-  }
-}</code></pre>
-          </div>
-
-          <h3>Requirements</h3>
-          <table class="docs-table">
-            <thead>
-              <tr>
-                <th>Server</th>
-                <th>Requirement</th>
-              </tr>
-            </thead>
-            <tbody>
-              <tr>
-                <td>Playwright</td>
-                <td>Node.js 18+ and npx</td>
-              </tr>
-              <tr>
-                <td>Context7</td>
-                <td>Internet connection (HTTP endpoint)</td>
-              </tr>
-            </tbody>
-          </table>
-
-          <h3>Verifying MCP Servers</h3>
-          <p>After you add the config, restart Claude Code. Then test that everything works:</p>
-          <div class="card-code-block">
-            <pre><code># Ask Claude what it has
-"What MCP tools do you have access to?"
-
-# Test Playwright (should work now)
-"Take a screenshot of the current directory listing"
-
-# Test Context7 (should fetch real docs)
-"Look up Rails Active Record documentation"
-
-# If either fails, double-check your JSON syntax and file paths</code></pre>
-          </div>
-        </section>
-
-        <!-- Navigation -->
-        <nav class="docs-nav-footer">
-          <a href="skills.html" class="nav-prev">
-            <span class="nav-label">Previous</span>
-            <span class="nav-title"><i class="fa-solid fa-arrow-left"></i> Skills</span>
-          </a>
-          <a href="getting-started.html" class="nav-next">
-            <span class="nav-label">Back to</span>
-            <span class="nav-title">Getting Started <i class="fa-solid fa-arrow-right"></i></span>
-          </a>
-        </nav>
-      </article>
-    </main>
-  </div>
-
-  <style>
-    .framework-grid {
-      display: grid;
-      grid-template-columns: repeat(2, 1fr);
-      gap: var(--space-l);
-      margin: var(--space-l) 0;
-    }
-
-    @media (min-width: 768px) {
-      .framework-grid {
-        grid-template-columns: repeat(4, 1fr);
-      }
-    }
-
-    .framework-category {
-      background-color: var(--color-surface);
-      padding: var(--space-l);
-      border-radius: var(--radius-m);
-      border: 1px solid var(--color-border);
-    }
-
-    .framework-category h4 {
-      margin: 0 0 var(--space-s) 0;
-      color: var(--color-accent);
-      font-size: var(--font-size-s);
-    }
-
-    .framework-category ul {
-      margin: 0;
-      padding-left: var(--space-l);
-    }
-
-    .framework-category li {
-      margin: var(--space-xs) 0;
-      font-size: var(--font-size-s);
-      color: var(--color-text-secondary);
-    }
-  </style>
-
-  <script>
-    document.querySelector('[data-sidebar-toggle]')?.addEventListener('click', () => {
-      document.querySelector('.docs-sidebar').classList.toggle('open');
-    });
-  </script>
-</body>
-
-</html>
--- a/docs/pages/skills.html
+++ b/docs/pages/skills.html
@@ -1,611 +0,0 @@
-<!DOCTYPE html>
-<html lang="en" class="theme-dark">
-
-<head>
-  <meta charset="utf-8" />
-  <title>Skill Reference - Compounding Engineering</title>
-  <meta content="Complete reference for all 12 intelligent skills in the Compounding Engineering plugin." name="description" />
-  <meta content="width=device-width, initial-scale=1" name="viewport" />
-
-  <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/6.5.1/css/all.min.css" />
-  <link href="../css/style.css" rel="stylesheet" type="text/css" />
-  <link href="../css/docs.css" rel="stylesheet" type="text/css" />
-  <script src="../js/main.js" type="text/javascript" defer></script>
-</head>
-
-<body>
-  <div class="background-gradient"></div>
-  <div class="docs-layout">
-    <aside class="docs-sidebar">
-      <div class="sidebar-header">
-        <a href="../index.html" class="nav-brand">
-          <span class="logo-icon"><i class="fa-solid fa-layer-group"></i></span>
-          <span class="logo-text">CE Docs</span>
-        </a>
-      </div>
-      <nav class="sidebar-nav">
-        <div class="nav-section">
-          <h3>Getting Started</h3>
-          <ul>
-            <li><a href="getting-started.html">Installation</a></li>
-          </ul>
-        </div>
-        <div class="nav-section">
-          <h3>Reference</h3>
-          <ul>
-            <li><a href="agents.html">Agents (27)</a></li>
-            <li><a href="commands.html">Commands (19)</a></li>
-            <li><a href="skills.html" class="active">Skills (12)</a></li>
-            <li><a href="mcp-servers.html">MCP Servers (2)</a></li>
-          </ul>
-        </div>
-        <div class="nav-section">
-          <h3>Resources</h3>
-          <ul>
-            <li><a href="changelog.html">Changelog</a></li>
-          </ul>
-        </div>
-        <div class="nav-section">
-          <h3>On This Page</h3>
-          <ul>
-            <li><a href="#development-tools">Development (8)</a></li>
-            <li><a href="#content-workflow">Content & Workflow (3)</a></li>
-            <li><a href="#image-generation">Image Generation (1)</a></li>
-          </ul>
-        </div>
-      </nav>
-    </aside>
-
-    <main class="docs-content">
-      <div class="docs-header">
-        <nav class="breadcrumb">
-          <a href="../index.html">Home</a>
-          <span>/</span>
-          <a href="getting-started.html">Docs</a>
-          <span>/</span>
-          <span>Skills</span>
-        </nav>
-        <button class="mobile-menu-toggle" data-sidebar-toggle>
-          <i class="fa-solid fa-bars"></i>
-        </button>
-      </div>
-
-      <article class="docs-article">
-        <h1><i class="fa-solid fa-wand-magic-sparkles color-accent"></i> Skill Reference</h1>
-        <p class="lead">
-          Think of skills as reference manuals that Claude Code can read mid-conversation. When you're writing Rails code and want DHH's style, or building a gem like Andrew Kane would, you don't need to paste documentation—just invoke the skill. Claude reads it, absorbs the patterns, and writes code that way.
-        </p>
-
-        <div class="usage-box">
-          <h3>How to Use Skills</h3>
-          <div class="card-code-block">
-            <pre><code># In your prompt, reference the skill
-skill: [skill-name]
-
-# Examples
-skill: gemini-imagegen
-skill: dhh-rails-style
-skill: create-agent-skills</code></pre>
-          </div>
-        </div>
-
-        <div class="callout callout-info">
-          <div class="callout-icon"><i class="fa-solid fa-circle-info"></i></div>
-          <div class="callout-content">
-            <h4>Skills vs Agents</h4>
-            <p>
-              <strong>Agents</strong> are personas—they <em>do</em> things. <strong>Skills</strong> are knowledge—they teach Claude <em>how</em> to do things. Use <code>claude agent [name]</code> when you want someone to review your code. Use <code>skill: [name]</code> when you want to write code in a particular style yourself.
-            </p>
-          </div>
-        </div>
-
-        <!-- Development Tools -->
-        <section id="development-tools">
-          <h2><i class="fa-solid fa-code"></i> Development Tools (8)</h2>
-          <p>These skills teach Claude specific coding styles and architectural patterns. Use them when you want code that follows a particular philosophy—not just any working code, but code that looks like it was written by a specific person or framework.</p>
-
-          <div class="skill-detail" id="create-agent-skills">
-            <div class="skill-detail-header">
-              <h3>create-agent-skills</h3>
-              <span class="skill-badge">Meta</span>
-            </div>
-            <p class="skill-detail-description">
-              You're writing a skill right now, but you're not sure if you're structuring the SKILL.md file correctly. Should the examples go before the theory? How do you organize workflows vs. references? This skill is the answer—it's the master template for building skills themselves.
-            </p>
-            <h4>Capabilities</h4>
-            <ul>
-              <li>Skill architecture and best practices</li>
-              <li>Router pattern for complex multi-step skills</li>
-              <li>Progressive disclosure design principles</li>
-              <li>SKILL.md structure guidance</li>
-              <li>Asset management (workflows, references, templates, scripts)</li>
-              <li>XML structure patterns</li>
-            </ul>
-            <h4>Workflows Included</h4>
-            <ul>
-              <li><code>create-new-skill</code> - Start from scratch</li>
-              <li><code>add-reference</code> - Add reference documentation</li>
-              <li><code>add-template</code> - Add code templates</li>
-              <li><code>add-workflow</code> - Add step-by-step procedures</li>
-              <li><code>add-script</code> - Add executable scripts</li>
-              <li><code>audit-skill</code> - Validate skill structure</li>
-              <li><code>verify-skill</code> - Test skill functionality</li>
-            </ul>
-            <div class="card-code-block">
-              <pre><code>skill: create-agent-skills</code></pre>
-            </div>
-          </div>
-
-          <div class="skill-detail" id="skill-creator">
-            <div class="skill-detail-header">
-              <h3>skill-creator</h3>
-              <span class="skill-badge">Meta</span>
-            </div>
-            <p class="skill-detail-description">
-              The simpler, step-by-step version of <code>create-agent-skills</code>. When you just want a checklist to follow from blank file to packaged skill, use this. It's less about theory, more about "do step 1, then step 2."
-            </p>
-            <h4>6-Step Process</h4>
-            <ol>
-              <li>Understand skill usage patterns with examples</li>
-              <li>Plan reusable skill contents</li>
-              <li>Initialize skill using template</li>
-              <li>Edit skill with clear instructions</li>
-              <li>Package skill into distributable zip</li>
-              <li>Iterate based on testing feedback</li>
-            </ol>
-            <div class="card-code-block">
-              <pre><code>skill: skill-creator</code></pre>
-            </div>
-          </div>
-
-          <div class="skill-detail" id="dhh-rails-style">
-            <div class="skill-detail-header">
-              <h3>dhh-rails-style</h3>
-              <span class="skill-badge">Rails</span>
-            </div>
-            <p class="skill-detail-description">
-              Comprehensive 37signals Rails conventions based on Marc Köhlbrugge's analysis of 265 PRs from the Fizzy codebase. Covers everything from REST mapping to state-as-records, Turbo/Stimulus patterns, CSS with OKLCH colors, Minitest with fixtures, and Solid Queue/Cache/Cable patterns.
-            </p>
-            <h4>Key Patterns</h4>
-            <ul>
-              <li><strong>REST Purity</strong> - Verbs become nouns (close → closure)</li>
-              <li><strong>State as Records</strong> - Boolean columns → separate records</li>
-              <li><strong>Fat Models</strong> - Business logic, authorization, broadcasting</li>
-              <li><strong>Thin Controllers</strong> - 1-5 line actions with concerns</li>
-              <li><strong>Current Attributes</strong> - Request context everywhere</li>
-              <li><strong>Hotwire/Turbo</strong> - Model-level broadcasting, morphing</li>
-            </ul>
-            <h4>Reference Files (6)</h4>
-            <ul>
-              <li><code>controllers.md</code> - REST mapping, concerns, Turbo responses</li>
-              <li><code>models.md</code> - Concerns, state records, callbacks, POROs</li>
-              <li><code>frontend.md</code> - Turbo, Stimulus, CSS layers, OKLCH</li>
-              <li><code>architecture.md</code> - Routing, auth, jobs, caching</li>
-              <li><code>testing.md</code> - Minitest, fixtures, integration tests</li>
-              <li><code>gems.md</code> - What to use vs avoid, decision framework</li>
-            </ul>
-            <div class="card-code-block">
-              <pre><code>skill: dhh-rails-style</code></pre>
-            </div>
-          </div>
-
-          <div class="skill-detail" id="andrew-kane-gem-writer">
-            <div class="skill-detail-header">
-              <h3>andrew-kane-gem-writer</h3>
-              <span class="skill-badge">Ruby</span>
-            </div>
-            <p class="skill-detail-description">
-              Andrew Kane has written 100+ Ruby gems with 374 million downloads. Every gem follows the same patterns: minimal dependencies, class macro DSLs, Rails integration without Rails coupling. When you're building a gem and want it to feel production-ready from day one, this is how you do it.
-            </p>
-            <h4>Philosophy</h4>
-            <ul>
-              <li>Simplicity over cleverness</li>
-              <li>Zero or minimal dependencies</li>
-              <li>Explicit code over metaprogramming</li>
-              <li>Rails integration without Rails coupling</li>
-            </ul>
-            <h4>Key Patterns</h4>
-            <ul>
-              <li>Class macro DSL for configuration</li>
-              <li><code>ActiveSupport.on_load</code> for Rails integration</li>
-              <li><code>class << self</code> with <code>attr_accessor</code></li>
-              <li>Railtie pattern for hooks</li>
-              <li>Minitest (no RSpec)</li>
-            </ul>
-            <h4>Reference Files</h4>
-            <ul>
-              <li><code>references/module-organization.md</code></li>
-              <li><code>references/rails-integration.md</code></li>
-              <li><code>references/database-adapters.md</code></li>
-              <li><code>references/testing-patterns.md</code></li>
-            </ul>
-            <div class="card-code-block">
-              <pre><code>skill: andrew-kane-gem-writer</code></pre>
-            </div>
-          </div>
-
-          <div class="skill-detail" id="dspy-ruby">
-            <div class="skill-detail-header">
-              <h3>dspy-ruby</h3>
-              <span class="skill-badge">AI</span>
-            </div>
-            <p class="skill-detail-description">
-              You're adding AI features to your Rails app, but you don't want brittle prompt strings scattered everywhere. DSPy.rb gives you type-safe signatures, composable predictors, and tool-using agents. This skill shows you how to use it—from basic inference to ReAct agents that iterate until they get the answer right.
-            </p>
-            <h4>Predictor Types</h4>
-            <ul>
-              <li><strong>Predict</strong> - Basic inference</li>
-              <li><strong>ChainOfThought</strong> - Reasoning with explanations</li>
-              <li><strong>ReAct</strong> - Tool-using agents with iteration</li>
-              <li><strong>CodeAct</strong> - Dynamic code generation</li>
-            </ul>
-            <h4>Supported Providers</h4>
-            <ul>
-              <li>OpenAI (GPT-4, GPT-4o-mini)</li>
-              <li>Anthropic Claude</li>
-              <li>Google Gemini</li>
-              <li>Ollama (free, local)</li>
-              <li>OpenRouter</li>
-            </ul>
-            <h4>Requirements</h4>
-            <table class="docs-table">
-              <tr>
-                <td><code>OPENAI_API_KEY</code></td>
-                <td>For OpenAI provider</td>
-              </tr>
-              <tr>
-                <td><code>ANTHROPIC_API_KEY</code></td>
-                <td>For Anthropic provider</td>
-              </tr>
-              <tr>
-                <td><code>GOOGLE_API_KEY</code></td>
-                <td>For Gemini provider</td>
-              </tr>
-            </table>
-            <div class="card-code-block">
-              <pre><code>skill: dspy-ruby</code></pre>
-            </div>
-          </div>
-
-          <div class="skill-detail" id="frontend-design">
-            <div class="skill-detail-header">
-              <h3>frontend-design</h3>
-              <span class="skill-badge">Design</span>
-            </div>
-            <p class="skill-detail-description">
-              You've seen what AI usually generates: Inter font, purple gradients, rounded corners on everything. This skill teaches Claude to design interfaces that don't look like every other AI-generated site. It's about purposeful typography, unexpected color palettes, and interfaces with personality.
-            </p>
-            <h4>Design Thinking</h4>
-            <ul>
-              <li><strong>Purpose</strong> - What is the interface for?</li>
-              <li><strong>Tone</strong> - What feeling should it evoke?</li>
-              <li><strong>Constraints</strong> - Technical and brand limitations</li>
-              <li><strong>Differentiation</strong> - How to stand out</li>
-            </ul>
-            <h4>Focus Areas</h4>
-            <ul>
-              <li>Typography with distinctive font choices</li>
-              <li>Color & theme coherence with CSS variables</li>
-              <li>Motion and animation patterns</li>
-              <li>Spatial composition with asymmetry</li>
-              <li>Backgrounds (gradients, textures, patterns)</li>
-            </ul>
-            <div class="callout callout-tip">
-              <div class="callout-icon"><i class="fa-solid fa-lightbulb"></i></div>
-              <div class="callout-content">
-                <p>Avoids generic AI aesthetics like Inter fonts, purple gradients, and rounded corners everywhere.</p>
-              </div>
-            </div>
-            <div class="card-code-block">
-              <pre><code>skill: frontend-design</code></pre>
-            </div>
-          </div>
-
-          <div class="skill-detail" id="compound-docs">
-            <div class="skill-detail-header">
-              <h3>compound-docs</h3>
-              <span class="skill-badge">Docs</span>
-            </div>
-            <p class="skill-detail-description">
-              You just fixed a weird build error after an hour of debugging. Tomorrow you'll forget how you fixed it. This skill automatically detects when you solve something (phrases like "that worked" or "it's fixed") and documents it with YAML frontmatter so you can find it again. Each documented solution compounds your team's knowledge.
-            </p>
-            <h4>Auto-Triggers</h4>
-            <p>Phrases: "that worked", "it's fixed", "working now", "problem solved"</p>
-            <h4>7-Step Process</h4>
-            <ol>
-              <li>Detect confirmation phrase</li>
-              <li>Gather context (module, symptom, investigation, root cause)</li>
-              <li>Check existing docs for similar issues</li>
-              <li>Generate filename</li>
-              <li>Validate YAML frontmatter</li>
-              <li>Create documentation in category directory</li>
-              <li>Cross-reference related issues</li>
-            </ol>
-            <h4>Categories</h4>
-            <ul>
-              <li><code>build-errors/</code></li>
-              <li><code>test-failures/</code></li>
-              <li><code>runtime-errors/</code></li>
-              <li><code>performance-issues/</code></li>
-              <li><code>database-issues/</code></li>
-              <li><code>security-issues/</code></li>
-            </ul>
-            <div class="card-code-block">
-              <pre><code>skill: compound-docs</code></pre>
-            </div>
-          </div>
-
-          <div class="skill-detail" id="agent-native-architecture">
-            <div class="skill-detail-header">
-              <h3>agent-native-architecture</h3>
-              <span class="skill-badge">AI</span>
-            </div>
-            <p class="skill-detail-description">
-              Build AI agents using prompt-native architecture where features are defined in prompts, not code. When creating autonomous agents, designing MCP servers, or implementing self-modifying systems, this skill guides the "trust the agent's intelligence" philosophy.
-            </p>
-            <h4>Key Patterns</h4>
-            <ul>
-              <li><strong>Prompt-Native Features</strong> - Define features in prompts, not code</li>
-              <li><strong>MCP Tool Design</strong> - Build tools agents can use effectively</li>
-              <li><strong>System Prompts</strong> - Write instructions that guide agent behavior</li>
-              <li><strong>Self-Modification</strong> - Allow agents to improve their own prompts</li>
-            </ul>
-            <h4>Core Principle</h4>
-            <p>Whatever the user can do, the agent can do. Whatever the user can see, the agent can see.</p>
-            <div class="card-code-block">
-              <pre><code>skill: agent-native-architecture</code></pre>
-            </div>
-          </div>
-        </section>
-
-        <!-- Content & Workflow -->
-        <section id="content-workflow">
-          <h2><i class="fa-solid fa-pen-fancy"></i> Content & Workflow (3)</h2>
-          <p>Writing, editing, and organizing work. These skills handle everything from style guide compliance to git worktree management—the meta-work that makes the real work easier.</p>
-
-          <div class="skill-detail" id="every-style-editor">
-            <div class="skill-detail-header">
-              <h3>every-style-editor</h3>
-              <span class="skill-badge">Content</span>
-            </div>
-            <p class="skill-detail-description">
-              You wrote a draft, but you're not sure if it matches Every's style guide. Should "internet" be capitalized? Is this comma splice allowed? This skill does a four-phase line-by-line review: context, detailed edits, mechanical checks, and actionable recommendations. It's like having a copy editor who never gets tired.
-            </p>
-            <h4>Four-Phase Review</h4>
-            <ol>
-              <li><strong>Initial Assessment</strong> - Context, type, audience, tone</li>
-              <li><strong>Detailed Line Edit</strong> - Sentence structure, punctuation, capitalization</li>
-              <li><strong>Mechanical Review</strong> - Spacing, formatting, consistency</li>
-              <li><strong>Recommendations</strong> - Actionable improvement suggestions</li>
-            </ol>
-            <h4>Style Checks</h4>
-            <ul>
-              <li>Grammar and punctuation</li>
-              <li>Style guide compliance</li>
-              <li>Capitalization rules</li>
-              <li>Word choice optimization</li>
-              <li>Formatting consistency</li>
-            </ul>
-            <div class="card-code-block">
-              <pre><code>skill: every-style-editor</code></pre>
-            </div>
-          </div>
-
-          <div class="skill-detail" id="file-todos">
-            <div class="skill-detail-header">
-              <h3>file-todos</h3>
-              <span class="skill-badge">Workflow</span>
-            </div>
-            <p class="skill-detail-description">
-              Your todo list is a bunch of markdown files in a <code>todos/</code> directory. Each filename encodes status, priority, and description. No database, no UI, just files with YAML frontmatter. When you need to track work without setting up Jira, this is the system.
-            </p>
-            <h4>File Format</h4>
-            <div class="card-code-block">
-              <pre><code># Naming convention
-{issue_id}-{status}-{priority}-{description}.md
-
-# Examples
-001-pending-p1-security-vulnerability.md
-002-ready-p2-performance-optimization.md
-003-complete-p3-code-cleanup.md</code></pre>
-            </div>
-            <h4>Status Values</h4>
-            <ul>
-              <li><code>pending</code> - Needs triage</li>
-              <li><code>ready</code> - Approved for work</li>
-              <li><code>complete</code> - Done</li>
-            </ul>
-            <h4>Priority Values</h4>
-            <ul>
-              <li><code>p1</code> - Critical</li>
-              <li><code>p2</code> - Important</li>
-              <li><code>p3</code> - Nice-to-have</li>
-            </ul>
-            <h4>YAML Frontmatter</h4>
-            <div class="card-code-block">
-              <pre><code>---
-status: pending
-priority: p1
-issue_id: "001"
-tags: [security, authentication]
-dependencies: []
---</code></pre>
-            </div>
-            <div class="card-code-block">
-              <pre><code>skill: file-todos</code></pre>
-            </div>
-          </div>
-
-          <div class="skill-detail" id="git-worktree">
-            <div class="skill-detail-header">
-              <h3>git-worktree</h3>
-              <span class="skill-badge">Git</span>
-            </div>
-            <p class="skill-detail-description">
-              You're working on a feature branch, but you need to review a PR without losing your current work. Git worktrees let you have multiple branches checked out simultaneously in separate directories. This skill manages them—create, switch, cleanup—so you can context-switch without stashing or committing half-finished code.
-            </p>
-            <h4>Commands</h4>
-            <div class="card-code-block">
-              <pre><code># Create new worktree
-bash scripts/worktree-manager.sh create feature-login
-
-# List worktrees
-bash scripts/worktree-manager.sh list
-
-# Switch to worktree
-bash scripts/worktree-manager.sh switch feature-login
-
-# Clean up completed worktrees
-bash scripts/worktree-manager.sh cleanup</code></pre>
-            </div>
-            <h4>Integration</h4>
-            <ul>
-              <li>Works with <code>/review</code> for isolated PR analysis</li>
-              <li>Works with <code>/work</code> for parallel feature development</li>
-            </ul>
-            <h4>Requirements</h4>
-            <ul>
-              <li>Git 2.8+ (for worktree support)</li>
-              <li>Worktrees stored in <code>.worktrees/</code> directory</li>
-            </ul>
-            <div class="card-code-block">
-              <pre><code>skill: git-worktree</code></pre>
-            </div>
-          </div>
-        </section>
-
-        <!-- Image Generation -->
-        <section id="image-generation">
-          <h2><i class="fa-solid fa-image"></i> Image Generation (1)</h2>
-          <p>Generate images with AI. Not stock photos you found on Unsplash—images you describe and the model creates.</p>
-
-          <div class="skill-detail featured" id="gemini-imagegen">
-            <div class="skill-detail-header">
-              <h3>gemini-imagegen</h3>
-              <span class="skill-badge highlight">AI Images</span>
-            </div>
-            <p class="skill-detail-description">
-              Need a logo with specific text? A product mockup on a marble surface? An illustration in a kawaii style? This skill wraps Google's Gemini image generation API. You describe what you want, it generates it. You can edit existing images, refine over multiple turns, or compose from reference images. All through simple Python scripts.
-            </p>
-
-            <h4>Features</h4>
-            <div class="skill-features">
-              <div class="feature-item"><i class="fa-solid fa-check"></i> Text-to-image generation</div>
-              <div class="feature-item"><i class="fa-solid fa-check"></i> Image editing & manipulation</div>
-              <div class="feature-item"><i class="fa-solid fa-check"></i> Multi-turn iterative refinement</div>
-              <div class="feature-item"><i class="fa-solid fa-check"></i> Multiple reference images (up to 14)</div>
-              <div class="feature-item"><i class="fa-solid fa-check"></i> Google Search grounding (Pro)</div>
-            </div>
-
-            <h4>Available Models</h4>
-            <table class="docs-table">
-              <thead>
-                <tr>
-                  <th>Model</th>
-                  <th>Resolution</th>
-                  <th>Best For</th>
-                </tr>
-              </thead>
-              <tbody>
-                <tr>
-                  <td><code>gemini-2.5-flash-image</code></td>
-                  <td>1024px</td>
-                  <td>Speed, high-volume tasks</td>
-                </tr>
-                <tr>
-                  <td><code>gemini-3-pro-image-preview</code></td>
-                  <td>Up to 4K</td>
-                  <td>Professional assets, complex instructions</td>
-                </tr>
-              </tbody>
-            </table>
-
-            <h4>Quick Start</h4>
-            <div class="card-code-block">
-              <pre><code># Text-to-image
-python scripts/generate_image.py "A cat wearing a wizard hat" output.png
-
-# Edit existing image
-python scripts/edit_image.py input.png "Add a rainbow in the background" output.png
-
-# Multi-turn chat
-python scripts/multi_turn_chat.py</code></pre>
-            </div>
-
-            <h4>Image Configuration</h4>
-            <div class="card-code-block">
-              <pre><code>from google.genai import types
-
-response = client.models.generate_content(
-    model="gemini-3-pro-image-preview",
-    contents=[prompt],
-    config=types.GenerateContentConfig(
-        response_modalities=['TEXT', 'IMAGE'],
-        image_config=types.ImageConfig(
-            aspect_ratio="16:9",  # 1:1, 2:3, 3:2, 4:3, 16:9, 21:9
-            image_size="2K"       # 1K, 2K, 4K (Pro only)
-        ),
-    )
-)</code></pre>
-            </div>
-
-            <h4>Prompting Best Practices</h4>
-            <ul>
-              <li><strong>Photorealistic</strong> - Include camera details: lens type, lighting, angle, mood</li>
-              <li><strong>Stylized Art</strong> - Specify style explicitly: kawaii, cel-shading, bold outlines</li>
-              <li><strong>Text in Images</strong> - Be explicit about font style and placement (use Pro model)</li>
-              <li><strong>Product Mockups</strong> - Describe lighting setup and surface</li>
-            </ul>
-
-            <h4>Requirements</h4>
-            <table class="docs-table">
-              <tr>
-                <td><code>GEMINI_API_KEY</code></td>
-                <td>Required environment variable</td>
-              </tr>
-              <tr>
-                <td><code>google-genai</code></td>
-                <td>Python package</td>
-              </tr>
-              <tr>
-                <td><code>pillow</code></td>
-                <td>Python package for image handling</td>
-              </tr>
-            </table>
-
-            <div class="callout callout-info">
-              <div class="callout-icon"><i class="fa-solid fa-circle-info"></i></div>
-              <div class="callout-content">
-                <p>All generated images include SynthID watermarks. Image-only mode won't work with Google Search grounding.</p>
-              </div>
-            </div>
-
-            <div class="card-code-block">
-              <pre><code>skill: gemini-imagegen</code></pre>
-            </div>
-          </div>
-        </section>
-
-        <!-- Navigation -->
-        <nav class="docs-nav-footer">
-          <a href="commands.html" class="nav-prev">
-            <span class="nav-label">Previous</span>
-            <span class="nav-title"><i class="fa-solid fa-arrow-left"></i> Commands</span>
-          </a>
-          <a href="mcp-servers.html" class="nav-next">
-            <span class="nav-label">Next</span>
-            <span class="nav-title">MCP Servers <i class="fa-solid fa-arrow-right"></i></span>
-          </a>
-        </nav>
-      </article>
-    </main>
-  </div>
-
-  <script>
-    document.querySelector('[data-sidebar-toggle]')?.addEventListener('click', () => {
-      document.querySelector('.docs-sidebar').classList.toggle('open');
-    });
-  </script>
-</body>
-
-</html>
--- a/docs/plans/2026-02-14-feat-add-copilot-converter-target-plan.md
+++ b/docs/plans/2026-02-14-feat-add-copilot-converter-target-plan.md
@@ -0,0 +1,328 @@
+---
+title: "feat: Add GitHub Copilot converter target"
+type: feat
+date: 2026-02-14
+status: complete
+---
+
+# feat: Add GitHub Copilot Converter Target
+
+## Overview
+
+Add GitHub Copilot as a converter target following the established `TargetHandler` pattern. This converts the compound-engineering Claude Code plugin into Copilot's native format: custom agents (`.agent.md`), agent skills (`SKILL.md`), and MCP server configuration JSON.
+
+**Brainstorm:** `docs/brainstorms/2026-02-14-copilot-converter-target-brainstorm.md`
+
+## Problem Statement
+
+The CLI tool (`compound`) already supports converting Claude Code plugins to 5 target formats (OpenCode, Codex, Droid, Cursor, Pi). GitHub Copilot is a widely-used AI coding assistant that now supports custom agents, skills, and MCP servers — but there's no converter target for it.
+
+## Proposed Solution
+
+Follow the existing converter pattern exactly:
+
+1. Define types (`src/types/copilot.ts`)
+2. Implement converter (`src/converters/claude-to-copilot.ts`)
+3. Implement writer (`src/targets/copilot.ts`)
+4. Register target (`src/targets/index.ts`)
+5. Add sync support (`src/sync/copilot.ts`, `src/commands/sync.ts`)
+6. Write tests and documentation
+
+### Component Mapping
+
+| Claude Code | Copilot | Output Path |
+|-------------|---------|-------------|
+| Agents (`.md`) | Custom Agents (`.agent.md`) | `.github/agents/{name}.agent.md` |
+| Commands (`.md`) | Agent Skills (`SKILL.md`) | `.github/skills/{name}/SKILL.md` |
+| Skills (`SKILL.md`) | Agent Skills (`SKILL.md`) | `.github/skills/{name}/SKILL.md` |
+| MCP Servers | Config JSON | `.github/copilot-mcp-config.json` |
+| Hooks | Skipped | Warning to stderr |
+
+## Technical Approach
+
+### Phase 1: Types
+
+**File:** `src/types/copilot.ts`
+
+```typescript
+export type CopilotAgent = {
+  name: string
+  content: string // Full .agent.md content with frontmatter
+}
+
+export type CopilotGeneratedSkill = {
+  name: string
+  content: string // SKILL.md content with frontmatter
+}
+
+export type CopilotSkillDir = {
+  name: string
+  sourceDir: string
+}
+
+export type CopilotMcpServer = {
+  type: string
+  command?: string
+  args?: string[]
+  url?: string
+  tools: string[]
+  env?: Record<string, string>
+  headers?: Record<string, string>
+}
+
+export type CopilotBundle = {
+  agents: CopilotAgent[]
+  generatedSkills: CopilotGeneratedSkill[]
+  skillDirs: CopilotSkillDir[]
+  mcpConfig?: Record<string, CopilotMcpServer>
+}
+```
+
+### Phase 2: Converter
+
+**File:** `src/converters/claude-to-copilot.ts`
+
+**Agent conversion:**
+- Frontmatter: `description` (required, fallback to `"Converted from Claude agent {name}"`), `tools: ["*"]`, `infer: true`
+- Pass through `model` if present
+- Fold `capabilities` into body as `## Capabilities` section (same as Cursor)
+- Use `formatFrontmatter()` utility
+- Warn if body exceeds 30,000 characters (`.length`)
+
+**Command → Skill conversion:**
+- Convert to SKILL.md format with frontmatter: `name`, `description`
+- Flatten namespaced names: `workflows:plan` → `plan`
+- Drop `allowed-tools`, `model`, `disable-model-invocation` silently
+- Include `argument-hint` as `## Arguments` section in body
+
+**Skill pass-through:**
+- Map to `CopilotSkillDir` as-is (same as Cursor)
+
+**MCP server conversion:**
+- Transform env var names: `API_KEY` → `COPILOT_MCP_API_KEY`
+- Skip vars already prefixed with `COPILOT_MCP_`
+- Add `type: "local"` for command-based servers, `type: "sse"` for URL-based
+- Set `tools: ["*"]` for all servers
+
+**Content transformation (`transformContentForCopilot`):**
+
+| Pattern | Input | Output |
+|---------|-------|--------|
+| Task calls | `Task repo-research-analyst(desc)` | `Use the repo-research-analyst skill to: desc` |
+| Slash commands | `/workflows:plan` | `/plan` |
+| Path rewriting | `.claude/` | `.github/` |
+| Home path rewriting | `~/.claude/` | `~/.copilot/` |
+| Agent references | `@security-sentinel` | `the security-sentinel agent` |
+
+**Hooks:** Warn to stderr if present, skip.
+
+### Phase 3: Writer
+
+**File:** `src/targets/copilot.ts`
+
+**Path resolution:**
+- If `outputRoot` basename is `.github`, write directly into it (avoid `.github/.github/` double-nesting)
+- Otherwise, nest under `.github/`
+
+**Write operations:**
+- Agents → `.github/agents/{name}.agent.md` (note: `.agent.md` extension)
+- Generated skills (from commands) → `.github/skills/{name}/SKILL.md`
+- Skill dirs → `.github/skills/{name}/` (copy via `copyDir`)
+- MCP config → `.github/copilot-mcp-config.json` (backup existing with `backupFile`)
+
+### Phase 4: Target Registration
+
+**File:** `src/targets/index.ts`
+
+Add import and register:
+
+```typescript
+import { convertClaudeToCopilot } from "../converters/claude-to-copilot"
+import { writeCopilotBundle } from "./copilot"
+
+// In targets record:
+copilot: {
+  name: "copilot",
+  implemented: true,
+  convert: convertClaudeToCopilot as TargetHandler<CopilotBundle>["convert"],
+  write: writeCopilotBundle as TargetHandler<CopilotBundle>["write"],
+},
+```
+
+### Phase 5: Sync Support
+
+**File:** `src/sync/copilot.ts`
+
+Follow the Cursor sync pattern (`src/sync/cursor.ts`):
+- Symlink skills to `.github/skills/` using `forceSymlink`
+- Validate skill names with `isValidSkillName`
+- Convert MCP servers with `COPILOT_MCP_` prefix transformation
+- Merge MCP config into existing `.github/copilot-mcp-config.json`
+
+**File:** `src/commands/sync.ts`
+
+- Add `"copilot"` to `validTargets` array
+- Add case in `resolveOutputRoot()`: `case "copilot": return path.join(process.cwd(), ".github")`
+- Add import and switch case for `syncToCopilot`
+- Update meta description to include "Copilot"
+
+### Phase 6: Tests
+
+**File:** `tests/copilot-converter.test.ts`
+
+Test cases (following `tests/cursor-converter.test.ts` pattern):
+
+```
+describe("convertClaudeToCopilot")
+  ✓ converts agents to .agent.md with Copilot frontmatter
+  ✓ agent description is required, fallback generated if missing
+  ✓ agent with empty body gets default body
+  ✓ agent capabilities are prepended to body
+  ✓ agent model field is passed through
+  ✓ agent tools defaults to ["*"]
+  ✓ agent infer defaults to true
+  ✓ warns when agent body exceeds 30k characters
+  ✓ converts commands to skills with SKILL.md format
+  ✓ flattens namespaced command names
+  ✓ command name collision after flattening is deduplicated
+  ✓ command allowedTools is silently dropped
+  ✓ command with argument-hint gets Arguments section
+  ✓ passes through skill directories
+  ✓ skill and generated skill name collision is deduplicated
+  ✓ converts MCP servers with COPILOT_MCP_ prefix
+  ✓ MCP env vars already prefixed are not double-prefixed
+  ✓ MCP servers get type field (local vs sse)
+  ✓ warns when hooks are present
+  ✓ no warning when hooks are absent
+  ✓ plugin with zero agents produces empty agents array
+  ✓ plugin with only skills works
+
+describe("transformContentForCopilot")
+  ✓ rewrites .claude/ paths to .github/
+  ✓ rewrites ~/.claude/ paths to ~/.copilot/
+  ✓ transforms Task agent calls to skill references
+  ✓ flattens slash commands
+  ✓ transforms @agent references to agent references
+```
+
+**File:** `tests/copilot-writer.test.ts`
+
+Test cases (following `tests/cursor-writer.test.ts` pattern):
+
+```
+describe("writeCopilotBundle")
+  ✓ writes agents, generated skills, copied skills, and MCP config
+  ✓ agents use .agent.md file extension
+  ✓ writes directly into .github output root without double-nesting
+  ✓ handles empty bundles gracefully
+  ✓ writes multiple agents as separate .agent.md files
+  ✓ backs up existing copilot-mcp-config.json before overwriting
+  ✓ creates skill directories with SKILL.md
+```
+
+**File:** `tests/sync-copilot.test.ts`
+
+Test cases (following `tests/sync-cursor.test.ts` pattern):
+
+```
+describe("syncToCopilot")
+  ✓ symlinks skills to .github/skills/
+  ✓ skips skills with invalid names
+  ✓ merges MCP config with existing file
+  ✓ transforms MCP env var names to COPILOT_MCP_ prefix
+  ✓ writes MCP config with restricted permissions (0o600)
+```
+
+### Phase 7: Documentation
+
+**File:** `docs/specs/copilot.md`
+
+Follow `docs/specs/cursor.md` format:
+- Last verified date
+- Primary sources (GitHub Docs URLs)
+- Config locations table
+- Agents section (`.agent.md` format, frontmatter fields)
+- Skills section (`SKILL.md` format)
+- MCP section (config structure, env var prefix requirement)
+- Character limits (30k agent body)
+
+**File:** `README.md`
+
+- Add "copilot" to the list of supported targets
+- Add usage example: `compound convert --to copilot ./plugins/compound-engineering`
+- Add sync example: `compound sync copilot`
+
+## Acceptance Criteria
+
+### Converter
+- [x] Agents convert to `.agent.md` with `description`, `tools: ["*"]`, `infer: true`
+- [x] Agent `model` passes through when present
+- [x] Agent `capabilities` fold into body as `## Capabilities`
+- [x] Missing description generates fallback
+- [x] Empty body generates fallback
+- [x] Body exceeding 30k chars triggers stderr warning
+- [x] Commands convert to SKILL.md format
+- [x] Command names flatten (`workflows:plan` → `plan`)
+- [x] Name collisions deduplicated with `-2`, `-3` suffix
+- [x] Command `allowed-tools` dropped silently
+- [x] Skills pass through as `CopilotSkillDir`
+- [x] MCP env vars prefixed with `COPILOT_MCP_`
+- [x] Already-prefixed env vars not double-prefixed
+- [x] MCP servers get `type` field (`local` or `sse`)
+- [x] Hooks trigger warning, skip conversion
+- [x] Content transformation: Task calls, slash commands, paths, @agent refs
+
+### Writer
+- [x] Agents written to `.github/agents/{name}.agent.md`
+- [x] Generated skills written to `.github/skills/{name}/SKILL.md`
+- [x] Skill dirs copied to `.github/skills/{name}/`
+- [x] MCP config written to `.github/copilot-mcp-config.json`
+- [x] Existing MCP config backed up before overwrite
+- [x] No double-nesting when outputRoot is `.github`
+- [x] Empty bundles handled gracefully
+
+### CLI Integration
+- [x] `compound convert --to copilot` works
+- [x] `compound sync copilot` works
+- [x] Copilot registered in `src/targets/index.ts`
+- [x] Sync resolves output to `.github/` in current directory
+
+### Tests
+- [x] `tests/copilot-converter.test.ts` — all converter tests pass
+- [x] `tests/copilot-writer.test.ts` — all writer tests pass
+- [x] `tests/sync-copilot.test.ts` — all sync tests pass
+
+### Documentation
+- [x] `docs/specs/copilot.md` — format specification
+- [x] `README.md` — updated with copilot target
+
+## Files to Create
+
+| File | Purpose |
+|------|---------|
+| `src/types/copilot.ts` | Type definitions |
+| `src/converters/claude-to-copilot.ts` | Converter logic |
+| `src/targets/copilot.ts` | Writer logic |
+| `src/sync/copilot.ts` | Sync handler |
+| `tests/copilot-converter.test.ts` | Converter tests |
+| `tests/copilot-writer.test.ts` | Writer tests |
+| `tests/sync-copilot.test.ts` | Sync tests |
+| `docs/specs/copilot.md` | Format specification |
+
+## Files to Modify
+
+| File | Change |
+|------|--------|
+| `src/targets/index.ts` | Register copilot target |
+| `src/commands/sync.ts` | Add copilot to valid targets, output root, switch case |
+| `README.md` | Add copilot to supported targets |
+
+## References
+
+- [Custom agents configuration - GitHub Docs](https://docs.github.com/en/copilot/reference/custom-agents-configuration)
+- [About Agent Skills - GitHub Docs](https://docs.github.com/en/copilot/concepts/agents/about-agent-skills)
+- [MCP and coding agent - GitHub Docs](https://docs.github.com/en/copilot/concepts/agents/coding-agent/mcp-and-coding-agent)
+- Existing converter: `src/converters/claude-to-cursor.ts`
+- Existing writer: `src/targets/cursor.ts`
+- Existing sync: `src/sync/cursor.ts`
+- Existing tests: `tests/cursor-converter.test.ts`, `tests/cursor-writer.test.ts`
--- a/docs/plans/2026-02-14-feat-auto-detect-install-and-gemini-sync-plan.md
+++ b/docs/plans/2026-02-14-feat-auto-detect-install-and-gemini-sync-plan.md
@@ -0,0 +1,360 @@
+---
+title: Auto-detect install targets and add Gemini sync
+type: feat
+status: completed
+date: 2026-02-14
+completed_date: 2026-02-14
+completed_by: "Claude Opus 4.6"
+actual_effort: "Completed in one session"
+---
+
+# Auto-detect Install Targets and Add Gemini Sync
+
+## Overview
+
+Two related improvements to the converter CLI:
+
+1. **`install --to all`** — Auto-detect which AI coding tools are installed and convert to all of them in one command
+2. **`sync --target gemini`** — Add Gemini CLI as a sync target (currently missing), then add `sync --target all` to sync personal config to every detected tool
+
+## Problem Statement
+
+Users currently must run 6 separate commands to install to all targets:
+
+```bash
+bunx @every-env/compound-plugin install compound-engineering --to opencode
+bunx @every-env/compound-plugin install compound-engineering --to codex
+bunx @every-env/compound-plugin install compound-engineering --to droid
+bunx @every-env/compound-plugin install compound-engineering --to cursor
+bunx @every-env/compound-plugin install compound-engineering --to pi
+bunx @every-env/compound-plugin install compound-engineering --to gemini
+```
+
+Similarly, sync requires separate commands per target. And Gemini sync doesn't exist yet.
+
+## Acceptance Criteria
+
+### Auto-detect install
+
+- [x]`install --to all` detects installed tools and installs to each
+- [x]Detection checks config directories and/or binaries for each tool
+- [x]Prints which tools were detected and which were skipped
+- [x]Tools with no detection signal are skipped (not errored)
+- [x]`convert --to all` also works (same detection logic)
+- [x]Existing `--to <target>` behavior unchanged
+- [x]Tests for detection logic and `all` target handling
+
+### Gemini sync
+
+- [x]`sync --target gemini` symlinks skills and writes MCP servers to `.gemini/settings.json`
+- [x]MCP servers merged into existing `settings.json` (same pattern as writer)
+- [x]`gemini` added to `validTargets` in `sync.ts`
+- [x]Tests for Gemini sync
+
+### Sync all
+
+- [x]`sync --target all` syncs to all detected tools
+- [x]Reuses same detection logic as install
+- [x]Prints summary of what was synced where
+
+## Implementation
+
+### Phase 1: Tool Detection Utility
+
+**Create `src/utils/detect-tools.ts`**
+
+```typescript
+import os from "os"
+import path from "path"
+import { pathExists } from "./files"
+
+export type DetectedTool = {
+  name: string
+  detected: boolean
+  reason: string // e.g. "found ~/.codex/" or "not found"
+}
+
+export async function detectInstalledTools(): Promise<DetectedTool[]> {
+  const home = os.homedir()
+  const cwd = process.cwd()
+
+  const checks: Array<{ name: string; paths: string[] }> = [
+    { name: "opencode", paths: [path.join(home, ".config", "opencode"), path.join(cwd, ".opencode")] },
+    { name: "codex", paths: [path.join(home, ".codex")] },
+    { name: "droid", paths: [path.join(home, ".factory")] },
+    { name: "cursor", paths: [path.join(cwd, ".cursor"), path.join(home, ".cursor")] },
+    { name: "pi", paths: [path.join(home, ".pi")] },
+    { name: "gemini", paths: [path.join(cwd, ".gemini"), path.join(home, ".gemini")] },
+  ]
+
+  const results: DetectedTool[] = []
+  for (const check of checks) {
+    let detected = false
+    let reason = "not found"
+    for (const p of check.paths) {
+      if (await pathExists(p)) {
+        detected = true
+        reason = `found ${p}`
+        break
+      }
+    }
+    results.push({ name: check.name, detected, reason })
+  }
+  return results
+}
+
+export async function getDetectedTargetNames(): Promise<string[]> {
+  const tools = await detectInstalledTools()
+  return tools.filter((t) => t.detected).map((t) => t.name)
+}
+```
+
+**Detection heuristics:**
+
+| Tool | Check paths | Notes |
+|------|------------|-------|
+| OpenCode | `~/.config/opencode/`, `.opencode/` | XDG config or project-local |
+| Codex | `~/.codex/` | Global only |
+| Droid | `~/.factory/` | Global only |
+| Cursor | `.cursor/`, `~/.cursor/` | Project-local or global |
+| Pi | `~/.pi/` | Global only |
+| Gemini | `.gemini/`, `~/.gemini/` | Project-local or global |
+
+### Phase 2: Gemini Sync
+
+**Create `src/sync/gemini.ts`**
+
+Follow the Cursor sync pattern (`src/sync/cursor.ts`) since both use JSON config with `mcpServers` key:
+
+```typescript
+import path from "path"
+import { symlinkSkills } from "../utils/symlink"
+import { backupFile, pathExists, readJson, writeJson } from "../utils/files"
+import type { ClaudeMcpServer } from "../types/claude"
+
+export async function syncToGemini(
+  skills: { name: string; sourceDir: string }[],
+  mcpServers: Record<string, ClaudeMcpServer>,
+  outputRoot: string,
+): Promise<void> {
+  const geminiDir = path.join(outputRoot, ".gemini")
+
+  // Symlink skills
+  if (skills.length > 0) {
+    const skillsDir = path.join(geminiDir, "skills")
+    await symlinkSkills(skills, skillsDir)
+  }
+
+  // Merge MCP servers into settings.json
+  if (Object.keys(mcpServers).length > 0) {
+    const settingsPath = path.join(geminiDir, "settings.json")
+    let existing: Record<string, unknown> = {}
+    if (await pathExists(settingsPath)) {
+      await backupFile(settingsPath)
+      try {
+        existing = await readJson<Record<string, unknown>>(settingsPath)
+      } catch {
+        console.warn("Warning: existing settings.json could not be parsed and will be replaced.")
+      }
+    }
+
+    const existingMcp = (existing.mcpServers && typeof existing.mcpServers === "object")
+      ? existing.mcpServers as Record<string, unknown>
+      : {}
+
+    const merged = { ...existing, mcpServers: { ...existingMcp, ...convertMcpServers(mcpServers) } }
+    await writeJson(settingsPath, merged)
+  }
+}
+
+function convertMcpServers(servers: Record<string, ClaudeMcpServer>) {
+  const result: Record<string, Record<string, unknown>> = {}
+  for (const [name, server] of Object.entries(servers)) {
+    const entry: Record<string, unknown> = {}
+    if (server.command) {
+      entry.command = server.command
+      if (server.args?.length) entry.args = server.args
+      if (server.env && Object.keys(server.env).length > 0) entry.env = server.env
+    } else if (server.url) {
+      entry.url = server.url
+      if (server.headers && Object.keys(server.headers).length > 0) entry.headers = server.headers
+    }
+    result[name] = entry
+  }
+  return result
+}
+```
+
+**Update `src/commands/sync.ts`:**
+
+- Add `"gemini"` to `validTargets` array
+- Import `syncToGemini` from `../sync/gemini`
+- Add case in switch for `"gemini"` calling `syncToGemini(skills, mcpServers, outputRoot)`
+
+### Phase 3: Wire `--to all` into Install and Convert
+
+**Modify `src/commands/install.ts`:**
+
+```typescript
+import { detectInstalledTools } from "../utils/detect-tools"
+
+// In args definition, update --to description:
+to: {
+  type: "string",
+  default: "opencode",
+  description: "Target format (opencode | codex | droid | cursor | pi | gemini | all)",
+},
+
+// In run(), before the existing target lookup:
+if (targetName === "all") {
+  const detected = await detectInstalledTools()
+  const activeTargets = detected.filter((t) => t.detected)
+
+  if (activeTargets.length === 0) {
+    console.log("No AI coding tools detected. Install at least one tool first.")
+    return
+  }
+
+  console.log(`Detected ${activeTargets.length} tools:`)
+  for (const tool of detected) {
+    console.log(`  ${tool.detected ? "✓" : "✗"} ${tool.name} — ${tool.reason}`)
+  }
+
+  // Install to each detected target
+  for (const tool of activeTargets) {
+    const handler = targets[tool.name]
+    const bundle = handler.convert(plugin, options)
+    if (!bundle) continue
+    const root = resolveTargetOutputRoot(tool.name, outputRoot, codexHome, piHome, hasExplicitOutput)
+    await handler.write(root, bundle)
+    console.log(`Installed ${plugin.manifest.name} to ${tool.name} at ${root}`)
+  }
+
+  // Codex post-processing
+  if (activeTargets.some((t) => t.name === "codex")) {
+    await ensureCodexAgentsFile(codexHome)
+  }
+  return
+}
+```
+
+**Same change in `src/commands/convert.ts`** with its version of `resolveTargetOutputRoot`.
+
+### Phase 4: Wire `--target all` into Sync
+
+**Modify `src/commands/sync.ts`:**
+
+```typescript
+import { detectInstalledTools } from "../utils/detect-tools"
+
+// Update validTargets:
+const validTargets = ["opencode", "codex", "pi", "droid", "cursor", "gemini", "all"] as const
+
+// In run(), handle "all":
+if (targetName === "all") {
+  const detected = await detectInstalledTools()
+  const activeTargets = detected.filter((t) => t.detected).map((t) => t.name)
+
+  if (activeTargets.length === 0) {
+    console.log("No AI coding tools detected.")
+    return
+  }
+
+  console.log(`Syncing to ${activeTargets.length} detected tools...`)
+  for (const name of activeTargets) {
+    // call existing sync logic for each target
+  }
+  return
+}
+```
+
+### Phase 5: Tests
+
+**Create `tests/detect-tools.test.ts`**
+
+- Test detection with mocked directories (create temp dirs, check detection)
+- Test `getDetectedTargetNames` returns only detected tools
+- Test empty detection returns empty array
+
+**Create `tests/gemini-sync.test.ts`**
+
+Follow `tests/sync-cursor.test.ts` pattern:
+
+- Test skills are symlinked to `.gemini/skills/`
+- Test MCP servers merged into `settings.json`
+- Test existing `settings.json` is backed up
+- Test empty skills/servers produce no output
+
+**Update `tests/cli.test.ts`**
+
+- Test `--to all` flag is accepted
+- Test `sync --target all` is accepted
+- Test `sync --target gemini` is accepted
+
+### Phase 6: Documentation
+
+**Update `README.md`:**
+
+Add to install section:
+```bash
+# auto-detect installed tools and install to all
+bunx @every-env/compound-plugin install compound-engineering --to all
+```
+
+Add to sync section:
+```bash
+# Sync to Gemini
+bunx @every-env/compound-plugin sync --target gemini
+
+# Sync to all detected tools
+bunx @every-env/compound-plugin sync --target all
+```
+
+## What We're NOT Doing
+
+- Not adding binary detection (`which cursor`, `which gemini`) — directory checks are sufficient and don't require shell execution
+- Not adding interactive prompts ("Install to Cursor? y/n") — auto-detect is fire-and-forget
+- Not adding `--exclude` flag for skipping specific targets — can use `--to X --also Y` for manual selection
+- Not adding Gemini to the `sync` symlink watcher (no watcher exists for any target)
+
+## Complexity Assessment
+
+**Low-medium change.** All patterns are established:
+- Detection utility is new but simple (pathExists checks)
+- Gemini sync follows cursor sync pattern exactly
+- `--to all` is plumbing — iterate detected tools through existing handlers
+- No new dependencies needed
+
+## References
+
+- Cursor sync (reference pattern): `src/sync/cursor.ts`
+- Gemini writer (merge pattern): `src/targets/gemini.ts`
+- Install command: `src/commands/install.ts`
+- Sync command: `src/commands/sync.ts`
+- File utilities: `src/utils/files.ts`
+- Symlink utilities: `src/utils/symlink.ts`
+
+## Completion Summary
+
+### What Was Delivered
+- Tool detection utility (`src/utils/detect-tools.ts`) with `detectInstalledTools()` and `getDetectedTargetNames()`
+- Gemini sync (`src/sync/gemini.ts`) following cursor sync pattern — symlinks skills, merges MCP servers into `settings.json`
+- `install --to all` and `convert --to all` auto-detect and install to all detected tools
+- `sync --target gemini` added to sync command
+- `sync --target all` syncs to all detected tools with summary output
+- 8 new tests across 2 test files (detect-tools + sync-gemini)
+
+### Implementation Statistics
+- 4 new files, 3 modified files
+- 139 tests passing (8 new + 131 existing)
+- No new dependencies
+
+### Git Commits
+- `e4d730d` feat: add detect-tools utility and Gemini sync with tests
+- `bc655f7` feat: wire --to all into install/convert and --target all/gemini into sync
+- `877e265` docs: add auto-detect and Gemini sync to README, bump to 0.8.0
+
+### Completion Details
+- **Completed By:** Claude Opus 4.6
+- **Date:** 2026-02-14
+- **Session:** Single session, TDD approach
--- a/docs/plans/2026-02-25-feat-windsurf-global-scope-support-plan.md
+++ b/docs/plans/2026-02-25-feat-windsurf-global-scope-support-plan.md
@@ -0,0 +1,627 @@
+---
+title: Windsurf Global Scope Support
+type: feat
+status: completed
+date: 2026-02-25
+deepened: 2026-02-25
+prior: docs/plans/2026-02-23-feat-add-windsurf-target-provider-plan.md (removed — superseded)
+---
+
+# Windsurf Global Scope Support
+
+## Post-Implementation Revisions (2026-02-26)
+
+After auditing the implementation against `docs/specs/windsurf.md`, two significant changes were made:
+
+1. **Agents → Skills (not Workflows)**: Claude agents map to Windsurf Skills (`skills/{name}/SKILL.md`), not Workflows. Skills are "complex multi-step tasks with supporting resources" — a better conceptual match for specialized expertise/personas. Workflows are "reusable step-by-step procedures" — a better match for Claude Commands (slash commands).
+
+2. **Workflows are flat files**: Command workflows are written to `global_workflows/{name}.md` (global scope) or `workflows/{name}.md` (workspace scope). No subdirectories — the spec requires flat files.
+
+3. **Content transforms updated**: `@agent-name` references are kept as-is (Windsurf skill invocation syntax). `/command` references produce `/{name}` (not `/commands/{name}`). `Task agent(args)` produces `Use the @agent-name skill: args`.
+
+### Final Component Mapping (per spec)
+
+| Claude Code | Windsurf | Output Path | Invocation |
+|---|---|---|---|
+| Agents (`.md`) | Skills | `skills/{name}/SKILL.md` | `@skill-name` or automatic |
+| Commands (`.md`) | Workflows (flat) | `global_workflows/{name}.md` (global) / `workflows/{name}.md` (workspace) | `/{workflow-name}` |
+| Skills (`SKILL.md`) | Skills (pass-through) | `skills/{name}/SKILL.md` | `@skill-name` |
+| MCP servers | `mcp_config.json` | `mcp_config.json` | N/A |
+| Hooks | Skipped with warning | N/A | N/A |
+| CLAUDE.md | Skipped | N/A | N/A |
+
+### Files Changed in Revision
+
+- `src/types/windsurf.ts` — `agentWorkflows` → `agentSkills: WindsurfGeneratedSkill[]`
+- `src/converters/claude-to-windsurf.ts` — `convertAgentToSkill()`, updated content transforms
+- `src/targets/windsurf.ts` — Skills written as `skills/{name}/SKILL.md`, flat workflows
+- Tests updated to match
+
+---
+
+## Enhancement Summary
+
+**Deepened on:** 2026-02-25
+**Research agents used:** architecture-strategist, kieran-typescript-reviewer, security-sentinel, code-simplicity-reviewer, pattern-recognition-specialist
+**External research:** Windsurf MCP docs, Windsurf tutorial docs
+
+### Key Improvements from Deepening
+1. **HTTP/SSE servers should be INCLUDED** — Windsurf supports all 3 transport types (stdio, Streamable HTTP, SSE). Original plan incorrectly skipped them.
+2. **File permissions: use `0o600`** — `mcp_config.json` contains secrets and must not be world-readable. Add secure write support.
+3. **Extract `resolveTargetOutputRoot` to shared utility** — both commands duplicate this; adding scope makes it worse. Extract first.
+4. **Bug fix: missing `result[name] = entry`** — all 5 review agents caught a copy-paste bug in the `buildMcpConfig` sample code.
+5. **`hasPotentialSecrets` to shared utility** — currently in sync.ts, would be duplicated. Extract to `src/utils/secrets.ts`.
+6. **Windsurf `mcp_config.json` is global-only** — per Windsurf docs, no per-project MCP config support. Workspace scope writes it for forward-compatibility but emit a warning.
+7. **Windsurf supports `${env:VAR}` interpolation** — consider writing env var references instead of literal values for secrets.
+
+### New Considerations Discovered
+- Backup files accumulate with secrets and are never cleaned up — cap at 3 backups
+- Workspace `mcp_config.json` could be committed to git — warn about `.gitignore`
+- `WindsurfMcpServerEntry` type needs `serverUrl` field for HTTP/SSE servers
+- Simplicity reviewer recommends handling scope as windsurf-specific in CLI rather than generic `TargetHandler` fields — but brainstorm explicitly chose "generic with windsurf as first adopter". **Decision: keep generic approach** per user's brainstorm decision, with JSDoc documenting the relationship between `defaultScope` and `supportedScopes`.
+
+---
+
+## Overview
+
+Add a generic `--scope global|workspace` flag to the converter CLI with Windsurf as the first adopter. Global scope writes to `~/.codeium/windsurf/`, making workflows, skills, and MCP servers available across all projects. This also upgrades MCP handling from a human-readable setup doc (`mcp-setup.md`) to a proper machine-readable config (`mcp_config.json`), and removes AGENTS.md generation (the plugin's CLAUDE.md contains development-internal instructions, not user-facing content).
+
+## Problem Statement / Motivation
+
+The current Windsurf converter (v0.10.0) writes everything to project-level `.windsurf/`, requiring re-installation per project. Windsurf supports global paths for skills (`~/.codeium/windsurf/skills/`) and MCP config (`~/.codeium/windsurf/mcp_config.json`). Users should install once and get capabilities everywhere.
+
+Additionally, the v0.10.0 MCP output was a markdown setup guide — not an actual integration. Windsurf reads `mcp_config.json` directly, so we should write to that file.
+
+## Breaking Changes from v0.10.0
+
+This is a **minor version bump** (v0.11.0) with intentional breaking changes to the experimental Windsurf target:
+
+1. **Default output location changed** — `--to windsurf` now defaults to global scope (`~/.codeium/windsurf/`). Use `--scope workspace` for the old behavior.
+2. **AGENTS.md no longer generated** — old files are left in place (not deleted).
+3. **`mcp-setup.md` replaced by `mcp_config.json`** — proper machine-readable integration. Old files left in place.
+4. **Env var secrets included with warning** — previously redacted, now included (required for the config file to work).
+5. **`--output` semantics changed** — `--output` now specifies the direct target directory (not a parent where `.windsurf/` is created).
+
+## Proposed Solution
+
+### Phase 0: Extract Shared Utilities (prerequisite)
+
+**Files:** `src/utils/resolve-output.ts` (new), `src/utils/secrets.ts` (new)
+
+#### 0a. Extract `resolveTargetOutputRoot` to shared utility
+
+Both `install.ts` and `convert.ts` have near-identical `resolveTargetOutputRoot` functions that are already diverging (`hasExplicitOutput` exists in install.ts but not convert.ts). Adding scope would make the duplication worse.
+
+- [x] Create `src/utils/resolve-output.ts` with a unified function:
+
+```typescript
+import os from "os"
+import path from "path"
+import type { TargetScope } from "../targets"
+
+export function resolveTargetOutputRoot(options: {
+  targetName: string
+  outputRoot: string
+  codexHome: string
+  piHome: string
+  hasExplicitOutput: boolean
+  scope?: TargetScope
+}): string {
+  const { targetName, outputRoot, codexHome, piHome, hasExplicitOutput, scope } = options
+  if (targetName === "codex") return codexHome
+  if (targetName === "pi") return piHome
+  if (targetName === "droid") return path.join(os.homedir(), ".factory")
+  if (targetName === "cursor") {
+    const base = hasExplicitOutput ? outputRoot : process.cwd()
+    return path.join(base, ".cursor")
+  }
+  if (targetName === "gemini") {
+    const base = hasExplicitOutput ? outputRoot : process.cwd()
+    return path.join(base, ".gemini")
+  }
+  if (targetName === "copilot") {
+    const base = hasExplicitOutput ? outputRoot : process.cwd()
+    return path.join(base, ".github")
+  }
+  if (targetName === "kiro") {
+    const base = hasExplicitOutput ? outputRoot : process.cwd()
+    return path.join(base, ".kiro")
+  }
+  if (targetName === "windsurf") {
+    if (hasExplicitOutput) return outputRoot
+    if (scope === "global") return path.join(os.homedir(), ".codeium", "windsurf")
+    return path.join(process.cwd(), ".windsurf")
+  }
+  return outputRoot
+}
+```
+
+- [x] Update `install.ts` to import and call `resolveTargetOutputRoot` from shared utility
+- [x] Update `convert.ts` to import and call `resolveTargetOutputRoot` from shared utility
+- [x] Add `hasExplicitOutput` tracking to `convert.ts` (currently missing)
+
+### Research Insights (Phase 0)
+
+**Architecture review:** Both commands will call the same function with the same signature. This eliminates the divergence and ensures scope resolution has a single source of truth. The `--also` loop in both commands also uses this function with `handler.defaultScope`.
+
+**Pattern review:** This follows the same extraction pattern as `resolveTargetHome` in `src/utils/resolve-home.ts`.
+
+#### 0b. Extract `hasPotentialSecrets` to shared utility
+
+Currently in `sync.ts:20-31`. The same regex pattern also appears in `claude-to-windsurf.ts:223` as `redactEnvValue`. Extract to avoid a third copy.
+
+- [x] Create `src/utils/secrets.ts`:
+
+```typescript
+const SENSITIVE_PATTERN = /key|token|secret|password|credential|api_key/i
+
+export function hasPotentialSecrets(
+  servers: Record<string, { env?: Record<string, string> }>,
+): boolean {
+  for (const server of Object.values(servers)) {
+    if (server.env) {
+      for (const key of Object.keys(server.env)) {
+        if (SENSITIVE_PATTERN.test(key)) return true
+      }
+    }
+  }
+  return false
+}
+```
+
+- [x] Update `sync.ts` to import from shared utility
+- [x] Use in new windsurf converter
+
+### Phase 1: Types and TargetHandler
+
+**Files:** `src/types/windsurf.ts`, `src/targets/index.ts`
+
+#### 1a. Update WindsurfBundle type
+
+```typescript
+// src/types/windsurf.ts
+export type WindsurfMcpServerEntry = {
+  command?: string
+  args?: string[]
+  env?: Record<string, string>
+  serverUrl?: string
+  headers?: Record<string, string>
+}
+
+export type WindsurfMcpConfig = {
+  mcpServers: Record<string, WindsurfMcpServerEntry>
+}
+
+export type WindsurfBundle = {
+  agentWorkflows: WindsurfWorkflow[]
+  commandWorkflows: WindsurfWorkflow[]
+  skillDirs: WindsurfSkillDir[]
+  mcpConfig: WindsurfMcpConfig | null
+}
+```
+
+- [x] Remove `agentsMd: string | null`
+- [x] Replace `mcpSetupDoc: string | null` with `mcpConfig: WindsurfMcpConfig | null`
+- [x] Add `WindsurfMcpServerEntry` (supports both stdio and HTTP/SSE) and `WindsurfMcpConfig` types
+
+### Research Insights (Phase 1a)
+
+**Windsurf docs confirm** three transport types: stdio (`command` + `args`), Streamable HTTP (`serverUrl`), and SSE (`serverUrl` or `url`). The `WindsurfMcpServerEntry` type must support all three — making `command` optional and adding `serverUrl` and `headers` fields.
+
+**TypeScript reviewer:** Consider making `WindsurfMcpServerEntry` a discriminated union if strict typing is desired. However, since this mirrors JSON config structure, a flat type with optional fields is pragmatically simpler.
+
+#### 1b. Add TargetScope to TargetHandler
+
+```typescript
+// src/targets/index.ts
+export type TargetScope = "global" | "workspace"
+
+export type TargetHandler<TBundle = unknown> = {
+  name: string
+  implemented: boolean
+  /**
+   * Default scope when --scope is not provided.
+   * Only meaningful when supportedScopes is defined.
+   * Falls back to "workspace" if absent.
+   */
+  defaultScope?: TargetScope
+  /** Valid scope values. If absent, the --scope flag is rejected for this target. */
+  supportedScopes?: TargetScope[]
+  convert: (plugin: ClaudePlugin, options: ClaudeToOpenCodeOptions) => TBundle | null
+  write: (outputRoot: string, bundle: TBundle) => Promise<void>
+}
+```
+
+- [x] Add `TargetScope` type export
+- [x] Add `defaultScope?` and `supportedScopes?` to `TargetHandler` with JSDoc
+- [x] Set windsurf target: `defaultScope: "global"`, `supportedScopes: ["global", "workspace"]`
+- [x] No changes to other targets (they have no scope fields, flag is ignored)
+
+### Research Insights (Phase 1b)
+
+**Simplicity review:** Argued this is premature generalization (only 1 of 8 targets uses scopes). Recommended handling scope as windsurf-specific with `if (targetName !== "windsurf")` guard instead. **Decision: keep generic approach** per brainstorm decision "Generic with windsurf as first adopter", but add JSDoc documenting the invariant.
+
+**TypeScript review:** Suggested a `ScopeConfig` grouped object to prevent `defaultScope` without `supportedScopes`. The JSDoc approach is simpler and sufficient for now.
+
+**Architecture review:** Adding optional fields to `TargetHandler` follows Open/Closed Principle — existing targets are unaffected. Clean extension.
+
+### Phase 2: Converter Changes
+
+**Files:** `src/converters/claude-to-windsurf.ts`
+
+#### 2a. Remove AGENTS.md generation
+
+- [x] Remove `buildAgentsMd()` function
+- [x] Remove `agentsMd` from return value
+
+#### 2b. Replace MCP setup doc with MCP config
+
+- [x] Remove `buildMcpSetupDoc()` function
+- [x] Remove `redactEnvValue()` helper
+- [x] Add `buildMcpConfig()` that returns `WindsurfMcpConfig | null`
+- [x] Include **all** env vars (including secrets) — no redaction
+- [x] Use shared `hasPotentialSecrets()` from `src/utils/secrets.ts`
+- [x] Include **both** stdio and HTTP/SSE servers (Windsurf supports all transport types)
+
+```typescript
+function buildMcpConfig(
+  servers?: Record<string, ClaudeMcpServer>,
+): WindsurfMcpConfig | null {
+  if (!servers || Object.keys(servers).length === 0) return null
+
+  const result: Record<string, WindsurfMcpServerEntry> = {}
+  for (const [name, server] of Object.entries(servers)) {
+    if (server.command) {
+      // stdio transport
+      const entry: WindsurfMcpServerEntry = { command: server.command }
+      if (server.args?.length) entry.args = server.args
+      if (server.env && Object.keys(server.env).length > 0) entry.env = server.env
+      result[name] = entry
+    } else if (server.url) {
+      // HTTP/SSE transport
+      const entry: WindsurfMcpServerEntry = { serverUrl: server.url }
+      if (server.headers && Object.keys(server.headers).length > 0) entry.headers = server.headers
+      if (server.env && Object.keys(server.env).length > 0) entry.env = server.env
+      result[name] = entry
+    } else {
+      console.warn(`Warning: MCP server "${name}" has no command or URL. Skipping.`)
+      continue
+    }
+  }
+
+  if (Object.keys(result).length === 0) return null
+
+  // Warn about secrets (don't redact — they're needed for the config to work)
+  if (hasPotentialSecrets(result)) {
+    console.warn(
+      "Warning: MCP servers contain env vars that may include secrets (API keys, tokens).\n" +
+      "   These will be written to mcp_config.json. Review before sharing the config file.",
+    )
+  }
+
+  return { mcpServers: result }
+}
+```
+
+### Research Insights (Phase 2)
+
+**Windsurf docs (critical correction):** Windsurf supports **stdio, Streamable HTTP, and SSE** transports in `mcp_config.json`. HTTP/SSE servers use `serverUrl` (not `url`). The original plan incorrectly planned to skip HTTP/SSE servers. This is now corrected — all transport types are included.
+
+**All 5 review agents flagged:** The original code sample was missing `result[name] = entry` — the entry was built but never stored. Fixed above.
+
+**Security review:** The warning message should enumerate which specific env var names triggered detection. Enhanced version:
+
+```typescript
+if (hasPotentialSecrets(result)) {
+  const flagged = Object.entries(result)
+    .filter(([, s]) => s.env && Object.keys(s.env).some(k => SENSITIVE_PATTERN.test(k)))
+    .map(([name]) => name)
+  console.warn(
+    `Warning: MCP servers contain env vars that may include secrets: ${flagged.join(", ")}.\n` +
+    "   These will be written to mcp_config.json. Review before sharing the config file.",
+  )
+}
+```
+
+**Windsurf env var interpolation:** Windsurf supports `${env:VARIABLE_NAME}` syntax in `mcp_config.json`. Future enhancement: write env var references instead of literal values for secrets. Out of scope for v0.11.0 (requires more research on which fields support interpolation).
+
+### Phase 3: Writer Changes
+
+**Files:** `src/targets/windsurf.ts`, `src/utils/files.ts`
+
+#### 3a. Simplify writer — remove AGENTS.md and double-nesting guard
+
+The writer always writes directly into `outputRoot`. The CLI resolves the correct output root based on scope.
+
+- [x] Remove AGENTS.md writing block (lines 10-17)
+- [x] Remove `resolveWindsurfPaths()` — no longer needed
+- [x] Write workflows, skills, and MCP config directly into `outputRoot`
+
+### Research Insights (Phase 3a)
+
+**Pattern review (dissent):** Every other writer (kiro, copilot, gemini, droid) has a `resolve*Paths()` function with a double-nesting guard. Removing it makes Windsurf the only target where the CLI fully owns nesting. This creates an inconsistency in the `write()` contract.
+
+**Resolution:** Accept the divergence — Windsurf has genuinely different semantics (global vs workspace). Add a JSDoc comment on `TargetHandler.write()` documenting that some writers may apply additional nesting while the Windsurf writer expects the final resolved path. Long-term, other targets could migrate to this pattern in a separate refactor.
+
+#### 3b. Replace MCP setup doc with JSON config merge
+
+Follow Kiro pattern (`src/targets/kiro.ts:68-92`) with security hardening:
+
+- [x] Read existing `mcp_config.json` if present
+- [x] Backup before overwrite (`backupFile()`)
+- [x] Parse existing JSON (warn and replace if corrupted; add `!Array.isArray()` guard)
+- [x] Merge at `mcpServers` key: plugin entries overwrite same-name entries, user entries preserved
+- [x] Preserve all other top-level keys in existing file
+- [x] Write merged result with **restrictive permissions** (`0o600`)
+- [x] Emit warning when writing to workspace scope (Windsurf `mcp_config.json` is global-only per docs)
+
+```typescript
+// MCP config merge with security hardening
+if (bundle.mcpConfig) {
+  const mcpPath = path.join(outputRoot, "mcp_config.json")
+  const backupPath = await backupFile(mcpPath)
+  if (backupPath) {
+    console.log(`Backed up existing mcp_config.json to ${backupPath}`)
+  }
+
+  let existingConfig: Record<string, unknown> = {}
+  if (await pathExists(mcpPath)) {
+    try {
+      const parsed = await readJson<unknown>(mcpPath)
+      if (parsed && typeof parsed === "object" && !Array.isArray(parsed)) {
+        existingConfig = parsed as Record<string, unknown>
+      }
+    } catch {
+      console.warn("Warning: existing mcp_config.json could not be parsed and will be replaced.")
+    }
+  }
+
+  const existingServers =
+    existingConfig.mcpServers &&
+    typeof existingConfig.mcpServers === "object" &&
+    !Array.isArray(existingConfig.mcpServers)
+      ? (existingConfig.mcpServers as Record<string, unknown>)
+      : {}
+  const merged = { ...existingConfig, mcpServers: { ...existingServers, ...bundle.mcpConfig.mcpServers } }
+  await writeJsonSecure(mcpPath, merged)  // 0o600 permissions
+}
+```
+
+### Research Insights (Phase 3b)
+
+**Security review (HIGH):** The current `writeJson()` in `src/utils/files.ts` uses default umask (`0o644`) — world-readable. The sync targets all use `{ mode: 0o600 }` for secret-containing files. The Windsurf writer (and Kiro writer) must do the same.
+
+**Implementation:** Add a `writeJsonSecure()` helper or add a `mode` parameter to `writeJson()`:
+
+```typescript
+// src/utils/files.ts
+export async function writeJsonSecure(filePath: string, data: unknown): Promise<void> {
+  const content = JSON.stringify(data, null, 2)
+  await ensureDir(path.dirname(filePath))
+  await fs.writeFile(filePath, content + "\n", { encoding: "utf8", mode: 0o600 })
+}
+```
+
+**Security review (MEDIUM):** Backup files inherit default permissions. Ensure `backupFile()` also sets `0o600` on the backup copy when the source may contain secrets.
+
+**Security review (MEDIUM):** Workspace `mcp_config.json` could be committed to git. After writing to workspace scope, emit a warning:
+
+```
+Warning: .windsurf/mcp_config.json may contain secrets. Ensure it is in .gitignore.
+```
+
+**TypeScript review:** The `readJson<Record<string, unknown>>` assertion is unsafe — a valid JSON array or string passes parsing but fails the type. Added `!Array.isArray()` guard.
+
+**TypeScript review:** The `bundle.mcpConfig` null check is sufficient — when non-null, `mcpServers` is guaranteed to have entries (the converter returns null for empty servers). Simplified from `bundle.mcpConfig && Object.keys(...)`.
+
+**Windsurf docs (important):** `mcp_config.json` is a **global configuration only** — Windsurf has no per-project MCP config support. Writing it to `.windsurf/` in workspace scope may not be discovered by Windsurf. Emit a warning for workspace scope but still write the file for forward-compatibility.
+
+#### 3c. Updated writer structure
+
+```typescript
+export async function writeWindsurfBundle(outputRoot: string, bundle: WindsurfBundle): Promise<void> {
+  await ensureDir(outputRoot)
+
+  // Write agent workflows
+  if (bundle.agentWorkflows.length > 0) {
+    const agentDir = path.join(outputRoot, "workflows", "agents")
+    await ensureDir(agentDir)
+    for (const workflow of bundle.agentWorkflows) {
+      validatePathSafe(workflow.name, "agent workflow")
+      const content = formatFrontmatter({ description: workflow.description }, `# ${workflow.name}\n\n${workflow.body}`)
+      await writeText(path.join(agentDir, `${workflow.name}.md`), content + "\n")
+    }
+  }
+
+  // Write command workflows
+  if (bundle.commandWorkflows.length > 0) {
+    const cmdDir = path.join(outputRoot, "workflows", "commands")
+    await ensureDir(cmdDir)
+    for (const workflow of bundle.commandWorkflows) {
+      validatePathSafe(workflow.name, "command workflow")
+      const content = formatFrontmatter({ description: workflow.description }, `# ${workflow.name}\n\n${workflow.body}`)
+      await writeText(path.join(cmdDir, `${workflow.name}.md`), content + "\n")
+    }
+  }
+
+  // Copy skill directories
+  if (bundle.skillDirs.length > 0) {
+    const skillsDir = path.join(outputRoot, "skills")
+    await ensureDir(skillsDir)
+    for (const skill of bundle.skillDirs) {
+      validatePathSafe(skill.name, "skill directory")
+      const destDir = path.join(skillsDir, skill.name)
+      const resolvedDest = path.resolve(destDir)
+      if (!resolvedDest.startsWith(path.resolve(skillsDir))) {
+        console.warn(`Warning: Skill name "${skill.name}" escapes skills/. Skipping.`)
+        continue
+      }
+      await copyDir(skill.sourceDir, destDir)
+    }
+  }
+
+  // Merge MCP config (see 3b above)
+  if (bundle.mcpConfig) {
+    // ... merge logic from 3b
+  }
+}
+```
+
+### Phase 4: CLI Wiring
+
+**Files:** `src/commands/install.ts`, `src/commands/convert.ts`
+
+#### 4a. Add `--scope` flag to both commands
+
+```typescript
+scope: {
+  type: "string",
+  description: "Scope level: global | workspace (default varies by target)",
+},
+```
+
+- [x] Add `scope` arg to `install.ts`
+- [x] Add `scope` arg to `convert.ts`
+
+#### 4b. Validate scope with type guard
+
+Use a proper type guard instead of unsafe `as TargetScope` cast:
+
+```typescript
+function isTargetScope(value: string): value is TargetScope {
+  return value === "global" || value === "workspace"
+}
+
+const scopeValue = args.scope ? String(args.scope) : undefined
+if (scopeValue !== undefined) {
+  if (!target.supportedScopes) {
+    throw new Error(`Target "${targetName}" does not support the --scope flag.`)
+  }
+  if (!isTargetScope(scopeValue) || !target.supportedScopes.includes(scopeValue)) {
+    throw new Error(`Target "${targetName}" does not support --scope ${scopeValue}. Supported: ${target.supportedScopes.join(", ")}`)
+  }
+}
+const resolvedScope = scopeValue ?? target.defaultScope ?? "workspace"
+```
+
+- [x] Add `isTargetScope` type guard
+- [x] Add scope validation in both commands (single block, not two separate checks)
+
+### Research Insights (Phase 4b)
+
+**TypeScript review:** The original plan cast `scopeValue as TargetScope` before validation — a type lie. Use a proper type guard function to keep the type system honest.
+
+**Simplicity review:** The two-step validation (check supported, then check exists) can be a single block with the type guard approach above.
+
+#### 4c. Update output root resolution
+
+Both commands now use the shared `resolveTargetOutputRoot` from Phase 0a.
+
+- [x] Call shared function with `scope: resolvedScope` for primary target
+- [x] Default scope: `target.defaultScope ?? "workspace"` (only used when target supports scopes)
+
+#### 4d. Handle `--also` targets
+
+`--scope` applies only to the primary `--to` target. Extra `--also` targets use their own `defaultScope`.
+
+- [x] Pass `handler.defaultScope` for `--also` targets (each uses its own default)
+- [x] Update the `--also` loop in both commands to use target-specific scope resolution
+
+### Research Insights (Phase 4d)
+
+**Architecture review:** There is no way for users to specify scope for an `--also` target (e.g., `--also windsurf:workspace`). Accept as a known v0.11.0 limitation. If users need workspace scope for windsurf, they can run two separate commands. Add a code comment indicating where per-target scope overrides would be added in the future.
+
+### Phase 5: Tests
+
+**Files:** `tests/windsurf-converter.test.ts`, `tests/windsurf-writer.test.ts`
+
+#### 5a. Update converter tests
+
+- [x] Remove all AGENTS.md tests (lines 275-303: empty plugin, CLAUDE.md missing)
+- [x] Remove all `mcpSetupDoc` tests (lines 305-366: stdio, HTTP/SSE, redaction, null)
+- [x] Update `fixturePlugin` default — remove `agentsMd` and `mcpSetupDoc` references
+- [x] Add `mcpConfig` tests:
+  - stdio server produces correct JSON structure with `command`, `args`, `env`
+  - HTTP/SSE server produces correct JSON structure with `serverUrl`, `headers`
+  - mixed servers (stdio + HTTP) both included
+  - env vars included (not redacted) — verify actual values present
+  - `hasPotentialSecrets()` emits console.warn for sensitive keys
+  - `hasPotentialSecrets()` does NOT warn when no sensitive keys
+  - no servers produces null mcpConfig
+  - empty bundle has null mcpConfig
+  - server with no command and no URL is skipped with warning
+
+#### 5b. Update writer tests
+
+- [x] Remove AGENTS.md tests (backup test, creation test, double-nesting AGENTS.md parent test)
+- [x] Remove double-nesting guard test (guard removed)
+- [x] Remove `mcp-setup.md` write test
+- [x] Update `emptyBundle` fixture — remove `agentsMd`, `mcpSetupDoc`, add `mcpConfig: null`
+- [x] Add `mcp_config.json` tests:
+  - writes mcp_config.json to outputRoot
+  - merges with existing mcp_config.json (preserves user servers)
+  - backs up existing mcp_config.json before overwrite
+  - handles corrupted existing mcp_config.json (warn and replace)
+  - handles existing mcp_config.json with array (not object) at root
+  - handles existing mcp_config.json with `mcpServers: null`
+  - preserves non-mcpServers keys in existing file
+  - server name collision: plugin entry wins
+  - file permissions are 0o600 (not world-readable)
+- [x] Update full bundle test — writer writes directly into outputRoot (no `.windsurf/` nesting)
+
+#### 5c. Add scope resolution tests
+
+Test the shared `resolveTargetOutputRoot` function:
+
+- [x] Default scope for windsurf is "global" → resolves to `~/.codeium/windsurf/`
+- [x] Explicit `--scope workspace` → resolves to `cwd/.windsurf/`
+- [x] `--output` overrides scope resolution (both global and workspace)
+- [x] Invalid scope value for windsurf → error
+- [x] `--scope` on non-scope target (e.g., opencode) → error
+- [x] `--also windsurf` uses windsurf's default scope ("global")
+- [x] `isTargetScope` type guard correctly identifies valid/invalid values
+
+### Phase 6: Documentation
+
+**Files:** `README.md`, `CHANGELOG.md`
+
+- [x] Update README.md Windsurf section to mention `--scope` flag and global default
+- [x] Add CHANGELOG entry for v0.11.0 with breaking changes documented
+- [x] Document migration path: `--scope workspace` for old behavior
+- [x] Note that Windsurf `mcp_config.json` is global-only (workspace MCP config may not be discovered)
+
+## Acceptance Criteria
+
+- [x] `install compound-engineering --to windsurf` writes to `~/.codeium/windsurf/` by default
+- [x] `install compound-engineering --to windsurf --scope workspace` writes to `cwd/.windsurf/`
+- [x] `--output /custom/path` overrides scope for both commands
+- [x] `--scope` on non-supporting target produces clear error
+- [x] `mcp_config.json` merges with existing file (backup created, user entries preserved)
+- [x] `mcp_config.json` written with `0o600` permissions (not world-readable)
+- [x] No AGENTS.md generated for either scope
+- [x] Env var secrets included in `mcp_config.json` with `console.warn` listing affected servers
+- [x] Both stdio and HTTP/SSE MCP servers included in `mcp_config.json`
+- [x] All existing tests updated, all new tests pass
+- [x] No regressions in other targets
+- [x] `resolveTargetOutputRoot` extracted to shared utility (no duplication)
+
+## Dependencies & Risks
+
+**Risk: Global workflow path is undocumented.** Windsurf may not discover workflows from `~/.codeium/windsurf/workflows/`. Mitigation: documented as a known assumption in the brainstorm. Users can `--scope workspace` if global workflows aren't discovered.
+
+**Risk: Breaking changes for existing v0.10.0 users.** Mitigation: document migration path clearly. `--scope workspace` restores previous behavior. Target is experimental with a small user base.
+
+**Risk: Workspace `mcp_config.json` not read by Windsurf.** Per Windsurf docs, `mcp_config.json` is global-only configuration. Workspace scope writes the file for forward-compatibility but emits a warning. The primary use case is global scope anyway.
+
+**Risk: Secrets in `mcp_config.json` committed to git.** Mitigation: `0o600` file permissions, console.warn about sensitive env vars, warning about `.gitignore` for workspace scope.
+
+## References & Research
+
+- Spec: `docs/specs/windsurf.md` (authoritative reference for component mapping)
+- Kiro MCP merge pattern: [src/targets/kiro.ts:68-92](../../src/targets/kiro.ts)
+- Sync secrets warning: [src/commands/sync.ts:20-28](../../src/commands/sync.ts)
+- Windsurf MCP docs: https://docs.windsurf.com/windsurf/cascade/mcp
+- Windsurf Skills global path: https://docs.windsurf.com/windsurf/cascade/skills
+- Windsurf MCP tutorial: https://windsurf.com/university/tutorials/configuring-first-mcp-server
+- Adding converter targets (learning): [docs/solutions/adding-converter-target-providers.md](../solutions/adding-converter-target-providers.md)
+- Plugin versioning (learning): [docs/solutions/plugin-versioning-requirements.md](../solutions/plugin-versioning-requirements.md)
--- a/docs/plans/2026-03-01-feat-ce-command-aliases-backwards-compatible-deprecation-plan.md
+++ b/docs/plans/2026-03-01-feat-ce-command-aliases-backwards-compatible-deprecation-plan.md
@@ -0,0 +1,261 @@
+---
+title: "feat: Add ce:* command aliases with backwards-compatible deprecation of workflows:*"
+type: feat
+status: active
+date: 2026-03-01
+---
+
+# feat: Add `ce:*` Command Aliases with Backwards-Compatible Deprecation of `workflows:*`
+
+## Overview
+
+Rename the five `workflows:*` commands to `ce:*` to make it clearer they belong to compound-engineering. Keep `workflows:*` working as thin deprecation wrappers that warn users and forward to the new commands.
+
+## Problem Statement / Motivation
+
+The current `workflows:plan`, `workflows:work`, `workflows:review`, `workflows:brainstorm`, and `workflows:compound` commands are prefixed with `workflows:` — a generic namespace that doesn't signal their origin. Users don't immediately associate them with the compound-engineering plugin.
+
+The `ce:` prefix is shorter, more memorable, and unambiguously identifies these as compound-engineering commands — consistent with how other plugin commands already use `compound-engineering:` as a namespace.
+
+## Proposed Solution
+
+### 1. Create New `ce:*` Commands (Primary)
+
+Create a `commands/ce/` directory with five new command files. Each file gets the full implementation content from the current `workflows:*` counterpart, with the `name:` frontmatter updated to the new name.
+
+| New Command | Source Content |
+|-------------|---------------|
+| `ce:plan` | `commands/workflows/plan.md` |
+| `ce:work` | `commands/workflows/work.md` |
+| `ce:review` | `commands/workflows/review.md` |
+| `ce:brainstorm` | `commands/workflows/brainstorm.md` |
+| `ce:compound` | `commands/workflows/compound.md` |
+
+### 2. Convert `workflows:*` to Deprecation Wrappers (Backwards Compatibility)
+
+Replace the full content of each `workflows:*` command with a thin wrapper that:
+1. Displays a visible deprecation warning to the user
+2. Invokes the new `ce:*` command with the same `$ARGUMENTS`
+
+Example wrapper body:
+
+```markdown
+---
+name: workflows:plan
+description: "[DEPRECATED] Use /ce:plan instead. Renamed for clarity."
+argument-hint: "[feature description]"
+---
+
+> ⚠️ **Deprecated:** `/workflows:plan` has been renamed to `/ce:plan`.
+> Please update your workflow to use `/ce:plan` instead.
+> This alias will be removed in a future version.
+
+/ce:plan $ARGUMENTS
+```
+
+### 3. Update All Internal References
+
+The grep reveals `workflows:*` is referenced in **many more places** than just `lfg`/`slfg`. All of these must be updated to point to the new `ce:*` names:
+
+**Orchestration commands (update to new names):**
+- `commands/lfg.md` — `/workflows:plan`, `/workflows:work`, `/workflows:review`
+- `commands/slfg.md` — `/workflows:plan`, `/workflows:work`, `/workflows:review`
+
+**Command bodies that cross-reference (update to new names):**
+- `commands/workflows/brainstorm.md` — references `/workflows:plan` multiple times (will be in the deprecated wrapper, so should forward to `/ce:plan`)
+- `commands/workflows/compound.md` — self-references and references `/workflows:plan`
+- `commands/workflows/plan.md` — references `/workflows:work` multiple times
+- `commands/deepen-plan.md` — references `/workflows:work`, `/workflows:compound`
+
+**Agents (update to new names):**
+- `agents/review/code-simplicity-reviewer.md` — references `/workflows:plan` and `/workflows:work`
+- `agents/research/git-history-analyzer.md` — references `/workflows:plan`
+- `agents/research/learnings-researcher.md` — references `/workflows:plan`
+
+**Skills (update to new names):**
+- `skills/document-review/SKILL.md` — references `/workflows:brainstorm`, `/workflows:plan`
+- `skills/git-worktree/SKILL.md` — references `/workflows:review`, `/workflows:work` extensively
+- `skills/setup/SKILL.md` — references `/workflows:review`, `/workflows:work`
+- `skills/brainstorming/SKILL.md` — references `/workflows:plan` multiple times
+- `skills/file-todos/SKILL.md` — references `/workflows:review`
+
+**Other commands (update to new names):**
+- `commands/test-xcode.md` — references `/workflows:review`
+
+**Historical docs (leave as-is — they document the old names intentionally):**
+- `docs/plans/*.md` — old plan files, historical record
+- `docs/brainstorms/*.md` — historical
+- `docs/solutions/*.md` — historical
+- `tests/fixtures/` — test fixtures for the converter (intentionally use `workflows:*` to test namespace handling)
+- `CHANGELOG.md` historical entries — don't rewrite history
+
+### 4. Update Documentation
+
+- `CHANGELOG.md` — add new entry documenting the rename and deprecation
+- `plugins/compound-engineering/README.md` — update command table to list `ce:*` as primary, note `workflows:*` as deprecated aliases
+- `plugins/compound-engineering/CLAUDE.md` — update command listing and the "Why `workflows:`?" section
+- Root `README.md` — update the command table (lines 133–136)
+
+### 5. Converter / bunx Install Script Considerations
+
+The `bunx` install script (`src/commands/install.ts`) **only writes files, never deletes them**. This has two implications:
+
+**Now (while deprecated wrappers exist):** No stale file problem. Running `bunx install compound-engineering --to gemini` after this change will:
+- Write `commands/ce/plan.toml` (new primary)
+- Write `commands/workflows/plan.toml` (deprecated wrapper, with deprecation content)
+
+Both coexist correctly. Users who re-run install get both.
+
+**Future (when deprecated wrappers are eventually removed):** The old `commands/workflows/` files will remain stale in users' converted targets. At that point, a cleanup step will be needed — either:
+- Manual instructions: "Delete `.gemini/commands/workflows/` after upgrading"
+- OR add a cleanup pass to the install script that removes known-renamed command directories
+
+For now, document in the plan that stale cleanup is a known future concern when `workflows:*` wrappers are eventually dropped.
+
+## Technical Considerations
+
+### Command Naming
+
+The `ce:` prefix maps to a `commands/ce/` directory. This follows the existing convention where `workflows:plan` maps to `commands/workflows/plan.md`.
+
+### Deprecation Warning Display
+
+Since commands are executed by Claude, the deprecation message in the wrapper body will be displayed to the user as Claude's response before the new command runs. The `>` blockquote markdown renders as a styled callout.
+
+The deprecated wrappers should **not** use `disable-model-invocation: true` — Claude needs to process the body to display the warning and invoke the new command.
+
+### Deprecation Wrapper Mechanism
+
+The deprecated wrappers **must** use `disable-model-invocation: true`. This is the same mechanism `lfg.md` uses — the CLI runtime parses the body and executes slash command invocations directly. Without it, Claude reads the body as text and cannot actually invoke `/ce:plan`.
+
+The deprecation notice in the wrapper body becomes a printed note (same as `lfg` step descriptions), not a styled Claude response. That's acceptable — it still communicates the message.
+
+### Context Token Budget
+
+The 5 new `ce:*` commands add descriptions to the context budget. Keep descriptions short (under 120 chars). The 5 deprecated `workflows:*` wrappers have minimal descriptions (tagged as deprecated) to minimize budget impact.
+
+### Count Impact
+
+Command count remains 22 (5 new `ce:*` + 5 updated `workflows:*` wrappers = net zero change). No version bump required for counts.
+
+## Acceptance Criteria
+
+- [ ] `commands/ce/` directory created with 5 new command files
+- [ ] Each `ce:*` command has the full implementation from its `workflows:*` counterpart
+- [ ] Each `ce:*` command frontmatter `name:` field set to `ce:plan`, `ce:work`, etc.
+- [ ] Each `workflows:*` command replaced with a thin deprecation wrapper
+- [ ] Deprecation wrapper shows a clear ⚠️ warning with the new command name
+- [ ] Deprecation wrapper invokes the new `ce:*` command with `$ARGUMENTS`
+- [ ] `lfg.md` updated to use `ce:plan`, `ce:work`, `ce:review`
+- [ ] `slfg.md` updated to use `ce:plan`, `ce:work`, `ce:review`
+- [ ] All agent `.md` files updated (code-simplicity-reviewer, git-history-analyzer, learnings-researcher)
+- [ ] All skill `SKILL.md` files updated (document-review, git-worktree, setup, brainstorming, file-todos)
+- [ ] `commands/deepen-plan.md` and `commands/test-xcode.md` updated
+- [ ] `CHANGELOG.md` updated with deprecation notice
+- [ ] `plugins/compound-engineering/README.md` command table updated
+- [ ] `plugins/compound-engineering/CLAUDE.md` command listing updated
+- [ ] Root `README.md` command table updated
+- [ ] Validate: `/ce:plan "test feature"` works end-to-end
+- [ ] Validate: `/workflows:plan "test feature"` shows deprecation warning and continues
+- [ ] Re-run `bunx install compound-engineering --to [target]` and confirm both `ce/` and `workflows/` output dirs are written correctly
+
+## Implementation Steps
+
+### Step 1: Create `commands/ce/` directory with 5 new files
+
+For each command, copy the source file and update only the `name:` frontmatter field:
+
+- `commands/ce/plan.md` — copy `commands/workflows/plan.md`, set `name: ce:plan`
+- `commands/ce/work.md` — copy `commands/workflows/work.md`, set `name: ce:work`
+- `commands/ce/review.md` — copy `commands/workflows/review.md`, set `name: ce:review`
+- `commands/ce/brainstorm.md` — copy `commands/workflows/brainstorm.md`, set `name: ce:brainstorm`
+- `commands/ce/compound.md` — copy `commands/workflows/compound.md`, set `name: ce:compound`
+
+### Step 2: Replace `commands/workflows/*.md` with deprecation wrappers
+
+Use `disable-model-invocation: true` so the CLI runtime directly invokes `/ce:<command>`. The deprecation note is printed as a step description.
+
+Template for each wrapper:
+
+```markdown
+---
+name: workflows:<command>
+description: "[DEPRECATED] Use /ce:<command> instead — renamed for clarity."
+argument-hint: "[...]"
+disable-model-invocation: true
+---
+
+NOTE: /workflows:<command> is deprecated. Please use /ce:<command> instead. This alias will be removed in a future version.
+
+/ce:<command> $ARGUMENTS
+```
+
+### Step 3: Update all internal references
+
+**Orchestration commands:**
+- `commands/lfg.md` — replace `/workflows:plan`, `/workflows:work`, `/workflows:review`
+- `commands/slfg.md` — same
+
+**Command bodies:**
+- `commands/deepen-plan.md` — replace `/workflows:work`, `/workflows:compound`
+- `commands/test-xcode.md` — replace `/workflows:review`
+- The deprecated `workflows/brainstorm.md`, `workflows/compound.md`, `workflows/plan.md` wrappers — references in their body text pointing to other `workflows:*` commands should also be updated to `ce:*` (since users reading them should see the new names)
+
+**Agents:**
+- `agents/review/code-simplicity-reviewer.md`
+- `agents/research/git-history-analyzer.md`
+- `agents/research/learnings-researcher.md`
+
+**Skills:**
+- `skills/document-review/SKILL.md`
+- `skills/git-worktree/SKILL.md`
+- `skills/setup/SKILL.md`
+- `skills/brainstorming/SKILL.md`
+- `skills/file-todos/SKILL.md`
+
+### Step 4: Update documentation
+
+**`plugins/compound-engineering/CHANGELOG.md`** — Add under new version section:
+```
+### Changed
+- `workflows:plan`, `workflows:work`, `workflows:review`, `workflows:brainstorm`, `workflows:compound` renamed to `ce:plan`, `ce:work`, `ce:review`, `ce:brainstorm`, `ce:compound` for clarity
+
+### Deprecated
+- `workflows:*` commands — use `ce:*` equivalents instead. Aliases remain functional and will be removed in a future version.
+```
+
+**`plugins/compound-engineering/README.md`** — Update the commands table to list `ce:*` as primary, show `workflows:*` as deprecated aliases.
+
+**`plugins/compound-engineering/CLAUDE.md`** — Update command listing and the "Why `workflows:`?" section to reflect new `ce:` namespace.
+
+**Root `README.md`** — Update the commands table (lines 133–136).
+
+### Step 5: Verify converter output
+
+After updating, re-run the bunx install script to confirm both targets are written:
+
+```bash
+bunx @every-env/compound-plugin install compound-engineering --to gemini --output /tmp/test-output
+ls /tmp/test-output/.gemini/commands/
+# Should show both: ce/ and workflows/
+```
+
+The `workflows/` output will contain the deprecation wrapper content. The `ce/` output will have the full implementation.
+
+**Future cleanup note:** When `workflows:*` wrappers are eventually removed, users must manually delete the stale `workflows/` directories from their converted targets (`.gemini/commands/workflows/`, `.codex/commands/workflows/`, etc.). Consider adding a migration note to the CHANGELOG at that time.
+
+### Step 6: Run `/release-docs` to update the docs site
+
+## Dependencies & Risks
+
+- **Risk:** Users with saved references to `workflows:*` commands in their CLAUDE.md files or scripts. **Mitigation:** The deprecation wrappers remain functional indefinitely.
+- **Risk:** Context token budget slightly increases (5 new command descriptions). **Mitigation:** Keep all descriptions short. Deprecated wrappers get minimal descriptions.
+- **Risk:** `lfg`/`slfg` orchestration breaks if update is partial. **Mitigation:** Update both in the same commit.
+
+## Sources & References
+
+- Existing commands: `plugins/compound-engineering/commands/workflows/*.md`
+- Orchestration commands: `plugins/compound-engineering/commands/lfg.md`, `plugins/compound-engineering/commands/slfg.md`
+- Plugin metadata: `plugins/compound-engineering/.claude-plugin/plugin.json`
+- Changelog: `plugins/compound-engineering/CHANGELOG.md`
+- README: `plugins/compound-engineering/README.md`
--- a/docs/plans/2026-03-01-fix-setup-skill-non-claude-llm-fallback-plan.md
+++ b/docs/plans/2026-03-01-fix-setup-skill-non-claude-llm-fallback-plan.md
@@ -0,0 +1,140 @@
+---
+title: "fix: Setup skill fails silently on non-Claude LLMs due to AskUserQuestion dependency"
+type: fix
+status: active
+date: 2026-03-01
+---
+
+## Enhancement Summary
+
+**Deepened on:** 2026-03-01
+**Research agents used:** best-practices-researcher, architecture-strategist, code-simplicity-reviewer, scope-explorer
+
+### Key Improvements
+1. Simplified preamble from 16 lines to 4 lines — drop platform name list and example blockquote (YAGNI)
+2. Expanded scope: `create-new-skill.md` also has `AskUserQuestion` and needs the same fix
+3. Clarified that `codex-agents.ts` change helps command/agent contexts only — does NOT reach skill execution (skills aren't converter-transformed)
+4. Added CLAUDE.md skill compliance policy as a third deliverable to prevent recurrence
+5. Separated two distinct failure modes: tool-not-found error vs silent auto-configuration
+
+### New Considerations Discovered
+- Only Pi converter transforms `AskUserQuestion` (incompletely); all others pass skill content through verbatim — the codex-agents.ts fix is independent of skill execution
+- `add-workflow.md` and `audit-skill.md` already explicitly prohibit `AskUserQuestion` — this undocumented policy should be formalized
+- Prose fallback is probabilistic (LLM compliance); converter-level transformation is the correct long-term architectural fix
+- The brainstorming skill avoids `AskUserQuestion` entirely and works cross-platform — that's the gold standard pattern
+
+---
+
+# fix: Setup Skill Cross-Platform Fallback for AskUserQuestion
+
+## Overview
+
+The `setup` skill uses `AskUserQuestion` at 5 decision points. On non-Claude platforms (Codex, Gemini, OpenCode, Copilot, Kiro, etc.), this tool doesn't exist — the LLM reads the skill body but cannot call the tool, causing silent failure or unconsented auto-configuration. Fix by adding a minimal fallback instruction to the skill body, applying the same to `create-new-skill.md`, and adding a policy to the CLAUDE.md skill checklist to prevent recurrence.
+
+## Problem Statement
+
+**Two distinct failure modes:**
+
+1. **Tool-not-found error** — LLM tries to call `AskUserQuestion` as a function; platform returns an error. Setup halts.
+2. **Silent skip** — LLM reads `AskUserQuestion` as prose, ignores the decision gate, auto-configures. User never consulted. This is worse — produces a `compound-engineering.local.md` the user never approved.
+
+`plugins/compound-engineering/skills/setup/SKILL.md` has 5 `AskUserQuestion` blocks:
+
+| Line | Decision Point |
+|------|----------------|
+| 13 | Check existing config: Reconfigure / View / Cancel |
+| 44 | Stack detection: Auto-configure / Customize |
+| 67 | Stack override (multi-option) |
+| 85 | Focus areas (multiSelect) |
+| 104 | Review depth: Thorough / Fast / Comprehensive |
+
+`plugins/compound-engineering/skills/create-agent-skills/workflows/create-new-skill.md` lines 22 and 45 also use `AskUserQuestion`.
+
+Only the Pi converter transforms the reference (incompletely). All other converters (Codex, Gemini, Copilot, Kiro, Droid, Windsurf) pass skill content through verbatim — **skills are not converter-transformed**.
+
+## Proposed Solution
+
+Three deliverables, each addressing a different layer:
+
+### 1. Add 4-line "Interaction Method" preamble to `setup/SKILL.md`
+
+Immediately after the `# Compound Engineering Setup` heading, insert:
+
+```markdown
+## Interaction Method
+
+If `AskUserQuestion` is available, use it for all prompts below.
+
+If not, present each question as a numbered list and wait for a reply before proceeding to the next step. For multiSelect questions, accept comma-separated numbers (e.g. `1, 3`). Never skip or auto-configure.
+```
+
+**Why 4 lines, not 16:** LLMs know what a numbered list is — no example blockquote needed. The branching condition is tool availability, not platform identity — no platform name list needed (YAGNI: new platforms will be added and lists go stale). State the "never skip" rule once here; don't repeat it in `codex-agents.ts`.
+
+**Why this works:** The skill body IS read by the LLM on all platforms when `/setup` is invoked. The agent follows prose instructions regardless of tool availability. This is the same pattern `brainstorming/SKILL.md` uses — it avoids `AskUserQuestion` entirely and uses inline numbered lists — the gold standard cross-platform approach.
+
+### 2. Apply the same preamble to `create-new-skill.md`
+
+`plugins/compound-engineering/skills/create-agent-skills/workflows/create-new-skill.md` uses `AskUserQuestion` at lines 22 and 45. Apply an identical preamble at the top of that file.
+
+### 3. Strengthen `codex-agents.ts` AskUserQuestion mapping
+
+This change does NOT fix skill execution (skills bypass the converter pipeline). It improves the AGENTS.md guidance for Codex command/agent contexts.
+
+Replace (`src/utils/codex-agents.ts` line 21):
+```
+- AskUserQuestion/Question: ask the user in chat
+```
+
+With:
+```
+- AskUserQuestion/Question: present choices as a numbered list in chat and wait for a reply number. For multi-select (multiSelect: true), accept comma-separated numbers. Never skip or auto-configure — always wait for the user's response before proceeding.
+```
+
+### 4. Add lint rule to CLAUDE.md skill compliance checklist
+
+Add to the "Skill Compliance Checklist" in `plugins/compound-engineering/CLAUDE.md`:
+
+```
+### AskUserQuestion Usage
+
+- [ ] If the skill uses `AskUserQuestion`, it must include an "Interaction Method" preamble explaining the numbered-list fallback for non-Claude environments
+- [ ] Prefer avoiding `AskUserQuestion` entirely (see brainstorming/SKILL.md pattern) for skills intended to run cross-platform
+```
+
+## Technical Considerations
+
+- `setup/SKILL.md` has `disable-model-invocation: true` — this controls session-startup context loading only, not skill-body execution at invocation time
+- The prose fallback is probabilistic (LLM compliance), not a build-time guarantee. The correct long-term architectural fix is converter-level transformation of skill content (a `transformSkillContent()` pass in each converter), but that is out of scope here
+- Commands with `AskUserQuestion` (`ce/brainstorm.md`, `ce/plan.md`, `test-browser.md`, etc.) have the same gap but are out of scope — explicitly noted as a future task
+
+## Acceptance Criteria
+
+- [ ] `setup/SKILL.md` has a 4-line "Interaction Method" preamble after the opening heading
+- [ ] `create-new-skill.md` has the same preamble
+- [ ] The skills still use `AskUserQuestion` as primary — no change to Claude Code behavior
+- [ ] `codex-agents.ts` AskUserQuestion line updated with structured guidance
+- [ ] `plugins/compound-engineering/CLAUDE.md` skill checklist includes AskUserQuestion policy
+- [ ] No regression: on Claude Code, setup works exactly as before
+
+## Files
+
+- `plugins/compound-engineering/skills/setup/SKILL.md` — Add 4-line preamble after line 8
+- `plugins/compound-engineering/skills/create-agent-skills/workflows/create-new-skill.md` — Add same preamble at top
+- `src/utils/codex-agents.ts` — Strengthen AskUserQuestion mapping (line 21)
+- `plugins/compound-engineering/CLAUDE.md` — Add AskUserQuestion policy to skill compliance checklist
+
+## Future Work (Out of Scope)
+
+- Converter-level `transformSkillContent()` for all targets — build-time guarantee instead of prose fallback
+- Commands with `AskUserQuestion` (`ce/brainstorm.md`, `ce/plan.md`, `test-browser.md`) — same failure mode, separate fix
+
+## Sources & References
+
+- Issue: [#204](https://github.com/EveryInc/compound-engineering-plugin/issues/204)
+- `plugins/compound-engineering/skills/setup/SKILL.md:13,44,67,85,104`
+- `plugins/compound-engineering/skills/create-agent-skills/workflows/create-new-skill.md:22,45`
+- `src/utils/codex-agents.ts:21`
+- `src/converters/claude-to-pi.ts:106` — Pi converter (reference pattern)
+- `plugins/compound-engineering/skills/brainstorming/SKILL.md` — gold standard cross-platform skill (no AskUserQuestion)
+- `plugins/compound-engineering/skills/create-agent-skills/workflows/add-workflow.md:12,37` — existing "DO NOT use AskUserQuestion" policy
+- `docs/solutions/adding-converter-target-providers.md`
--- a/docs/plans/2026-03-03-feat-sync-claude-mcp-all-supported-providers-plan.md
+++ b/docs/plans/2026-03-03-feat-sync-claude-mcp-all-supported-providers-plan.md
@@ -0,0 +1,639 @@
+---
+title: "feat: Sync Claude MCP servers to all supported providers"
+type: feat
+date: 2026-03-03
+status: completed
+deepened: 2026-03-03
+---
+
+# feat: Sync Claude MCP servers to all supported providers
+
+## Overview
+
+Expand the `sync` command so a user's local Claude Code MCP configuration can be propagated to every provider this CLI can reasonably support, instead of only the current partial set.
+
+Today, `sync` already symlinks Claude skills and syncs MCP servers for a subset of targets. The gap is that install/convert support has grown much faster than sync support, so the product promise in `README.md` has drifted away from what `src/commands/sync.ts` can actually do.
+
+This feature should close that parity gap without changing the core sync contract:
+
+- Claude remains the source of truth for personal skills and MCP servers.
+- Skills stay symlinked, not copied.
+- Existing user config in the destination tool is preserved where possible.
+- Target-specific MCP formats stay target-specific.
+
+## Problem Statement
+
+The current implementation has three concrete problems:
+
+1. `sync` only knows about `opencode`, `codex`, `pi`, `droid`, `copilot`, and `gemini`, while install/convert now supports `kiro`, `windsurf`, `openclaw`, and `qwen` too.
+2. `sync --target all` relies on stale detection metadata that still includes `cursor`, but misses newer supported tools.
+3. Existing MCP sync support is incomplete even for some already-supported targets:
+   - `codex` only emits stdio servers and silently drops remote MCP servers.
+   - `droid` is still skills-only even though Factory now documents `mcp.json`.
+
+User impact:
+
+- A user can install the plugin to more providers than they can sync their personal Claude setup to.
+- `sync --target all` does not mean "all supported tools" anymore.
+- Users with remote MCP servers in Claude get partial results depending on target.
+
+## Research Summary
+
+### No Relevant Brainstorm
+
+I checked recent brainstorms in `docs/brainstorms/` and found no relevant document for this feature within the last 14 days.
+
+### Internal Findings
+
+- `src/commands/sync.ts:15-125` hardcodes the sync target list, output roots, and per-target dispatch. It omits `windsurf`, `kiro`, `openclaw`, and `qwen`.
+- `src/utils/detect-tools.ts:15-22` still detects `cursor`, but not `windsurf`, `kiro`, `openclaw`, or `qwen`.
+- `src/parsers/claude-home.ts:11-19` already gives sync exactly the right inputs: personal skills plus `settings.json` `mcpServers`.
+- `src/sync/codex.ts:25-91` only serializes stdio MCP servers, even though Codex supports remote MCP config.
+- `src/sync/droid.ts:6-21` symlinks skills but ignores MCP entirely.
+- Target writers already encode several missing MCP formats and merge behaviors:
+  - `src/targets/windsurf.ts:65-92`
+  - `src/targets/kiro.ts:68-91`
+  - `src/targets/openclaw.ts:34-42`
+  - `src/targets/qwen.ts:9-15`
+- `README.md:89-123` promises "Sync Personal Config" but only documents the old subset of targets.
+
+### Institutional Learnings
+
+`docs/solutions/adding-converter-target-providers.md:20-32` and `docs/solutions/adding-converter-target-providers.md:208-214` reinforce the right pattern for this feature:
+
+- keep target mappings explicit,
+- treat MCP conversion as target-specific,
+- warn on unsupported features instead of forcing fake parity,
+- and add tests for each mapping.
+
+Note: `docs/solutions/patterns/critical-patterns.md` does not exist in this repository, so there was no critical-patterns file to apply.
+
+### External Findings
+
+Official docs confirm that the missing targets are not all equivalent, so this cannot be solved with a generic JSON pass-through.
+
+| Target | Official MCP / skills location | Key notes |
+| --- | --- | --- |
+| Factory Droid | `~/.factory/mcp.json`, `.factory/mcp.json`, `~/.factory/skills/` | Supports `stdio` and `http`; user config overrides project config. |
+| Windsurf | `~/.codeium/windsurf/mcp_config.json`, `~/.codeium/windsurf/skills/` | Supports `stdio`, Streamable HTTP, and SSE; remote config uses `serverUrl` or `url`. |
+| Kiro | `~/.kiro/settings/mcp.json`, `.kiro/settings/mcp.json`, `~/.kiro/skills/` | Supports user and workspace config; remote MCP support was added after this repo's local Kiro spec was written. |
+| Qwen Code | `~/.qwen/settings.json`, `.qwen/settings.json`, `~/.qwen/skills/`, `.qwen/skills/` | Supports `stdio`, `http`, and `sse`; official docs say prefer `http`, with `sse` treated as legacy/deprecated. |
+| OpenClaw | `~/.openclaw/skills`, `<workspace>/skills`, `~/.openclaw/openclaw.json` | Skills are well-documented; a generic MCP server config surface is not clearly documented in official docs, so MCP sync needs validation before implementation is promised. |
+
+Additional important findings:
+
+- Kiro's current official behavior supersedes the local repo spec that says "workspace only" and "stdio only".
+- Qwen's current docs explicitly distinguish `httpUrl` from legacy SSE `url`; blindly copying Claude's `url` is too lossy.
+- Factory and Windsurf both support remote MCP, so `droid` should no longer be treated as skills-only.
+
+## Proposed Solution
+
+### Product Decision
+
+Treat this as **sync parity for MCP-capable providers**, not as a one-off patch.
+
+That means this feature should:
+
+- add missing sync targets where the provider has a documented skills/MCP surface,
+- upgrade partial implementations where existing sync support drops valid Claude MCP data,
+- and replace stale detection metadata so `sync --target all` is truthful again.
+
+### Scope
+
+#### In Scope
+
+- Add MCP sync coverage for:
+  - `droid`
+  - `windsurf`
+  - `kiro`
+  - `qwen`
+- Expand `codex` sync to support remote MCP servers.
+- Add provider detection for newly supported sync targets.
+- Keep skills syncing for all synced targets.
+- Update CLI help text, README sync docs, and tests.
+
+#### Conditional / Validation Gate
+
+- `openclaw` skills sync is straightforward and should be included if the target is added to `sync`.
+- `openclaw` MCP sync should only be implemented if its config surface is validated against current upstream docs or current upstream source. If that validation fails, the feature should explicitly skip OpenClaw MCP sync with a warning rather than inventing a format.
+
+#### Out of Scope
+
+- Standardizing all existing sync targets onto user-level paths only.
+- Reworking install/convert output roots.
+- Hook sync.
+- A full rewrite of target writers.
+
+### Design Decisions
+
+#### 0. Keep existing sync roots stable unless this feature is explicitly adding a new target
+
+Do not use this feature to migrate existing `copilot` and `gemini` sync behavior.
+
+Backward-compatibility rule:
+
+- existing targets keep their current sync roots unless a correctness bug forces a change,
+- newly added sync targets use the provider's documented personal/global config surface,
+- and any future root migration belongs in a separate plan.
+
+Planned sync roots after this feature:
+
+| Target | Sync root | Notes |
+| --- | --- | --- |
+| `opencode` | `~/.config/opencode` | unchanged |
+| `codex` | `~/.codex` | unchanged |
+| `pi` | `~/.pi/agent` | unchanged |
+| `droid` | `~/.factory` | unchanged root, new MCP file |
+| `copilot` | `.github` | unchanged for backwards compatibility |
+| `gemini` | `.gemini` | unchanged for backwards compatibility |
+| `windsurf` | `~/.codeium/windsurf` | new |
+| `kiro` | `~/.kiro` | new |
+| `qwen` | `~/.qwen` | new |
+| `openclaw` | `~/.openclaw` | new, MCP still validation-gated |
+
+#### 1. Add a dedicated sync target registry
+
+Do not keep growing `sync.ts` as a hand-maintained switch statement.
+
+Create a dedicated sync registry, for example:
+
+### `src/sync/registry.ts`
+
+```ts
+import os from "os"
+import path from "path"
+import type { ClaudeHomeConfig } from "../parsers/claude-home"
+
+export type SyncTargetDefinition = {
+  name: string
+  detectPaths: (home: string, cwd: string) => string[]
+  resolveOutputRoot: (home: string, cwd: string) => string
+  sync: (config: ClaudeHomeConfig, outputRoot: string) => Promise<void>
+}
+```
+
+This registry becomes the single source of truth for:
+
+- valid `sync` targets,
+- `sync --target all` detection,
+- output root resolution,
+- and dispatch.
+
+This avoids the current drift between:
+
+- `src/commands/sync.ts`
+- `src/utils/detect-tools.ts`
+- `README.md`
+
+#### 2. Preserve sync semantics, not writer semantics
+
+Do not directly reuse install target writers for sync.
+
+Reason:
+
+- writers mostly copy skill directories,
+- sync intentionally symlinks skills,
+- writers often emit full plugin/install bundles,
+- sync only needs personal skills plus MCP config.
+
+However, provider-specific MCP conversion helpers should be extracted or reused where practical so sync and writer logic do not diverge again.
+
+#### 3. Keep merge behavior additive, with Claude winning on same-name collisions
+
+For JSON-based targets:
+
+- preserve unrelated user keys,
+- preserve unrelated user MCP servers,
+- but if the same server name exists in Claude and the target config, Claude's value should overwrite that server entry during sync.
+
+Codex remains the special case:
+
+- continue using the managed marker block,
+- remove the previous managed block,
+- rewrite the managed block from Claude,
+- leave the rest of `config.toml` untouched.
+
+#### 4. Secure config writes where secrets may exist
+
+Any config file that may contain MCP headers or env vars should be written with restrictive permissions where the platform already supports that pattern.
+
+At minimum:
+
+- `config.toml`
+- `mcp.json`
+- `mcp_config.json`
+- `settings.json`
+
+should follow the repo's existing "secure write" conventions where possible.
+
+#### 5. Do not silently coerce ambiguous remote transports
+
+Qwen and possibly future targets distinguish Streamable HTTP from legacy SSE.
+
+Use this mapping rule:
+
+- if Claude explicitly provides `type: "sse"` or an equivalent known signal, map to the target's SSE field,
+- otherwise prefer the target's HTTP form for remote URLs,
+- and log a warning when a target requires more specificity than Claude provides.
+
+## Provider Mapping Plan
+
+### Existing Targets to Upgrade
+
+#### Codex
+
+Current issue:
+
+- only stdio servers are synced.
+
+Implementation:
+
+- extend `syncToCodex()` so remote MCP servers are serialized into the Codex TOML format, not dropped.
+- keep the existing marker-based idempotent section handling.
+
+Notes:
+
+- This is a correctness fix, not a new target.
+
+#### Droid / Factory
+
+Current issue:
+
+- skills-only sync despite current official MCP support.
+
+Implementation:
+
+- add `src/sync/droid.ts` MCP config writing to `~/.factory/mcp.json`.
+- merge with existing `mcpServers`.
+- support both `stdio` and `http`.
+
+### New Sync Targets
+
+#### Windsurf
+
+Add `src/sync/windsurf.ts`:
+
+- symlink Claude skills into `~/.codeium/windsurf/skills/`
+- merge MCP servers into `~/.codeium/windsurf/mcp_config.json`
+- support `stdio`, Streamable HTTP, and SSE
+- prefer `serverUrl` for remote HTTP config
+- preserve unrelated existing servers
+- write with secure permissions
+
+Reference implementation:
+
+- `src/targets/windsurf.ts:65-92`
+
+#### Kiro
+
+Add `src/sync/kiro.ts`:
+
+- symlink Claude skills into `~/.kiro/skills/`
+- merge MCP servers into `~/.kiro/settings/mcp.json`
+- support both local and remote MCP servers
+- preserve user config already present in `mcp.json`
+
+Important:
+
+- This feature must treat the repository's local Kiro spec as stale where it conflicts with official 2025-2026 Kiro docs/blog posts.
+
+Reference implementation:
+
+- `src/targets/kiro.ts:68-91`
+
+#### Qwen
+
+Add `src/sync/qwen.ts`:
+
+- symlink Claude skills into `~/.qwen/skills/`
+- merge MCP servers into `~/.qwen/settings.json`
+- map stdio directly
+- map remote URLs to `httpUrl` by default
+- only emit legacy SSE `url` when Claude transport clearly indicates SSE
+
+Important:
+
+- capture the deprecation note in docs/comments: SSE is legacy, so HTTP is the default remote mapping.
+
+#### OpenClaw
+
+Add `src/sync/openclaw.ts` only if validated during implementation:
+
+- symlink skills into `~/.openclaw/skills`
+- optionally merge MCP config into `~/.openclaw/openclaw.json` if the official/current upstream contract is confirmed
+
+Fallback behavior if MCP config cannot be validated:
+
+- sync skills only,
+- emit a warning that OpenClaw MCP sync is skipped because the official config surface is not documented clearly enough.
+
+## Implementation Phases
+
+### Phase 1: Registry and shared helpers
+
+Files:
+
+- `src/commands/sync.ts`
+- `src/utils/detect-tools.ts`
+- `src/sync/registry.ts` (new)
+- `src/sync/skills.ts` or `src/utils/symlink.ts` extension
+- optional `src/sync/mcp-merge.ts`
+
+Tasks:
+
+- move sync target metadata into a single registry
+- make `validTargets` derive from the registry
+- make `sync --target all` use the registry
+- update detection to include supported sync targets instead of stale `cursor`
+- extract a shared helper for validated skill symlinking
+
+### Phase 2: Upgrade existing partial targets
+
+Files:
+
+- `src/sync/codex.ts`
+- `src/sync/droid.ts`
+- `tests/sync-droid.test.ts`
+- new or expanded `tests/sync-codex.test.ts`
+
+Tasks:
+
+- add remote MCP support to Codex sync
+- add MCP config writing to Droid sync
+- preserve current skill symlink behavior
+
+### Phase 3: Add missing sync targets
+
+Files:
+
+- `src/sync/windsurf.ts`
+- `src/sync/kiro.ts`
+- `src/sync/qwen.ts`
+- optionally `src/sync/openclaw.ts`
+- `tests/sync-windsurf.test.ts`
+- `tests/sync-kiro.test.ts`
+- `tests/sync-qwen.test.ts`
+- optionally `tests/sync-openclaw.test.ts`
+
+Tasks:
+
+- implement skill symlink + MCP merge for each target
+- align output paths with the target's documented personal config surface
+- secure writes and corrupted-config fallbacks
+
+### Phase 4: CLI, docs, and detection parity
+
+Files:
+
+- `src/commands/sync.ts`
+- `src/utils/detect-tools.ts`
+- `tests/detect-tools.test.ts`
+- `tests/cli.test.ts`
+- `README.md`
+- optionally `docs/specs/kiro.md`
+
+Tasks:
+
+- update `sync` help text and summary output
+- ensure `sync --target all` only reports real sync-capable tools
+- document newly supported sync targets
+- fix stale Kiro assumptions if repository docs are updated in the same change
+
+## SpecFlow Analysis
+
+### Primary user flows
+
+#### Flow 1: Explicit sync to one target
+
+1. User runs `bunx @every-env/compound-plugin sync --target <provider>`
+2. CLI loads `~/.claude/skills` and `~/.claude/settings.json`
+3. CLI resolves that provider's sync root
+4. Skills are symlinked
+5. MCP config is merged
+6. CLI prints the destination path and completion summary
+
+#### Flow 2: Sync to all detected tools
+
+1. User runs `bunx @every-env/compound-plugin sync`
+2. CLI detects installed/supported tools
+3. CLI prints which tools were found and which were skipped
+4. CLI syncs each detected target in sequence
+5. CLI prints per-target success lines
+
+#### Flow 3: Existing config already present
+
+1. User already has destination config file(s)
+2. Sync reads and parses the existing file
+3. Existing unrelated keys are preserved
+4. Claude MCP entries are merged in
+5. Corrupt config produces a warning and replacement behavior
+
+### Edge cases to account for
+
+- Claude has zero MCP servers: skills still sync, no config file is written.
+- Claude has remote MCP servers: targets that support remote config receive them; unsupported transports warn, not crash.
+- Existing target config is invalid JSON/TOML: warn and replace the managed portion.
+- Skill name contains path traversal characters: skip with warning, same as current behavior.
+- Real directory already exists where a symlink would go: skip safely, do not delete user data.
+- `sync --target all` detects a tool with skills support but unclear MCP support: sync only the documented subset and warn explicitly.
+
+### Critical product decisions already assumed
+
+- `sync` remains additive and non-destructive.
+- Sync roots may differ from install roots when the provider has a documented personal config location.
+- OpenClaw MCP support is validation-gated rather than assumed.
+
+## Acceptance Criteria
+
+### Functional Requirements
+
+- [x] `sync --target` accepts `windsurf`, `kiro`, and `qwen`, in addition to the existing targets.
+- [x] `sync --target droid` writes MCP servers to Factory's documented `mcp.json` format instead of remaining skills-only.
+- [x] `sync --target codex` syncs both stdio and remote MCP servers.
+- [x] `sync --target all` detects only sync-capable supported tools and includes the new targets.
+- [x] Claude personal skills continue to be symlinked, not copied.
+- [x] Existing destination config keys unrelated to MCP are preserved during merge.
+- [x] Existing same-named MCP entries are refreshed from Claude for sync-managed targets.
+- [x] Unsafe skill names are skipped without deleting user content.
+- [x] If OpenClaw MCP sync is not validated, the CLI warns and skips MCP sync for OpenClaw instead of writing an invented format.
+
+### Non-Functional Requirements
+
+- [x] MCP config files that may contain secrets are written with restrictive permissions where supported.
+- [x] Corrupt destination config files warn and recover cleanly.
+- [x] New sync code does not duplicate target detection metadata in multiple places.
+- [x] Remote transport mapping is explicit and tested, especially for Qwen and Codex.
+
+### Quality Gates
+
+- [x] Add target-level sync tests for every new or upgraded provider.
+- [x] Update `tests/detect-tools.test.ts` for new detection rules and remove stale cursor expectations.
+- [x] Add or expand CLI coverage for `sync --target all`.
+- [x] `bun test` passes.
+
+## Testing Plan
+
+### Unit / integration tests
+
+Add or expand:
+
+- `tests/sync-codex.test.ts`
+  - remote URL server is emitted
+  - existing non-managed TOML content is preserved
+- `tests/sync-droid.test.ts`
+  - writes `mcp.json`
+  - merges with existing file
+- `tests/sync-windsurf.test.ts`
+  - writes `mcp_config.json`
+  - merges existing servers
+  - preserves HTTP/SSE fields
+- `tests/sync-kiro.test.ts`
+  - writes `settings/mcp.json`
+  - supports user-scope root
+  - preserves remote servers
+- `tests/sync-qwen.test.ts`
+  - writes `settings.json`
+  - maps remote servers to `httpUrl`
+  - emits legacy SSE only when explicitly indicated
+- `tests/sync-openclaw.test.ts` if implemented
+  - skills path
+  - MCP behavior or explicit skip warning
+
+### CLI tests
+
+Expand `tests/cli.test.ts` or add focused sync CLI coverage for:
+
+- `sync --target windsurf`
+- `sync --target kiro`
+- `sync --target qwen`
+- `sync --target all` with detected new tool homes
+- `sync --target all` no longer surfacing unsupported `cursor`
+
+## Risks and Mitigations
+
+### Risk: local specs are stale relative to current provider docs
+
+Impact:
+
+- implementing from local docs alone would produce incorrect paths and transport support.
+
+Mitigation:
+
+- treat official 2025-2026 docs/blog posts as source of truth where they supersede local specs
+- update any obviously stale repo docs touched by this feature
+
+### Risk: transport ambiguity for remote MCP servers
+
+Impact:
+
+- a Claude `url` may map incorrectly for targets that distinguish HTTP vs SSE.
+
+Mitigation:
+
+- prefer HTTP where the target recommends it
+- only emit legacy SSE when Claude transport is explicit
+- warn when mapping is lossy
+
+### Risk: OpenClaw MCP surface is not sufficiently documented
+
+Impact:
+
+- writing a guessed MCP config could create a broken or misleading feature.
+
+Mitigation:
+
+- validation gate during implementation
+- if validation fails, ship OpenClaw skills sync only and document MCP as a follow-up
+
+### Risk: `sync --target all` remains easy to drift out of sync again
+
+Impact:
+
+- future providers get added to install/convert but missed by sync.
+
+Mitigation:
+
+- derive sync valid targets and detection from a shared registry
+- add tests that assert detection and sync target lists match expected supported names
+
+## Alternative Approaches Considered
+
+### 1. Just add more cases to `sync.ts`
+
+Rejected:
+
+- this is exactly how the current drift happened.
+
+### 2. Reuse target writers directly
+
+Rejected:
+
+- writers copy directories and emit install bundles;
+- sync must symlink skills and only manage personal config subsets.
+
+### 3. Standardize every sync target on user-level output now
+
+Rejected for this feature:
+
+- it would change existing `gemini` and `copilot` behavior and broaden scope into a migration project.
+
+## Documentation Plan
+
+- Update `README.md` sync section to list all supported sync targets and call out any exceptions.
+- Update sync examples for `windsurf`, `kiro`, and `qwen`.
+- If OpenClaw MCP is skipped, document that explicitly.
+- If repository specs are corrected during implementation, update `docs/specs/kiro.md` to match official current behavior.
+
+## Success Metrics
+
+- `sync --target all` covers the same provider surface users reasonably expect from the current CLI, excluding only targets that lack a validated MCP config contract.
+- A Claude config with one stdio server and one remote server syncs correctly to every documented MCP-capable provider.
+- No user data is deleted during sync.
+- Documentation and CLI help no longer over-promise relative to actual behavior.
+
+## AI Pairing Notes
+
+- Treat official provider docs as authoritative over older local notes, especially for Kiro and Qwen transport handling.
+- Have a human review any AI-generated MCP mapping code before merge because these config files may contain secrets and lossy transport assumptions are easy to miss.
+- When using an implementation agent, keep the work split by target so each provider's config contract can be tested independently.
+
+## References & Research
+
+### Internal References
+
+- `src/commands/sync.ts:15-125`
+- `src/utils/detect-tools.ts:11-46`
+- `src/parsers/claude-home.ts:11-64`
+- `src/sync/codex.ts:7-92`
+- `src/sync/droid.ts:6-21`
+- `src/targets/windsurf.ts:13-93`
+- `src/targets/kiro.ts:5-93`
+- `src/targets/openclaw.ts:6-95`
+- `src/targets/qwen.ts:5-64`
+- `docs/solutions/adding-converter-target-providers.md:20-32`
+- `docs/solutions/adding-converter-target-providers.md:208-214`
+- `README.md:89-123`
+
+### External References
+
+- Factory MCP docs: https://docs.factory.ai/factory-cli/configuration/mcp
+- Factory skills docs: https://docs.factory.ai/cli/configuration/skills
+- Windsurf MCP docs: https://docs.windsurf.com/windsurf/cascade/mcp
+- Kiro MCP overview: https://kiro.dev/blog/unlock-your-development-productivity-with-kiro-and-mcp/
+- Kiro remote MCP support: https://kiro.dev/blog/introducing-remote-mcp/
+- Kiro skills announcement: https://kiro.dev/blog/custom-subagents-skills-and-enterprise-controls/
+- Qwen settings docs: https://qwenlm.github.io/qwen-code-docs/en/users/configuration/settings/
+- Qwen MCP docs: https://qwenlm.github.io/qwen-code-docs/en/users/features/mcp/
+- Qwen skills docs: https://qwenlm.github.io/qwen-code-docs/zh/users/features/skills/
+- OpenClaw setup/config docs: https://docs.openclaw.ai/start/setup
+- OpenClaw skills docs: https://docs.openclaw.ai/skills
+
+## Implementation Notes for the Follow-Up `/workflows-work` Step
+
+Suggested implementation order:
+
+1. registry + detection cleanup
+2. codex remote MCP + droid MCP
+3. windsurf + kiro + qwen sync modules
+4. openclaw validation and implementation or explicit warning path
+5. docs + tests
--- a/docs/plans/feature_opencode-commands-as-md-and-config-merge.md
+++ b/docs/plans/feature_opencode-commands-as-md-and-config-merge.md
@@ -0,0 +1,574 @@
+# Feature: OpenCode Commands as .md Files, Config Merge, and Permissions Default Fix
+
+**Type:** feature + bug fix (consolidated)
+**Date:** 2026-02-20
+**Starting point:** Branch `main` at commit `174cd4c`
+**Create feature branch:** `feature/opencode-commands-md-merge-permissions`
+**Baseline tests:** 180 pass, 0 fail (run `bun test` to confirm before starting)
+
+---
+
+## Context
+
+### User-Facing Goal
+
+When running `bunx @every-env/compound-plugin install compound-engineering --to opencode`, three problems exist:
+
+1. **Commands overwrite `opencode.json`**: Plugin commands are written into the `command` key of `opencode.json`, which replaces the user's existing configuration file (the writer does `writeJson(configPath, bundle.config)` — a full overwrite). The user loses their personal settings (model, theme, provider keys, MCP servers they previously configured).
+
+2. **Commands should be `.md` files, not JSON**: OpenCode supports defining commands as individual `.md` files in `~/.config/opencode/commands/`. This is additive and non-destructive — one file per command, never touches `opencode.json`.
+
+3. **`--permissions broad` is the default and pollutes global config**: The `--permissions` flag defaults to `"broad"`, which writes 14 `permission: allow` entries and 14 `tools: true` entries into `opencode.json` on every install. These are global settings that affect ALL OpenCode sessions, not just plugin commands. Even `--permissions from-commands` is semantically wrong — it unions per-command `allowedTools` restrictions into a single global block, which inverts restriction semantics (a command allowing only `Read` gets merged with one allowing `Bash`, producing global `bash: allow`).
+
+### Expected Behavior After This Plan
+
+- Commands are written as `~/.config/opencode/commands/<name>.md` with YAML frontmatter (`description`, `model`). The `command` key is never written to `opencode.json`.
+- `opencode.json` is deep-merged (not overwritten): existing user keys survive, plugin's MCP servers are added. User values win on conflict.
+- `--permissions` defaults to `"none"` — no `permission` or `tools` entries are written to `opencode.json` unless the user explicitly passes `--permissions broad` or `--permissions from-commands`.
+
+### Relevant File Paths
+
+| File | Current State on `main` | What Changes |
+|---|---|---|
+| `src/types/opencode.ts` | `OpenCodeBundle` has no `commandFiles` field. Has `OpenCodeCommandConfig` type and `command` field on `OpenCodeConfig`. | Add `OpenCodeCommandFile` type. Add `commandFiles` to `OpenCodeBundle`. Remove `OpenCodeCommandConfig` type and `command` field from `OpenCodeConfig`. |
+| `src/converters/claude-to-opencode.ts` | `convertCommands()` returns `Record<string, OpenCodeCommandConfig>`. Result set on `config.command`. `applyPermissions()` writes `config.permission` and `config.tools`. | `convertCommands()` returns `OpenCodeCommandFile[]`. `config.command` is never set. No changes to `applyPermissions()` itself. |
+| `src/targets/opencode.ts` | `writeOpenCodeBundle()` does `writeJson(configPath, bundle.config)` — full overwrite. No `commandsDir`. No merge logic. | Add `commandsDir` to path resolver. Write command `.md` files with backup. Replace overwrite with `mergeOpenCodeConfig()` — read existing, deep-merge, write back. |
+| `src/commands/install.ts` | `--permissions` default is `"broad"` (line 51). | Change default to `"none"`. Update description string. |
+| `src/utils/files.ts` | Has `readJson()`, `pathExists()`, `backupFile()` already. | No changes needed — utilities already exist. |
+| `tests/converter.test.ts` | Tests reference `bundle.config.command` (lines 19, 74, 202-214, 243). Test `"maps commands, permissions, and agents"` tests `from-commands` mode. | Update all to use `bundle.commandFiles`. Rename permission-related test to clarify opt-in nature. |
+| `tests/opencode-writer.test.ts` | 4 tests, none have `commandFiles` in bundles. `"backs up existing opencode.json before overwriting"` test expects full overwrite. | Add `commandFiles: []` to all existing bundles. Rewrite backup test to test merge behavior. Add new tests for command file writing and merge. |
+| `tests/cli.test.ts` | 10 tests. None check for commands directory. | Add test for `--permissions none` default. Add test for command `.md` file existence. |
+| `AGENTS.md` | Line 10: "Keep OpenCode output at `opencode.json` and `.opencode/{agents,skills,plugins}`." | Update to document commands go to `commands/<name>.md`, `opencode.json` is deep-merged. |
+| `README.md` | Line 54: "OpenCode output is written to `~/.config/opencode` by default, with `opencode.json` at the root..." | Update to document `.md` command files, merge behavior, `--permissions` default. |
+
+### Prior Context (Pre-Investigation)
+
+- **No `docs/decisions/` directory on `main`**: ADRs will be created fresh during this plan.
+- **No prior plans touch the same area**: The `2026-02-08-feat-convert-local-md-settings-for-opencode-codex-plan.md` discusses path rewriting in command bodies but does not touch command output format or permissions.
+- **OpenCode docs (confirmed via context7 MCP, library `/sst/opencode`):**
+  - Command `.md` frontmatter supports: `description`, `agent`, `model`. Does NOT support `permission` or `tools`. Placed in `~/.config/opencode/commands/` (global) or `.opencode/commands/` (project).
+  - Agent `.md` frontmatter supports: `description`, `mode`, `model`, `temperature`, `tools`, `permission`. Placed in `~/.config/opencode/agents/` or `.opencode/agents/`.
+  - `opencode.json` is the only place for: `mcp`, global `permission`, global `tools`, `model`, `provider`, `theme`, `server`, `compaction`, `watcher`, `share`.
+
+### Rejected Approaches
+
+**1. Map `allowedTools` to per-agent `.md` frontmatter permissions.**
+Rejected: Claude commands are not agents. There is no per-command-to-per-agent mapping. Commands don't specify which agent to run with. Even if they did, the union of multiple commands' restrictions onto a single agent's permissions loses the per-command scoping. Agent `.md` files DO support `permission` in frontmatter, but this would require creating synthetic agents just to hold permissions — misleading and fragile.
+
+**2. Write permissions into command `.md` file frontmatter.**
+Rejected: OpenCode command `.md` files only support `description`, `agent`, `model` in frontmatter. There is no `permission` or `tools` key. Confirmed via context7 docs. Anything else is silently ignored.
+
+**3. Keep `from-commands` as the default but fix the flattening logic.**
+Rejected: There is no correct way to flatten per-command tool restrictions into a single global permission block. Any flattening loses information and inverts semantics.
+
+**4. Remove the `--permissions` flag entirely.**
+Rejected: Some users may want to write permissions to `opencode.json` as a convenience. Keeping the flag with a changed default preserves optionality.
+
+**5. Write commands as both `.md` files AND in `opencode.json` `command` block.**
+Rejected: Redundant and defeats the purpose of avoiding `opencode.json` pollution. `.md` files are the sole output format.
+
+---
+
+## Decision Record
+
+### Decision 1: Commands emitted as individual `.md` files, never in `opencode.json`
+
+- **Decision:** `convertCommands()` returns `OpenCodeCommandFile[]` (one `.md` file per command with YAML frontmatter). The `command` key is never set on `OpenCodeConfig`. The writer creates `<commandsDir>/<name>.md` for each file.
+- **Context:** OpenCode supports two equivalent formats for commands — JSON in config and `.md` files. The `.md` format is additive (new files) rather than destructive (rewriting JSON). This is consistent with how agents and skills are already handled as `.md` files.
+- **Alternatives rejected:** JSON-only (destructive), both formats (redundant). See Rejected Approaches above.
+- **Assumptions:** OpenCode resolves commands from the `commands/` directory at runtime. Confirmed via docs.
+- **Reversal trigger:** If OpenCode deprecates `.md` command files or the format changes incompatibly.
+
+### Decision 2: `opencode.json` deep-merged, not overwritten
+
+- **Decision:** `writeOpenCodeBundle()` reads the existing `opencode.json` (if present), deep-merges plugin-provided keys (MCP servers, and optionally permission/tools if `--permissions` is not `none`) without overwriting user-set values, and writes the merged result. User keys always win on conflict.
+- **Context:** Users have personal configuration in `opencode.json` (API keys, model preferences, themes, existing MCP servers). The current full-overwrite destroys all of this.
+- **Alternatives rejected:** Skip writing `opencode.json` entirely — rejected because MCP servers must be written there (no `.md` alternative exists for MCP).
+- **Assumptions:** `readJson()` and `pathExists()` already exist in `src/utils/files.ts`. Malformed JSON in existing file should warn and fall back to plugin-only config (do not crash, do not destroy).
+- **Reversal trigger:** If OpenCode adds a separate mechanism for plugin MCP server registration that doesn't involve `opencode.json`.
+
+### Decision 3: `--permissions` default changed from `"broad"` to `"none"`
+
+- **Decision:** The `--permissions` CLI flag default changes from `"broad"` to `"none"`. No `permission` or `tools` keys are written to `opencode.json` unless the user explicitly opts in.
+- **Context:** `"broad"` silently writes 14 global tool permissions. `"from-commands"` has a semantic inversion bug (unions per-command restrictions into global allows). Both are destructive to user config. `applyPermissions()` already short-circuits on `"none"` (line 299: `if (mode === "none") return`), so no changes to that function are needed.
+- **Alternatives rejected:** Fix `from-commands` flattening — impossible to do correctly with global-only target. Remove flag entirely — too restrictive for power users.
+- **Assumptions:** The `applyPermissions()` function with mode `"none"` leaves `config.permission` and `config.tools` as `undefined`.
+- **Reversal trigger:** If OpenCode adds per-command permission scoping, `from-commands` could become meaningful again.
+
+---
+
+## ADRs To Create
+
+Create `docs/decisions/` directory (does not exist on `main`). ADRs follow `AGENTS.md` numbering convention: `0001-short-title.md`.
+
+### ADR 0001: OpenCode commands written as `.md` files, not in `opencode.json`
+
+- **Context:** OpenCode supports two equivalent formats for custom commands. Writing to `opencode.json` requires overwriting or merging the user's config file. Writing `.md` files is additive and non-destructive.
+- **Decision:** The OpenCode target always emits commands as individual `.md` files in the `commands/` subdirectory. The `command` key is never written to `opencode.json` by this tool.
+- **Consequences:**
+  - Positive: Installs are non-destructive. Commands are visible as individual files, easy to inspect. Consistent with agents/skills handling.
+  - Negative: Users inspecting `opencode.json` won't see plugin commands; they must look in `commands/`.
+  - Neutral: Requires OpenCode >= the version with command file support (confirmed stable).
+
+### ADR 0002: Plugin merges into existing `opencode.json` rather than replacing it
+
+- **Context:** Users have existing `opencode.json` files with personal configuration. The install command previously backed up and replaced this file entirely, destroying user settings.
+- **Decision:** `writeOpenCodeBundle` reads existing `opencode.json` (if present), deep-merges plugin-provided keys without overwriting user-set values, and writes the merged result. User keys always win on conflict.
+- **Consequences:**
+  - Positive: User config preserved across installs. Re-installs are idempotent for user-set values.
+  - Negative: Plugin cannot remove or update an MCP server entry if the user already has one with the same name.
+  - Neutral: Backup of pre-merge file is still created for safety.
+
+### ADR 0003: Global permissions not written to `opencode.json` by default
+
+- **Context:** Claude commands carry `allowedTools` as per-command restrictions. OpenCode has no per-command permission mechanism. Writing per-command restrictions as global permissions is semantically incorrect and pollutes the user's global config.
+- **Decision:** `--permissions` defaults to `"none"`. The plugin never writes `permission` or `tools` to `opencode.json` unless the user explicitly passes `--permissions broad` or `--permissions from-commands`.
+- **Consequences:**
+  - Positive: User's global OpenCode permissions are never silently modified.
+  - Negative: Users who relied on auto-set permissions must now pass the flag explicitly.
+  - Neutral: The `"broad"` and `"from-commands"` modes still work as documented for opt-in use.
+
+---
+
+## Assumptions & Invalidation Triggers
+
+- **Assumption:** OpenCode command `.md` frontmatter supports `description`, `agent`, `model` and does NOT support `permission` or `tools`.
+  - **If this changes:** The converter could emit per-command permissions in command frontmatter, making `from-commands` mode semantically correct. Phase 2 would need a new code path.
+
+- **Assumption:** `readJson()` and `pathExists()` exist in `src/utils/files.ts` and work as expected.
+  - **If this changes:** Phase 4's merge logic needs alternative I/O utilities.
+
+- **Assumption:** `applyPermissions()` with mode `"none"` returns early at line 299 and does not set `config.permission` or `config.tools`.
+  - **If this changes:** The merge logic in Phase 4 might still merge stale data. Verify before implementing.
+
+- **Assumption:** 180 tests pass on `main` at commit `174cd4c` with `bun test`.
+  - **If this changes:** Do not proceed until the discrepancy is understood.
+
+- **Assumption:** `formatFrontmatter()` in `src/utils/frontmatter.ts` handles `Record<string, unknown>` data and string body, producing valid YAML frontmatter. It filters out `undefined` values (line 35). It already supports nested objects/arrays via `formatYamlLine()`.
+  - **If this changes:** Phase 2's command file content generation would produce malformed output.
+
+- **Assumption:** The `backupFile()` function in `src/utils/files.ts` returns `null` if the file does not exist, and returns the backup path if it does. It does NOT throw on missing files.
+  - **If this changes:** Phase 4's backup-before-write for command files would need error handling.
+
+---
+
+## Phases
+
+### Phase 1: Add `OpenCodeCommandFile` type and update `OpenCodeBundle`
+
+**What:** In `src/types/opencode.ts`:
+- Add a new type `OpenCodeCommandFile` with `name: string` (command name, used as filename stem) and `content: string` (full file content: YAML frontmatter + body).
+- Add `commandFiles: OpenCodeCommandFile[]` field to `OpenCodeBundle`.
+- Remove `command?: Record<string, OpenCodeCommandConfig>` from `OpenCodeConfig`.
+- Remove the `OpenCodeCommandConfig` type entirely (lines 23-28).
+
+**Why:** This is the foundational type change that all subsequent phases depend on. Commands move from the config object to individual file entries in the bundle.
+
+**Test first:**
+
+File: `tests/converter.test.ts`
+
+Before making any type changes, update the test file to reflect the new shape. The existing tests will fail because they reference `bundle.config.command` and `OpenCodeBundle` doesn't have `commandFiles` yet.
+
+Tests to modify (they will fail after type changes, then pass after Phase 2):
+- `"maps commands, permissions, and agents"` (line 11): Change `bundle.config.command?.["workflows:review"]` to `bundle.commandFiles.find(f => f.name === "workflows:review")`. Change `bundle.config.command?.["plan_review"]` to `bundle.commandFiles.find(f => f.name === "plan_review")`.
+- `"normalizes models and infers temperature"` (line 60): Change `bundle.config.command?.["workflows:work"]` to check `bundle.commandFiles.find(f => f.name === "workflows:work")` and parse its frontmatter for model.
+- `"excludes commands with disable-model-invocation from command map"` (line 202): Change `bundle.config.command?.["deploy-docs"]` to `bundle.commandFiles.find(f => f.name === "deploy-docs")`.
+- `"rewrites .claude/ paths to .opencode/ in command bodies"` (line 217): Change `bundle.config.command?.["review"]?.template` to access `bundle.commandFiles.find(f => f.name === "review")?.content`.
+
+Also update `tests/opencode-writer.test.ts`:
+- Add `commandFiles: []` to every `OpenCodeBundle` literal in all 4 existing tests (lines 20, 43, 67, 98). These bundles currently only have `config`, `agents`, `plugins`, `skillDirs`.
+
+**Implementation:**
+
+In `src/types/opencode.ts`:
+1. Remove lines 23-28 (`OpenCodeCommandConfig` type).
+2. Remove line 10 (`command?: Record<string, OpenCodeCommandConfig>`) from `OpenCodeConfig`.
+3. Add after line 47:
+```typescript
+export type OpenCodeCommandFile = {
+  name: string    // command name, used as the filename stem: <name>.md
+  content: string // full file content: YAML frontmatter + body
+}
+```
+4. Add `commandFiles: OpenCodeCommandFile[]` to `OpenCodeBundle` (between `agents` and `plugins`).
+
+In `src/converters/claude-to-opencode.ts`:
+- Update the import on line 11: Remove `OpenCodeCommandConfig` from the import. Add `OpenCodeCommandFile`.
+
+**Code comments required:**
+- Above the `commandFiles` field in `OpenCodeBundle`: `// Commands are written as individual .md files, not in opencode.json. See ADR-001.`
+
+**Verification:** `bun test` will show failures in converter tests (they reference the old command format). This is expected — Phase 2 fixes them.
+
+---
+
+### Phase 2: Convert `convertCommands()` to emit `.md` command files
+
+**What:** In `src/converters/claude-to-opencode.ts`:
+- Rewrite `convertCommands()` (line 114) to return `OpenCodeCommandFile[]` instead of `Record<string, OpenCodeCommandConfig>`.
+- Each command becomes a `.md` file with YAML frontmatter (`description`, optionally `model`) and body (the template text with Claude path rewriting applied).
+- In `convertClaudeToOpenCode()` (line 64): replace `commandMap` with `commandFiles`. Remove `config.command` assignment. Add `commandFiles` to returned bundle.
+
+**Why:** This is the core conversion logic change that implements ADR-001.
+
+**Test first:**
+
+File: `tests/converter.test.ts`
+
+The tests were already updated in Phase 1 to reference `bundle.commandFiles`. Now they need to pass. Specific assertions:
+
+1. Rename `"maps commands, permissions, and agents"` to `"from-commands mode: maps allowedTools to global permission block"` — to clarify this tests an opt-in mode, not the default.
+   - Assert `bundle.config.command` is `undefined` (it no longer exists on the type, but accessing it returns `undefined`).
+   - Assert `bundle.commandFiles.find(f => f.name === "workflows:review")` is defined.
+   - Assert `bundle.commandFiles.find(f => f.name === "plan_review")` is defined.
+   - Permission assertions remain unchanged (they test `from-commands` mode explicitly).
+
+2. `"normalizes models and infers temperature"`:
+   - Find `workflows:work` in `bundle.commandFiles`, parse its frontmatter with `parseFrontmatter()`, assert `data.model === "openai/gpt-4o"`.
+
+3. `"excludes commands with disable-model-invocation from command map"` — rename to `"excludes commands with disable-model-invocation from commandFiles"`:
+   - Assert `bundle.commandFiles.find(f => f.name === "deploy-docs")` is `undefined`.
+   - Assert `bundle.commandFiles.find(f => f.name === "workflows:review")` is defined.
+
+4. `"rewrites .claude/ paths to .opencode/ in command bodies"`:
+   - Find `review` in `bundle.commandFiles`, assert `content` contains `"compound-engineering.local.md"`.
+
+5. Add NEW test: `"command .md files include description in frontmatter"`:
+   - Create a minimal `ClaudePlugin` with one command (`name: "test-cmd"`, `description: "Test description"`, `body: "Do the thing"`).
+   - Convert with `permissions: "none"`.
+   - Find the command file, parse frontmatter, assert `data.description === "Test description"`.
+   - Assert the body (after frontmatter) contains `"Do the thing"`.
+
+**Implementation:**
+
+In `src/converters/claude-to-opencode.ts`:
+
+Replace lines 114-128 (`convertCommands` function):
+```typescript
+// Commands are written as individual .md files rather than entries in opencode.json.
+// Chosen over JSON map because opencode resolves commands by filename at runtime (ADR-001).
+function convertCommands(commands: ClaudeCommand[]): OpenCodeCommandFile[] {
+  const files: OpenCodeCommandFile[] = []
+  for (const command of commands) {
+    if (command.disableModelInvocation) continue
+    const frontmatter: Record<string, unknown> = {
+      description: command.description,
+    }
+    if (command.model && command.model !== "inherit") {
+      frontmatter.model = normalizeModel(command.model)
+    }
+    const content = formatFrontmatter(frontmatter, rewriteClaudePaths(command.body))
+    files.push({ name: command.name, content })
+  }
+  return files
+}
+```
+
+Replace lines 64-87 (`convertClaudeToOpenCode` function body):
+- Change line 69: `const commandFiles = convertCommands(plugin.commands)`
+- Change lines 73-77 (config construction): Remove the `command: ...` line. Config should only have `$schema` and `mcp`.
+- Change line 81-86 (return): Replace `plugins` in the return with `commandFiles, plugins` (add `commandFiles` field to returned bundle).
+
+**Code comments required:**
+- Above `convertCommands()`: `// Commands are written as individual .md files rather than entries in opencode.json.` and `// Chosen over JSON map because opencode resolves commands by filename at runtime (ADR-001).`
+
+**Verification:** Run `bun test tests/converter.test.ts`. All converter tests must pass. Then run `bun test` — writer tests should still fail (they expect the old bundle shape; fixed in Phase 1's test updates) but converter tests pass.
+
+---
+
+### Phase 3: Add `commandsDir` to path resolver and write command files
+
+**What:** In `src/targets/opencode.ts`:
+- Add `commandsDir` to the return value of `resolveOpenCodePaths()` for both branches (global and custom output dir).
+- In `writeOpenCodeBundle()`, iterate `bundle.commandFiles` and write each as `<commandsDir>/<name>.md` with backup-before-overwrite.
+
+**Why:** This creates the file output mechanism for command `.md` files. Separated from Phase 4 (merge logic) for testability.
+
+**Test first:**
+
+File: `tests/opencode-writer.test.ts`
+
+Add these new tests:
+
+1. `"writes command files as .md in commands/ directory"`:
+   - Create a bundle with one `commandFiles` entry: `{ name: "my-cmd", content: "---\ndescription: Test\n---\n\nDo something." }`.
+   - Use an output root of `path.join(tempRoot, ".config", "opencode")` (global-style).
+   - Assert `exists(path.join(outputRoot, "commands", "my-cmd.md"))` is true.
+   - Read the file, assert content matches (with trailing newline: `content + "\n"`).
+
+2. `"backs up existing command .md file before overwriting"`:
+   - Pre-create `commands/my-cmd.md` with old content.
+   - Write a bundle with a `commandFiles` entry for `my-cmd`.
+   - Assert a `.bak.` file exists in `commands/` directory.
+   - Assert new content is written.
+
+**Implementation:**
+
+In `resolveOpenCodePaths()`:
+- In the global branch (line 39-46): Add `commandsDir: path.join(outputRoot, "commands")` with comment: `// .md command files; alternative to the command key in opencode.json`
+- In the custom branch (line 49-56): Add `commandsDir: path.join(outputRoot, ".opencode", "commands")` with same comment.
+
+In `writeOpenCodeBundle()`:
+- After the agents loop (line 18), add:
+```typescript
+const commandsDir = paths.commandsDir
+for (const commandFile of bundle.commandFiles) {
+  const dest = path.join(commandsDir, `${commandFile.name}.md`)
+  const cmdBackupPath = await backupFile(dest)
+  if (cmdBackupPath) {
+    console.log(`Backed up existing command file to ${cmdBackupPath}`)
+  }
+  await writeText(dest, commandFile.content + "\n")
+}
+```
+
+**Code comments required:**
+- Inline comment on `commandsDir` in both `resolveOpenCodePaths` branches: `// .md command files; alternative to the command key in opencode.json`
+
+**Verification:** Run `bun test tests/opencode-writer.test.ts`. The two new command file tests must pass. Existing tests must still pass (they have `commandFiles: []` from Phase 1 updates).
+
+---
+
+### Phase 4: Replace config overwrite with deep-merge
+
+**What:** In `src/targets/opencode.ts`:
+- Replace `writeJson(paths.configPath, bundle.config)` (line 13) with a call to a new `mergeOpenCodeConfig()` function.
+- `mergeOpenCodeConfig()` reads the existing `opencode.json` (if present), merges plugin-provided keys using user-wins-on-conflict strategy, and returns the merged config.
+- Import `pathExists` and `readJson` from `../utils/files` (add to existing import on line 2).
+
+**Why:** This implements ADR-002 — the user's existing config is preserved across installs.
+
+**Test first:**
+
+File: `tests/opencode-writer.test.ts`
+
+Modify existing test and add new tests:
+
+1. Rename `"backs up existing opencode.json before overwriting"` (line 88) to `"merges plugin config into existing opencode.json without destroying user keys"`:
+   - Pre-create `opencode.json` with `{ $schema: "https://opencode.ai/config.json", custom: "value" }`.
+   - Write a bundle with `config: { $schema: "...", mcp: { "plugin-server": { type: "local", command: "uvx", args: ["plugin-srv"] } } }`.
+   - Assert merged config has BOTH `custom: "value"` (user key) AND `mcp["plugin-server"]` (plugin key).
+   - Assert backup file exists with original content.
+
+2. NEW: `"merges mcp servers without overwriting user entries"`:
+   - Pre-create `opencode.json` with `{ mcp: { "user-server": { type: "local", command: "uvx", args: ["user-srv"] } } }`.
+   - Write a bundle with `config.mcp` containing both `"plugin-server"` (new) and `"user-server"` (conflict — different args).
+   - Assert both servers exist in merged output.
+   - Assert `user-server` keeps user's original args (user wins on conflict).
+   - Assert `plugin-server` is present with plugin's args.
+
+3. NEW: `"preserves unrelated user keys when merging opencode.json"`:
+   - Pre-create `opencode.json` with `{ model: "my-model", theme: "dark", mcp: {} }`.
+   - Write a bundle with `config: { $schema: "...", mcp: { "plugin-server": ... }, permission: { "bash": "allow" } }`.
+   - Assert `model` and `theme` are preserved.
+   - Assert plugin additions are present.
+
+**Implementation:**
+
+Add to imports in `src/targets/opencode.ts` line 2:
+```typescript
+import { backupFile, copyDir, ensureDir, pathExists, readJson, writeJson, writeText } from "../utils/files"
+import type { OpenCodeBundle, OpenCodeConfig } from "../types/opencode"
+```
+
+Add `mergeOpenCodeConfig()` function:
+```typescript
+async function mergeOpenCodeConfig(
+  configPath: string,
+  incoming: OpenCodeConfig,
+): Promise<OpenCodeConfig> {
+  // If no existing config, write plugin config as-is
+  if (!(await pathExists(configPath))) return incoming
+
+  let existing: OpenCodeConfig
+  try {
+    existing = await readJson<OpenCodeConfig>(configPath)
+  } catch {
+    // Safety first per AGENTS.md -- do not destroy user data even if their config is malformed.
+    // Warn and fall back to plugin-only config rather than crashing.
+    console.warn(
+      `Warning: existing ${configPath} is not valid JSON. Writing plugin config without merging.`
+    )
+    return incoming
+  }
+
+  // User config wins on conflict -- see ADR-002
+  // MCP servers: add plugin entries, skip keys already in user config.
+  const mergedMcp = {
+    ...(incoming.mcp ?? {}),
+    ...(existing.mcp ?? {}), // existing takes precedence (overwrites same-named plugin entries)
+  }
+
+  // Permission: add plugin entries, skip keys already in user config.
+  const mergedPermission = incoming.permission
+    ? {
+        ...(incoming.permission),
+        ...(existing.permission ?? {}), // existing takes precedence
+      }
+    : existing.permission
+
+  // Tools: same pattern
+  const mergedTools = incoming.tools
+    ? {
+        ...(incoming.tools),
+        ...(existing.tools ?? {}),
+      }
+    : existing.tools
+
+  return {
+    ...existing,                    // all user keys preserved
+    $schema: incoming.$schema ?? existing.$schema,
+    mcp: Object.keys(mergedMcp).length > 0 ? mergedMcp : undefined,
+    permission: mergedPermission,
+    tools: mergedTools,
+  }
+}
+```
+
+In `writeOpenCodeBundle()`, replace line 13 (`await writeJson(paths.configPath, bundle.config)`) with:
+```typescript
+const merged = await mergeOpenCodeConfig(paths.configPath, bundle.config)
+await writeJson(paths.configPath, merged)
+```
+
+**Code comments required:**
+- Above `mergeOpenCodeConfig()`: `// Merges plugin config into existing opencode.json. User keys win on conflict. See ADR-002.`
+- On the `...(existing.mcp ?? {})` line: `// existing takes precedence (overwrites same-named plugin entries)`
+- On malformed JSON catch: `// Safety first per AGENTS.md -- do not destroy user data even if their config is malformed.`
+
+**Verification:** Run `bun test tests/opencode-writer.test.ts`. All tests must pass including the renamed test and the 2 new merge tests.
+
+---
+
+### Phase 5: Change `--permissions` default to `"none"`
+
+**What:** In `src/commands/install.ts`, change line 51 `default: "broad"` to `default: "none"`. Update the description string.
+
+**Why:** This implements ADR-003 — stops polluting user's global config with permissions by default.
+
+**Test first:**
+
+File: `tests/cli.test.ts`
+
+Add these tests:
+
+1. `"install --to opencode uses permissions:none by default"`:
+   - Run install with no `--permissions` flag against the fixture plugin.
+   - Read the written `opencode.json`.
+   - Assert it does NOT contain a `permission` key.
+   - Assert it does NOT contain a `tools` key.
+
+2. `"install --to opencode --permissions broad writes permission block"`:
+   - Run install with `--permissions broad` against the fixture plugin.
+   - Read the written `opencode.json`.
+   - Assert it DOES contain a `permission` key with values.
+
+**Implementation:**
+
+In `src/commands/install.ts`:
+- Line 51: Change `default: "broad"` to `default: "none"`.
+- Line 52: Change description to `"Permission mapping written to opencode.json: none (default) | broad | from-commands"`.
+
+**Code comments required:**
+- On the `default: "none"` line: `// Default is "none" -- writing global permissions to opencode.json pollutes user config. See ADR-003.`
+
+**Verification:** Run `bun test tests/cli.test.ts`. All CLI tests must pass including the 2 new permission tests. Then run `bun test` — all tests (180 original + new ones) must pass.
+
+---
+
+### Phase 6: Update `AGENTS.md` and `README.md`
+
+**What:** Update documentation to reflect all three changes.
+
+**Why:** Keeps docs accurate for future contributors and users.
+
+**Test first:** No tests required for documentation changes.
+
+**Implementation:**
+
+In `AGENTS.md` line 10, replace:
+```
+- **Output Paths:** Keep OpenCode output at `opencode.json` and `.opencode/{agents,skills,plugins}`.
+```
+with:
+```
+- **Output Paths:** Keep OpenCode output at `opencode.json` and `.opencode/{agents,skills,plugins}`. For OpenCode, commands go to `~/.config/opencode/commands/<name>.md`; `opencode.json` is deep-merged (never overwritten wholesale).
+```
+
+In `README.md` line 54, replace:
+```
+OpenCode output is written to `~/.config/opencode` by default, with `opencode.json` at the root and `agents/`, `skills/`, and `plugins/` alongside it.
+```
+with:
+```
+OpenCode output is written to `~/.config/opencode` by default. Commands are written as individual `.md` files to `~/.config/opencode/commands/<name>.md`. Agents, skills, and plugins are written to the corresponding subdirectories alongside. `opencode.json` (MCP servers) is deep-merged into any existing file -- user keys such as `model`, `theme`, and `provider` are preserved, and user values win on conflicts. Command files are backed up before being overwritten.
+```
+
+Also update `AGENTS.md` to add a Repository Docs Conventions section if not present:
+```
+## Repository Docs Conventions
+
+- **ADRs** live in `docs/decisions/` and are numbered with 4-digit zero-padding: `0001-short-title.md`, `0002-short-title.md`, etc.
+- **Orchestrator run reports** live in `docs/reports/`.
+
+When recording a significant decision (new provider, output format change, merge strategy), create an ADR in `docs/decisions/` following the numbering sequence.
+```
+
+**Code comments required:** None.
+
+**Verification:** Read the updated files and confirm accuracy. Run `bun test` to confirm no regressions.
+
+---
+
+## TDD Enforcement
+
+The executing agent MUST follow this sequence for every phase that touches source code:
+
+1. Write the test(s) first in the test file.
+2. Run `bun test <test-file>` and confirm the new/modified tests FAIL (red).
+3. Implement the code change.
+4. Run `bun test <test-file>` and confirm the new/modified tests PASS (green).
+5. Run `bun test` (all tests) and confirm no regressions.
+
+**Exception:** Phase 6 is documentation only. Run `bun test` after to confirm no regressions but no red/green cycle needed.
+
+**Note on Phase 1:** Type changes alone will cause test failures. Phase 1 and Phase 2 are tightly coupled — the tests updated in Phase 1 will not pass until Phase 2's implementation is complete. The executing agent should:
+1. Update tests in Phase 1 (expect them to fail — both due to type errors and logic changes).
+2. Implement type changes in Phase 1.
+3. Implement converter changes in Phase 2.
+4. Confirm all converter tests pass after Phase 2.
+
+---
+
+## Constraints
+
+**Do not modify:**
+- `src/converters/claude-to-opencode.ts` lines 294-417 (`applyPermissions()`, `normalizeTool()`, `parseToolSpec()`, `normalizePattern()`) — these functions are correct for `"broad"` and `"from-commands"` modes. Only the default that triggers them is changing.
+- Any files under `tests/fixtures/` — these are data files, not test logic.
+- `src/types/claude.ts` — no changes to source types.
+- `src/parsers/claude.ts` — no changes to parser logic.
+- `src/utils/files.ts` — all needed utilities already exist. Do not add new utility functions.
+- `src/utils/frontmatter.ts` — already handles the needed formatting.
+
+**Dependencies not to add:** None. No new npm/bun packages.
+
+**Patterns to follow:**
+- Existing writer tests in `tests/opencode-writer.test.ts` use `fs.mkdtemp()` for temp directories and the local `exists()` helper function.
+- Existing CLI tests in `tests/cli.test.ts` use `Bun.spawn()` to invoke the CLI.
+- Existing converter tests in `tests/converter.test.ts` use `loadClaudePlugin(fixtureRoot)` for real fixtures and inline `ClaudePlugin` objects for isolated tests.
+- ADR format: Follow `AGENTS.md` numbering convention `0001-short-title.md` with sections: Status, Date, Context, Decision, Consequences, Plan Reference.
+- Commits: Use conventional commit format. Reference ADRs in commit bodies.
+- Branch: Create `feature/opencode-commands-md-merge-permissions` from `main`.
+
+## Final Checklist
+
+After all phases complete:
+- [ ] `bun test` passes all tests (180 original + new ones, 0 fail)
+- [ ] `docs/decisions/0001-opencode-command-output-format.md` exists
+- [ ] `docs/decisions/0002-opencode-json-merge-strategy.md` exists
+- [ ] `docs/decisions/0003-opencode-permissions-default-none.md` exists
+- [ ] `opencode.json` is never fully overwritten — merge logic confirmed by test
+- [ ] Commands are written as `.md` files — confirmed by test
+- [ ] `--permissions` defaults to `"none"` — confirmed by CLI test
+- [ ] `AGENTS.md` and `README.md` updated to reflect new behavior
--- a/docs/solutions/adding-converter-target-providers.md
+++ b/docs/solutions/adding-converter-target-providers.md
@@ -0,0 +1,693 @@
+---
+title: Adding New Converter Target Providers
+category: architecture
+tags: [converter, target-provider, plugin-conversion, multi-platform, pattern]
+created: 2026-02-23
+severity: medium
+component: converter-cli
+problem_type: best_practice
+root_cause: architectural_pattern
+---
+
+# Adding New Converter Target Providers
+
+## Problem
+
+When adding support for a new AI platform (e.g., Devin, Cursor, Copilot), the converter CLI architecture requires consistent implementation across types, converters, writers, CLI integration, and tests. Without documented patterns and learnings, new targets take longer to implement and risk architectural inconsistency.
+
+## Solution
+
+The compound-engineering-plugin uses a proven **6-phase target provider pattern** that has been successfully applied to 8 targets:
+
+1. **OpenCode** (primary target, reference implementation)
+2. **Codex** (second target, established pattern)
+3. **Droid/Factory** (workflow/agent conversion)
+4. **Pi** (MCPorter ecosystem)
+5. **Gemini CLI** (content transformation patterns)
+6. **Cursor** (command flattening, rule formats)
+7. **Copilot** (GitHub native, MCP prefixing)
+8. **Kiro** (limited MCP support)
+9. **Devin** (playbook conversion, knowledge entries)
+
+Each implementation follows this architecture precisely, ensuring consistency and maintainability.
+
+## Architecture: The 6-Phase Pattern
+
+### Phase 1: Type Definitions (`src/types/{target}.ts`)
+
+**Purpose:** Define TypeScript types for the intermediate bundle format
+
+**Key Pattern:**
+
+```typescript
+// Exported bundle type used by converter and writer
+export type {TargetName}Bundle = {
+  // Component arrays matching the target format
+  agents?: {TargetName}Agent[]
+  commands?: {TargetName}Command[]
+  skillDirs?: {TargetName}SkillDir[]
+  mcpServers?: Record<string, {TargetName}McpServer>
+  // Target-specific fields
+  setup?: string  // Instructions file content
+}
+
+// Individual component types
+export type {TargetName}Agent = {
+  name: string
+  content: string  // Full file content (with frontmatter if applicable)
+  category?: string  // e.g., "agent", "rule", "playbook"
+  meta?: Record<string, unknown>  // Target-specific metadata
+}
+```
+
+**Key Learnings:**
+
+- Always include a `content` field (full file text) rather than decomposed fields — it's simpler and matches how files are written
+- Use intermediate types for complex sections (e.g., `DevinPlaybookSections` in Devin converter) to make section building independently testable
+- Avoid target-specific fields in the base bundle unless essential — aim for shared structure across targets
+- Include a `category` field if the target has file-type variants (agents vs. commands vs. rules)
+
+**Reference Implementations:**
+- OpenCode: `src/types/opencode.ts` (command + agent split)
+- Devin: `src/types/devin.ts` (playbooks + knowledge entries)
+- Copilot: `src/types/copilot.ts` (agents + skills + MCP)
+
+---
+
+### Phase 2: Converter (`src/converters/claude-to-{target}.ts`)
+
+**Purpose:** Transform Claude Code plugin format → target-specific bundle format
+
+**Key Pattern:**
+
+```typescript
+export type ClaudeTo{Target}Options = ClaudeToOpenCodeOptions  // Reuse common options
+
+export function convertClaudeTo{Target}(
+  plugin: ClaudePlugin,
+  _options: ClaudeTo{Target}Options,
+): {Target}Bundle {
+  // Pre-scan: build maps for cross-reference resolution (agents, commands)
+  // Needed if target requires deduplication or reference tracking
+  const refMap: Record<string, string> = {}
+  for (const agent of plugin.agents) {
+    refMap[normalize(agent.name)] = macroName(agent.name)
+  }
+
+  // Phase 1: Convert agents
+  const agents = plugin.agents.map(a => convert{Target}Agent(a, usedNames, refMap))
+
+  // Phase 2: Convert commands (may depend on agent names for dedup)
+  const commands = plugin.commands.map(c => convert{Target}Command(c, usedNames, refMap))
+
+  // Phase 3: Handle skills (usually pass-through, sometimes conversion)
+  const skillDirs = plugin.skills.map(s => ({ name: s.name, sourceDir: s.sourceDir }))
+
+  // Phase 4: Convert MCP servers (target-specific prefixing/type mapping)
+  const mcpConfig = convertMcpServers(plugin.mcpServers)
+
+  // Phase 5: Warn on unsupported features
+  if (plugin.hooks && Object.keys(plugin.hooks.hooks).length > 0) {
+    console.warn("Warning: {Target} does not support hooks. Hooks were skipped.")
+  }
+
+  return { agents, commands, skillDirs, mcpConfig }
+}
+```
+
+**Content Transformation (`transformContentFor{Target}`):**
+
+Applied to both agent bodies and command bodies to rewrite paths, command references, and agent mentions:
+
+```typescript
+export function transformContentFor{Target}(body: string): string {
+  let result = body
+
+  // 1. Rewrite paths (.claude/ → .github/, ~/.claude/ → ~/.{target}/)
+  result = result
+    .replace(/~\/\.claude\//g, `~/.${targetDir}/`)
+    .replace(/\.claude\//g, `.${targetDir}/`)
+
+  // 2. Transform Task agent calls (to natural language)
+  const taskPattern = /Task\s+([a-z][a-z0-9-]*)\(([^)]+)\)/gm
+  result = result.replace(taskPattern, (_match, agentName: string, args: string) => {
+    const skillName = normalize(agentName)
+    return `Use the ${skillName} skill to: ${args.trim()}`
+  })
+
+  // 3. Flatten slash commands (/workflows:plan → /plan)
+  const slashPattern = /(?<![:\w])\/([a-z][a-z0-9_:-]*?)(?=[\s,."')\]}`]|$)/gi
+  result = result.replace(slashPattern, (match, commandName: string) => {
+    if (commandName.includes("/")) return match  // Skip file paths
+    const normalized = normalize(commandName)
+    return `/${normalized}`
+  })
+
+  // 4. Transform @agent-name references
+  const agentPattern = /@([a-z][a-z0-9-]*-(?:agent|reviewer|analyst|...))/gi
+  result = result.replace(agentPattern, (_match, agentName: string) => {
+    return `the ${normalize(agentName)} agent`  // or "rule", "playbook", etc.
+  })
+
+  // 5. Remove examples (if target doesn't support them)
+  result = result.replace(/<examples>[\s\S]*?<\/examples>/g, "")
+
+  return result
+}
+```
+
+**Deduplication Pattern (`uniqueName`):**
+
+Used when target has flat namespaces (Cursor, Copilot, Devin) or when name collisions occur:
+
+```typescript
+function uniqueName(base: string, used: Set<string>): string {
+  if (!used.has(base)) {
+    used.add(base)
+    return base
+  }
+  let index = 2
+  while (used.has(`${base}-${index}`)) {
+    index += 1
+  }
+  const name = `${base}-${index}`
+  used.add(name)
+  return name
+}
+
+function normalizeName(value: string): string {
+  const trimmed = value.trim()
+  if (!trimmed) return "item"
+  const normalized = trimmed
+    .toLowerCase()
+    .replace(/[\\/]+/g, "-")
+    .replace(/[:\s]+/g, "-")
+    .replace(/[^a-z0-9_-]+/g, "-")
+    .replace(/-+/g, "-")
+    .replace(/^-+|-+$/g, "")
+  return normalized || "item"
+}
+
+// Flatten: drops namespace prefix (workflows:plan → plan)
+function flattenCommandName(name: string): string {
+  const normalized = normalizeName(name)
+  return normalized.replace(/^[a-z]+-/, "")  // Drop prefix before first dash
+}
+```
+
+**Key Learnings:**
+
+1. **Pre-scan for cross-references** — If target requires reference names (macros, URIs, IDs), build a map before conversion. Example: Devin needs macro names like `agent_kieran_rails_reviewer`, so pre-scan builds the map.
+
+2. **Content transformation is fragile** — Test extensively. Patterns that work for slash commands might false-match on file paths. Use negative lookahead to skip `/etc`, `/usr`, `/var`, etc.
+
+3. **Simplify heuristics, trust structural mapping** — Don't try to parse agent body for "You are..." or "NEVER do..." patterns. Instead, map agent.description → Overview, agent.body → Procedure, agent.capabilities → Specifications. Heuristics fail on edge cases and are hard to test.
+
+4. **Normalize early and consistently** — Use the same `normalizeName()` function throughout. Inconsistent normalization causes deduplication bugs.
+
+5. **MCP servers need target-specific handling:**
+   - **OpenCode:** Merge into `opencode.json` (preserve user keys)
+   - **Copilot:** Prefix env vars with `COPILOT_MCP_`, emit JSON
+   - **Devin:** Write setup instructions file (config is via web UI)
+   - **Cursor:** Pass through as-is
+
+6. **Warn on unsupported features** — Hooks, Gemini extensions, Kiro-incompatible MCP types. Emit to stderr and continue conversion.
+
+**Reference Implementations:**
+- OpenCode: `src/converters/claude-to-opencode.ts` (most comprehensive)
+- Devin: `src/converters/claude-to-devin.ts` (content transformation + cross-references)
+- Copilot: `src/converters/claude-to-copilot.ts` (MCP prefixing pattern)
+
+---
+
+### Phase 3: Writer (`src/targets/{target}.ts`)
+
+**Purpose:** Write converted bundle to disk in target-specific directory structure
+
+**Key Pattern:**
+
+```typescript
+export async function write{Target}Bundle(outputRoot: string, bundle: {Target}Bundle): Promise<void> {
+  const paths = resolve{Target}Paths(outputRoot)
+  await ensureDir(paths.root)
+
+  // Write each component type
+  if (bundle.agents?.length > 0) {
+    const agentsDir = path.join(paths.root, "agents")
+    for (const agent of bundle.agents) {
+      await writeText(path.join(agentsDir, `${agent.name}.ext`), agent.content + "\n")
+    }
+  }
+
+  if (bundle.commands?.length > 0) {
+    const commandsDir = path.join(paths.root, "commands")
+    for (const command of bundle.commands) {
+      await writeText(path.join(commandsDir, `${command.name}.ext`), command.content + "\n")
+    }
+  }
+
+  // Copy skills (pass-through case)
+  if (bundle.skillDirs?.length > 0) {
+    const skillsDir = path.join(paths.root, "skills")
+    for (const skill of bundle.skillDirs) {
+      await copyDir(skill.sourceDir, path.join(skillsDir, skill.name))
+    }
+  }
+
+  // Write generated skills (converted from commands)
+  if (bundle.generatedSkills?.length > 0) {
+    const skillsDir = path.join(paths.root, "skills")
+    for (const skill of bundle.generatedSkills) {
+      await writeText(path.join(skillsDir, skill.name, "SKILL.md"), skill.content + "\n")
+    }
+  }
+
+  // Write MCP config (target-specific location and format)
+  if (bundle.mcpServers && Object.keys(bundle.mcpServers).length > 0) {
+    const mcpPath = path.join(paths.root, "mcp.json")  // or copilot-mcp-config.json, etc.
+    const backupPath = await backupFile(mcpPath)
+    if (backupPath) {
+      console.log(`Backed up existing MCP config to ${backupPath}`)
+    }
+    await writeJson(mcpPath, { mcpServers: bundle.mcpServers })
+  }
+
+  // Write instructions or setup guides
+  if (bundle.setupInstructions) {
+    const setupPath = path.join(paths.root, "setup-instructions.md")
+    await writeText(setupPath, bundle.setupInstructions + "\n")
+  }
+}
+
+// Avoid double-nesting (.target/.target/)
+function resolve{Target}Paths(outputRoot: string) {
+  const base = path.basename(outputRoot)
+  // If already pointing at .target, write directly into it
+  if (base === ".target") {
+    return { root: outputRoot }
+  }
+  // Otherwise nest under .target
+  return { root: path.join(outputRoot, ".target") }
+}
+```
+
+**Backup Pattern (MCP configs only):**
+
+MCP configs are often pre-existing and user-edited. Backup before overwrite:
+
+```typescript
+// From src/utils/files.ts
+export async function backupFile(filePath: string): Promise<string | null> {
+  if (!existsSync(filePath)) return null
+  const timestamp = new Date().toISOString().replace(/[:.]/g, "-")
+  const dirname = path.dirname(filePath)
+  const basename = path.basename(filePath)
+  const ext = path.extname(basename)
+  const name = basename.slice(0, -ext.length)
+  const backupPath = path.join(dirname, `${name}.${timestamp}${ext}`)
+  await copyFile(filePath, backupPath)
+  return backupPath
+}
+```
+
+**Key Learnings:**
+
+1. **Always check for double-nesting** — If output root is already `.target`, don't nest again. Pattern:
+   ```typescript
+   if (path.basename(outputRoot) === ".target") {
+     return { root: outputRoot }  // Write directly
+   }
+   return { root: path.join(outputRoot, ".target") }  // Nest
+   ```
+
+2. **Use `writeText` and `writeJson` helpers** — These handle directory creation and line endings consistently
+
+3. **Backup MCP configs before overwriting** — MCP JSON files are often hand-edited. Always backup with timestamp.
+
+4. **Empty bundles should succeed gracefully** — Don't fail if a component array is empty. Many plugins may have no commands or no skills.
+
+5. **File extensions matter** — Match target conventions exactly:
+   - Copilot: `.agent.md` (note the dot)
+   - Cursor: `.mdc` for rules
+   - Devin: `.devin.md` for playbooks
+   - OpenCode: `.md` for commands
+
+6. **Permissions for sensitive files** — MCP config with API keys should use `0o600`:
+   ```typescript
+   await writeJson(mcpPath, config, { mode: 0o600 })
+   ```
+
+**Reference Implementations:**
+- Droid: `src/targets/droid.ts` (simpler pattern, good for learning)
+- Copilot: `src/targets/copilot.ts` (double-nesting pattern)
+- Devin: `src/targets/devin.ts` (setup instructions file)
+
+---
+
+### Phase 4: CLI Wiring
+
+**File: `src/targets/index.ts`**
+
+Register the new target in the global target registry:
+
+```typescript
+import { convertClaudeTo{Target} } from "../converters/claude-to-{target}"
+import { write{Target}Bundle } from "./{target}"
+import type { {Target}Bundle } from "../types/{target}"
+
+export const targets: Record<string, TargetHandler<any>> = {
+  // ... existing targets ...
+  {target}: {
+    name: "{target}",
+    implemented: true,
+    convert: convertClaudeTo{Target} as TargetHandler<{Target}Bundle>["convert"],
+    write: write{Target}Bundle as TargetHandler<{Target}Bundle>["write"],
+  },
+}
+```
+
+**File: `src/commands/convert.ts` and `src/commands/install.ts`**
+
+Add output root resolution:
+
+```typescript
+// In resolveTargetOutputRoot()
+if (targetName === "{target}") {
+  return path.join(outputRoot, ".{target}")
+}
+
+// Update --to flag description
+const toDescription = "Target format (opencode | codex | droid | cursor | copilot | kiro | {target})"
+```
+
+---
+
+### Phase 5: Sync Support (Optional)
+
+**File: `src/sync/{target}.ts`**
+
+If the target supports syncing personal skills and MCP servers:
+
+```typescript
+export async function syncTo{Target}(outputRoot: string): Promise<void> {
+  const personalSkillsDir = path.join(expandHome("~/.claude/skills"))
+  const personalSettings = loadSettings(expandHome("~/.claude/settings.json"))
+
+  const skillsDest = path.join(outputRoot, ".{target}", "skills")
+  await ensureDir(skillsDest)
+
+  // Symlink personal skills
+  if (existsSync(personalSkillsDir)) {
+    const skills = readdirSync(personalSkillsDir)
+    for (const skill of skills) {
+      if (!isValidSkillName(skill)) continue
+      const source = path.join(personalSkillsDir, skill)
+      const dest = path.join(skillsDest, skill)
+      await forceSymlink(source, dest)
+    }
+  }
+
+  // Merge MCP servers if applicable
+  if (personalSettings.mcpServers) {
+    const mcpPath = path.join(outputRoot, ".{target}", "mcp.json")
+    const existing = readJson(mcpPath) || {}
+    const merged = {
+      ...existing,
+      mcpServers: {
+        ...existing.mcpServers,
+        ...personalSettings.mcpServers,
+      },
+    }
+    await writeJson(mcpPath, merged, { mode: 0o600 })
+  }
+}
+```
+
+**File: `src/commands/sync.ts`**
+
+```typescript
+// Add to validTargets array
+const validTargets = ["opencode", "codex", "droid", "cursor", "pi", "{target}"] as const
+
+// In resolveOutputRoot()
+case "{target}":
+  return path.join(process.cwd(), ".{target}")
+
+// In main switch
+case "{target}":
+  await syncTo{Target}(outputRoot)
+  break
+```
+
+---
+
+### Phase 6: Tests
+
+**File: `tests/{target}-converter.test.ts`**
+
+Test converter using inline `ClaudePlugin` fixtures:
+
+```typescript
+describe("convertClaudeTo{Target}", () => {
+  it("converts agents to {target} format", () => {
+    const plugin: ClaudePlugin = {
+      name: "test",
+      agents: [
+        {
+          name: "test-agent",
+          description: "Test description",
+          body: "Test body",
+          capabilities: ["Cap 1", "Cap 2"],
+        },
+      ],
+      commands: [],
+      skills: [],
+    }
+
+    const bundle = convertClaudeTo{Target}(plugin, {})
+
+    expect(bundle.agents).toHaveLength(1)
+    expect(bundle.agents[0].name).toBe("test-agent")
+    expect(bundle.agents[0].content).toContain("Test description")
+  })
+
+  it("normalizes agent names", () => {
+    const plugin: ClaudePlugin = {
+      name: "test",
+      agents: [
+        { name: "Test Agent", description: "", body: "", capabilities: [] },
+      ],
+      commands: [],
+      skills: [],
+    }
+
+    const bundle = convertClaudeTo{Target}(plugin, {})
+    expect(bundle.agents[0].name).toBe("test-agent")
+  })
+
+  it("deduplicates colliding names", () => {
+    const plugin: ClaudePlugin = {
+      name: "test",
+      agents: [
+        { name: "Agent Name", description: "", body: "", capabilities: [] },
+        { name: "Agent Name", description: "", body: "", capabilities: [] },
+      ],
+      commands: [],
+      skills: [],
+    }
+
+    const bundle = convertClaudeTo{Target}(plugin, {})
+    expect(bundle.agents.map(a => a.name)).toEqual(["agent-name", "agent-name-2"])
+  })
+
+  it("transforms content paths (.claude → .{target})", () => {
+    const result = transformContentFor{Target}("See ~/.claude/config")
+    expect(result).toContain("~/.{target}/config")
+  })
+
+  it("warns when hooks are present", () => {
+    const spy = jest.spyOn(console, "warn")
+    const plugin: ClaudePlugin = {
+      name: "test",
+      agents: [],
+      commands: [],
+      skills: [],
+      hooks: { hooks: { "file:save": "test" } },
+    }
+
+    convertClaudeTo{Target}(plugin, {})
+    expect(spy).toHaveBeenCalledWith(expect.stringContaining("hooks"))
+  })
+})
+```
+
+**File: `tests/{target}-writer.test.ts`**
+
+Test writer using temp directories (from `tmp` package):
+
+```typescript
+describe("write{Target}Bundle", () => {
+  it("writes agents to {target} format", async () => {
+    const tmpDir = await tmp.dir()
+    const bundle: {Target}Bundle = {
+      agents: [{ name: "test", content: "# Test\nBody" }],
+      commands: [],
+      skillDirs: [],
+    }
+
+    await write{Target}Bundle(tmpDir.path, bundle)
+
+    const written = readFileSync(path.join(tmpDir.path, ".{target}", "agents", "test.ext"), "utf-8")
+    expect(written).toContain("# Test")
+  })
+
+  it("does not double-nest when output root is .{target}", async () => {
+    const tmpDir = await tmp.dir()
+    const targetDir = path.join(tmpDir.path, ".{target}")
+    await ensureDir(targetDir)
+
+    const bundle: {Target}Bundle = {
+      agents: [{ name: "test", content: "# Test" }],
+      commands: [],
+      skillDirs: [],
+    }
+
+    await write{Target}Bundle(targetDir, bundle)
+
+    // Should write to targetDir directly, not targetDir/.{target}
+    const written = path.join(targetDir, "agents", "test.ext")
+    expect(existsSync(written)).toBe(true)
+  })
+
+  it("backs up existing MCP config", async () => {
+    const tmpDir = await tmp.dir()
+    const mcpPath = path.join(tmpDir.path, ".{target}", "mcp.json")
+    await ensureDir(path.dirname(mcpPath))
+    await writeJson(mcpPath, { existing: true })
+
+    const bundle: {Target}Bundle = {
+      agents: [],
+      commands: [],
+      skillDirs: [],
+      mcpServers: { "test": { command: "test" } },
+    }
+
+    await write{Target}Bundle(tmpDir.path, bundle)
+
+    // Backup should exist
+    const backups = readdirSync(path.dirname(mcpPath)).filter(f => f.includes("mcp") && f.includes("-"))
+    expect(backups.length).toBeGreaterThan(0)
+  })
+})
+```
+
+**Key Testing Patterns:**
+
+- Test normalization, deduplication, content transformation separately
+- Use inline plugin fixtures (not file-based)
+- For writer tests, use temp directories and verify file existence
+- Test edge cases: empty names, empty bodies, special characters
+- Test error handling: missing files, permission issues
+
+---
+
+## Documentation Requirements
+
+**File: `docs/specs/{target}.md`**
+
+Document the target format specification:
+
+- Last verified date (link to official docs)
+- Config file locations (project-level vs. user-level)
+- Agent/command/skill format with field descriptions
+- MCP configuration structure
+- Character limits (if any)
+- Example file
+
+**File: `README.md`**
+
+Add to supported targets list and include usage examples.
+
+---
+
+## Common Pitfalls and Solutions
+
+| Pitfall | Solution |
+|---------|----------|
+| **Double-nesting** (`.cursor/.cursor/`) | Check `path.basename(outputRoot)` before nesting |
+| **Inconsistent name normalization** | Use single `normalizeName()` function everywhere |
+| **Fragile content transformation** | Test regex patterns against edge cases (file paths, URLs) |
+| **Heuristic section extraction fails** | Use structural mapping (description → Overview, body → Procedure) instead |
+| **MCP config overwrites user edits** | Always backup with timestamp before overwriting |
+| **Skill body not loaded** | Verify `ClaudeSkill` has `skillPath` field for file reading |
+| **Missing deduplication** | Build `usedNames` set before conversion, pass to each converter |
+| **Unsupported features cause silent loss** | Always warn to stderr (hooks, incompatible MCP types, etc.) |
+| **Test isolation failures** | Use unique temp directories per test, clean up afterward |
+| **Command namespace collisions after flattening** | Use `uniqueName()` with deduplication, test multiple collisions |
+
+---
+
+## Checklist for Adding a New Target
+
+Use this checklist when adding a new target provider:
+
+### Implementation
+- [ ] Create `src/types/{target}.ts` with bundle and component types
+- [ ] Implement `src/converters/claude-to-{target}.ts` with converter and content transformer
+- [ ] Implement `src/targets/{target}.ts` with writer
+- [ ] Register target in `src/targets/index.ts`
+- [ ] Update `src/commands/convert.ts` (add output root resolution, update help text)
+- [ ] Update `src/commands/install.ts` (same as convert.ts)
+- [ ] (Optional) Implement `src/sync/{target}.ts` and update `src/commands/sync.ts`
+
+### Testing
+- [ ] Create `tests/{target}-converter.test.ts` with converter tests
+- [ ] Create `tests/{target}-writer.test.ts` with writer tests
+- [ ] (Optional) Create `tests/sync-{target}.test.ts` with sync tests
+- [ ] Run full test suite: `bun test`
+- [ ] Manual test: `bun run src/index.ts convert --to {target} ./plugins/compound-engineering`
+
+### Documentation
+- [ ] Create `docs/specs/{target}.md` with format specification
+- [ ] Update `README.md` with target in list and usage examples
+- [ ] Update `CHANGELOG.md` with new target
+
+### Version Bumping
+- [ ] Use a `feat(...)` conventional commit so semantic-release cuts the next minor root CLI release on `main`
+- [ ] Do not hand-start a separate root CLI version line in `package.json`; the root package follows the repo `v*` tags and semantic-release writes that version back after release
+- [ ] Update plugin.json description if component counts changed
+- [ ] Verify CHANGELOG entry is clear
+
+---
+
+## References
+
+### Implementation Examples
+
+**Reference implementations by priority (easiest to hardest):**
+
+1. **Droid** (`src/targets/droid.ts`, `src/converters/claude-to-droid.ts`) — Simplest pattern, good learning baseline
+2. **Copilot** (`src/targets/copilot.ts`, `src/converters/claude-to-copilot.ts`) — MCP prefixing, double-nesting guard
+3. **Devin** (`src/converters/claude-to-devin.ts`) — Content transformation, cross-references, intermediate types
+4. **OpenCode** (`src/converters/claude-to-opencode.ts`) — Most comprehensive, handles command structure and config merging
+
+### Key Utilities
+
+- `src/utils/frontmatter.ts` — `formatFrontmatter()` and `parseFrontmatter()`
+- `src/utils/files.ts` — `writeText()`, `writeJson()`, `copyDir()`, `backupFile()`, `ensureDir()`
+- `src/utils/resolve-home.ts` — `expandHome()` for `~/.{target}` path resolution
+
+### Existing Tests
+
+- `tests/cursor-converter.test.ts` — Comprehensive converter tests
+- `tests/copilot-writer.test.ts` — Writer tests with temp directories
+- `tests/sync-copilot.test.ts` — Sync pattern with symlinks and config merge
+
+---
+
+## Related Files
+
+- `/C:/Source/compound-engineering-plugin/.claude-plugin/plugin.json` — Version and component counts
+- `/C:/Source/compound-engineering-plugin/CHANGELOG.md` — Recent additions and patterns
+- `/C:/Source/compound-engineering-plugin/README.md` — Usage examples for all targets
+- `/C:/Source/compound-engineering-plugin/docs/solutions/plugin-versioning-requirements.md` — Checklist for releases
--- a/docs/solutions/plugin-versioning-requirements.md
+++ b/docs/solutions/plugin-versioning-requirements.md
@@ -13,22 +13,22 @@ component: plugin-development

 When making changes to the compound-engineering plugin, documentation can get out of sync with the actual components (agents, commands, skills). This leads to confusion about what's included in each version and makes it difficult to track changes over time.

+This document applies to the embedded marketplace plugin metadata, not the root CLI package release version. The root CLI package (`package.json`, root `CHANGELOG.md`, repo `v*` tags) is managed by semantic-release and follows the repository tag line.
+
 ## Solution

-**Every change to the plugin MUST include:**
+**Routine PRs should not cut plugin releases.**

-1. **Version bump in `plugin.json`**
-   - Follow semantic versioning (semver)
-   - MAJOR: Breaking changes or major reorganization
-   - MINOR: New agents, commands, or skills added
-   - PATCH: Bug fixes, documentation updates, minor improvements
+The embedded plugin version is release-owned metadata. The maintainer uses a local slash command to choose the next version and generate release changelog entries after deciding which merged changes ship together. Because multiple PRs may merge before release, contributors should not guess release versions inside individual PRs.

-2. **CHANGELOG.md update**
-   - Add entry under `## [Unreleased]` or new version section
-   - Use Keep a Changelog format
-   - Categories: Added, Changed, Deprecated, Removed, Fixed, Security
+Contributors should:

-3. **README.md verification**
+1. **Avoid release bookkeeping in normal PRs**
+   - Do not manually bump `.claude-plugin/plugin.json`
+   - Do not manually bump `.claude-plugin/marketplace.json`
+   - Do not cut release sections in `CHANGELOG.md`
+
+2. **Keep substantive docs accurate**
   - Verify component counts match actual files
   - Verify agent/command/skill tables are accurate
   - Update descriptions if functionality changed
@@ -38,8 +38,9 @@ When making changes to the compound-engineering plugin, documentation can get ou
 ```markdown
 Before committing changes to compound-engineering plugin:

- [ ] Version bumped in `.claude-plugin/plugin.json`
- [ ] CHANGELOG.md updated with changes
+- [ ] No manual version bump in `.claude-plugin/plugin.json`
+- [ ] No manual version bump in `.claude-plugin/marketplace.json`
+- [ ] No manual release section added to `CHANGELOG.md`
 - [ ] README.md component counts verified
 - [ ] README.md tables updated (if adding/removing/renaming)
 - [ ] plugin.json description updated (if component counts changed)
@@ -47,8 +48,8 @@ Before committing changes to compound-engineering plugin:

 ## File Locations

- Version: `.claude-plugin/plugin.json` → `"version": "X.Y.Z"`
- Changelog: `CHANGELOG.md`
+- Version is release-owned: `.claude-plugin/plugin.json` and `.claude-plugin/marketplace.json`
+- Changelog release sections are release-owned: `CHANGELOG.md`
 - Readme: `README.md`

 ## Example Workflow
@@ -56,11 +57,10 @@ Before committing changes to compound-engineering plugin:
 When adding a new agent:

 1. Create the agent file in `agents/[category]/`
-2. Bump version in `plugin.json` (minor version for new agent)
-3. Add to CHANGELOG under `### Added`
-4. Add row to README agent table
-5. Update README component count
-6. Update plugin.json description with new counts
+2. Update README agent table
+3. Update README component count
+4. Update plugin metadata description with new counts if needed
+5. Leave version selection and release changelog generation to the maintainer's release command

 ## Prevention

@@ -68,10 +68,12 @@ This documentation serves as a reminder. When Claude Code works on this plugin,

 1. Check this doc before committing changes
 2. Follow the checklist above
-3. Never commit partial updates (all three files must be updated together)
+3. Do not guess release versions in feature PRs

 ## Related Files

- `/Users/kieranklaassen/every-marketplace/plugins/compound-engineering/.claude-plugin/plugin.json`
- `/Users/kieranklaassen/every-marketplace/plugins/compound-engineering/CHANGELOG.md`
- `/Users/kieranklaassen/every-marketplace/plugins/compound-engineering/README.md`
+- `/Users/kieranklaassen/compound-engineering-plugin/plugins/compound-engineering/.claude-plugin/plugin.json`
+- `/Users/kieranklaassen/compound-engineering-plugin/plugins/compound-engineering/CHANGELOG.md`
+- `/Users/kieranklaassen/compound-engineering-plugin/plugins/compound-engineering/README.md`
+- `/Users/kieranklaassen/compound-engineering-plugin/package.json`
+- `/Users/kieranklaassen/compound-engineering-plugin/CHANGELOG.md`
--- a/docs/specs/copilot.md
+++ b/docs/specs/copilot.md
@@ -0,0 +1,122 @@
+# GitHub Copilot Spec (Agents, Skills, MCP)
+
+Last verified: 2026-02-14
+
+## Primary sources
+
+```
+https://docs.github.com/en/copilot/reference/custom-agents-configuration
+https://docs.github.com/en/copilot/concepts/agents/about-agent-skills
+https://docs.github.com/en/copilot/concepts/agents/coding-agent/mcp-and-coding-agent
+```
+
+## Config locations
+
+| Scope | Path |
+|-------|------|
+| Project agents | `.github/agents/*.agent.md` |
+| Project skills | `.github/skills/*/SKILL.md` |
+| Project instructions | `.github/copilot-instructions.md` |
+| Path-specific instructions | `.github/instructions/*.instructions.md` |
+| Project prompts | `.github/prompts/*.prompt.md` |
+| Org/enterprise agents | `.github-private/agents/*.agent.md` |
+| Personal skills | `~/.copilot/skills/*/SKILL.md` |
+| Directory instructions | `AGENTS.md` (nearest ancestor wins) |
+
+## Agents (.agent.md files)
+
+- Custom agents are Markdown files with YAML frontmatter stored in `.github/agents/`.
+- File extension is `.agent.md` (or `.md`). Filenames may only contain: `.`, `-`, `_`, `a-z`, `A-Z`, `0-9`.
+- `description` is the only required frontmatter field.
+
+### Frontmatter fields
+
+| Field | Required | Default | Description |
+|-------|----------|---------|-------------|
+| `name` | No | Derived from filename | Display name |
+| `description` | **Yes** | — | What the agent does |
+| `tools` | No | `["*"]` | Tool access list. `[]` disables all tools. |
+| `target` | No | both | `vscode`, `github-copilot`, or omit for both |
+| `infer` | No | `true` | Auto-select based on task context |
+| `model` | No | Platform default | AI model (works in IDE, may be ignored on github.com) |
+| `mcp-servers` | No | — | MCP config (org/enterprise agents only) |
+| `metadata` | No | — | Arbitrary key-value annotations |
+
+### Character limit
+
+Agent body content is limited to **30,000 characters**.
+
+### Tool names
+
+| Name | Aliases | Purpose |
+|------|---------|---------|
+| `execute` | `shell`, `Bash` | Run shell commands |
+| `read` | `Read` | Read files |
+| `edit` | `Edit`, `Write` | Modify files |
+| `search` | `Grep`, `Glob` | Search files |
+| `agent` | `Task` | Invoke other agents |
+| `web` | `WebSearch`, `WebFetch` | Web access |
+
+## Skills (SKILL.md)
+
+- Skills follow the open SKILL.md standard (same format as Claude Code and Cursor).
+- A skill is a directory containing `SKILL.md` plus optional `scripts/`, `references/`, and `assets/`.
+- YAML frontmatter requires `name` and `description` fields.
+- Skills are loaded on-demand when Copilot determines relevance.
+
+### Discovery locations
+
+| Scope | Path |
+|-------|------|
+| Project | `.github/skills/*/SKILL.md` |
+| Project (Claude-compatible) | `.claude/skills/*/SKILL.md` |
+| Project (auto-discovery) | `.agents/skills/*/SKILL.md` |
+| Personal | `~/.copilot/skills/*/SKILL.md` |
+
+## MCP (Model Context Protocol)
+
+- MCP configuration is set via **Repository Settings > Copilot > Coding agent > MCP configuration** on GitHub.
+- Repository-level agents **cannot** define MCP servers inline; use repository settings instead.
+- Org/enterprise agents can embed MCP server definitions in frontmatter.
+- All env var names must use the `COPILOT_MCP_` prefix.
+- Only MCP tools are supported (not resources or prompts).
+
+### Config structure
+
+```json
+{
+  "mcpServers": {
+    "server-name": {
+      "type": "local",
+      "command": "npx",
+      "args": ["package"],
+      "tools": ["*"],
+      "env": {
+        "API_KEY": "COPILOT_MCP_API_KEY"
+      }
+    }
+  }
+}
+```
+
+### Server types
+
+| Type | Fields |
+|------|--------|
+| Local/stdio | `type: "local"`, `command`, `args`, `tools`, `env` |
+| Remote/SSE | `type: "sse"`, `url`, `tools`, `headers` |
+
+## Prompts (.prompt.md)
+
+- Reusable prompt files stored in `.github/prompts/`.
+- Available in VS Code, Visual Studio, and JetBrains IDEs only (not on github.com).
+- Invoked via `/promptname` in chat.
+- Support variable syntax: `${input:name}`, `${file}`, `${selection}`.
+
+## Precedence
+
+1. Repository-level agents
+2. Organization-level agents (`.github-private`)
+3. Enterprise-level agents (`.github-private`)
+
+Within a repo, `AGENTS.md` files in directories provide nearest-ancestor-wins instructions.
--- a/docs/specs/kiro.md
+++ b/docs/specs/kiro.md
@@ -0,0 +1,171 @@
+# Kiro CLI Spec (Custom Agents, Skills, Steering, MCP, Settings)
+
+Last verified: 2026-02-17
+
+## Primary sources
+
+```
+https://kiro.dev/docs/cli/
+https://kiro.dev/docs/cli/custom-agents/configuration-reference/
+https://kiro.dev/docs/cli/skills/
+https://kiro.dev/docs/cli/steering/
+https://kiro.dev/docs/cli/mcp/
+https://kiro.dev/docs/cli/hooks/
+https://agentskills.io
+```
+
+## Config locations
+
+- Project-level config: `.kiro/` directory at project root.
+- No global/user-level config directory — all config is project-scoped.
+
+## Directory structure
+
+```
+.kiro/
+├── agents/
+│   ├── <name>.json              # Agent configuration
+│   └── prompts/
+│       └── <name>.md            # Agent prompt files
+├── skills/
+│   └── <name>/
+│       └── SKILL.md             # Skill definition
+├── steering/
+│   └── <name>.md                # Always-on context files
+└── settings/
+    └── mcp.json                 # MCP server configuration
+```
+
+## Custom agents (JSON config + prompt files)
+
+- Custom agents are JSON files in `.kiro/agents/`.
+- Each agent has a corresponding prompt `.md` file, referenced via `file://` URI.
+- Agent config has 14 possible fields (see below).
+- Agents are activated by user selection (no auto-activation).
+- The converter outputs a subset of fields relevant to converted plugins.
+
+### Agent config fields
+
+| Field | Type | Used in conversion | Notes |
+|---|---|---|---|
+| `name` | string | Yes | Agent display name |
+| `description` | string | Yes | Human-readable description |
+| `prompt` | string or `file://` URI | Yes | System prompt or file reference |
+| `tools` | string[] | Yes (`["*"]`) | Available tools |
+| `resources` | string[] | Yes | `file://`, `skill://`, `knowledgeBase` URIs |
+| `includeMcpJson` | boolean | Yes (`true`) | Inherit project MCP servers |
+| `welcomeMessage` | string | Yes | Agent switch greeting |
+| `mcpServers` | object | No | Per-agent MCP config (use includeMcpJson instead) |
+| `toolAliases` | Record | No | Tool name remapping |
+| `allowedTools` | string[] | No | Auto-approve patterns |
+| `toolsSettings` | object | No | Per-tool configuration |
+| `hooks` | object | No (future work) | 5 trigger types |
+| `model` | string | No | Model selection |
+| `keyboardShortcut` | string | No | Quick-switch shortcut |
+
+### Example agent config
+
+```json
+{
+  "name": "security-reviewer",
+  "description": "Reviews code for security vulnerabilities",
+  "prompt": "file://./prompts/security-reviewer.md",
+  "tools": ["*"],
+  "resources": [
+    "file://.kiro/steering/**/*.md",
+    "skill://.kiro/skills/**/SKILL.md"
+  ],
+  "includeMcpJson": true,
+  "welcomeMessage": "Switching to security-reviewer. Reviews code for security vulnerabilities"
+}
+```
+
+## Skills (SKILL.md standard)
+
+- Skills follow the open [Agent Skills](https://agentskills.io) standard.
+- A skill is a folder containing `SKILL.md` plus optional supporting files.
+- Skills live in `.kiro/skills/`.
+- `SKILL.md` uses YAML frontmatter with `name` and `description` fields.
+- Kiro activates skills on demand based on description matching.
+- The `description` field is critical — Kiro uses it to decide when to activate the skill.
+
+### Constraints
+
+- Skill name: max 64 characters, pattern `^[a-z][a-z0-9-]*$`, no consecutive hyphens (`--`).
+- Skill description: max 1024 characters.
+- Skill name must match parent directory name.
+
+### Example
+
+```yaml
+---
+name: workflows-plan
+description: Plan work by analyzing requirements and creating actionable steps
+---
+
+# Planning Workflow
+
+Detailed instructions...
+```
+
+## Steering files
+
+- Markdown files in `.kiro/steering/`.
+- Always loaded into every agent session's context.
+- Equivalent to Claude Code's CLAUDE.md.
+- Used for project-wide instructions, coding standards, and conventions.
+
+## MCP server configuration
+
+- MCP servers are configured in `.kiro/settings/mcp.json`.
+- **Only stdio transport is supported** — `command` + `args` + `env`.
+- HTTP/SSE transport (`url`, `headers`) is NOT supported by Kiro CLI.
+- The converter skips HTTP-only MCP servers with a warning.
+
+### Example
+
+```json
+{
+  "mcpServers": {
+    "playwright": {
+      "command": "npx",
+      "args": ["-y", "@anthropic/mcp-playwright"]
+    },
+    "context7": {
+      "command": "npx",
+      "args": ["-y", "@context7/mcp-server"]
+    }
+  }
+}
+```
+
+## Hooks
+
+- Kiro supports 5 hook trigger types: `agentSpawn`, `userPromptSubmit`, `preToolUse`, `postToolUse`, `stop`.
+- Hooks are configured inside agent JSON configs (not separate files).
+- 3 of 5 triggers map to Claude Code hooks (`preToolUse`, `postToolUse`, `stop`).
+- Not converted by the plugin converter for MVP — a warning is emitted.
+
+## Conversion lossy mappings
+
+| Claude Code Feature | Kiro Status | Notes |
+|---|---|---|
+| `Edit` tool (surgical replacement) | Degraded -> `write` (full-file) | Kiro write overwrites entire files |
+| `context: fork` | Lost | No execution isolation control |
+| `!`command`` dynamic injection | Lost | No pre-processing of markdown |
+| `disable-model-invocation` | Lost | No invocation control |
+| `allowed-tools` per skill | Lost | No tool permission scoping per skill |
+| `$ARGUMENTS` interpolation | Lost | No structured argument passing |
+| Claude hooks | Skipped | Future follow-up (near-1:1 for 3/5 triggers) |
+| HTTP MCP servers | Skipped | Kiro only supports stdio transport |
+
+## Overwrite behavior during conversion
+
+| Content Type | Strategy | Rationale |
+|---|---|---|
+| Generated agents (JSON + prompt) | Overwrite | Generated, not user-authored |
+| Generated skills (from commands) | Overwrite | Generated, not user-authored |
+| Copied skills (pass-through) | Overwrite | Plugin is source of truth |
+| Steering files | Overwrite | Generated from CLAUDE.md |
+| `mcp.json` | Merge with backup | User may have added their own servers |
+| User-created agents/skills | Preserved | Don't delete orphans |
--- a/docs/specs/windsurf.md
+++ b/docs/specs/windsurf.md
@@ -0,0 +1,477 @@
+# Windsurf Editor Global Configuration Guide
+
+> **Purpose**: Technical reference for programmatically creating and managing Windsurf's global Skills, Workflows, and Rules.
+>
+> **Source**: Official Windsurf documentation at [docs.windsurf.com](https://docs.windsurf.com) + local file analysis.
+>
+> **Last Updated**: February 2026
+
+---
+
+## Table of Contents
+
+1. [Overview](#overview)
+2. [Base Directory Structure](#base-directory-structure)
+3. [Skills](#skills)
+4. [Workflows](#workflows)
+5. [Rules](#rules)
+6. [Memories](#memories)
+7. [System-Level Configuration (Enterprise)](#system-level-configuration-enterprise)
+8. [Programmatic Creation Reference](#programmatic-creation-reference)
+9. [Best Practices](#best-practices)
+
+---
+
+## Overview
+
+Windsurf provides three main customization mechanisms:
+
+| Feature | Purpose | Invocation |
+|---------|---------|------------|
+| **Skills** | Complex multi-step tasks with supporting resources | Automatic (progressive disclosure) or `@skill-name` |
+| **Workflows** | Reusable step-by-step procedures | Slash command `/workflow-name` |
+| **Rules** | Behavioral guidelines and preferences | Trigger-based (always-on, glob, manual, or model decision) |
+
+All three support both **workspace-level** (project-specific) and **global** (user-wide) scopes.
+
+---
+
+## Base Directory Structure
+
+### Global Configuration Root
+
+| OS | Path |
+|----|------|
+| **Windows** | `C:\Users\{USERNAME}\.codeium\windsurf\` |
+| **macOS** | `~/.codeium/windsurf/` |
+| **Linux** | `~/.codeium/windsurf/` |
+
+### Directory Layout
+
+```
+~/.codeium/windsurf/
+├── skills/                    # Global skills (directories)
+│   └── {skill-name}/
+│       └── SKILL.md
+├── global_workflows/           # Global workflows (flat .md files)
+│   └── {workflow-name}.md
+├── rules/                     # Global rules (flat .md files)  
+│   └── {rule-name}.md
+├── memories/
+│   ├── global_rules.md        # Always-on global rules (plain text)
+│   └── *.pb                   # Auto-generated memories (protobuf)
+├── mcp_config.json            # MCP server configuration
+└── user_settings.pb           # User settings (protobuf)
+```
+
+---
+
+## Skills
+
+Skills bundle instructions with supporting resources for complex, multi-step tasks. Cascade uses **progressive disclosure** to automatically invoke skills when relevant.
+
+### Storage Locations
+
+| Scope | Location |
+|-------|----------|
+| **Global** | `~/.codeium/windsurf/skills/{skill-name}/SKILL.md` |
+| **Workspace** | `.windsurf/skills/{skill-name}/SKILL.md` |
+
+### Directory Structure
+
+Each skill is a **directory** (not a single file) containing:
+
+```
+{skill-name}/
+├── SKILL.md              # Required: Main skill definition
+├── references/           # Optional: Reference documentation
+├── assets/               # Optional: Images, diagrams, etc.
+├── scripts/              # Optional: Helper scripts
+└── {any-other-files}     # Optional: Templates, configs, etc.
+```
+
+### SKILL.md Format
+
+```markdown
+---
+name: skill-name
+description: Brief description shown to model to help it decide when to invoke the skill
+---
+
+# Skill Title
+
+Instructions for the skill go here in markdown format.
+
+## Section 1
+Step-by-step guidance...
+
+## Section 2
+Reference supporting files using relative paths:
+- See [deployment-checklist.md](./deployment-checklist.md)
+- Run script: [deploy.sh](./scripts/deploy.sh)
+```
+
+### Required YAML Frontmatter Fields
+
+| Field | Required | Description |
+|-------|----------|-------------|
+| `name` | **Yes** | Unique identifier (lowercase letters, numbers, hyphens only). Must match directory name. |
+| `description` | **Yes** | Explains what the skill does and when to use it. Critical for automatic invocation. |
+
+### Naming Convention
+
+- Use **lowercase-kebab-case**: `deploy-to-staging`, `code-review`, `setup-dev-environment`
+- Name must match the directory name exactly
+
+### Invocation Methods
+
+1. **Automatic**: Cascade automatically invokes when request matches skill description
+2. **Manual**: Type `@skill-name` in Cascade input
+
+### Example: Complete Skill
+
+```
+~/.codeium/windsurf/skills/deploy-to-production/
+├── SKILL.md
+├── deployment-checklist.md
+├── rollback-procedure.md
+└── config-template.yaml
+```
+
+**SKILL.md:**
+```markdown
+---
+name: deploy-to-production
+description: Guides the deployment process to production with safety checks. Use when deploying to prod, releasing, or pushing to production environment.
+---
+
+## Pre-deployment Checklist
+1. Run all tests
+2. Check for uncommitted changes
+3. Verify environment variables
+
+## Deployment Steps
+Follow these steps to deploy safely...
+
+See [deployment-checklist.md](./deployment-checklist.md) for full checklist.
+See [rollback-procedure.md](./rollback-procedure.md) if issues occur.
+```
+
+---
+
+## Workflows
+
+Workflows define step-by-step procedures invoked via slash commands. They guide Cascade through repetitive tasks.
+
+### Storage Locations
+
+| Scope | Location |
+|-------|----------|
+| **Global** | `~/.codeium/windsurf/global_workflows/{workflow-name}.md` |
+| **Workspace** | `.windsurf/workflows/{workflow-name}.md` |
+
+### File Format
+
+Workflows are **single markdown files** (not directories):
+
+```markdown
+---
+description: Short description of what the workflow does
+---
+
+# Workflow Title
+
+> Arguments: [optional arguments description]
+
+Step-by-step instructions in markdown.
+
+1. First step
+2. Second step
+3. Third step
+```
+
+### Required YAML Frontmatter Fields
+
+| Field | Required | Description |
+|-------|----------|-------------|
+| `description` | **Yes** | Short title/description shown in UI |
+
+### Invocation
+
+- Slash command: `/workflow-name`
+- Filename becomes the command (e.g., `deploy.md` → `/deploy`)
+
+### Constraints
+
+- **Character limit**: 12,000 characters per workflow file
+- Workflows can call other workflows: Include instructions like "Call `/other-workflow`"
+
+### Example: Complete Workflow
+
+**File**: `~/.codeium/windsurf/global_workflows/address-pr-comments.md`
+
+```markdown
+---
+description: Address all PR review comments systematically
+---
+
+# Address PR Comments
+
+> Arguments: [PR number]
+
+1. Check out the PR branch: `gh pr checkout [id]`
+
+2. Get comments on PR:
+   ```bash
+   gh api --paginate repos/[owner]/[repo]/pulls/[id]/comments | jq '.[] | {user: .user.login, body, path, line}'
+   ```
+
+3. For EACH comment:
+   a. Print: "(index). From [user] on [file]:[lines] — [body]"
+   b. Analyze the file and line range
+   c. If unclear, ask for clarification
+   d. Make the change before moving to next comment
+
+4. Summarize what was done and which comments need attention
+```
+
+---
+
+## Rules
+
+Rules provide persistent behavioral guidelines that influence how Cascade responds.
+
+### Storage Locations
+
+| Scope | Location |
+|-------|----------|
+| **Global** | `~/.codeium/windsurf/rules/{rule-name}.md` |
+| **Workspace** | `.windsurf/rules/{rule-name}.md` |
+
+### File Format
+
+Rules are **single markdown files**:
+
+```markdown
+---
+description: When to use this rule
+trigger: activation_mode
+globs: ["*.py", "src/**/*.ts"]
+---
+
+Rule instructions in markdown format.
+
+- Guideline 1
+- Guideline 2
+- Guideline 3
+```
+
+### YAML Frontmatter Fields
+
+| Field | Required | Description |
+|-------|----------|-------------|
+| `description` | **Yes** | Describes when to use the rule |
+| `trigger` | Optional | Activation mode (see below) |
+| `globs` | Optional | File patterns for glob trigger |
+
+### Activation Modes (trigger field)
+
+| Mode | Value | Description |
+|------|-------|-------------|
+| **Manual** | `manual` | Activated via `@mention` in Cascade input |
+| **Always On** | `always` | Always applied to every conversation |
+| **Model Decision** | `model_decision` | Model decides based on description |
+| **Glob** | `glob` | Applied when working with files matching pattern |
+
+### Constraints
+
+- **Character limit**: 12,000 characters per rule file
+
+### Example: Complete Rule
+
+**File**: `~/.codeium/windsurf/rules/python-style.md`
+
+```markdown
+---
+description: Python coding standards and style guidelines. Use when writing or reviewing Python code.
+trigger: glob
+globs: ["*.py", "**/*.py"]
+---
+
+# Python Coding Guidelines
+
+- Use type hints for all function parameters and return values
+- Follow PEP 8 style guide
+- Use early returns when possible
+- Always add docstrings to public functions and classes
+- Prefer f-strings over .format() or % formatting
+- Use pathlib instead of os.path for file operations
+```
+
+---
+
+## Memories
+
+### Global Rules (Always-On)
+
+**Location**: `~/.codeium/windsurf/memories/global_rules.md`
+
+This is a special file for rules that **always apply** to all conversations. Unlike rules in the `rules/` directory, this file:
+
+- Does **not** require YAML frontmatter
+- Is plain text/markdown
+- Is always active (no trigger configuration)
+
+**Format:**
+```markdown
+Plain text rules that always apply to all conversations.
+
+- Rule 1
+- Rule 2
+- Rule 3
+```
+
+### Auto-Generated Memories
+
+Cascade automatically creates memories during conversations, stored as `.pb` (protobuf) files in `~/.codeium/windsurf/memories/`. These are managed by Windsurf and should not be manually edited.
+
+---
+
+## System-Level Configuration (Enterprise)
+
+Enterprise organizations can deploy system-level configurations that apply globally and cannot be modified by end users.
+
+### System-Level Paths
+
+| Type | Windows | macOS | Linux/WSL |
+|------|---------|-------|-----------|
+| **Rules** | `C:\ProgramData\Windsurf\rules\*.md` | `/Library/Application Support/Windsurf/rules/*.md` | `/etc/windsurf/rules/*.md` |
+| **Workflows** | `C:\ProgramData\Windsurf\workflows\*.md` | `/Library/Application Support/Windsurf/workflows/*.md` | `/etc/windsurf/workflows/*.md` |
+
+### Precedence Order
+
+When items with the same name exist at multiple levels:
+
+1. **System** (highest priority) - Organization-wide, deployed by IT
+2. **Workspace** - Project-specific in `.windsurf/`
+3. **Global** - User-defined in `~/.codeium/windsurf/`
+4. **Built-in** - Default items provided by Windsurf
+
+---
+
+## Programmatic Creation Reference
+
+### Quick Reference Table
+
+| Type | Path Pattern | Format | Key Fields |
+|------|--------------|--------|------------|
+| **Skill** | `skills/{name}/SKILL.md` | YAML frontmatter + markdown | `name`, `description` |
+| **Workflow** | `global_workflows/{name}.md` (global) or `workflows/{name}.md` (workspace) | YAML frontmatter + markdown | `description` |
+| **Rule** | `rules/{name}.md` | YAML frontmatter + markdown | `description`, `trigger`, `globs` |
+| **Global Rules** | `memories/global_rules.md` | Plain text/markdown | None |
+
+### Minimal Templates
+
+#### Skill (SKILL.md)
+```markdown
+---
+name: my-skill
+description: What this skill does and when to use it
+---
+
+Instructions here.
+```
+
+#### Workflow
+```markdown
+---
+description: What this workflow does
+---
+
+1. Step one
+2. Step two
+```
+
+#### Rule
+```markdown
+---
+description: When this rule applies
+trigger: model_decision
+---
+
+- Guideline one
+- Guideline two
+```
+
+### Validation Checklist
+
+When programmatically creating items:
+
+- [ ] **Skills**: Directory exists with `SKILL.md` inside
+- [ ] **Skills**: `name` field matches directory name exactly
+- [ ] **Skills**: Name uses only lowercase letters, numbers, hyphens
+- [ ] **Workflows/Rules**: File is `.md` extension
+- [ ] **All**: YAML frontmatter uses `---` delimiters
+- [ ] **All**: `description` field is present and meaningful
+- [ ] **All**: File size under 12,000 characters (workflows/rules)
+
+---
+
+## Best Practices
+
+### Writing Effective Descriptions
+
+The `description` field is critical for automatic invocation. Be specific:
+
+**Good:**
+```yaml
+description: Guides deployment to staging environment with pre-flight checks. Use when deploying to staging, testing releases, or preparing for production.
+```
+
+**Bad:**
+```yaml
+description: Deployment stuff
+```
+
+### Formatting Guidelines
+
+- Use bullet points and numbered lists (easier for Cascade to follow)
+- Use markdown headers to organize sections
+- Keep rules concise and specific
+- Avoid generic rules like "write good code" (already built-in)
+
+### XML Tags for Grouping
+
+XML tags can effectively group related rules:
+
+```markdown
+<coding_guidelines>
+- Use early returns when possible
+- Always add documentation for new functions
+- Prefer composition over inheritance
+</coding_guidelines>
+
+<testing_requirements>
+- Write unit tests for all public methods
+- Maintain 80% code coverage
+</testing_requirements>
+```
+
+### Skills vs Rules vs Workflows
+
+| Use Case | Recommended |
+|----------|-------------|
+| Multi-step procedure with supporting files | **Skill** |
+| Repeatable CLI/automation sequence | **Workflow** |
+| Coding style preferences | **Rule** |
+| Project conventions | **Rule** |
+| Deployment procedure | **Skill** or **Workflow** |
+| Code review checklist | **Skill** |
+
+---
+
+## Additional Resources
+
+- **Official Documentation**: [docs.windsurf.com](https://docs.windsurf.com)
+- **Skills Specification**: [agentskills.io](https://agentskills.io/home)
+- **Rule Templates**: [windsurf.com/editor/directory](https://windsurf.com/editor/directory)
--- a/package.json
+++ b/package.json
@@ -1,11 +1,13 @@
 {
  "name": "@every-env/compound-plugin",
-  "version": "0.7.0",
+  "version": "2.37.1",
  "type": "module",
  "private": false,
  "bin": {
-    "compound-plugin": "./src/index.ts"
+    "compound-plugin": "src/index.ts"
  },
+  "homepage": "https://github.com/EveryInc/compound-engineering-plugin",
+  "repository": "https://github.com/EveryInc/compound-engineering-plugin",
  "publishConfig": {
    "access": "public"
  },
@@ -14,13 +16,17 @@
    "convert": "bun run src/index.ts convert",
    "list": "bun run src/index.ts list",
    "cli:install": "bun run src/index.ts install",
-    "test": "bun test"
+    "test": "bun test",
+    "release:dry-run": "semantic-release --dry-run"
  },
  "dependencies": {
    "citty": "^0.1.6",
    "js-yaml": "^4.1.0"
  },
  "devDependencies": {
-    "bun-types": "^1.0.0"
+    "@semantic-release/changelog": "^6.0.3",
+    "@semantic-release/git": "^10.0.1",
+    "bun-types": "^1.0.0",
+    "semantic-release": "^25.0.3"
  }
 }
--- a/plans/grow-your-own-garden-plugin-architecture.md
+++ b/plans/grow-your-own-garden-plugin-architecture.md
@@ -1,102 +0,0 @@
-# Grow Your Own Garden: Adaptive Agent Ecosystem
-
-> **Issue:** https://github.com/EveryInc/compound-engineering-plugin/issues/20
-
-## The Idea
-
-Everyone grows their own garden, but we're all using the same process.
-
-Start from a **seed** (minimal core: `/plan`, `/work`, `/review`, `/compound`). Each `/compound` loop can suggest adding agents based on what you're working on—like building up a test suite to prevent regressions, but for code review expertise.
-
-## Current Problem
-
- Monolithic plugin: 24 agents, users use ~30%
- No personalization (same agents for Rails dev and Python dev)
- Static collection that doesn't adapt
-
-## Proposed Solution
-
-### The Seed (Core Plugin)
-
-4 commands + minimal agents:
-
-| Component | What's Included |
-|-----------|-----------------|
-| Commands | `/plan`, `/work`, `/review`, `/compound` |
-| Review Agents | security, performance, simplicity, architecture, patterns |
-| Research Agents | best-practices, framework-docs, git-history, repo-analyst |
-| Skills | compound-docs, file-todos, git-worktree |
-| MCP Servers | playwright, context7 |
-
-### The Growth Loop
-
-After each `/compound`:
-
-```
-✅ Learning documented
-
-💡 It looks like you're using Rails.
-   Would you like to add the "DHH Rails Reviewer"?
-
-   [y] Yes  [n] No  [x] Never ask
-```
-
-Three sources of new agents:
-1. **Predefined** - "You're using Rails, add DHH reviewer?"
-2. **Dynamic** - "You're using actor model, create an expert?"
-3. **Custom** - "Want to create an agent for this pattern?"
-
-### Agent Storage
-
-```
-.claude/agents/       → Project-specific (highest priority)
-~/.claude/agents/     → User's garden
-plugin/agents/        → From installed plugins
-```
-
-## Implementation Phases
-
-### Phase 1: Split the Plugin
- Create `agent-library/` with framework-specific agents (Rails, Python, TypeScript, Frontend)
- Keep `compound-engineering` as core with universal agents
- No breaking changes—existing users unaffected
-
-### Phase 2: Agent Discovery
- `/review` discovers agents from all three locations
- Project agents override user agents override plugin agents
-
-### Phase 3: Growth via /compound
- Detect tech stack (Gemfile, package.json, etc.)
- Suggest relevant agents after documenting learnings
- Install accepted agents to `~/.claude/agents/`
-
-### Phase 4: Management
- `/agents list` - See your garden
- `/agents add <name>` - Add from library
- `/agents disable <name>` - Temporarily disable
-
-## What Goes Where
-
-**Core (seed):** 11 framework-agnostic agents
- security-sentinel, performance-oracle, code-simplicity-reviewer
- architecture-strategist, pattern-recognition-specialist
- 4 research agents, 2 workflow agents
-
-**Agent Library:** 10 specialized agents
- Rails: kieran-rails, dhh-rails, data-integrity (3)
- Python: kieran-python (1)
- TypeScript: kieran-typescript (1)
- Frontend: julik-races, design-iterator, design-reviewer, figma-sync (4)
- Editorial: every-style-editor (1)
-
-## Key Constraint
-
-Claude Code doesn't support plugin dependencies. Each plugin must be independent. Users manually install what they need, or we suggest additions via `/compound`.
-
-## Acceptance Criteria
-
- [ ] Core plugin works standalone with universal agents
- [ ] `/compound` suggests agents based on detected tech stack
- [ ] Users can accept/decline suggestions
- [ ] `/agents` command for garden management
- [ ] No breaking changes for existing users
--- a/plans/landing-page-launchkit-refresh.md
+++ b/plans/landing-page-launchkit-refresh.md
@@ -1,279 +0,0 @@
-# Landing Page LaunchKit Refresh
-
-## Overview
-
-Review and enhance the `/docs/index.html` landing page using LaunchKit elements and Pragmatic Technical Writing style (Hunt/Thomas, Joel Spolsky). The current implementation is strong but can be refined section-by-section.
-
-## Current State Assessment
-
-### What's Working Well
- Specific, outcome-focused hero headline ("12 expert opinions in 30 seconds")
- Developer-authentic copywriting (N+1 queries, CORS, SQL injection)
- Stats section with clear metrics (23 agents, 16 commands, 11 skills, 2 MCP servers)
- Philosophy section with concrete story (N+1 query bug)
- Three-step installation with actual commands
- FAQ accordion following LaunchKit patterns
- Categorized feature sections with code examples
-
-### Missing Elements (From Best Practices Research)
-1. **Social Proof Section** - No testimonials, GitHub stars, or user metrics
-2. **Visual Demo** - No GIF/animation showing the tool in action
-3. **Arrow icons on CTAs** - 26% conversion boost from studies
-4. **Trust indicators** - Open source badge, license info
-
---
-
-## Section-by-Section Review Plan
-
-### 1. Hero Section (lines 56-78)
-
-**Current:**
-```html
-<h1>Your Code Reviews Just Got 12 Expert Opinions. In 30 Seconds.</h1>
-```
-
-**Review Checklist:**
- [ ] Headline follows Pragmatic Writing (concrete before abstract) ✅
- [ ] Eyebrow badge is current (Version 2.6.0) - verify
- [ ] Description paragraph under 3 sentences ✅
- [ ] Button group has arrow icon on primary CTA
- [ ] "Read the Docs" secondary CTA present ✅
-
-**Potential Improvements:**
- Add `→` arrow to "Install Plugin" button
- Consider adding animated terminal GIF below buttons showing `/review` in action
-
-### 2. Stats Section (lines 81-104)
-
-**Current:** 4 stat cards (23 agents, 16 commands, 11 skills, 2 MCP servers)
-
-**Review Checklist:**
- [ ] Numbers are accurate (verify against actual file counts)
- [ ] Icons are appropriate for each stat
- [ ] Hover effects working properly
- [ ] Mobile layout (2x2 grid) is readable
-
-**Potential Improvements:**
- Add "developers using" or "reviews run" metric if available
- Consider adding subtle animation on scroll
-
-### 3. Philosophy Section (lines 107-192)
-
-**Current:** "Why Your Third Code Review Should Be Easier Than Your First" with N+1 query story
-
-**Review Checklist:**
- [ ] Opens with concrete story (N+1 query) ✅
- [ ] Quote block is memorable and quotable
- [ ] Four pillars (Plan, Delegate, Assess, Codify) are clear
- [ ] Each pillar has: tagline, description, tool tags
- [ ] Descriptions use "you" voice ✅
-
-**Potential Improvements:**
- Review pillar descriptions for passive voice
- Ensure each pillar description follows PAS (Problem, Agitate, Solve) pattern
- Check tool tags are accurate and current
-
-### 4. Agents Section (lines 195-423)
-
-**Current:** 23 agents in 5 categories (Review, Research, Design, Workflow, Docs)
-
-**Review Checklist:**
- [ ] All 23 agents are listed (count actual files)
- [ ] Categories are logical and scannable
- [ ] Each card has: name, badge, description, usage code
- [ ] Descriptions are conversational (not passive)
- [ ] Critical badges (Security, Data) stand out
-
-**Potential Improvements:**
- Review agent descriptions against pragmatic writing checklist
- Ensure descriptions answer "when would I use this?"
- Add concrete scenarios to generic descriptions
-
-### 5. Commands Section (lines 426-561)
-
-**Current:** 16 commands in 2 categories (Workflow, Utility)
-
-**Review Checklist:**
- [ ] All 16 commands are listed (count actual files)
- [ ] Core workflow commands are highlighted
- [ ] Descriptions are action-oriented
- [ ] Command names match actual implementation
-
-**Potential Improvements:**
- Review command descriptions for passive voice
- Lead with outcomes, not features
- Add "saves you X minutes" framing where appropriate
-
-### 6. Skills Section (lines 564-703)
-
-**Current:** 11 skills in 3 categories (Development, Content/Workflow, Image Generation)
-
-**Review Checklist:**
- [ ] All 11 skills are listed (count actual directories)
- [ ] Featured skill (gemini-imagegen) is properly highlighted
- [ ] API key requirement is clear
- [ ] Skill invocation syntax is correct
-
-**Potential Improvements:**
- Review skill descriptions against pragmatic writing
- Ensure each skill answers "what problem does this solve?"
-
-### 7. MCP Servers Section (lines 706-751)
-
-**Current:** 2 MCP servers (Playwright, Context7)
-
-**Review Checklist:**
- [ ] Tool lists are accurate
- [ ] Descriptions explain WHY not just WHAT
- [ ] Framework support list is current (100+)
-
-**Potential Improvements:**
- Add concrete example of each server in action
- Consider before/after comparison
-
-### 8. Installation Section (lines 754-798)
-
-**Current:** "Three Commands. Zero Configuration." with 3 steps
-
-**Review Checklist:**
- [ ] Commands are accurate and work
- [ ] Step 3 shows actual usage examples
- [ ] Timeline visual (vertical line) renders correctly
- [ ] Copy buttons work on code blocks
-
-**Potential Improvements:**
- Add copy-to-clipboard functionality if missing
- Consider adding "What you'll see" output example
-
-### 9. FAQ Section (lines 801-864)
-
-**Current:** 5 questions in accordion format
-
-**Review Checklist:**
- [ ] Questions address real objections
- [ ] Answers are conversational (use "you")
- [ ] Accordion expand/collapse works
- [ ] No passive voice in answers
-
-**Potential Improvements:**
- Review for weasel words ("best practices suggest")
- Ensure answers are direct and actionable
-
-### 10. CTA Section (lines 868-886)
-
-**Current:** "Install Once. Compound Forever." with Install + GitHub buttons
-
-**Review Checklist:**
- [ ] Badge is eye-catching ("Free & Open Source")
- [ ] Headline restates core value proposition
- [ ] Primary CTA has arrow icon ✅
- [ ] Trust line at bottom
-
-**Potential Improvements:**
- Review trust line copy
- Consider adding social proof element
-
---
-
-## NEW: Social Proof Section (To Add)
-
-**Position:** After Stats section, before Philosophy section
-
-**Components:**
- GitHub stars counter (dynamic or static)
- "Trusted by X developers" metric
- 2-3 testimonial quotes (if available)
- Company logos (if applicable)
-
-**LaunchKit Pattern:**
-```html
-<section class="social-proof-section">
-  <div class="heading centered">
-    <p class="paragraph m secondary">Trusted by developers at</p>
-  </div>
-  <div class="logo-grid">
-    <!-- Company logos or GitHub badge -->
-  </div>
-</section>
-```
-
---
-
-## Pragmatic Writing Style Checklist (Apply to ALL Copy)
-
-### The Five Laws
-1. **Concrete Before Abstract** - Story/example first, then principle
-2. **Physical Analogies** - Import metaphors readers understand
-3. **Conversational Register** - Use "you", contractions, asides
-4. **Numbered Frameworks** - Create referenceable structures
-5. **Humor as Architecture** - Mental anchors for dense content
-
-### Anti-Patterns to Find and Fix
- [ ] "It is recommended that..." → "Do this:"
- [ ] "Best practices suggest..." → "Here's what works:"
- [ ] Passive voice → Active voice
- [ ] Abstract claims → Specific examples
- [ ] Walls of text → Scannable lists
-
-### Quality Checklist (Per Section)
- [ ] Opens with concrete story or example?
- [ ] Can reader skim headers and get the arc?
- [ ] Uses "you" at least once?
- [ ] Clear action reader can take?
- [ ] Reads aloud like speech?
-
---
-
-## Implementation Phases
-
-### Phase 1: Copy Audit (No HTML Changes)
-1. Read through entire page
-2. Flag passive voice instances
-3. Flag abstract claims without examples
-4. Flag missing "you" voice
-5. Document improvements needed
-
-### Phase 2: Copy Rewrites
-1. Rewrite flagged sections following pragmatic style
-2. Ensure each section passes quality checklist
-3. Maintain existing HTML structure
-
-### Phase 3: Component Additions
-1. Add arrow icons to primary CTAs
-2. Add social proof section (if data available)
-3. Consider visual demo element
-
-### Phase 4: Verification
-1. Validate all counts (agents, commands, skills)
-2. Test all links and buttons
-3. Verify mobile responsiveness
-4. Check accessibility
-
---
-
-## Files to Modify
-
-| File | Changes |
-|------|---------|
-| `docs/index.html` | Copy rewrites, potential new section |
-| `docs/css/style.css` | Social proof styles (if adding) |
-
---
-
-## Success Criteria
-
-1. All copy passes Pragmatic Writing quality checklist
-2. No passive voice in any description
-3. Every feature section answers "why should I care?"
-4. Stats are accurate against actual file counts
-5. Page loads in <3 seconds
-6. Mobile layout is fully functional
-
---
-
-## References
-
- LaunchKit Template: https://launchkit.evilmartians.io/
- Pragmatic Writing Skill: `~/.claude/skills/pragmatic-writing-skill/SKILL.md`
- Current Landing Page: `/Users/kieranklaassen/every-marketplace/docs/index.html`
- Style CSS: `/Users/kieranklaassen/every-marketplace/docs/css/style.css`
--- a/plugins/coding-tutor/.cursor-plugin/plugin.json
+++ b/plugins/coding-tutor/.cursor-plugin/plugin.json
@@ -0,0 +1,21 @@
+{
+  "name": "coding-tutor",
+  "displayName": "Coding Tutor",
+  "version": "1.2.1",
+  "description": "Personalized coding tutorials that use your actual codebase for examples with spaced repetition quizzes",
+  "author": {
+    "name": "Nityesh Agarwal"
+  },
+  "homepage": "https://github.com/EveryInc/compound-engineering-plugin",
+  "repository": "https://github.com/EveryInc/compound-engineering-plugin",
+  "license": "MIT",
+  "keywords": [
+    "cursor",
+    "plugin",
+    "coding",
+    "programming",
+    "tutorial",
+    "learning",
+    "spaced-repetition"
+  ]
+}
--- a/plugins/compound-engineering/.claude-plugin/plugin.json
+++ b/plugins/compound-engineering/.claude-plugin/plugin.json
@@ -1,7 +1,7 @@
 {
  "name": "compound-engineering",
-  "version": "2.39.0",
-  "description": "AI-powered development tools. 25 agents, 25 commands, 24 skills, 1 MCP server for code review, research, design, and workflow automation.",
+  "version": "2.40.0",
+  "description": "AI-powered development tools. 30 agents, 56 skills, 7 commands, 1 MCP server for code review, research, design, and workflow automation.",
  "author": {
    "name": "Kieran Klaassen",
    "email": "kieran@every.to",
@@ -15,7 +15,8 @@
    "compound-engineering",
    "workflow-automation",
    "code-review",
-    "fastapi",
+    "rails",
+    "ruby",
    "python",
    "typescript",
    "knowledge-management",
--- a/plugins/compound-engineering/.cursor-plugin/plugin.json
+++ b/plugins/compound-engineering/.cursor-plugin/plugin.json
@@ -0,0 +1,31 @@
+{
+  "name": "compound-engineering",
+  "displayName": "Compound Engineering",
+  "version": "2.33.0",
+  "description": "AI-powered development tools. 28 agents, 22 commands, 19 skills, 1 MCP server for code review, research, design, and workflow automation.",
+  "author": {
+    "name": "Kieran Klaassen",
+    "email": "kieran@every.to",
+    "url": "https://github.com/kieranklaassen"
+  },
+  "homepage": "https://every.to/source-code/my-ai-had-already-fixed-the-code-before-i-saw-it",
+  "repository": "https://github.com/EveryInc/compound-engineering-plugin",
+  "license": "MIT",
+  "keywords": [
+    "cursor",
+    "plugin",
+    "ai-powered",
+    "compound-engineering",
+    "workflow-automation",
+    "code-review",
+    "rails",
+    "ruby",
+    "python",
+    "typescript",
+    "knowledge-management",
+    "image-generation",
+    "agent-browser",
+    "browser-automation"
+  ],
+  "mcpServers": ".mcp.json"
+}
--- a/plugins/compound-engineering/.mcp.json
+++ b/plugins/compound-engineering/.mcp.json
@@ -0,0 +1,11 @@
+{
+  "mcpServers": {
+    "context7": {
+      "type": "http",
+      "url": "https://mcp.context7.com/mcp",
+      "headers": {
+        "x-api-key": "${CONTEXT7_API_KEY:-}"
+      }
+    }
+  }
+}
--- a/plugins/compound-engineering/CHANGELOG.md
+++ b/plugins/compound-engineering/CHANGELOG.md
@@ -5,79 +5,120 @@ All notable changes to the compound-engineering plugin will be documented in thi
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

-<<<<<<< Updated upstream
 ## [2.39.0] - 2026-03-10

 ### Added

- **`/essay-edit` command** - Expert essay editor that polishes written work through two passes: structural review using the Saunders framework (via `story-lens` skill) and granular line-level editing. Preserves the author's voice (via `john-voice` skill) and guards against "timid scribe" syndrome — edits sharpen language without softening intent or defanging strong claims.
-
-## [2.38.0] - 2026-03-08
-
-### Added
-
- **`/essay-outline` command** - Transform a brain dump into a story-structured essay outline. Pressure tests ideas for a real thesis and payoff, applies the Saunders storytelling framework (via `story-lens` skill) to validate hook, escalation, and conclusion, then produces a tight outline written to file.
-
-## [2.37.0] - 2026-03-08
-
-### Added
-
- **`story-lens` skill** - Evaluate prose quality using George Saunders's storytelling framework (beat causality, escalation, three E's, character accumulation, moral/technical unity)
- **`sync-confluence` skill** - Sync local markdown docs to Confluence Cloud pages via REST API. Handles first-time setup, page creation, and bulk updates with automatic mapping file management.
-
-## [2.36.0] - 2026-02-27
-
-### Added
-
- **`john-voice` skill** - Write content in John Lamb's authentic voice across all venues and audiences
- **`jira-ticket-writer` skill** - Draft and create Jira tickets with tone pressure-testing and user approval via Atlassian MCP
- **`excalidraw-png-export` skill** - Create diagrams, architecture visuals, and flowcharts as PNG files using Excalidraw MCP and Playwright
+- **ce:compound context budget precheck** — Warns when context is constrained and offers compact-safe mode to avoid compaction mid-compound ([#235](https://github.com/EveryInc/compound-engineering-plugin/pull/235))
+- **ce:plan daily sequence numbers** — Plan filenames now include a 3-digit daily sequence number (e.g., `2026-03-10-001-feat-...`) to prevent collisions ([#238](https://github.com/EveryInc/compound-engineering-plugin/pull/238))
+- **ce:review serial mode** — Pass `--serial` flag (or auto-detects when 6+ agents configured) to run review agents sequentially, preventing context limit crashes ([#237](https://github.com/EveryInc/compound-engineering-plugin/pull/237))
+- **agent-browser inspection & debugging commands** — Added JS eval, console/errors, network, storage, device emulation, element debugging, recording/tracing, tabs, and advanced mouse commands to agent-browser skill ([#236](https://github.com/EveryInc/compound-engineering-plugin/pull/236))
+- **test-browser port detection** — Auto-detects dev server port from CLAUDE.md, package.json, or .env files; supports `--port` flag ([#233](https://github.com/EveryInc/compound-engineering-plugin/pull/233))
+- **lfg phase gating** — Added explicit GATE checks between /lfg steps to enforce plan-before-work ordering ([#231](https://github.com/EveryInc/compound-engineering-plugin/pull/231))

 ### Fixed

- Updated component counts across plugin.json, marketplace.json, and README to reflect actual file counts (22 skills)
- Synced marketplace.json version to match plugin.json
-
-## [2.35.1] - 2026-02-17
-
-### Added
-
- **`upstream-merge` skill** - Structured workflow for incorporating upstream git changes while preserving local fork intent. Integrates with file-todos system for triage tracking.
+- **Context7 API key auth** — MCP server config now passes `CONTEXT7_API_KEY` via `x-api-key` header to avoid anonymous rate limits ([#232](https://github.com/EveryInc/compound-engineering-plugin/pull/232))
+- **CLI: MCP server merge order** — `sync` now correctly overwrites same-named MCP servers with plugin values instead of preserving stale entries

 ### Removed

- **`dspy-python` skill** - Deleted per triage decision (project uses LangChain/LangGraph, not DSPy)
+- **every-style-editor agent** — Removed duplicate agent; functionality already exists as `every-style-editor` skill ([#234](https://github.com/EveryInc/compound-engineering-plugin/pull/234))

-## [2.35.0] - 2026-02-16
+### Contributors
+
+- Matt Van Horn ([@mvanhorn](https://x.com/mvanhorn)) — PRs #231–#238
+
+---
+
+## [2.38.1] - 2026-03-01
+
+### Fixed
+
+- **Cross-platform `AskUserQuestion` fallback** — `setup` skill and `create-new-skill`/`add-workflow` workflows now include an "Interaction Method" preamble that instructs non-Claude LLMs (Codex, Gemini, Copilot, Kiro) to use numbered lists instead of `AskUserQuestion`, preventing silent auto-configuration. ([#204](https://github.com/EveryInc/compound-engineering-plugin/issues/204))
+- **Codex AGENTS.md `AskUserQuestion` mapping** — Strengthened from "ask the user in chat" to structured numbered-list guidance with multi-select support and a "never skip or auto-configure" rule.
+- **Skill compliance checklist** — Added `AskUserQuestion` lint rule to `CLAUDE.md` to prevent recurrence.
+
+---
+
+## [2.38.0] - 2026-03-01
+
+### Changed
+- `workflows:plan`, `workflows:work`, `workflows:review`, `workflows:brainstorm`, `workflows:compound` renamed to `ce:plan`, `ce:work`, `ce:review`, `ce:brainstorm`, `ce:compound` for clarity — the `ce:` prefix unambiguously identifies these as compound-engineering commands
+
+### Deprecated
+- `workflows:*` commands — all five remain functional as aliases that forward to their `ce:*` equivalents with a deprecation notice. Will be removed in a future version.
+
+---
+
+## [2.37.2] - 2026-03-01
+
+### Added
+
+- **CLI: auto-detect install targets** — `bunx @every-env/compound-plugin install compound-engineering --to all` auto-detects installed AI coding tools and installs to all of them in one command. ([#191](https://github.com/EveryInc/compound-engineering-plugin/pull/191))
+- **CLI: Gemini sync** — `sync --target gemini` symlinks personal skills to `.gemini/skills/` and merges MCP servers into `.gemini/settings.json`. ([#191](https://github.com/EveryInc/compound-engineering-plugin/pull/191))
+- **CLI: sync defaults to `--target all`** — Running `sync` with no target now syncs to all detected tools automatically. ([#191](https://github.com/EveryInc/compound-engineering-plugin/pull/191))
+
+---
+
+## [2.37.1] - 2026-03-01
+
+### Fixed
+
+- **`/workflows:review` rendering** — Fixed broken markdown output: "Next Steps" items 3 & 4 and Severity Breakdown no longer leak outside the Summary Report template, section numbering fixed (was jumping 5→7, now correct), removed orphaned fenced code block delimiters that caused the entire End-to-End Testing section to render as a code block, and fixed unclosed quoted string in section 1. ([#214](https://github.com/EveryInc/compound-engineering-plugin/pull/214)) — thanks [@XSAM](https://github.com/XSAM)!
+- **`.worktrees` gitignore** — Added `.worktrees/` to `.gitignore` to prevent worktree directories created by the `git-worktree` skill from being tracked. ([#213](https://github.com/EveryInc/compound-engineering-plugin/pull/213)) — thanks [@XSAM](https://github.com/XSAM)!
+
+---
+
+## [2.37.0] - 2026-03-01
+
+### Added
+
+- **`proof` skill** — Create, edit, comment on, and share markdown documents via Proof's web API and local bridge. Supports document creation, track-changes suggestions, comments, and bulk rewrites. No authentication required for creating shared documents.
+- **Optional Proof sharing in `/workflows:brainstorm`** — "Share to Proof" is now a menu option in Phase 4 handoff, letting you upload the brainstorm document when you want to, rather than automatically on every run.
+- **Optional Proof sharing in `/workflows:plan`** — "Share to Proof" is now a menu option in Post-Generation Options, letting you upload the plan file on demand rather than automatically.
+
+---
+
+## [2.36.0] - 2026-03-01
+
+### Added
+
+- **OpenClaw install target** — `bunx @every-env/compound-plugin install compound-engineering --to openclaw` now installs the plugin to OpenClaw's extensions directory. ([#217](https://github.com/EveryInc/compound-engineering-plugin/pull/217)) — thanks [@TrendpilotAI](https://github.com/TrendpilotAI)!
+- **Qwen Code install target** — `bunx @every-env/compound-plugin install compound-engineering --to qwen` now installs the plugin to Qwen Code's extensions directory. ([#220](https://github.com/EveryInc/compound-engineering-plugin/pull/220)) — thanks [@rlam3](https://github.com/rlam3)!
+- **Windsurf install target** — `bunx @every-env/compound-plugin install compound-engineering --to windsurf` converts plugins to Windsurf format. Agents become Windsurf skills, commands become flat workflows, and MCP servers write to `mcp_config.json`. Defaults to global scope (`~/.codeium/windsurf/`); use `--scope workspace` for project-level output. ([#202](https://github.com/EveryInc/compound-engineering-plugin/pull/202)) — thanks [@rburnham52](https://github.com/rburnham52)!
+
+### Fixed
+
+- **`create-agent-skill` / `heal-skill` YAML crash** — `argument-hint` values containing special characters now properly quoted to prevent YAML parse errors in the Claude Code TUI. ([#219](https://github.com/EveryInc/compound-engineering-plugin/pull/219)) — thanks [@solon](https://github.com/solon)!
+- **`resolve-pr-parallel` skill name** — Renamed from `resolve_pr_parallel` (underscore) to `resolve-pr-parallel` (hyphen) to match the standard naming convention. ([#202](https://github.com/EveryInc/compound-engineering-plugin/pull/202)) — thanks [@rburnham52](https://github.com/rburnham52)!
+
+---
+
+## [2.35.2] - 2026-02-20

 ### Changed

- **Backend focus shift: Ruby/Rails -> Python/FastAPI** - Comprehensive conversion of backend-focused components
-  - All backend-related agents and skills now target Python/FastAPI instead of Ruby/Rails
-  - TypeScript/React frontend components remain unchanged
+- **`/workflows:plan` brainstorm integration** — When plan finds a brainstorm document, it now heavily references it throughout. Added `origin:` frontmatter field to plan templates, brainstorm cross-check in final review, and "Sources" section at the bottom of all three plan templates (MINIMAL, MORE, A LOT). Brainstorm decisions are carried forward with explicit references (`see brainstorm: <path>`) and a mandatory scan before finalizing ensures nothing is dropped.

-### Added
+---

- **`tiangolo-fastapi-reviewer` agent** - FastAPI code review from Sebastián Ramírez's perspective
- **`python-package-readme-writer` agent** - Create concise READMEs for Python packages
- **`fastapi-style` skill** - Write FastAPI code following opinionated best practices
- **`python-package-writer` skill** - Write Python packages following production-ready patterns
- **Enhanced `kieran-python-reviewer` agent** - Now includes 9 FastAPI-specific convention sections
- **Updated `lint` agent** - Now targets Python files
- **`/pr-comments-to-todos` command** - Fetch PR review comments and convert them into todo files for triage
- **Pressure Test framework** in workflows:review - Critical evaluation of agent findings before creating todos
+## [2.35.1] - 2026-02-18

-### Removed
+### Changed

- **`dhh-rails-reviewer` agent** - Replaced by tiangolo-fastapi-reviewer
- **`kieran-rails-reviewer` agent** - Functionality merged into kieran-python-reviewer
- **`ankane-readme-writer` agent** - Replaced by python-package-readme-writer
- **3 design agents** - design-implementation-reviewer, design-iterator, figma-design-sync
- **`dhh-rails-style` skill** - Replaced by fastapi-style
- **`andrew-kane-gem-writer` skill** - Replaced by python-package-writer
- **`dspy-ruby` skill** - Removed (not used; LangChain/LangGraph is the actual stack)
- **`dspy-python` skill** - Removed (not used; LangChain/LangGraph is the actual stack)
- **`/plan_review` command** - Absorbed into workflows/plan via document-review skill
+- **`/workflows:work` system-wide test check** — Added "System-Wide Test Check" to the task execution loop. Before marking a task done, forces five questions: what callbacks/middleware fire when this runs? Do tests exercise the real chain or just mocked isolation? Can failure leave orphaned state? What other interfaces need the same change? Do error strategies align across layers? Includes skip criteria for leaf-node changes. Also added integration test guidance to the "Test Continuously" section.
+- **`/workflows:plan` system-wide impact templates** — Added "System-Wide Impact" section to MORE and A LOT plan templates (interaction graph, error propagation, state lifecycle, API surface parity, integration test scenarios) as lightweight prompts to flag risks during planning.
+
+---
+
+## [2.35.0] - 2026-02-17
+
+### Fixed
+
+- **`/lfg` and `/slfg` first-run failures** — Made ralph-loop step optional with graceful fallback when `ralph-wiggum` skill is not installed (#154). Added explicit "do not stop" instruction across all steps (#134).
+- **`/workflows:plan` not writing file in pipeline** — Added mandatory "Write Plan File" step with explicit Write tool instructions before Post-Generation Options. The file is now always written to disk before any interactive prompts (#155). Also adds pipeline-mode note to skip AskUserQuestion calls when invoked from LFG/SLFG (#134).
+- **Agent namespace typo in `/workflows:plan`** — `Task spec-flow-analyzer(...)` now uses the full qualified name `Task compound-engineering:workflow:spec-flow-analyzer(...)` to prevent Claude from prepending the wrong `workflows:` prefix (#193).

 ---

@@ -149,7 +190,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
  - All 29 agent descriptions trimmed from ~1,400 to ~180 chars avg (examples moved to agent body)
  - 18 manual commands marked `disable-model-invocation: true` (side-effect commands like `/lfg`, `/deploy-docs`, `/triage`, etc.)
  - 6 manual skills marked `disable-model-invocation: true` (`orchestrating-swarms`, `git-worktree`, `skill-creator`, `compound-docs`, `file-todos`, `resolve-pr-parallel`)
- **git-worktree**: Remove confirmation prompt for worktree creation ([@Sam Xie](https://github.com/samxie))
+- **git-worktree**: Remove confirmation prompt for worktree creation ([@Sam Xie](https://github.com/XSAM))
 - **Prevent subagents from writing intermediary files** in compound workflow ([@Trevin Chow](https://github.com/trevin))

 ### Fixed
--- a/plugins/compound-engineering/CLAUDE.md
+++ b/plugins/compound-engineering/CLAUDE.md
@@ -2,24 +2,24 @@

 ## Versioning Requirements

-**IMPORTANT**: Every change to this plugin MUST include updates to all three files:
+**IMPORTANT**: Routine PRs should not cut releases for this plugin.

-1. **`.claude-plugin/plugin.json`** - Bump version using semver
-2. **`CHANGELOG.md`** - Document changes using Keep a Changelog format
-3. **`README.md`** - Verify/update component counts and tables
+The repo uses an automatied release process to prepare plugin releases, including version selection and changelog generation. Because multiple PRs may merge before the next release, contributors cannot know the final released version from within an individual PR.

-### Version Bumping Rules
+### Contributor Rules

- **MAJOR** (1.0.0 → 2.0.0): Breaking changes, major reorganization
- **MINOR** (1.0.0 → 1.1.0): New agents, commands, or skills
- **PATCH** (1.0.0 → 1.0.1): Bug fixes, doc updates, minor improvements
+- Do **not** manually bump `.claude-plugin/plugin.json` version in a normal feature PR.
+- Do **not** manually bump `.claude-plugin/marketplace.json` plugin version in a normal feature PR.
+- Do **not** cut a release section in `CHANGELOG.md` for a normal feature PR.
+- Do update substantive docs that are part of the actual change, such as `README.md`, component tables, usage instructions, or counts when they would otherwise become inaccurate.

 ### Pre-Commit Checklist

 Before committing ANY changes:

- [ ] Version bumped in `.claude-plugin/plugin.json`
- [ ] CHANGELOG.md updated with changes
+- [ ] No manual release-version bump in `.claude-plugin/plugin.json`
+- [ ] No manual release-version bump in `.claude-plugin/marketplace.json`
+- [ ] No manual release entry added to `CHANGELOG.md`
 - [ ] README.md component counts verified
 - [ ] README.md tables accurate (agents, commands, skills)
 - [ ] plugin.json description matches current counts
@@ -34,23 +34,26 @@ agents/
 ├── workflow/   # Workflow automation agents
 └── docs/       # Documentation agents

-commands/
-├── workflows/  # Core workflow commands (workflows:plan, workflows:review, etc.)
-└── *.md        # Utility commands
-
 skills/
-└── *.md        # All skills at root level
+├── ce-*/          # Core workflow skills (ce:plan, ce:review, etc.)
+├── workflows-*/   # Deprecated aliases for ce:* skills
+└── */             # All other skills
 ```

+> **Note:** Commands were migrated to skills in v2.39.0. All former
+> `/command-name` slash commands now live under `skills/command-name/SKILL.md`
+> and work identically (Claude Code 2.1.3+ merged the two formats).
+
 ## Command Naming Convention

-**Workflow commands** use `workflows:` prefix to avoid collisions with built-in commands:
- `/workflows:plan` - Create implementation plans
- `/workflows:review` - Run comprehensive code reviews
- `/workflows:work` - Execute work items systematically
- `/workflows:compound` - Document solved problems
+**Workflow commands** use `ce:` prefix to unambiguously identify them as compound-engineering commands:
+- `/ce:plan` - Create implementation plans
+- `/ce:review` - Run comprehensive code reviews
+- `/ce:work` - Execute work items systematically
+- `/ce:compound` - Document solved problems
+- `/ce:brainstorm` - Explore requirements and approaches before planning

-**Why `workflows:`?** Claude Code has built-in `/plan` and `/review` commands. Using `name: workflows:plan` in frontmatter creates a unique `/workflows:plan` command with no collision.
+**Why `ce:`?** Claude Code has built-in `/plan` and `/review` commands. The `ce:` namespace (short for compound-engineering) makes it immediately clear these commands belong to this plugin. The legacy `workflows:` prefix is still supported as deprecated aliases that forward to the `ce:*` equivalents.

 ## Skill Compliance Checklist

@@ -73,6 +76,11 @@ When adding or modifying skills, verify compliance with skill-creator spec:
 - [ ] Use imperative/infinitive form (verb-first instructions)
 - [ ] Avoid second person ("you should") - use objective language ("To accomplish X, do Y")

+### AskUserQuestion Usage
+
+- [ ] If the skill uses `AskUserQuestion`, it must include an "Interaction Method" preamble explaining the numbered-list fallback for non-Claude environments
+- [ ] Prefer avoiding `AskUserQuestion` entirely (see `brainstorming/SKILL.md` pattern) for skills intended to run cross-platform
+
 ### Quick Validation Command

 ```bash
--- a/plugins/compound-engineering/README.md
+++ b/plugins/compound-engineering/README.md
@@ -6,16 +6,16 @@ AI-powered development tools that get smarter with every use. Make each unit of

 | Component | Count |
 |-----------|-------|
-| Agents | 25 |
-| Commands | 25 |
-| Skills | 24 |
+| Agents | 28 |
+| Commands | 22 |
+| Skills | 20 |
 | MCP Servers | 1 |

 ## Agents

 Agents are organized into categories for easier discovery.

-### Review (14)
+### Review (15)

 | Agent | Description |
 |-------|-------------|
@@ -25,14 +25,15 @@ Agents are organized into categories for easier discovery.
 | `data-integrity-guardian` | Database migrations and data integrity |
 | `data-migration-expert` | Validate ID mappings match production, check for swapped values |
 | `deployment-verification-agent` | Create Go/No-Go deployment checklists for risky data changes |
+| `dhh-rails-reviewer` | Rails review from DHH's perspective |
 | `julik-frontend-races-reviewer` | Review JavaScript/Stimulus code for race conditions |
+| `kieran-rails-reviewer` | Rails code review with strict conventions |
 | `kieran-python-reviewer` | Python code review with strict conventions |
 | `kieran-typescript-reviewer` | TypeScript code review with strict conventions |
 | `pattern-recognition-specialist` | Analyze code for patterns and anti-patterns |
 | `performance-oracle` | Performance analysis and optimization |
-| `schema-drift-detector` | Detect unrelated schema changes in PRs |
+| `schema-drift-detector` | Detect unrelated schema.rb changes in PRs |
 | `security-sentinel` | Security audits and vulnerability assessments |
-| `tiangolo-fastapi-reviewer` | FastAPI code review from tiangolo's perspective |

 ### Research (5)

@@ -44,13 +45,20 @@ Agents are organized into categories for easier discovery.
 | `learnings-researcher` | Search institutional learnings for relevant past solutions |
 | `repo-research-analyst` | Research repository structure and conventions |

-### Workflow (5)
+### Design (3)
+
+| Agent | Description |
+|-------|-------------|
+| `design-implementation-reviewer` | Verify UI implementations match Figma designs |
+| `design-iterator` | Iteratively refine UI through systematic design iterations |
+| `figma-design-sync` | Synchronize web implementations with Figma designs |
+
+### Workflow (4)

 | Agent | Description |
 |-------|-------------|
 | `bug-reproduction-validator` | Systematically reproduce and validate bug reports |
-| `every-style-editor` | Edit content to conform to Every's style guide |
-| `lint` | Run linting and code quality checks on Python files |
+| `lint` | Run linting and code quality checks on Ruby and ERB files |
 | `pr-comment-resolver` | Address PR comments and implement fixes |
 | `spec-flow-analyzer` | Analyze user flows and identify gaps in specifications |

@@ -58,21 +66,23 @@ Agents are organized into categories for easier discovery.

 | Agent | Description |
 |-------|-------------|
-| `python-package-readme-writer` | Create READMEs following concise documentation style for Python packages |
+| `ankane-readme-writer` | Create READMEs following Ankane-style template for Ruby gems |

 ## Commands

 ### Workflow Commands

-Core workflow commands use `workflows:` prefix to avoid collisions with built-in commands:
+Core workflow commands use `ce:` prefix to unambiguously identify them as compound-engineering commands:

 | Command | Description |
 |---------|-------------|
-| `/workflows:brainstorm` | Explore requirements and approaches before planning |
-| `/workflows:plan` | Create implementation plans |
-| `/workflows:review` | Run comprehensive code reviews |
-| `/workflows:work` | Execute work items systematically |
-| `/workflows:compound` | Document solved problems to compound team knowledge |
+| `/ce:brainstorm` | Explore requirements and approaches before planning |
+| `/ce:plan` | Create implementation plans |
+| `/ce:review` | Run comprehensive code reviews |
+| `/ce:work` | Execute work items systematically |
+| `/ce:compound` | Document solved problems to compound team knowledge |
+
+> **Deprecated aliases:** `/workflows:plan`, `/workflows:work`, `/workflows:review`, `/workflows:brainstorm`, `/workflows:compound` still work but show a deprecation warning. Use `ce:*` equivalents.

 ### Utility Commands

@@ -85,19 +95,16 @@ Core workflow commands use `workflows:` prefix to avoid collisions with built-in
 | `/create-agent-skill` | Create or edit Claude Code skills |
 | `/generate_command` | Generate new slash commands |
 | `/heal-skill` | Fix skill documentation issues |
+| `/sync` | Sync Claude Code config across machines |
 | `/report-bug` | Report a bug in the plugin |
 | `/reproduce-bug` | Reproduce bugs using logs and console |
 | `/resolve_parallel` | Resolve TODO comments in parallel |
+| `/resolve_pr_parallel` | Resolve PR comments in parallel |
 | `/resolve_todo_parallel` | Resolve todos in parallel |
 | `/triage` | Triage and prioritize issues |
 | `/test-browser` | Run browser tests on PR-affected pages |
-| `/test-xcode` | Build and test iOS apps on simulator |
+| `/xcode-test` | Build and test iOS apps on simulator |
 | `/feature-video` | Record video walkthroughs and add to PR description |
-| `/agent-native-audit` | Run comprehensive agent-native architecture review |
-| `/deploy-docs` | Validate and prepare documentation for GitHub Pages |
-| `/pr-comments-to-todos` | Fetch PR comments and convert to todo files |
-| `/essay-outline` | Transform a brain dump into a story-structured essay outline |
-| `/essay-edit` | Polish written essays with expert structural and line-level editing |

 ## Skills

@@ -111,12 +118,13 @@ Core workflow commands use `workflows:` prefix to avoid collisions with built-in

 | Skill | Description |
 |-------|-------------|
+| `andrew-kane-gem-writer` | Write Ruby gems following Andrew Kane's patterns |
 | `compound-docs` | Capture solved problems as categorized documentation |
 | `create-agent-skills` | Expert guidance for creating Claude Code skills |
-| `fastapi-style` | Write Python/FastAPI code following opinionated best practices |
+| `dhh-rails-style` | Write Ruby/Rails code in DHH's 37signals style |
+| `dspy-ruby` | Build type-safe LLM applications with DSPy.rb |
 | `frontend-design` | Create production-grade frontend interfaces |
-| `python-package-writer` | Write Python packages following production-ready patterns |
-| `skill-creator` | Guide for creating effective Claude Code skills |
+

 ### Content & Workflow

@@ -127,12 +135,9 @@ Core workflow commands use `workflows:` prefix to avoid collisions with built-in
 | `every-style-editor` | Review copy for Every's style guide compliance |
 | `file-todos` | File-based todo tracking system |
 | `git-worktree` | Manage Git worktrees for parallel development |
-| `jira-ticket-writer` | Draft and create Jira tickets with tone review and user approval |
-| `john-voice` | Write content in John Lamb's authentic voice across all venues |
+| `proof` | Create, edit, and share documents via Proof collaborative editor |
 | `resolve-pr-parallel` | Resolve PR review comments in parallel |
 | `setup` | Configure which review agents run for your project |
-| `story-lens` | Evaluate prose quality using George Saunders's storytelling framework |
-| `upstream-merge` | Incorporate upstream git changes while preserving local fork intent |

 ### Multi-Agent Orchestration

@@ -152,12 +157,6 @@ Core workflow commands use `workflows:` prefix to avoid collisions with built-in
 |-------|-------------|
 | `agent-browser` | CLI-based browser automation using Vercel's agent-browser |

-### Diagramming & Visualization
-
-| Skill | Description |
-|-------|-------------|
-| `excalidraw-png-export` | Create diagrams and flowcharts as PNG using Excalidraw MCP |
-
 ### Image Generation

 | Skill | Description |
@@ -186,10 +185,12 @@ Core workflow commands use `workflows:` prefix to avoid collisions with built-in
 - `resolve-library-id` - Find library ID for a framework/package
 - `get-library-docs` - Get documentation for a specific library

-Supports 100+ frameworks including FastAPI, React, Next.js, Vue, Django, SQLAlchemy, and more.
+Supports 100+ frameworks including Rails, React, Next.js, Vue, Django, Laravel, and more.

 MCP servers start automatically when the plugin is enabled.

+**Authentication:** To avoid anonymous rate limits, set the `CONTEXT7_API_KEY` environment variable with your Context7 API key. The plugin passes this automatically via the `x-api-key` header. Without it, requests go unauthenticated and will quickly hit the anonymous quota limit.
+
 ## Browser Automation

 This plugin uses **agent-browser CLI** for browser automation tasks. Install it globally:
@@ -220,13 +221,16 @@ claude /plugin install compound-engineering
  "mcpServers": {
    "context7": {
      "type": "http",
-      "url": "https://mcp.context7.com/mcp"
+      "url": "https://mcp.context7.com/mcp",
+      "headers": {
+        "x-api-key": "${CONTEXT7_API_KEY:-}"
+      }
    }
  }
 }
 ```

-Or add it globally in `~/.claude/settings.json` for all projects.
+Set `CONTEXT7_API_KEY` in your environment to authenticate. Or add it globally in `~/.claude/settings.json` for all projects.

 ## Version History

--- a/plugins/compound-engineering/agents/research/git-history-analyzer.md
+++ b/plugins/compound-engineering/agents/research/git-history-analyzer.md
@@ -56,4 +56,4 @@ When analyzing, consider:

 Your insights should help developers understand not just what the code does, but why it evolved to its current state, informing better decisions for future changes.

-Note that files in `docs/plans/` and `docs/solutions/` are compound-engineering pipeline artifacts created by `/workflows:plan`. They are intentional, permanent living documents — do not recommend their removal or characterize them as unnecessary.
+Note that files in `docs/plans/` and `docs/solutions/` are compound-engineering pipeline artifacts created by `/ce:plan`. They are intentional, permanent living documents — do not recommend their removal or characterize them as unnecessary.
--- a/plugins/compound-engineering/agents/research/learnings-researcher.md
+++ b/plugins/compound-engineering/agents/research/learnings-researcher.md
@@ -1,7 +1,7 @@
 ---
 name: learnings-researcher
 description: "Searches docs/solutions/ for relevant past solutions by frontmatter metadata. Use before implementing features or fixing problems to surface institutional knowledge and prevent repeated mistakes."
-model: haiku
+model: inherit
 ---

 <examples>
@@ -257,7 +257,7 @@ Structure your findings as:
 ## Integration Points

 This agent is designed to be invoked by:
- `/workflows:plan` - To inform planning with institutional knowledge
+- `/ce:plan` - To inform planning with institutional knowledge
 - `/deepen-plan` - To add depth with relevant learnings
 - Manual invocation before starting work on a feature

--- a/plugins/compound-engineering/agents/review/code-simplicity-reviewer.md
+++ b/plugins/compound-engineering/agents/review/code-simplicity-reviewer.md
@@ -48,7 +48,7 @@ When reviewing code, you will:
   - Eliminate extensibility points without clear use cases
   - Question generic solutions for specific problems
   - Remove "just in case" code
-   - Never flag `docs/plans/*.md` or `docs/solutions/*.md` for removal — these are compound-engineering pipeline artifacts created by `/workflows:plan` and used as living documents by `/workflows:work`
+   - Never flag `docs/plans/*.md` or `docs/solutions/*.md` for removal — these are compound-engineering pipeline artifacts created by `/ce:plan` and used as living documents by `/ce:work`

 6. **Optimize for Readability**:
   - Prefer self-documenting code over comments
--- a/plugins/compound-engineering/agents/workflow/every-style-editor.md
+++ b/plugins/compound-engineering/agents/workflow/every-style-editor.md
@@ -1,64 +0,0 @@
---
-name: every-style-editor
-description: "Reviews and edits text content to conform to Every's editorial style guide. Use when written content needs style compliance checks for headlines, punctuation, voice, and formatting."
-tools: Task, Glob, Grep, LS, ExitPlanMode, Read, Edit, MultiEdit, Write, NotebookRead, NotebookEdit, WebFetch, TodoWrite, WebSearch
-model: inherit
---
-
-You are an expert copy editor specializing in Every's house style guide. Your role is to meticulously review text content and suggest edits to ensure compliance with Every's specific editorial standards.
-
-When reviewing content, you will:
-
-1. **Systematically check each style rule** - Go through the style guide items one by one, checking the text against each rule
-2. **Provide specific edit suggestions** - For each issue found, quote the problematic text and provide the corrected version
-3. **Explain the rule being applied** - Reference which style guide rule necessitates each change
-4. **Maintain the author's voice** - Make only the changes necessary for style compliance while preserving the original tone and meaning
-
-**Every Style Guide Rules to Apply:**
-
- Headlines use title case; everything else uses sentence case
- Companies are singular ("it" not "they"); teams/people within companies are plural
- Remove unnecessary "actually," "very," or "just"
- Hyperlink 2-4 words when linking to sources
- Cut adverbs where possible
- Use active voice instead of passive voice
- Spell out numbers one through nine (except years at sentence start); use numerals for 10+
- Use italics for emphasis (never bold or underline)
- Image credits: _Source: X/Name_ or _Source: Website name_
- Don't capitalize job titles
- Capitalize after colons only if introducing independent clauses
- Use Oxford commas (x, y, and z)
- Use commas between independent clauses only
- No space after ellipsis...
- Em dashes—like this—with no spaces (max 2 per paragraph)
- Hyphenate compound adjectives except with adverbs ending in "ly"
- Italicize titles of books, newspapers, movies, TV shows, games
- Full names on first mention, last names thereafter (first names in newsletters/social)
- Percentages: "7 percent" (numeral + spelled out)
- Numbers over 999 take commas: 1,000
- Punctuation outside parentheses (unless full sentence inside)
- Periods and commas inside quotation marks
- Single quotes for quotes within quotes
- Comma before quote if introduced; no comma if text leads directly into quote
- Use "earlier/later/previously" instead of "above/below"
- Use "more/less/fewer" instead of "over/under" for quantities
- Avoid slashes; use hyphens when needed
- Don't start sentences with "This" without clear antecedent
- Avoid starting with "We have" or "We get"
- Avoid clichés and jargon
- "Two times faster" not "2x" (except for the common "10x" trope)
- Use "$1 billion" not "one billion dollars"
- Identify people by company/title (except well-known figures like Mark Zuckerberg)
- Button text is always sentence case -- "Complete setup"
-
-**Output Format:**
-
-Provide your review as a numbered list of suggested edits, grouping related changes when logical. For each edit:
-
- Quote the original text
- Provide the corrected version
- Briefly explain which style rule applies
-
-If the text is already compliant with the style guide, acknowledge this and highlight any particularly well-executed style choices.
-
-Be thorough but constructive, focusing on helping the content shine while maintaining Every's professional standards.
--- a/plugins/compound-engineering/commands/lfg.md
+++ b/plugins/compound-engineering/commands/lfg.md
@@ -1,20 +0,0 @@
---
-name: lfg
-description: Full autonomous engineering workflow
-argument-hint: "[feature description]"
-disable-model-invocation: true
---
-
-Run these slash commands in order. Do not do anything else.
-
-1. `/ralph-wiggum:ralph-loop "finish all slash commands" --completion-promise "DONE"`
-2. `/workflows:plan $ARGUMENTS`
-3. `/compound-engineering:deepen-plan`
-4. `/workflows:work`
-5. `/workflows:review`
-6. `/compound-engineering:resolve_todo_parallel`
-7. `/compound-engineering:test-browser`
-8. `/compound-engineering:feature-video`
-9. Output `<promise>DONE</promise>` when video is in PR
-
-Start with step 1 now.
--- a/plugins/compound-engineering/skills/agent-browser/SKILL.md
+++ b/plugins/compound-engineering/skills/agent-browser/SKILL.md
@@ -3,9 +3,9 @@ name: agent-browser
 description: Browser automation using Vercel's agent-browser CLI. Use when you need to interact with web pages, fill forms, take screenshots, or scrape data. Alternative to Playwright MCP - uses Bash commands with ref-based element selection. Triggers on "browse website", "fill form", "click button", "take screenshot", "scrape page", "web automation".
 ---

-# agent-browser: CLI Browser Automation
+# Browser Automation with agent-browser

-Vercel's headless browser automation CLI designed for AI agents. Uses ref-based selection (@e1, @e2) from accessibility snapshots.
+The CLI uses Chrome/Chromium via CDP directly. Install via `npm i -g agent-browser`, `brew install agent-browser`, or `cargo install agent-browser`. Run `agent-browser install` to download Chrome.

 ## Setup Check

@@ -23,185 +23,627 @@ agent-browser install  # Downloads Chromium

 ## Core Workflow

-**The snapshot + ref pattern is optimal for LLMs:**
+Every browser automation follows this pattern:

-1. **Navigate** to URL
-2. **Snapshot** to get interactive elements with refs
-3. **Interact** using refs (@e1, @e2, etc.)
-4. **Re-snapshot** after navigation or DOM changes
+1. **Navigate**: `agent-browser open <url>`
+2. **Snapshot**: `agent-browser snapshot -i` (get element refs like `@e1`, `@e2`)
+3. **Interact**: Use refs to click, fill, select
+4. **Re-snapshot**: After navigation or DOM changes, get fresh refs

 ```bash
-# Step 1: Open URL
-agent-browser open https://example.com
-
-# Step 2: Get interactive elements with refs
-agent-browser snapshot -i --json
-
-# Step 3: Interact using refs
-agent-browser click @e1
-agent-browser fill @e2 "search query"
-
-# Step 4: Re-snapshot after changes
+agent-browser open https://example.com/form
 agent-browser snapshot -i
-```
+# Output: @e1 [input type="email"], @e2 [input type="password"], @e3 [button] "Submit"

-## Key Commands
-
-### Navigation
-
-```bash
-agent-browser open <url>       # Navigate to URL
-agent-browser back             # Go back
-agent-browser forward          # Go forward
-agent-browser reload           # Reload page
-agent-browser close            # Close browser
-```
-
-### Snapshots (Essential for AI)
-
-```bash
-agent-browser snapshot              # Full accessibility tree
-agent-browser snapshot -i           # Interactive elements only (recommended)
-agent-browser snapshot -i --json    # JSON output for parsing
-agent-browser snapshot -c           # Compact (remove empty elements)
-agent-browser snapshot -d 3         # Limit depth
-```
-
-### Interactions
-
-```bash
-agent-browser click @e1                    # Click element
-agent-browser dblclick @e1                 # Double-click
-agent-browser fill @e1 "text"              # Clear and fill input
-agent-browser type @e1 "text"              # Type without clearing
-agent-browser press Enter                  # Press key
-agent-browser hover @e1                    # Hover element
-agent-browser check @e1                    # Check checkbox
-agent-browser uncheck @e1                  # Uncheck checkbox
-agent-browser select @e1 "option"          # Select dropdown option
-agent-browser scroll down 500              # Scroll (up/down/left/right)
-agent-browser scrollintoview @e1           # Scroll element into view
-```
-
-### Get Information
-
-```bash
-agent-browser get text @e1          # Get element text
-agent-browser get html @e1          # Get element HTML
-agent-browser get value @e1         # Get input value
-agent-browser get attr href @e1     # Get attribute
-agent-browser get title             # Get page title
-agent-browser get url               # Get current URL
-agent-browser get count "button"    # Count matching elements
-```
-
-### Screenshots & PDFs
-
-```bash
-agent-browser screenshot                      # Viewport screenshot
-agent-browser screenshot --full               # Full page
-agent-browser screenshot output.png           # Save to file
-agent-browser screenshot --full output.png    # Full page to file
-agent-browser pdf output.pdf                  # Save as PDF
-```
-
-### Wait
-
-```bash
-agent-browser wait @e1              # Wait for element
-agent-browser wait 2000             # Wait milliseconds
-agent-browser wait "text"           # Wait for text to appear
-```
-
-## Semantic Locators (Alternative to Refs)
-
-```bash
-agent-browser find role button click --name "Submit"
-agent-browser find text "Sign up" click
-agent-browser find label "Email" fill "user@example.com"
-agent-browser find placeholder "Search..." fill "query"
-```
-
-## Sessions (Parallel Browsers)
-
-```bash
-# Run multiple independent browser sessions
-agent-browser --session browser1 open https://site1.com
-agent-browser --session browser2 open https://site2.com
-
-# List active sessions
-agent-browser session list
-```
-
-## Examples
-
-### Login Flow
-
-```bash
-agent-browser open https://app.example.com/login
-agent-browser snapshot -i
-# Output shows: textbox "Email" [ref=e1], textbox "Password" [ref=e2], button "Sign in" [ref=e3]
 agent-browser fill @e1 "user@example.com"
 agent-browser fill @e2 "password123"
 agent-browser click @e3
-agent-browser wait 2000
-agent-browser snapshot -i  # Verify logged in
+agent-browser wait --load networkidle
+agent-browser snapshot -i  # Check result
 ```

-### Search and Extract
+## Command Chaining
+
+Commands can be chained with `&&` in a single shell invocation. The browser persists between commands via a background daemon, so chaining is safe and more efficient than separate calls.

 ```bash
-agent-browser open https://news.ycombinator.com
-agent-browser snapshot -i --json
-# Parse JSON to find story links
-agent-browser get text @e12  # Get headline text
-agent-browser click @e12     # Click to open story
+# Chain open + wait + snapshot in one call
+agent-browser open https://example.com && agent-browser wait --load networkidle && agent-browser snapshot -i
+
+# Chain multiple interactions
+agent-browser fill @e1 "user@example.com" && agent-browser fill @e2 "password123" && agent-browser click @e3
+
+# Navigate and capture
+agent-browser open https://example.com && agent-browser wait --load networkidle && agent-browser screenshot page.png
 ```

-### Form Filling
+**When to chain:** Use `&&` when you don't need to read the output of an intermediate command before proceeding (e.g., open + wait + screenshot). Run commands separately when you need to parse the output first (e.g., snapshot to discover refs, then interact using those refs).
+
+## Handling Authentication
+
+When automating a site that requires login, choose the approach that fits:
+
+**Option 1: Import auth from the user's browser (fastest for one-off tasks)**

 ```bash
-agent-browser open https://forms.example.com
+# Connect to the user's running Chrome (they're already logged in)
+agent-browser --auto-connect state save ./auth.json
+# Use that auth state
+agent-browser --state ./auth.json open https://app.example.com/dashboard
+```
+
+State files contain session tokens in plaintext -- add to `.gitignore` and delete when no longer needed. Set `AGENT_BROWSER_ENCRYPTION_KEY` for encryption at rest.
+
+**Option 2: Persistent profile (simplest for recurring tasks)**
+
+```bash
+# First run: login manually or via automation
+agent-browser --profile ~/.myapp open https://app.example.com/login
+# ... fill credentials, submit ...
+
+# All future runs: already authenticated
+agent-browser --profile ~/.myapp open https://app.example.com/dashboard
+```
+
+**Option 3: Session name (auto-save/restore cookies + localStorage)**
+
+```bash
+agent-browser --session-name myapp open https://app.example.com/login
+# ... login flow ...
+agent-browser close  # State auto-saved
+
+# Next time: state auto-restored
+agent-browser --session-name myapp open https://app.example.com/dashboard
+```
+
+**Option 4: Auth vault (credentials stored encrypted, login by name)**
+
+```bash
+echo "$PASSWORD" | agent-browser auth save myapp --url https://app.example.com/login --username user --password-stdin
+agent-browser auth login myapp
+```
+
+**Option 5: State file (manual save/load)**
+
+```bash
+# After logging in:
+agent-browser state save ./auth.json
+# In a future session:
+agent-browser state load ./auth.json
+agent-browser open https://app.example.com/dashboard
+```
+
+See [references/authentication.md](references/authentication.md) for OAuth, 2FA, cookie-based auth, and token refresh patterns.
+
+## Essential Commands
+
+```bash
+# Navigation
+agent-browser open <url>              # Navigate (aliases: goto, navigate)
+agent-browser close                   # Close browser
+
+# Snapshot
+agent-browser snapshot -i             # Interactive elements with refs (recommended)
+agent-browser snapshot -i -C          # Include cursor-interactive elements (divs with onclick, cursor:pointer)
+agent-browser snapshot -s "#selector" # Scope to CSS selector
+
+# Interaction (use @refs from snapshot)
+agent-browser click @e1               # Click element
+agent-browser click @e1 --new-tab     # Click and open in new tab
+agent-browser fill @e2 "text"         # Clear and type text
+agent-browser type @e2 "text"         # Type without clearing
+agent-browser select @e1 "option"     # Select dropdown option
+agent-browser check @e1               # Check checkbox
+agent-browser press Enter             # Press key
+agent-browser keyboard type "text"    # Type at current focus (no selector)
+agent-browser keyboard inserttext "text"  # Insert without key events
+agent-browser scroll down 500         # Scroll page
+agent-browser scroll down 500 --selector "div.content"  # Scroll within a specific container
+
+# Get information
+agent-browser get text @e1            # Get element text
+agent-browser get url                 # Get current URL
+agent-browser get title               # Get page title
+agent-browser get cdp-url             # Get CDP WebSocket URL
+
+# Wait
+agent-browser wait @e1                # Wait for element
+agent-browser wait --load networkidle # Wait for network idle
+agent-browser wait --url "**/page"    # Wait for URL pattern
+agent-browser wait 2000               # Wait milliseconds
+agent-browser wait --text "Welcome"    # Wait for text to appear (substring match)
+agent-browser wait --fn "!document.body.innerText.includes('Loading...')"  # Wait for text to disappear
+agent-browser wait "#spinner" --state hidden  # Wait for element to disappear
+
+# Downloads
+agent-browser download @e1 ./file.pdf          # Click element to trigger download
+agent-browser wait --download ./output.zip     # Wait for any download to complete
+agent-browser --download-path ./downloads open <url>  # Set default download directory
+
+# Viewport & Device Emulation
+agent-browser set viewport 1920 1080          # Set viewport size (default: 1280x720)
+agent-browser set viewport 1920 1080 2        # 2x retina (same CSS size, higher res screenshots)
+agent-browser set device "iPhone 14"          # Emulate device (viewport + user agent)
+
+# Capture
+agent-browser screenshot              # Screenshot to temp dir
+agent-browser screenshot --full       # Full page screenshot
+agent-browser screenshot --annotate   # Annotated screenshot with numbered element labels
+agent-browser screenshot --screenshot-dir ./shots  # Save to custom directory
+agent-browser screenshot --screenshot-format jpeg --screenshot-quality 80
+agent-browser pdf output.pdf          # Save as PDF
+
+# Clipboard
+agent-browser clipboard read                      # Read text from clipboard
+agent-browser clipboard write "Hello, World!"     # Write text to clipboard
+agent-browser clipboard copy                      # Copy current selection
+agent-browser clipboard paste                     # Paste from clipboard
+
+# Diff (compare page states)
+agent-browser diff snapshot                          # Compare current vs last snapshot
+agent-browser diff snapshot --baseline before.txt    # Compare current vs saved file
+agent-browser diff screenshot --baseline before.png  # Visual pixel diff
+agent-browser diff url <url1> <url2>                 # Compare two pages
+agent-browser diff url <url1> <url2> --wait-until networkidle  # Custom wait strategy
+agent-browser diff url <url1> <url2> --selector "#main"  # Scope to element
+```
+
+## Common Patterns
+
+### Form Submission
+
+```bash
+agent-browser open https://example.com/signup
 agent-browser snapshot -i
-agent-browser fill @e1 "John Doe"
-agent-browser fill @e2 "john@example.com"
-agent-browser select @e3 "United States"
-agent-browser check @e4  # Agree to terms
-agent-browser click @e5  # Submit button
-agent-browser screenshot confirmation.png
+agent-browser fill @e1 "Jane Doe"
+agent-browser fill @e2 "jane@example.com"
+agent-browser select @e3 "California"
+agent-browser check @e4
+agent-browser click @e5
+agent-browser wait --load networkidle
 ```

-### Debug Mode
+### Authentication with Auth Vault (Recommended)

 ```bash
-# Run with visible browser window
-agent-browser --headed open https://example.com
-agent-browser --headed snapshot -i
-agent-browser --headed click @e1
+# Save credentials once (encrypted with AGENT_BROWSER_ENCRYPTION_KEY)
+# Recommended: pipe password via stdin to avoid shell history exposure
+echo "pass" | agent-browser auth save github --url https://github.com/login --username user --password-stdin
+
+# Login using saved profile (LLM never sees password)
+agent-browser auth login github
+
+# List/show/delete profiles
+agent-browser auth list
+agent-browser auth show github
+agent-browser auth delete github
 ```

-## JSON Output
-
-Add `--json` for structured output:
+### Authentication with State Persistence

 ```bash
+# Login once and save state
+agent-browser open https://app.example.com/login
+agent-browser snapshot -i
+agent-browser fill @e1 "$USERNAME"
+agent-browser fill @e2 "$PASSWORD"
+agent-browser click @e3
+agent-browser wait --url "**/dashboard"
+agent-browser state save auth.json
+
+# Reuse in future sessions
+agent-browser state load auth.json
+agent-browser open https://app.example.com/dashboard
+```
+
+### Session Persistence
+
+```bash
+# Auto-save/restore cookies and localStorage across browser restarts
+agent-browser --session-name myapp open https://app.example.com/login
+# ... login flow ...
+agent-browser close  # State auto-saved to ~/.agent-browser/sessions/
+
+# Next time, state is auto-loaded
+agent-browser --session-name myapp open https://app.example.com/dashboard
+
+# Encrypt state at rest
+export AGENT_BROWSER_ENCRYPTION_KEY=$(openssl rand -hex 32)
+agent-browser --session-name secure open https://app.example.com
+
+# Manage saved states
+agent-browser state list
+agent-browser state show myapp-default.json
+agent-browser state clear myapp
+agent-browser state clean --older-than 7
+```
+
+### Data Extraction
+
+```bash
+agent-browser open https://example.com/products
+agent-browser snapshot -i
+agent-browser get text @e5           # Get specific element text
+agent-browser get text body > page.txt  # Get all page text
+
+# JSON output for parsing
 agent-browser snapshot -i --json
+agent-browser get text @e1 --json
 ```

-Returns:
+### Parallel Sessions
+
+```bash
+agent-browser --session site1 open https://site-a.com
+agent-browser --session site2 open https://site-b.com
+
+agent-browser --session site1 snapshot -i
+agent-browser --session site2 snapshot -i
+
+agent-browser session list
+```
+
+### Connect to Existing Chrome
+
+```bash
+# Auto-discover running Chrome with remote debugging enabled
+agent-browser --auto-connect open https://example.com
+agent-browser --auto-connect snapshot
+
+# Or with explicit CDP port
+agent-browser --cdp 9222 snapshot
+```
+
+### Color Scheme (Dark Mode)
+
+```bash
+# Persistent dark mode via flag (applies to all pages and new tabs)
+agent-browser --color-scheme dark open https://example.com
+
+# Or via environment variable
+AGENT_BROWSER_COLOR_SCHEME=dark agent-browser open https://example.com
+
+# Or set during session (persists for subsequent commands)
+agent-browser set media dark
+```
+
+### Viewport & Responsive Testing
+
+```bash
+# Set a custom viewport size (default is 1280x720)
+agent-browser set viewport 1920 1080
+agent-browser screenshot desktop.png
+
+# Test mobile-width layout
+agent-browser set viewport 375 812
+agent-browser screenshot mobile.png
+
+# Retina/HiDPI: same CSS layout at 2x pixel density
+# Screenshots stay at logical viewport size, but content renders at higher DPI
+agent-browser set viewport 1920 1080 2
+agent-browser screenshot retina.png
+
+# Device emulation (sets viewport + user agent in one step)
+agent-browser set device "iPhone 14"
+agent-browser screenshot device.png
+```
+
+The `scale` parameter (3rd argument) sets `window.devicePixelRatio` without changing CSS layout. Use it when testing retina rendering or capturing higher-resolution screenshots.
+
+### Visual Browser (Debugging)
+
+```bash
+agent-browser --headed open https://example.com
+agent-browser highlight @e1          # Highlight element
+agent-browser inspect                # Open Chrome DevTools for the active page
+agent-browser record start demo.webm # Record session
+agent-browser profiler start         # Start Chrome DevTools profiling
+agent-browser profiler stop trace.json # Stop and save profile (path optional)
+```
+
+Use `AGENT_BROWSER_HEADED=1` to enable headed mode via environment variable. Browser extensions work in both headed and headless mode.
+
+### Local Files (PDFs, HTML)
+
+```bash
+# Open local files with file:// URLs
+agent-browser --allow-file-access open file:///path/to/document.pdf
+agent-browser --allow-file-access open file:///path/to/page.html
+agent-browser screenshot output.png
+```
+
+### iOS Simulator (Mobile Safari)
+
+```bash
+# List available iOS simulators
+agent-browser device list
+
+# Launch Safari on a specific device
+agent-browser -p ios --device "iPhone 16 Pro" open https://example.com
+
+# Same workflow as desktop - snapshot, interact, re-snapshot
+agent-browser -p ios snapshot -i
+agent-browser -p ios tap @e1          # Tap (alias for click)
+agent-browser -p ios fill @e2 "text"
+agent-browser -p ios swipe up         # Mobile-specific gesture
+
+# Take screenshot
+agent-browser -p ios screenshot mobile.png
+
+# Close session (shuts down simulator)
+agent-browser -p ios close
+```
+
+**Requirements:** macOS with Xcode, Appium (`npm install -g appium && appium driver install xcuitest`)
+
+**Real devices:** Works with physical iOS devices if pre-configured. Use `--device "<UDID>"` where UDID is from `xcrun xctrace list devices`.
+
+## Security
+
+All security features are opt-in. By default, agent-browser imposes no restrictions on navigation, actions, or output.
+
+### Content Boundaries (Recommended for AI Agents)
+
+Enable `--content-boundaries` to wrap page-sourced output in markers that help LLMs distinguish tool output from untrusted page content:
+
+```bash
+export AGENT_BROWSER_CONTENT_BOUNDARIES=1
+agent-browser snapshot
+# Output:
+# --- AGENT_BROWSER_PAGE_CONTENT nonce=<hex> origin=https://example.com ---
+# [accessibility tree]
+# --- END_AGENT_BROWSER_PAGE_CONTENT nonce=<hex> ---
+```
+
+### Domain Allowlist
+
+Restrict navigation to trusted domains. Wildcards like `*.example.com` also match the bare domain `example.com`. Sub-resource requests, WebSocket, and EventSource connections to non-allowed domains are also blocked. Include CDN domains your target pages depend on:
+
+```bash
+export AGENT_BROWSER_ALLOWED_DOMAINS="example.com,*.example.com"
+agent-browser open https://example.com        # OK
+agent-browser open https://malicious.com       # Blocked
+```
+
+### Action Policy
+
+Use a policy file to gate destructive actions:
+
+```bash
+export AGENT_BROWSER_ACTION_POLICY=./policy.json
+```
+
+Example `policy.json`:
+
+```json
+{ "default": "deny", "allow": ["navigate", "snapshot", "click", "scroll", "wait", "get"] }
+```
+
+Auth vault operations (`auth login`, etc.) bypass action policy but domain allowlist still applies.
+
+### Output Limits
+
+Prevent context flooding from large pages:
+
+```bash
+export AGENT_BROWSER_MAX_OUTPUT=50000
+```
+
+## Diffing (Verifying Changes)
+
+Use `diff snapshot` after performing an action to verify it had the intended effect. This compares the current accessibility tree against the last snapshot taken in the session.
+
+```bash
+# Typical workflow: snapshot -> action -> diff
+agent-browser snapshot -i          # Take baseline snapshot
+agent-browser click @e2            # Perform action
+agent-browser diff snapshot        # See what changed (auto-compares to last snapshot)
+```
+
+For visual regression testing or monitoring:
+
+```bash
+# Save a baseline screenshot, then compare later
+agent-browser screenshot baseline.png
+# ... time passes or changes are made ...
+agent-browser diff screenshot --baseline baseline.png
+
+# Compare staging vs production
+agent-browser diff url https://staging.example.com https://prod.example.com --screenshot
+```
+
+`diff snapshot` output uses `+` for additions and `-` for removals, similar to git diff. `diff screenshot` produces a diff image with changed pixels highlighted in red, plus a mismatch percentage.
+
+## Timeouts and Slow Pages
+
+The default timeout is 25 seconds. This can be overridden with the `AGENT_BROWSER_DEFAULT_TIMEOUT` environment variable (value in milliseconds). For slow websites or large pages, use explicit waits instead of relying on the default timeout:
+
+```bash
+# Wait for network activity to settle (best for slow pages)
+agent-browser wait --load networkidle
+
+# Wait for a specific element to appear
+agent-browser wait "#content"
+agent-browser wait @e1
+
+# Wait for a specific URL pattern (useful after redirects)
+agent-browser wait --url "**/dashboard"
+
+# Wait for a JavaScript condition
+agent-browser wait --fn "document.readyState === 'complete'"
+
+# Wait a fixed duration (milliseconds) as a last resort
+agent-browser wait 5000
+```
+
+When dealing with consistently slow websites, use `wait --load networkidle` after `open` to ensure the page is fully loaded before taking a snapshot. If a specific element is slow to render, wait for it directly with `wait <selector>` or `wait @ref`.
+
+## Session Management and Cleanup
+
+When running multiple agents or automations concurrently, always use named sessions to avoid conflicts:
+
+```bash
+# Each agent gets its own isolated session
+agent-browser --session agent1 open site-a.com
+agent-browser --session agent2 open site-b.com
+
+# Check active sessions
+agent-browser session list
+```
+
+Always close your browser session when done to avoid leaked processes:
+
+```bash
+agent-browser close                    # Close default session
+agent-browser --session agent1 close   # Close specific session
+```
+
+If a previous session was not closed properly, the daemon may still be running. Use `agent-browser close` to clean it up before starting new work.
+
+To auto-shutdown the daemon after a period of inactivity (useful for ephemeral/CI environments):
+
+```bash
+AGENT_BROWSER_IDLE_TIMEOUT_MS=60000 agent-browser open example.com
+```
+
+## Ref Lifecycle (Important)
+
+Refs (`@e1`, `@e2`, etc.) are invalidated when the page changes. Always re-snapshot after:
+
+- Clicking links or buttons that navigate
+- Form submissions
+- Dynamic content loading (dropdowns, modals)
+
+```bash
+agent-browser click @e5              # Navigates to new page
+agent-browser snapshot -i            # MUST re-snapshot
+agent-browser click @e1              # Use new refs
+```
+
+## Annotated Screenshots (Vision Mode)
+
+Use `--annotate` to take a screenshot with numbered labels overlaid on interactive elements. Each label `[N]` maps to ref `@eN`. This also caches refs, so you can interact with elements immediately without a separate snapshot.
+
+```bash
+agent-browser screenshot --annotate
+# Output includes the image path and a legend:
+#   [1] @e1 button "Submit"
+#   [2] @e2 link "Home"
+#   [3] @e3 textbox "Email"
+agent-browser click @e2              # Click using ref from annotated screenshot
+```
+
+Use annotated screenshots when:
+
+- The page has unlabeled icon buttons or visual-only elements
+- You need to verify visual layout or styling
+- Canvas or chart elements are present (invisible to text snapshots)
+- You need spatial reasoning about element positions
+
+## Semantic Locators (Alternative to Refs)
+
+When refs are unavailable or unreliable, use semantic locators:
+
+```bash
+agent-browser find text "Sign In" click
+agent-browser find label "Email" fill "user@test.com"
+agent-browser find role button click --name "Submit"
+agent-browser find placeholder "Search" type "query"
+agent-browser find testid "submit-btn" click
+```
+
+## JavaScript Evaluation (eval)
+
+Use `eval` to run JavaScript in the browser context. **Shell quoting can corrupt complex expressions** -- use `--stdin` or `-b` to avoid issues.
+
+```bash
+# Simple expressions work with regular quoting
+agent-browser eval 'document.title'
+agent-browser eval 'document.querySelectorAll("img").length'
+
+# Complex JS: use --stdin with heredoc (RECOMMENDED)
+agent-browser eval --stdin <<'EVALEOF'
+JSON.stringify(
+  Array.from(document.querySelectorAll("img"))
+    .filter(i => !i.alt)
+    .map(i => ({ src: i.src.split("/").pop(), width: i.width }))
+)
+EVALEOF
+
+# Alternative: base64 encoding (avoids all shell escaping issues)
+agent-browser eval -b "$(echo -n 'Array.from(document.querySelectorAll("a")).map(a => a.href)' | base64)"
+```
+
+**Why this matters:** When the shell processes your command, inner double quotes, `!` characters (history expansion), backticks, and `$()` can all corrupt the JavaScript before it reaches agent-browser. The `--stdin` and `-b` flags bypass shell interpretation entirely.
+
+**Rules of thumb:**
+
+- Single-line, no nested quotes -> regular `eval 'expression'` with single quotes is fine
+- Nested quotes, arrow functions, template literals, or multiline -> use `eval --stdin <<'EVALEOF'`
+- Programmatic/generated scripts -> use `eval -b` with base64
+
+## Configuration File
+
+Create `agent-browser.json` in the project root for persistent settings:
+
 ```json
 {
-  "success": true,
-  "data": {
-    "refs": {
-      "e1": {"name": "Submit", "role": "button"},
-      "e2": {"name": "Email", "role": "textbox"}
-    },
-    "snapshot": "- button \"Submit\" [ref=e1]\n- textbox \"Email\" [ref=e2]"
-  }
+  "headed": true,
+  "proxy": "http://localhost:8080",
+  "profile": "./browser-data"
 }
 ```

+Priority (lowest to highest): `~/.agent-browser/config.json` < `./agent-browser.json` < env vars < CLI flags. Use `--config <path>` or `AGENT_BROWSER_CONFIG` env var for a custom config file (exits with error if missing/invalid). All CLI options map to camelCase keys (e.g., `--executable-path` -> `"executablePath"`). Boolean flags accept `true`/`false` values (e.g., `--headed false` overrides config). Extensions from user and project configs are merged, not replaced.
+
+## Browser Engine Selection
+
+Use `--engine` to choose a local browser engine. The default is `chrome`.
+
+```bash
+# Use Lightpanda (fast headless browser, requires separate install)
+agent-browser --engine lightpanda open example.com
+
+# Via environment variable
+export AGENT_BROWSER_ENGINE=lightpanda
+agent-browser open example.com
+
+# With custom binary path
+agent-browser --engine lightpanda --executable-path /path/to/lightpanda open example.com
+```
+
+Supported engines:
+- `chrome` (default) -- Chrome/Chromium via CDP
+- `lightpanda` -- Lightpanda headless browser via CDP (10x faster, 10x less memory than Chrome)
+
+Lightpanda does not support `--extension`, `--profile`, `--state`, or `--allow-file-access`. Install Lightpanda from https://lightpanda.io/docs/open-source/installation.
+
+## Deep-Dive Documentation
+
+| Reference                                                            | When to Use                                               |
+| -------------------------------------------------------------------- | --------------------------------------------------------- |
+| [references/commands.md](references/commands.md)                     | Full command reference with all options                   |
+| [references/snapshot-refs.md](references/snapshot-refs.md)           | Ref lifecycle, invalidation rules, troubleshooting        |
+| [references/session-management.md](references/session-management.md) | Parallel sessions, state persistence, concurrent scraping |
+| [references/authentication.md](references/authentication.md)         | Login flows, OAuth, 2FA handling, state reuse             |
+| [references/video-recording.md](references/video-recording.md)       | Recording workflows for debugging and documentation       |
+| [references/profiling.md](references/profiling.md)                   | Chrome DevTools profiling for performance analysis        |
+| [references/proxy-support.md](references/proxy-support.md)           | Proxy configuration, geo-testing, rotating proxies        |
+
+## Ready-to-Use Templates
+
+| Template                                                                 | Description                         |
+| ------------------------------------------------------------------------ | ----------------------------------- |
+| [templates/form-automation.sh](templates/form-automation.sh)             | Form filling with validation        |
+| [templates/authenticated-session.sh](templates/authenticated-session.sh) | Login once, reuse state             |
+| [templates/capture-workflow.sh](templates/capture-workflow.sh)           | Content extraction with screenshots |
+
+```bash
+./templates/form-automation.sh https://example.com/form
+./templates/authenticated-session.sh https://app.example.com/login
+./templates/capture-workflow.sh https://example.com ./output
+```
+
 ## vs Playwright MCP

 | Feature | agent-browser (CLI) | Playwright MCP |
--- a/plugins/compound-engineering/skills/agent-browser/references/authentication.md
+++ b/plugins/compound-engineering/skills/agent-browser/references/authentication.md
@@ -0,0 +1,303 @@
+# Authentication Patterns
+
+Login flows, session persistence, OAuth, 2FA, and authenticated browsing.
+
+**Related**: [commands.md](commands.md) for full command reference, [SKILL.md](../SKILL.md) for quick start.
+
+## Contents
+
+- [Import Auth from Your Browser](#import-auth-from-your-browser)
+- [Persistent Profiles](#persistent-profiles)
+- [Session Persistence](#session-persistence)
+- [Basic Login Flow](#basic-login-flow)
+- [Saving Authentication State](#saving-authentication-state)
+- [Restoring Authentication](#restoring-authentication)
+- [OAuth / SSO Flows](#oauth--sso-flows)
+- [Two-Factor Authentication](#two-factor-authentication)
+- [HTTP Basic Auth](#http-basic-auth)
+- [Cookie-Based Auth](#cookie-based-auth)
+- [Token Refresh Handling](#token-refresh-handling)
+- [Security Best Practices](#security-best-practices)
+
+## Import Auth from Your Browser
+
+The fastest way to authenticate is to reuse cookies from a Chrome session you are already logged into.
+
+**Step 1: Start Chrome with remote debugging**
+
+```bash
+# macOS
+"/Applications/Google Chrome.app/Contents/MacOS/Google Chrome" --remote-debugging-port=9222
+
+# Linux
+google-chrome --remote-debugging-port=9222
+
+# Windows
+"C:\Program Files\Google\Chrome\Application\chrome.exe" --remote-debugging-port=9222
+```
+
+Log in to your target site(s) in this Chrome window as you normally would.
+
+> **Security note:** `--remote-debugging-port` exposes full browser control on localhost. Any local process can connect and read cookies, execute JS, etc. Only use on trusted machines and close Chrome when done.
+
+**Step 2: Grab the auth state**
+
+```bash
+# Auto-discover the running Chrome and save its cookies + localStorage
+agent-browser --auto-connect state save ./my-auth.json
+```
+
+**Step 3: Reuse in automation**
+
+```bash
+# Load auth at launch
+agent-browser --state ./my-auth.json open https://app.example.com/dashboard
+
+# Or load into an existing session
+agent-browser state load ./my-auth.json
+agent-browser open https://app.example.com/dashboard
+```
+
+This works for any site, including those with complex OAuth flows, SSO, or 2FA -- as long as Chrome already has valid session cookies.
+
+> **Security note:** State files contain session tokens in plaintext. Add them to `.gitignore`, delete when no longer needed, and set `AGENT_BROWSER_ENCRYPTION_KEY` for encryption at rest. See [Security Best Practices](#security-best-practices).
+
+**Tip:** Combine with `--session-name` so the imported auth auto-persists across restarts:
+
+```bash
+agent-browser --session-name myapp state load ./my-auth.json
+# From now on, state is auto-saved/restored for "myapp"
+```
+
+## Persistent Profiles
+
+Use `--profile` to point agent-browser at a Chrome user data directory. This persists everything (cookies, IndexedDB, service workers, cache) across browser restarts without explicit save/load:
+
+```bash
+# First run: login once
+agent-browser --profile ~/.myapp-profile open https://app.example.com/login
+# ... complete login flow ...
+
+# All subsequent runs: already authenticated
+agent-browser --profile ~/.myapp-profile open https://app.example.com/dashboard
+```
+
+Use different paths for different projects or test users:
+
+```bash
+agent-browser --profile ~/.profiles/admin open https://app.example.com
+agent-browser --profile ~/.profiles/viewer open https://app.example.com
+```
+
+Or set via environment variable:
+
+```bash
+export AGENT_BROWSER_PROFILE=~/.myapp-profile
+agent-browser open https://app.example.com/dashboard
+```
+
+## Session Persistence
+
+Use `--session-name` to auto-save and restore cookies + localStorage by name, without managing files:
+
+```bash
+# Auto-saves state on close, auto-restores on next launch
+agent-browser --session-name twitter open https://twitter.com
+# ... login flow ...
+agent-browser close  # state saved to ~/.agent-browser/sessions/
+
+# Next time: state is automatically restored
+agent-browser --session-name twitter open https://twitter.com
+```
+
+Encrypt state at rest:
+
+```bash
+export AGENT_BROWSER_ENCRYPTION_KEY=$(openssl rand -hex 32)
+agent-browser --session-name secure open https://app.example.com
+```
+
+## Basic Login Flow
+
+```bash
+# Navigate to login page
+agent-browser open https://app.example.com/login
+agent-browser wait --load networkidle
+
+# Get form elements
+agent-browser snapshot -i
+# Output: @e1 [input type="email"], @e2 [input type="password"], @e3 [button] "Sign In"
+
+# Fill credentials
+agent-browser fill @e1 "user@example.com"
+agent-browser fill @e2 "password123"
+
+# Submit
+agent-browser click @e3
+agent-browser wait --load networkidle
+
+# Verify login succeeded
+agent-browser get url  # Should be dashboard, not login
+```
+
+## Saving Authentication State
+
+After logging in, save state for reuse:
+
+```bash
+# Login first (see above)
+agent-browser open https://app.example.com/login
+agent-browser snapshot -i
+agent-browser fill @e1 "user@example.com"
+agent-browser fill @e2 "password123"
+agent-browser click @e3
+agent-browser wait --url "**/dashboard"
+
+# Save authenticated state
+agent-browser state save ./auth-state.json
+```
+
+## Restoring Authentication
+
+Skip login by loading saved state:
+
+```bash
+# Load saved auth state
+agent-browser state load ./auth-state.json
+
+# Navigate directly to protected page
+agent-browser open https://app.example.com/dashboard
+
+# Verify authenticated
+agent-browser snapshot -i
+```
+
+## OAuth / SSO Flows
+
+For OAuth redirects:
+
+```bash
+# Start OAuth flow
+agent-browser open https://app.example.com/auth/google
+
+# Handle redirects automatically
+agent-browser wait --url "**/accounts.google.com**"
+agent-browser snapshot -i
+
+# Fill Google credentials
+agent-browser fill @e1 "user@gmail.com"
+agent-browser click @e2  # Next button
+agent-browser wait 2000
+agent-browser snapshot -i
+agent-browser fill @e3 "password"
+agent-browser click @e4  # Sign in
+
+# Wait for redirect back
+agent-browser wait --url "**/app.example.com**"
+agent-browser state save ./oauth-state.json
+```
+
+## Two-Factor Authentication
+
+Handle 2FA with manual intervention:
+
+```bash
+# Login with credentials
+agent-browser open https://app.example.com/login --headed  # Show browser
+agent-browser snapshot -i
+agent-browser fill @e1 "user@example.com"
+agent-browser fill @e2 "password123"
+agent-browser click @e3
+
+# Wait for user to complete 2FA manually
+echo "Complete 2FA in the browser window..."
+agent-browser wait --url "**/dashboard" --timeout 120000
+
+# Save state after 2FA
+agent-browser state save ./2fa-state.json
+```
+
+## HTTP Basic Auth
+
+For sites using HTTP Basic Authentication:
+
+```bash
+# Set credentials before navigation
+agent-browser set credentials username password
+
+# Navigate to protected resource
+agent-browser open https://protected.example.com/api
+```
+
+## Cookie-Based Auth
+
+Manually set authentication cookies:
+
+```bash
+# Set auth cookie
+agent-browser cookies set session_token "abc123xyz"
+
+# Navigate to protected page
+agent-browser open https://app.example.com/dashboard
+```
+
+## Token Refresh Handling
+
+For sessions with expiring tokens:
+
+```bash
+#!/bin/bash
+# Wrapper that handles token refresh
+
+STATE_FILE="./auth-state.json"
+
+# Try loading existing state
+if [[ -f "$STATE_FILE" ]]; then
+    agent-browser state load "$STATE_FILE"
+    agent-browser open https://app.example.com/dashboard
+
+    # Check if session is still valid
+    URL=$(agent-browser get url)
+    if [[ "$URL" == *"/login"* ]]; then
+        echo "Session expired, re-authenticating..."
+        # Perform fresh login
+        agent-browser snapshot -i
+        agent-browser fill @e1 "$USERNAME"
+        agent-browser fill @e2 "$PASSWORD"
+        agent-browser click @e3
+        agent-browser wait --url "**/dashboard"
+        agent-browser state save "$STATE_FILE"
+    fi
+else
+    # First-time login
+    agent-browser open https://app.example.com/login
+    # ... login flow ...
+fi
+```
+
+## Security Best Practices
+
+1. **Never commit state files** - They contain session tokens
+   ```bash
+   echo "*.auth-state.json" >> .gitignore
+   ```
+
+2. **Use environment variables for credentials**
+   ```bash
+   agent-browser fill @e1 "$APP_USERNAME"
+   agent-browser fill @e2 "$APP_PASSWORD"
+   ```
+
+3. **Clean up after automation**
+   ```bash
+   agent-browser cookies clear
+   rm -f ./auth-state.json
+   ```
+
+4. **Use short-lived sessions for CI/CD**
+   ```bash
+   # Don't persist state in CI
+   agent-browser open https://app.example.com/login
+   # ... login and perform actions ...
+   agent-browser close  # Session ends, nothing persisted
+   ```
--- a/plugins/compound-engineering/skills/agent-browser/references/commands.md
+++ b/plugins/compound-engineering/skills/agent-browser/references/commands.md
@@ -0,0 +1,266 @@
+# Command Reference
+
+Complete reference for all agent-browser commands. For quick start and common patterns, see SKILL.md.
+
+## Navigation
+
+```bash
+agent-browser open <url>      # Navigate to URL (aliases: goto, navigate)
+                              # Supports: https://, http://, file://, about:, data://
+                              # Auto-prepends https:// if no protocol given
+agent-browser back            # Go back
+agent-browser forward         # Go forward
+agent-browser reload          # Reload page
+agent-browser close           # Close browser (aliases: quit, exit)
+agent-browser connect 9222    # Connect to browser via CDP port
+```
+
+## Snapshot (page analysis)
+
+```bash
+agent-browser snapshot            # Full accessibility tree
+agent-browser snapshot -i         # Interactive elements only (recommended)
+agent-browser snapshot -c         # Compact output
+agent-browser snapshot -d 3       # Limit depth to 3
+agent-browser snapshot -s "#main" # Scope to CSS selector
+```
+
+## Interactions (use @refs from snapshot)
+
+```bash
+agent-browser click @e1           # Click
+agent-browser click @e1 --new-tab # Click and open in new tab
+agent-browser dblclick @e1        # Double-click
+agent-browser focus @e1           # Focus element
+agent-browser fill @e2 "text"     # Clear and type
+agent-browser type @e2 "text"     # Type without clearing
+agent-browser press Enter         # Press key (alias: key)
+agent-browser press Control+a     # Key combination
+agent-browser keydown Shift       # Hold key down
+agent-browser keyup Shift         # Release key
+agent-browser hover @e1           # Hover
+agent-browser check @e1           # Check checkbox
+agent-browser uncheck @e1         # Uncheck checkbox
+agent-browser select @e1 "value"  # Select dropdown option
+agent-browser select @e1 "a" "b"  # Select multiple options
+agent-browser scroll down 500     # Scroll page (default: down 300px)
+agent-browser scrollintoview @e1  # Scroll element into view (alias: scrollinto)
+agent-browser drag @e1 @e2        # Drag and drop
+agent-browser upload @e1 file.pdf # Upload files
+```
+
+## Get Information
+
+```bash
+agent-browser get text @e1        # Get element text
+agent-browser get html @e1        # Get innerHTML
+agent-browser get value @e1       # Get input value
+agent-browser get attr @e1 href   # Get attribute
+agent-browser get title           # Get page title
+agent-browser get url             # Get current URL
+agent-browser get cdp-url         # Get CDP WebSocket URL
+agent-browser get count ".item"   # Count matching elements
+agent-browser get box @e1         # Get bounding box
+agent-browser get styles @e1      # Get computed styles (font, color, bg, etc.)
+```
+
+## Check State
+
+```bash
+agent-browser is visible @e1      # Check if visible
+agent-browser is enabled @e1      # Check if enabled
+agent-browser is checked @e1      # Check if checked
+```
+
+## Screenshots and PDF
+
+```bash
+agent-browser screenshot          # Save to temporary directory
+agent-browser screenshot path.png # Save to specific path
+agent-browser screenshot --full   # Full page
+agent-browser pdf output.pdf      # Save as PDF
+```
+
+## Video Recording
+
+```bash
+agent-browser record start ./demo.webm    # Start recording
+agent-browser click @e1                   # Perform actions
+agent-browser record stop                 # Stop and save video
+agent-browser record restart ./take2.webm # Stop current + start new
+```
+
+## Wait
+
+```bash
+agent-browser wait @e1                     # Wait for element
+agent-browser wait 2000                    # Wait milliseconds
+agent-browser wait --text "Success"        # Wait for text (or -t)
+agent-browser wait --url "**/dashboard"    # Wait for URL pattern (or -u)
+agent-browser wait --load networkidle      # Wait for network idle (or -l)
+agent-browser wait --fn "window.ready"     # Wait for JS condition (or -f)
+```
+
+## Mouse Control
+
+```bash
+agent-browser mouse move 100 200      # Move mouse
+agent-browser mouse down left         # Press button
+agent-browser mouse up left           # Release button
+agent-browser mouse wheel 100         # Scroll wheel
+```
+
+## Semantic Locators (alternative to refs)
+
+```bash
+agent-browser find role button click --name "Submit"
+agent-browser find text "Sign In" click
+agent-browser find text "Sign In" click --exact      # Exact match only
+agent-browser find label "Email" fill "user@test.com"
+agent-browser find placeholder "Search" type "query"
+agent-browser find alt "Logo" click
+agent-browser find title "Close" click
+agent-browser find testid "submit-btn" click
+agent-browser find first ".item" click
+agent-browser find last ".item" click
+agent-browser find nth 2 "a" hover
+```
+
+## Browser Settings
+
+```bash
+agent-browser set viewport 1920 1080          # Set viewport size
+agent-browser set viewport 1920 1080 2        # 2x retina (same CSS size, higher res screenshots)
+agent-browser set device "iPhone 14"          # Emulate device
+agent-browser set geo 37.7749 -122.4194       # Set geolocation (alias: geolocation)
+agent-browser set offline on                  # Toggle offline mode
+agent-browser set headers '{"X-Key":"v"}'     # Extra HTTP headers
+agent-browser set credentials user pass       # HTTP basic auth (alias: auth)
+agent-browser set media dark                  # Emulate color scheme
+agent-browser set media light reduced-motion  # Light mode + reduced motion
+```
+
+## Cookies and Storage
+
+```bash
+agent-browser cookies                     # Get all cookies
+agent-browser cookies set name value      # Set cookie
+agent-browser cookies clear               # Clear cookies
+agent-browser storage local               # Get all localStorage
+agent-browser storage local key           # Get specific key
+agent-browser storage local set k v       # Set value
+agent-browser storage local clear         # Clear all
+```
+
+## Network
+
+```bash
+agent-browser network route <url>              # Intercept requests
+agent-browser network route <url> --abort      # Block requests
+agent-browser network route <url> --body '{}'  # Mock response
+agent-browser network unroute [url]            # Remove routes
+agent-browser network requests                 # View tracked requests
+agent-browser network requests --filter api    # Filter requests
+```
+
+## Tabs and Windows
+
+```bash
+agent-browser tab                 # List tabs
+agent-browser tab new [url]       # New tab
+agent-browser tab 2               # Switch to tab by index
+agent-browser tab close           # Close current tab
+agent-browser tab close 2         # Close tab by index
+agent-browser window new          # New window
+```
+
+## Frames
+
+```bash
+agent-browser frame "#iframe"     # Switch to iframe
+agent-browser frame main          # Back to main frame
+```
+
+## Dialogs
+
+```bash
+agent-browser dialog accept [text]  # Accept dialog
+agent-browser dialog dismiss        # Dismiss dialog
+```
+
+## JavaScript
+
+```bash
+agent-browser eval "document.title"          # Simple expressions only
+agent-browser eval -b "<base64>"             # Any JavaScript (base64 encoded)
+agent-browser eval --stdin                   # Read script from stdin
+```
+
+Use `-b`/`--base64` or `--stdin` for reliable execution. Shell escaping with nested quotes and special characters is error-prone.
+
+```bash
+# Base64 encode your script, then:
+agent-browser eval -b "ZG9jdW1lbnQucXVlcnlTZWxlY3RvcignW3NyYyo9Il9uZXh0Il0nKQ=="
+
+# Or use stdin with heredoc for multiline scripts:
+cat <<'EOF' | agent-browser eval --stdin
+const links = document.querySelectorAll('a');
+Array.from(links).map(a => a.href);
+EOF
+```
+
+## State Management
+
+```bash
+agent-browser state save auth.json    # Save cookies, storage, auth state
+agent-browser state load auth.json    # Restore saved state
+```
+
+## Global Options
+
+```bash
+agent-browser --session <name> ...    # Isolated browser session
+agent-browser --json ...              # JSON output for parsing
+agent-browser --headed ...            # Show browser window (not headless)
+agent-browser --full ...              # Full page screenshot (-f)
+agent-browser --cdp <port> ...        # Connect via Chrome DevTools Protocol
+agent-browser -p <provider> ...       # Cloud browser provider (--provider)
+agent-browser --proxy <url> ...       # Use proxy server
+agent-browser --proxy-bypass <hosts>  # Hosts to bypass proxy
+agent-browser --headers <json> ...    # HTTP headers scoped to URL's origin
+agent-browser --executable-path <p>   # Custom browser executable
+agent-browser --extension <path> ...  # Load browser extension (repeatable)
+agent-browser --ignore-https-errors   # Ignore SSL certificate errors
+agent-browser --help                  # Show help (-h)
+agent-browser --version               # Show version (-V)
+agent-browser <command> --help        # Show detailed help for a command
+```
+
+## Debugging
+
+```bash
+agent-browser --headed open example.com   # Show browser window
+agent-browser --cdp 9222 snapshot         # Connect via CDP port
+agent-browser connect 9222                # Alternative: connect command
+agent-browser console                     # View console messages
+agent-browser console --clear             # Clear console
+agent-browser errors                      # View page errors
+agent-browser errors --clear              # Clear errors
+agent-browser highlight @e1               # Highlight element
+agent-browser inspect                     # Open Chrome DevTools for this session
+agent-browser trace start                 # Start recording trace
+agent-browser trace stop trace.zip        # Stop and save trace
+agent-browser profiler start              # Start Chrome DevTools profiling
+agent-browser profiler stop trace.json    # Stop and save profile
+```
+
+## Environment Variables
+
+```bash
+AGENT_BROWSER_SESSION="mysession"            # Default session name
+AGENT_BROWSER_EXECUTABLE_PATH="/path/chrome" # Custom browser path
+AGENT_BROWSER_EXTENSIONS="/ext1,/ext2"       # Comma-separated extension paths
+AGENT_BROWSER_PROVIDER="browserbase"         # Cloud browser provider
+AGENT_BROWSER_STREAM_PORT="9223"             # WebSocket streaming port
+AGENT_BROWSER_HOME="/path/to/agent-browser"  # Custom install location
+```
--- a/plugins/compound-engineering/skills/agent-browser/references/profiling.md
+++ b/plugins/compound-engineering/skills/agent-browser/references/profiling.md
@@ -0,0 +1,120 @@
+# Profiling
+
+Capture Chrome DevTools performance profiles during browser automation for performance analysis.
+
+**Related**: [commands.md](commands.md) for full command reference, [SKILL.md](../SKILL.md) for quick start.
+
+## Contents
+
+- [Basic Profiling](#basic-profiling)
+- [Profiler Commands](#profiler-commands)
+- [Categories](#categories)
+- [Use Cases](#use-cases)
+- [Output Format](#output-format)
+- [Viewing Profiles](#viewing-profiles)
+- [Limitations](#limitations)
+
+## Basic Profiling
+
+```bash
+# Start profiling
+agent-browser profiler start
+
+# Perform actions
+agent-browser navigate https://example.com
+agent-browser click "#button"
+agent-browser wait 1000
+
+# Stop and save
+agent-browser profiler stop ./trace.json
+```
+
+## Profiler Commands
+
+```bash
+# Start profiling with default categories
+agent-browser profiler start
+
+# Start with custom trace categories
+agent-browser profiler start --categories "devtools.timeline,v8.execute,blink.user_timing"
+
+# Stop profiling and save to file
+agent-browser profiler stop ./trace.json
+```
+
+## Categories
+
+The `--categories` flag accepts a comma-separated list of Chrome trace categories. Default categories include:
+
+- `devtools.timeline` -- standard DevTools performance traces
+- `v8.execute` -- time spent running JavaScript
+- `blink` -- renderer events
+- `blink.user_timing` -- `performance.mark()` / `performance.measure()` calls
+- `latencyInfo` -- input-to-latency tracking
+- `renderer.scheduler` -- task scheduling and execution
+- `toplevel` -- broad-spectrum basic events
+
+Several `disabled-by-default-*` categories are also included for detailed timeline, call stack, and V8 CPU profiling data.
+
+## Use Cases
+
+### Diagnosing Slow Page Loads
+
+```bash
+agent-browser profiler start
+agent-browser navigate https://app.example.com
+agent-browser wait --load networkidle
+agent-browser profiler stop ./page-load-profile.json
+```
+
+### Profiling User Interactions
+
+```bash
+agent-browser navigate https://app.example.com
+agent-browser profiler start
+agent-browser click "#submit"
+agent-browser wait 2000
+agent-browser profiler stop ./interaction-profile.json
+```
+
+### CI Performance Regression Checks
+
+```bash
+#!/bin/bash
+agent-browser profiler start
+agent-browser navigate https://app.example.com
+agent-browser wait --load networkidle
+agent-browser profiler stop "./profiles/build-${BUILD_ID}.json"
+```
+
+## Output Format
+
+The output is a JSON file in Chrome Trace Event format:
+
+```json
+{
+  "traceEvents": [
+    { "cat": "devtools.timeline", "name": "RunTask", "ph": "X", "ts": 12345, "dur": 100 },
+    ...
+  ],
+  "metadata": {
+    "clock-domain": "LINUX_CLOCK_MONOTONIC"
+  }
+}
+```
+
+The `metadata.clock-domain` field is set based on the host platform (Linux or macOS). On Windows it is omitted.
+
+## Viewing Profiles
+
+Load the output JSON file in any of these tools:
+
+- **Chrome DevTools**: Performance panel > Load profile (Ctrl+Shift+I > Performance)
+- **Perfetto UI**: https://ui.perfetto.dev/ -- drag and drop the JSON file
+- **Trace Viewer**: `chrome://tracing` in any Chromium browser
+
+## Limitations
+
+- Only works with Chromium-based browsers (Chrome, Edge). Not supported on Firefox or WebKit.
+- Trace data accumulates in memory while profiling is active (capped at 5 million events). Stop profiling promptly after the area of interest.
+- Data collection on stop has a 30-second timeout. If the browser is unresponsive, the stop command may fail.
--- a/plugins/compound-engineering/skills/agent-browser/references/proxy-support.md
+++ b/plugins/compound-engineering/skills/agent-browser/references/proxy-support.md
@@ -0,0 +1,194 @@
+# Proxy Support
+
+Proxy configuration for geo-testing, rate limiting avoidance, and corporate environments.
+
+**Related**: [commands.md](commands.md) for global options, [SKILL.md](../SKILL.md) for quick start.
+
+## Contents
+
+- [Basic Proxy Configuration](#basic-proxy-configuration)
+- [Authenticated Proxy](#authenticated-proxy)
+- [SOCKS Proxy](#socks-proxy)
+- [Proxy Bypass](#proxy-bypass)
+- [Common Use Cases](#common-use-cases)
+- [Verifying Proxy Connection](#verifying-proxy-connection)
+- [Troubleshooting](#troubleshooting)
+- [Best Practices](#best-practices)
+
+## Basic Proxy Configuration
+
+Use the `--proxy` flag or set proxy via environment variable:
+
+```bash
+# Via CLI flag
+agent-browser --proxy "http://proxy.example.com:8080" open https://example.com
+
+# Via environment variable
+export HTTP_PROXY="http://proxy.example.com:8080"
+agent-browser open https://example.com
+
+# HTTPS proxy
+export HTTPS_PROXY="https://proxy.example.com:8080"
+agent-browser open https://example.com
+
+# Both
+export HTTP_PROXY="http://proxy.example.com:8080"
+export HTTPS_PROXY="http://proxy.example.com:8080"
+agent-browser open https://example.com
+```
+
+## Authenticated Proxy
+
+For proxies requiring authentication:
+
+```bash
+# Include credentials in URL
+export HTTP_PROXY="http://username:password@proxy.example.com:8080"
+agent-browser open https://example.com
+```
+
+## SOCKS Proxy
+
+```bash
+# SOCKS5 proxy
+export ALL_PROXY="socks5://proxy.example.com:1080"
+agent-browser open https://example.com
+
+# SOCKS5 with auth
+export ALL_PROXY="socks5://user:pass@proxy.example.com:1080"
+agent-browser open https://example.com
+```
+
+## Proxy Bypass
+
+Skip proxy for specific domains using `--proxy-bypass` or `NO_PROXY`:
+
+```bash
+# Via CLI flag
+agent-browser --proxy "http://proxy.example.com:8080" --proxy-bypass "localhost,*.internal.com" open https://example.com
+
+# Via environment variable
+export NO_PROXY="localhost,127.0.0.1,.internal.company.com"
+agent-browser open https://internal.company.com  # Direct connection
+agent-browser open https://external.com          # Via proxy
+```
+
+## Common Use Cases
+
+### Geo-Location Testing
+
+```bash
+#!/bin/bash
+# Test site from different regions using geo-located proxies
+
+PROXIES=(
+    "http://us-proxy.example.com:8080"
+    "http://eu-proxy.example.com:8080"
+    "http://asia-proxy.example.com:8080"
+)
+
+for proxy in "${PROXIES[@]}"; do
+    export HTTP_PROXY="$proxy"
+    export HTTPS_PROXY="$proxy"
+
+    region=$(echo "$proxy" | grep -oP '^\w+-\w+')
+    echo "Testing from: $region"
+
+    agent-browser --session "$region" open https://example.com
+    agent-browser --session "$region" screenshot "./screenshots/$region.png"
+    agent-browser --session "$region" close
+done
+```
+
+### Rotating Proxies for Scraping
+
+```bash
+#!/bin/bash
+# Rotate through proxy list to avoid rate limiting
+
+PROXY_LIST=(
+    "http://proxy1.example.com:8080"
+    "http://proxy2.example.com:8080"
+    "http://proxy3.example.com:8080"
+)
+
+URLS=(
+    "https://site.com/page1"
+    "https://site.com/page2"
+    "https://site.com/page3"
+)
+
+for i in "${!URLS[@]}"; do
+    proxy_index=$((i % ${#PROXY_LIST[@]}))
+    export HTTP_PROXY="${PROXY_LIST[$proxy_index]}"
+    export HTTPS_PROXY="${PROXY_LIST[$proxy_index]}"
+
+    agent-browser open "${URLS[$i]}"
+    agent-browser get text body > "output-$i.txt"
+    agent-browser close
+
+    sleep 1  # Polite delay
+done
+```
+
+### Corporate Network Access
+
+```bash
+#!/bin/bash
+# Access internal sites via corporate proxy
+
+export HTTP_PROXY="http://corpproxy.company.com:8080"
+export HTTPS_PROXY="http://corpproxy.company.com:8080"
+export NO_PROXY="localhost,127.0.0.1,.company.com"
+
+# External sites go through proxy
+agent-browser open https://external-vendor.com
+
+# Internal sites bypass proxy
+agent-browser open https://intranet.company.com
+```
+
+## Verifying Proxy Connection
+
+```bash
+# Check your apparent IP
+agent-browser open https://httpbin.org/ip
+agent-browser get text body
+# Should show proxy's IP, not your real IP
+```
+
+## Troubleshooting
+
+### Proxy Connection Failed
+
+```bash
+# Test proxy connectivity first
+curl -x http://proxy.example.com:8080 https://httpbin.org/ip
+
+# Check if proxy requires auth
+export HTTP_PROXY="http://user:pass@proxy.example.com:8080"
+```
+
+### SSL/TLS Errors Through Proxy
+
+Some proxies perform SSL inspection. If you encounter certificate errors:
+
+```bash
+# For testing only - not recommended for production
+agent-browser open https://example.com --ignore-https-errors
+```
+
+### Slow Performance
+
+```bash
+# Use proxy only when necessary
+export NO_PROXY="*.cdn.com,*.static.com"  # Direct CDN access
+```
+
+## Best Practices
+
+1. **Use environment variables** - Don't hardcode proxy credentials
+2. **Set NO_PROXY appropriately** - Avoid routing local traffic through proxy
+3. **Test proxy before automation** - Verify connectivity with simple requests
+4. **Handle proxy failures gracefully** - Implement retry logic for unstable proxies
+5. **Rotate proxies for large scraping jobs** - Distribute load and avoid bans
--- a/plugins/compound-engineering/skills/agent-browser/references/session-management.md
+++ b/plugins/compound-engineering/skills/agent-browser/references/session-management.md
@@ -0,0 +1,193 @@
+# Session Management
+
+Multiple isolated browser sessions with state persistence and concurrent browsing.
+
+**Related**: [authentication.md](authentication.md) for login patterns, [SKILL.md](../SKILL.md) for quick start.
+
+## Contents
+
+- [Named Sessions](#named-sessions)
+- [Session Isolation Properties](#session-isolation-properties)
+- [Session State Persistence](#session-state-persistence)
+- [Common Patterns](#common-patterns)
+- [Default Session](#default-session)
+- [Session Cleanup](#session-cleanup)
+- [Best Practices](#best-practices)
+
+## Named Sessions
+
+Use `--session` flag to isolate browser contexts:
+
+```bash
+# Session 1: Authentication flow
+agent-browser --session auth open https://app.example.com/login
+
+# Session 2: Public browsing (separate cookies, storage)
+agent-browser --session public open https://example.com
+
+# Commands are isolated by session
+agent-browser --session auth fill @e1 "user@example.com"
+agent-browser --session public get text body
+```
+
+## Session Isolation Properties
+
+Each session has independent:
+- Cookies
+- LocalStorage / SessionStorage
+- IndexedDB
+- Cache
+- Browsing history
+- Open tabs
+
+## Session State Persistence
+
+### Save Session State
+
+```bash
+# Save cookies, storage, and auth state
+agent-browser state save /path/to/auth-state.json
+```
+
+### Load Session State
+
+```bash
+# Restore saved state
+agent-browser state load /path/to/auth-state.json
+
+# Continue with authenticated session
+agent-browser open https://app.example.com/dashboard
+```
+
+### State File Contents
+
+```json
+{
+  "cookies": [...],
+  "localStorage": {...},
+  "sessionStorage": {...},
+  "origins": [...]
+}
+```
+
+## Common Patterns
+
+### Authenticated Session Reuse
+
+```bash
+#!/bin/bash
+# Save login state once, reuse many times
+
+STATE_FILE="/tmp/auth-state.json"
+
+# Check if we have saved state
+if [[ -f "$STATE_FILE" ]]; then
+    agent-browser state load "$STATE_FILE"
+    agent-browser open https://app.example.com/dashboard
+else
+    # Perform login
+    agent-browser open https://app.example.com/login
+    agent-browser snapshot -i
+    agent-browser fill @e1 "$USERNAME"
+    agent-browser fill @e2 "$PASSWORD"
+    agent-browser click @e3
+    agent-browser wait --load networkidle
+
+    # Save for future use
+    agent-browser state save "$STATE_FILE"
+fi
+```
+
+### Concurrent Scraping
+
+```bash
+#!/bin/bash
+# Scrape multiple sites concurrently
+
+# Start all sessions
+agent-browser --session site1 open https://site1.com &
+agent-browser --session site2 open https://site2.com &
+agent-browser --session site3 open https://site3.com &
+wait
+
+# Extract from each
+agent-browser --session site1 get text body > site1.txt
+agent-browser --session site2 get text body > site2.txt
+agent-browser --session site3 get text body > site3.txt
+
+# Cleanup
+agent-browser --session site1 close
+agent-browser --session site2 close
+agent-browser --session site3 close
+```
+
+### A/B Testing Sessions
+
+```bash
+# Test different user experiences
+agent-browser --session variant-a open "https://app.com?variant=a"
+agent-browser --session variant-b open "https://app.com?variant=b"
+
+# Compare
+agent-browser --session variant-a screenshot /tmp/variant-a.png
+agent-browser --session variant-b screenshot /tmp/variant-b.png
+```
+
+## Default Session
+
+When `--session` is omitted, commands use the default session:
+
+```bash
+# These use the same default session
+agent-browser open https://example.com
+agent-browser snapshot -i
+agent-browser close  # Closes default session
+```
+
+## Session Cleanup
+
+```bash
+# Close specific session
+agent-browser --session auth close
+
+# List active sessions
+agent-browser session list
+```
+
+## Best Practices
+
+### 1. Name Sessions Semantically
+
+```bash
+# GOOD: Clear purpose
+agent-browser --session github-auth open https://github.com
+agent-browser --session docs-scrape open https://docs.example.com
+
+# AVOID: Generic names
+agent-browser --session s1 open https://github.com
+```
+
+### 2. Always Clean Up
+
+```bash
+# Close sessions when done
+agent-browser --session auth close
+agent-browser --session scrape close
+```
+
+### 3. Handle State Files Securely
+
+```bash
+# Don't commit state files (contain auth tokens!)
+echo "*.auth-state.json" >> .gitignore
+
+# Delete after use
+rm /tmp/auth-state.json
+```
+
+### 4. Timeout Long Sessions
+
+```bash
+# Set timeout for automated scripts
+timeout 60 agent-browser --session long-task get text body
+```
--- a/plugins/compound-engineering/skills/agent-browser/references/snapshot-refs.md
+++ b/plugins/compound-engineering/skills/agent-browser/references/snapshot-refs.md
@@ -0,0 +1,194 @@
+# Snapshot and Refs
+
+Compact element references that reduce context usage dramatically for AI agents.
+
+**Related**: [commands.md](commands.md) for full command reference, [SKILL.md](../SKILL.md) for quick start.
+
+## Contents
+
+- [How Refs Work](#how-refs-work)
+- [Snapshot Command](#the-snapshot-command)
+- [Using Refs](#using-refs)
+- [Ref Lifecycle](#ref-lifecycle)
+- [Best Practices](#best-practices)
+- [Ref Notation Details](#ref-notation-details)
+- [Troubleshooting](#troubleshooting)
+
+## How Refs Work
+
+Traditional approach:
+```
+Full DOM/HTML -> AI parses -> CSS selector -> Action (~3000-5000 tokens)
+```
+
+agent-browser approach:
+```
+Compact snapshot -> @refs assigned -> Direct interaction (~200-400 tokens)
+```
+
+## The Snapshot Command
+
+```bash
+# Basic snapshot (shows page structure)
+agent-browser snapshot
+
+# Interactive snapshot (-i flag) - RECOMMENDED
+agent-browser snapshot -i
+```
+
+### Snapshot Output Format
+
+```
+Page: Example Site - Home
+URL: https://example.com
+
+@e1 [header]
+  @e2 [nav]
+    @e3 [a] "Home"
+    @e4 [a] "Products"
+    @e5 [a] "About"
+  @e6 [button] "Sign In"
+
+@e7 [main]
+  @e8 [h1] "Welcome"
+  @e9 [form]
+    @e10 [input type="email"] placeholder="Email"
+    @e11 [input type="password"] placeholder="Password"
+    @e12 [button type="submit"] "Log In"
+
+@e13 [footer]
+  @e14 [a] "Privacy Policy"
+```
+
+## Using Refs
+
+Once you have refs, interact directly:
+
+```bash
+# Click the "Sign In" button
+agent-browser click @e6
+
+# Fill email input
+agent-browser fill @e10 "user@example.com"
+
+# Fill password
+agent-browser fill @e11 "password123"
+
+# Submit the form
+agent-browser click @e12
+```
+
+## Ref Lifecycle
+
+**IMPORTANT**: Refs are invalidated when the page changes!
+
+```bash
+# Get initial snapshot
+agent-browser snapshot -i
+# @e1 [button] "Next"
+
+# Click triggers page change
+agent-browser click @e1
+
+# MUST re-snapshot to get new refs!
+agent-browser snapshot -i
+# @e1 [h1] "Page 2"  <- Different element now!
+```
+
+## Best Practices
+
+### 1. Always Snapshot Before Interacting
+
+```bash
+# CORRECT
+agent-browser open https://example.com
+agent-browser snapshot -i          # Get refs first
+agent-browser click @e1            # Use ref
+
+# WRONG
+agent-browser open https://example.com
+agent-browser click @e1            # Ref doesn't exist yet!
+```
+
+### 2. Re-Snapshot After Navigation
+
+```bash
+agent-browser click @e5            # Navigates to new page
+agent-browser snapshot -i          # Get new refs
+agent-browser click @e1            # Use new refs
+```
+
+### 3. Re-Snapshot After Dynamic Changes
+
+```bash
+agent-browser click @e1            # Opens dropdown
+agent-browser snapshot -i          # See dropdown items
+agent-browser click @e7            # Select item
+```
+
+### 4. Snapshot Specific Regions
+
+For complex pages, snapshot specific areas:
+
+```bash
+# Snapshot just the form
+agent-browser snapshot @e9
+```
+
+## Ref Notation Details
+
+```
+@e1 [tag type="value"] "text content" placeholder="hint"
+|    |   |             |               |
+|    |   |             |               +- Additional attributes
+|    |   |             +- Visible text
+|    |   +- Key attributes shown
+|    +- HTML tag name
+- Unique ref ID
+```
+
+### Common Patterns
+
+```
+@e1 [button] "Submit"                    # Button with text
+@e2 [input type="email"]                 # Email input
+@e3 [input type="password"]              # Password input
+@e4 [a href="/page"] "Link Text"         # Anchor link
+@e5 [select]                             # Dropdown
+@e6 [textarea] placeholder="Message"     # Text area
+@e7 [div class="modal"]                  # Container (when relevant)
+@e8 [img alt="Logo"]                     # Image
+@e9 [checkbox] checked                   # Checked checkbox
+@e10 [radio] selected                    # Selected radio
+```
+
+## Troubleshooting
+
+### "Ref not found" Error
+
+```bash
+# Ref may have changed - re-snapshot
+agent-browser snapshot -i
+```
+
+### Element Not Visible in Snapshot
+
+```bash
+# Scroll down to reveal element
+agent-browser scroll down 1000
+agent-browser snapshot -i
+
+# Or wait for dynamic content
+agent-browser wait 1000
+agent-browser snapshot -i
+```
+
+### Too Many Elements
+
+```bash
+# Snapshot specific container
+agent-browser snapshot @e5
+
+# Or use get text for content-only extraction
+agent-browser get text @e5
+```
--- a/plugins/compound-engineering/skills/agent-browser/references/video-recording.md
+++ b/plugins/compound-engineering/skills/agent-browser/references/video-recording.md
@@ -0,0 +1,173 @@
+# Video Recording
+
+Capture browser automation as video for debugging, documentation, or verification.
+
+**Related**: [commands.md](commands.md) for full command reference, [SKILL.md](../SKILL.md) for quick start.
+
+## Contents
+
+- [Basic Recording](#basic-recording)
+- [Recording Commands](#recording-commands)
+- [Use Cases](#use-cases)
+- [Best Practices](#best-practices)
+- [Output Format](#output-format)
+- [Limitations](#limitations)
+
+## Basic Recording
+
+```bash
+# Start recording
+agent-browser record start ./demo.webm
+
+# Perform actions
+agent-browser open https://example.com
+agent-browser snapshot -i
+agent-browser click @e1
+agent-browser fill @e2 "test input"
+
+# Stop and save
+agent-browser record stop
+```
+
+## Recording Commands
+
+```bash
+# Start recording to file
+agent-browser record start ./output.webm
+
+# Stop current recording
+agent-browser record stop
+
+# Restart with new file (stops current + starts new)
+agent-browser record restart ./take2.webm
+```
+
+## Use Cases
+
+### Debugging Failed Automation
+
+```bash
+#!/bin/bash
+# Record automation for debugging
+
+agent-browser record start ./debug-$(date +%Y%m%d-%H%M%S).webm
+
+# Run your automation
+agent-browser open https://app.example.com
+agent-browser snapshot -i
+agent-browser click @e1 || {
+    echo "Click failed - check recording"
+    agent-browser record stop
+    exit 1
+}
+
+agent-browser record stop
+```
+
+### Documentation Generation
+
+```bash
+#!/bin/bash
+# Record workflow for documentation
+
+agent-browser record start ./docs/how-to-login.webm
+
+agent-browser open https://app.example.com/login
+agent-browser wait 1000  # Pause for visibility
+
+agent-browser snapshot -i
+agent-browser fill @e1 "demo@example.com"
+agent-browser wait 500
+
+agent-browser fill @e2 "password"
+agent-browser wait 500
+
+agent-browser click @e3
+agent-browser wait --load networkidle
+agent-browser wait 1000  # Show result
+
+agent-browser record stop
+```
+
+### CI/CD Test Evidence
+
+```bash
+#!/bin/bash
+# Record E2E test runs for CI artifacts
+
+TEST_NAME="${1:-e2e-test}"
+RECORDING_DIR="./test-recordings"
+mkdir -p "$RECORDING_DIR"
+
+agent-browser record start "$RECORDING_DIR/$TEST_NAME-$(date +%s).webm"
+
+# Run test
+if run_e2e_test; then
+    echo "Test passed"
+else
+    echo "Test failed - recording saved"
+fi
+
+agent-browser record stop
+```
+
+## Best Practices
+
+### 1. Add Pauses for Clarity
+
+```bash
+# Slow down for human viewing
+agent-browser click @e1
+agent-browser wait 500  # Let viewer see result
+```
+
+### 2. Use Descriptive Filenames
+
+```bash
+# Include context in filename
+agent-browser record start ./recordings/login-flow-2024-01-15.webm
+agent-browser record start ./recordings/checkout-test-run-42.webm
+```
+
+### 3. Handle Recording in Error Cases
+
+```bash
+#!/bin/bash
+set -e
+
+cleanup() {
+    agent-browser record stop 2>/dev/null || true
+    agent-browser close 2>/dev/null || true
+}
+trap cleanup EXIT
+
+agent-browser record start ./automation.webm
+# ... automation steps ...
+```
+
+### 4. Combine with Screenshots
+
+```bash
+# Record video AND capture key frames
+agent-browser record start ./flow.webm
+
+agent-browser open https://example.com
+agent-browser screenshot ./screenshots/step1-homepage.png
+
+agent-browser click @e1
+agent-browser screenshot ./screenshots/step2-after-click.png
+
+agent-browser record stop
+```
+
+## Output Format
+
+- Default format: WebM (VP8/VP9 codec)
+- Compatible with all modern browsers and video players
+- Compressed but high quality
+
+## Limitations
+
+- Recording adds slight overhead to automation
+- Large recordings can consume significant disk space
+- Some headless environments may have codec limitations
--- a/plugins/compound-engineering/skills/agent-browser/templates/authenticated-session.sh
+++ b/plugins/compound-engineering/skills/agent-browser/templates/authenticated-session.sh
@@ -0,0 +1,105 @@
+#!/bin/bash
+# Template: Authenticated Session Workflow
+# Purpose: Login once, save state, reuse for subsequent runs
+# Usage: ./authenticated-session.sh <login-url> [state-file]
+#
+# RECOMMENDED: Use the auth vault instead of this template:
+#   echo "<pass>" | agent-browser auth save myapp --url <login-url> --username <user> --password-stdin
+#   agent-browser auth login myapp
+# The auth vault stores credentials securely and the LLM never sees passwords.
+#
+# Environment variables:
+#   APP_USERNAME - Login username/email
+#   APP_PASSWORD - Login password
+#
+# Two modes:
+#   1. Discovery mode (default): Shows form structure so you can identify refs
+#   2. Login mode: Performs actual login after you update the refs
+#
+# Setup steps:
+#   1. Run once to see form structure (discovery mode)
+#   2. Update refs in LOGIN FLOW section below
+#   3. Set APP_USERNAME and APP_PASSWORD
+#   4. Delete the DISCOVERY section
+
+set -euo pipefail
+
+LOGIN_URL="${1:?Usage: $0 <login-url> [state-file]}"
+STATE_FILE="${2:-./auth-state.json}"
+
+echo "Authentication workflow: $LOGIN_URL"
+
+# ================================================================
+# SAVED STATE: Skip login if valid saved state exists
+# ================================================================
+if [[ -f "$STATE_FILE" ]]; then
+    echo "Loading saved state from $STATE_FILE..."
+    if agent-browser --state "$STATE_FILE" open "$LOGIN_URL" 2>/dev/null; then
+        agent-browser wait --load networkidle
+
+        CURRENT_URL=$(agent-browser get url)
+        if [[ "$CURRENT_URL" != *"login"* ]] && [[ "$CURRENT_URL" != *"signin"* ]]; then
+            echo "Session restored successfully"
+            agent-browser snapshot -i
+            exit 0
+        fi
+        echo "Session expired, performing fresh login..."
+        agent-browser close 2>/dev/null || true
+    else
+        echo "Failed to load state, re-authenticating..."
+    fi
+    rm -f "$STATE_FILE"
+fi
+
+# ================================================================
+# DISCOVERY MODE: Shows form structure (delete after setup)
+# ================================================================
+echo "Opening login page..."
+agent-browser open "$LOGIN_URL"
+agent-browser wait --load networkidle
+
+echo ""
+echo "Login form structure:"
+echo "---"
+agent-browser snapshot -i
+echo "---"
+echo ""
+echo "Next steps:"
+echo "  1. Note the refs: username=@e?, password=@e?, submit=@e?"
+echo "  2. Update the LOGIN FLOW section below with your refs"
+echo "  3. Set: export APP_USERNAME='...' APP_PASSWORD='...'"
+echo "  4. Delete this DISCOVERY MODE section"
+echo ""
+agent-browser close
+exit 0
+
+# ================================================================
+# LOGIN FLOW: Uncomment and customize after discovery
+# ================================================================
+# : "${APP_USERNAME:?Set APP_USERNAME environment variable}"
+# : "${APP_PASSWORD:?Set APP_PASSWORD environment variable}"
+#
+# agent-browser open "$LOGIN_URL"
+# agent-browser wait --load networkidle
+# agent-browser snapshot -i
+#
+# # Fill credentials (update refs to match your form)
+# agent-browser fill @e1 "$APP_USERNAME"
+# agent-browser fill @e2 "$APP_PASSWORD"
+# agent-browser click @e3
+# agent-browser wait --load networkidle
+#
+# # Verify login succeeded
+# FINAL_URL=$(agent-browser get url)
+# if [[ "$FINAL_URL" == *"login"* ]] || [[ "$FINAL_URL" == *"signin"* ]]; then
+#     echo "Login failed - still on login page"
+#     agent-browser screenshot /tmp/login-failed.png
+#     agent-browser close
+#     exit 1
+# fi
+#
+# # Save state for future runs
+# echo "Saving state to $STATE_FILE"
+# agent-browser state save "$STATE_FILE"
+# echo "Login successful"
+# agent-browser snapshot -i
--- a/plugins/compound-engineering/skills/agent-browser/templates/capture-workflow.sh
+++ b/plugins/compound-engineering/skills/agent-browser/templates/capture-workflow.sh
@@ -0,0 +1,69 @@
+#!/bin/bash
+# Template: Content Capture Workflow
+# Purpose: Extract content from web pages (text, screenshots, PDF)
+# Usage: ./capture-workflow.sh <url> [output-dir]
+#
+# Outputs:
+#   - page-full.png: Full page screenshot
+#   - page-structure.txt: Page element structure with refs
+#   - page-text.txt: All text content
+#   - page.pdf: PDF version
+#
+# Optional: Load auth state for protected pages
+
+set -euo pipefail
+
+TARGET_URL="${1:?Usage: $0 <url> [output-dir]}"
+OUTPUT_DIR="${2:-.}"
+
+echo "Capturing: $TARGET_URL"
+mkdir -p "$OUTPUT_DIR"
+
+# Optional: Load authentication state
+# if [[ -f "./auth-state.json" ]]; then
+#     echo "Loading authentication state..."
+#     agent-browser state load "./auth-state.json"
+# fi
+
+# Navigate to target
+agent-browser open "$TARGET_URL"
+agent-browser wait --load networkidle
+
+# Get metadata
+TITLE=$(agent-browser get title)
+URL=$(agent-browser get url)
+echo "Title: $TITLE"
+echo "URL: $URL"
+
+# Capture full page screenshot
+agent-browser screenshot --full "$OUTPUT_DIR/page-full.png"
+echo "Saved: $OUTPUT_DIR/page-full.png"
+
+# Get page structure with refs
+agent-browser snapshot -i > "$OUTPUT_DIR/page-structure.txt"
+echo "Saved: $OUTPUT_DIR/page-structure.txt"
+
+# Extract all text content
+agent-browser get text body > "$OUTPUT_DIR/page-text.txt"
+echo "Saved: $OUTPUT_DIR/page-text.txt"
+
+# Save as PDF
+agent-browser pdf "$OUTPUT_DIR/page.pdf"
+echo "Saved: $OUTPUT_DIR/page.pdf"
+
+# Optional: Extract specific elements using refs from structure
+# agent-browser get text @e5 > "$OUTPUT_DIR/main-content.txt"
+
+# Optional: Handle infinite scroll pages
+# for i in {1..5}; do
+#     agent-browser scroll down 1000
+#     agent-browser wait 1000
+# done
+# agent-browser screenshot --full "$OUTPUT_DIR/page-scrolled.png"
+
+# Cleanup
+agent-browser close
+
+echo ""
+echo "Capture complete:"
+ls -la "$OUTPUT_DIR"
--- a/plugins/compound-engineering/skills/agent-browser/templates/form-automation.sh
+++ b/plugins/compound-engineering/skills/agent-browser/templates/form-automation.sh
@@ -0,0 +1,62 @@
+#!/bin/bash
+# Template: Form Automation Workflow
+# Purpose: Fill and submit web forms with validation
+# Usage: ./form-automation.sh <form-url>
+#
+# This template demonstrates the snapshot-interact-verify pattern:
+# 1. Navigate to form
+# 2. Snapshot to get element refs
+# 3. Fill fields using refs
+# 4. Submit and verify result
+#
+# Customize: Update the refs (@e1, @e2, etc.) based on your form's snapshot output
+
+set -euo pipefail
+
+FORM_URL="${1:?Usage: $0 <form-url>}"
+
+echo "Form automation: $FORM_URL"
+
+# Step 1: Navigate to form
+agent-browser open "$FORM_URL"
+agent-browser wait --load networkidle
+
+# Step 2: Snapshot to discover form elements
+echo ""
+echo "Form structure:"
+agent-browser snapshot -i
+
+# Step 3: Fill form fields (customize these refs based on snapshot output)
+#
+# Common field types:
+#   agent-browser fill @e1 "John Doe"           # Text input
+#   agent-browser fill @e2 "user@example.com"   # Email input
+#   agent-browser fill @e3 "SecureP@ss123"      # Password input
+#   agent-browser select @e4 "Option Value"     # Dropdown
+#   agent-browser check @e5                     # Checkbox
+#   agent-browser click @e6                     # Radio button
+#   agent-browser fill @e7 "Multi-line text"   # Textarea
+#   agent-browser upload @e8 /path/to/file.pdf # File upload
+#
+# Uncomment and modify:
+# agent-browser fill @e1 "Test User"
+# agent-browser fill @e2 "test@example.com"
+# agent-browser click @e3  # Submit button
+
+# Step 4: Wait for submission
+# agent-browser wait --load networkidle
+# agent-browser wait --url "**/success"  # Or wait for redirect
+
+# Step 5: Verify result
+echo ""
+echo "Result:"
+agent-browser get url
+agent-browser snapshot -i
+
+# Optional: Capture evidence
+agent-browser screenshot /tmp/form-result.png
+echo "Screenshot saved: /tmp/form-result.png"
+
+# Cleanup
+agent-browser close
+echo "Done"
--- a/plugins/compound-engineering/skills/agent-native-audit/SKILL.md
+++ b/plugins/compound-engineering/skills/agent-native-audit/SKILL.md
--- a/plugins/compound-engineering/skills/brainstorming/SKILL.md
+++ b/plugins/compound-engineering/skills/brainstorming/SKILL.md
@@ -131,7 +131,7 @@ topic: <kebab-case-topic>
 - [Any unresolved questions for the planning phase]

 ## Next Steps
-→ `/workflows:plan` for implementation details
+→ `/ce:plan` for implementation details
 ```

 **Output Location:** `docs/brainstorms/YYYY-MM-DD-<topic>-brainstorm.md`
@@ -140,7 +140,7 @@ topic: <kebab-case-topic>

 Present clear options for what to do next:

-1. **Proceed to planning** → Run `/workflows:plan`
+1. **Proceed to planning** → Run `/ce:plan`
 2. **Refine further** → Continue exploring the design
 3. **Done for now** → User will return later

@@ -187,4 +187,4 @@ Planning answers **HOW** to build it:
 - Technical details and code patterns
 - Testing strategy and verification

-When brainstorm output exists, `/workflows:plan` should detect it and use it as input, skipping its own idea refinement phase.
+When brainstorm output exists, `/ce:plan` should detect it and use it as input, skipping its own idea refinement phase.
--- a/plugins/compound-engineering/commands/workflows/brainstorm.md
+++ b/plugins/compound-engineering/commands/workflows/brainstorm.md
@@ -1,5 +1,5 @@
 ---
-name: workflows:brainstorm
+name: ce:brainstorm
 description: Explore requirements and approaches through collaborative dialogue before planning implementation
 argument-hint: "[feature idea or problem to explore]"
 ---
@@ -8,7 +8,7 @@ argument-hint: "[feature idea or problem to explore]"

 **Note: The current year is 2026.** Use this when dating brainstorm documents.

-Brainstorming helps answer **WHAT** to build through collaborative dialogue. It precedes `/workflows:plan`, which answers **HOW** to build it.
+Brainstorming helps answer **WHAT** to build through collaborative dialogue. It precedes `/ce:plan`, which answers **HOW** to build it.

 **Process knowledge:** Load the `brainstorming` skill for detailed question techniques, approach exploration patterns, and YAGNI principles.

@@ -33,7 +33,7 @@ Evaluate whether brainstorming is needed based on the feature description.
 - Constrained, well-defined scope

 **If requirements are already clear:**
-Use **AskUserQuestion tool** to suggest: "Your requirements seem detailed enough to proceed directly to planning. Should I run `/workflows:plan` instead, or would you like to explore the idea further?"
+Use **AskUserQuestion tool** to suggest: "Your requirements seem detailed enough to proceed directly to planning. Should I run `/ce:plan` instead, or would you like to explore the idea further?"

 ### Phase 1: Understand the Idea

@@ -41,7 +41,7 @@ Use **AskUserQuestion tool** to suggest: "Your requirements seem detailed enough

 Run a quick repo scan to understand existing patterns:

- Task repo-research-analyst("Understand existing patterns related to: <feature_description>")
+- Task compound-engineering:research:repo-research-analyst("Understand existing patterns related to: <feature_description>")

 Focus on: similar features, established patterns, CLAUDE.md guidance.

@@ -88,9 +88,25 @@ Use **AskUserQuestion tool** to present next steps:

 **Options:**
 1. **Review and refine** - Improve the document through structured self-review
-2. **Proceed to planning** - Run `/workflows:plan` (will auto-detect this brainstorm)
-3. **Ask more questions** - I have more questions to clarify before moving on
-4. **Done for now** - Return later
+2. **Proceed to planning** - Run `/ce:plan` (will auto-detect this brainstorm)
+3. **Share to Proof** - Upload to Proof for collaborative review and sharing
+4. **Ask more questions** - I have more questions to clarify before moving on
+5. **Done for now** - Return later
+
+**If user selects "Share to Proof":**
+
+```bash
+CONTENT=$(cat docs/brainstorms/YYYY-MM-DD-<topic>-brainstorm.md)
+TITLE="Brainstorm: <topic title>"
+RESPONSE=$(curl -s -X POST https://www.proofeditor.ai/share/markdown \
+  -H "Content-Type: application/json" \
+  -d "$(jq -n --arg title "$TITLE" --arg markdown "$CONTENT" --arg by "ai:compound" '{title: $title, markdown: $markdown, by: $by}')")
+PROOF_URL=$(echo "$RESPONSE" | jq -r '.tokenUrl')
+```
+
+Display the URL prominently: `View & collaborate in Proof: <PROOF_URL>`
+
+If the curl fails, skip silently. Then return to the Phase 4 options.

 **If user selects "Ask more questions":** YOU (Claude) return to Phase 1.2 (Collaborative Dialogue) and continue asking the USER questions one at a time to further refine the design. The user wants YOU to probe deeper - ask about edge cases, constraints, preferences, or areas not yet explored. Continue until the user is satisfied, then return to Phase 4.

@@ -100,8 +116,8 @@ Load the `document-review` skill and apply it to the brainstorm document.

 When document-review returns "Review complete", present next steps:

-1. **Move to planning** - Continue to `/workflows:plan` with this document
-2. **Done for now** - Brainstorming complete. To start planning later: `/workflows:plan [document-path]`
+1. **Move to planning** - Continue to `/ce:plan` with this document
+2. **Done for now** - Brainstorming complete. To start planning later: `/ce:plan [document-path]`

 ## Output Summary

@@ -116,7 +132,7 @@ Key decisions:
 - [Decision 1]
 - [Decision 2]

-Next: Run `/workflows:plan` when ready to implement.
+Next: Run `/ce:plan` when ready to implement.
 ```

 ## Important Guidelines
--- a/plugins/compound-engineering/commands/workflows/compound.md
+++ b/plugins/compound-engineering/commands/workflows/compound.md
@@ -1,5 +1,5 @@
 ---
-name: workflows:compound
+name: ce:compound
 description: Document a recently solved problem to compound your team's knowledge
 argument-hint: "[optional: brief context about the fix]"
 ---
@@ -17,11 +17,19 @@ Captures problem solutions while context is fresh, creating structured documenta
 ## Usage

 ```bash
-/workflows:compound                    # Document the most recent fix
-/workflows:compound [brief context]    # Provide additional context hint
+/ce:compound                    # Document the most recent fix
+/ce:compound [brief context]    # Provide additional context hint
 ```

-## Execution Strategy: Two-Phase Orchestration
+## Execution Strategy
+
+**Always run full mode by default.** Proceed directly to Phase 1 unless the user explicitly requests compact-safe mode (e.g., `/ce:compound --compact` or "use compact mode").
+
+Compact-safe mode exists as a lightweight alternative — see the **Compact-Safe Mode** section below. It's there if the user wants it, not something to push.
+
+---
+
+### Full Mode

 <critical_requirement>
 **Only ONE file gets written - the final documentation.**
@@ -99,6 +107,44 @@ Based on problem type, optionally invoke specialized agents to review the docume

 </parallel_tasks>

+---
+
+### Compact-Safe Mode
+
+<critical_requirement>
+**Single-pass alternative for context-constrained sessions.**
+
+When context budget is tight, this mode skips parallel subagents entirely. The orchestrator performs all work in a single pass, producing a minimal but complete solution document.
+</critical_requirement>
+
+The orchestrator (main conversation) performs ALL of the following in one sequential pass:
+
+1. **Extract from conversation**: Identify the problem, root cause, and solution from conversation history
+2. **Classify**: Determine category and filename (same categories as full mode)
+3. **Write minimal doc**: Create `docs/solutions/[category]/[filename].md` with:
+   - YAML frontmatter (title, category, date, tags)
+   - Problem description (1-2 sentences)
+   - Root cause (1-2 sentences)
+   - Solution with key code snippets
+   - One prevention tip
+4. **Skip specialized agent reviews** (Phase 3) to conserve context
+
+**Compact-safe output:**
+```
+✓ Documentation complete (compact-safe mode)
+
+File created:
+- docs/solutions/[category]/[filename].md
+
+Note: This was created in compact-safe mode. For richer documentation
+(cross-references, detailed prevention strategies, specialized reviews),
+re-run /compound in a fresh session.
+```
+
+**No subagents are launched. No parallel tasks. One file written.**
+
+---
+
 ## What It Captures

 - **Problem symptom**: Exact error messages, observable behavior
@@ -203,7 +249,7 @@ Build → Test → Find Issue → Research → Improve → Document → Validate

 <auto_invoke> <trigger_phrases> - "that worked" - "it's fixed" - "working now" - "problem solved" </trigger_phrases>

-<manual_override> Use /workflows:compound [context] to document immediately without waiting for auto-detection. </manual_override> </auto_invoke>
+<manual_override> Use /ce:compound [context] to document immediately without waiting for auto-detection. </manual_override> </auto_invoke>

 ## Routes To

@@ -231,10 +277,10 @@ Based on problem type, these agents can enhance documentation:

 ### When to Invoke
 - **Auto-triggered** (optional): Agents can run post-documentation for enhancement
- **Manual trigger**: User can invoke agents after /workflows:compound completes for deeper review
+- **Manual trigger**: User can invoke agents after /ce:compound completes for deeper review
 - **Customize agents**: Edit `compound-engineering.local.md` or invoke the `setup` skill to configure which review agents are used across all workflows

 ## Related Commands

 - `/research [topic]` - Deep investigation (searches docs/solutions/ for patterns)
- `/workflows:plan` - Planning workflow (references documented solutions)
+- `/ce:plan` - Planning workflow (references documented solutions)
--- a/plugins/compound-engineering/skills/ce-plan/SKILL.md
+++ b/plugins/compound-engineering/skills/ce-plan/SKILL.md
@@ -0,0 +1,641 @@
+---
+name: ce:plan
+description: Transform feature descriptions into well-structured project plans following conventions
+argument-hint: "[feature description, bug report, or improvement idea]"
+---
+
+# Create a plan for a new feature or bug fix
+
+## Introduction
+
+**Note: The current year is 2026.** Use this when dating plans and searching for recent documentation.
+
+Transform feature descriptions, bug reports, or improvement ideas into well-structured markdown files issues that follow project conventions and best practices. This command provides flexible detail levels to match your needs.
+
+## Feature Description
+
+<feature_description> #$ARGUMENTS </feature_description>
+
+**If the feature description above is empty, ask the user:** "What would you like to plan? Please describe the feature, bug fix, or improvement you have in mind."
+
+Do not proceed until you have a clear feature description from the user.
+
+### 0. Idea Refinement
+
+**Check for brainstorm output first:**
+
+Before asking questions, look for recent brainstorm documents in `docs/brainstorms/` that match this feature:
+
+```bash
+ls -la docs/brainstorms/*.md 2>/dev/null | head -10
+```
+
+**Relevance criteria:** A brainstorm is relevant if:
+- The topic (from filename or YAML frontmatter) semantically matches the feature description
+- Created within the last 14 days
+- If multiple candidates match, use the most recent one
+
+**If a relevant brainstorm exists:**
+1. Read the brainstorm document **thoroughly** — every section matters
+2. Announce: "Found brainstorm from [date]: [topic]. Using as foundation for planning."
+3. Extract and carry forward **ALL** of the following into the plan:
+   - Key decisions and their rationale
+   - Chosen approach and why alternatives were rejected
+   - Constraints and requirements discovered during brainstorming
+   - Open questions (flag these for resolution during planning)
+   - Success criteria and scope boundaries
+   - Any specific technical choices or patterns discussed
+4. **Skip the idea refinement questions below** — the brainstorm already answered WHAT to build
+5. Use brainstorm content as the **primary input** to research and planning phases
+6. **Critical: The brainstorm is the origin document.** Throughout the plan, reference specific decisions with `(see brainstorm: docs/brainstorms/<filename>)` when carrying forward conclusions. Do not paraphrase decisions in a way that loses their original context — link back to the source.
+7. **Do not omit brainstorm content** — if the brainstorm discussed it, the plan must address it (even if briefly). Scan each brainstorm section before finalizing the plan to verify nothing was dropped.
+
+**If multiple brainstorms could match:**
+Use **AskUserQuestion tool** to ask which brainstorm to use, or whether to proceed without one.
+
+**If no brainstorm found (or not relevant), run idea refinement:**
+
+Refine the idea through collaborative dialogue using the **AskUserQuestion tool**:
+
+- Ask questions one at a time to understand the idea fully
+- Prefer multiple choice questions when natural options exist
+- Focus on understanding: purpose, constraints and success criteria
+- Continue until the idea is clear OR user says "proceed"
+
+**Gather signals for research decision.** During refinement, note:
+
+- **User's familiarity**: Do they know the codebase patterns? Are they pointing to examples?
+- **User's intent**: Speed vs thoroughness? Exploration vs execution?
+- **Topic risk**: Security, payments, external APIs warrant more caution
+- **Uncertainty level**: Is the approach clear or open-ended?
+
+**Skip option:** If the feature description is already detailed, offer:
+"Your description is clear. Should I proceed with research, or would you like to refine it further?"
+
+## Main Tasks
+
+### 1. Local Research (Always Runs - Parallel)
+
+<thinking>
+First, I need to understand the project's conventions, existing patterns, and any documented learnings. This is fast and local - it informs whether external research is needed.
+</thinking>
+
+Run these agents **in parallel** to gather local context:
+
+- Task compound-engineering:research:repo-research-analyst(feature_description)
+- Task compound-engineering:research:learnings-researcher(feature_description)
+
+**What to look for:**
+- **Repo research:** existing patterns, CLAUDE.md guidance, technology familiarity, pattern consistency
+- **Learnings:** documented solutions in `docs/solutions/` that might apply (gotchas, patterns, lessons learned)
+
+These findings inform the next step.
+
+### 1.5. Research Decision
+
+Based on signals from Step 0 and findings from Step 1, decide on external research.
+
+**High-risk topics → always research.** Security, payments, external APIs, data privacy. The cost of missing something is too high. This takes precedence over speed signals.
+
+**Strong local context → skip external research.** Codebase has good patterns, CLAUDE.md has guidance, user knows what they want. External research adds little value.
+
+**Uncertainty or unfamiliar territory → research.** User is exploring, codebase has no examples, new technology. External perspective is valuable.
+
+**Announce the decision and proceed.** Brief explanation, then continue. User can redirect if needed.
+
+Examples:
+- "Your codebase has solid patterns for this. Proceeding without external research."
+- "This involves payment processing, so I'll research current best practices first."
+
+### 1.5b. External Research (Conditional)
+
+**Only run if Step 1.5 indicates external research is valuable.**
+
+Run these agents in parallel:
+
+- Task compound-engineering:research:best-practices-researcher(feature_description)
+- Task compound-engineering:research:framework-docs-researcher(feature_description)
+
+### 1.6. Consolidate Research
+
+After all research steps complete, consolidate findings:
+
+- Document relevant file paths from repo research (e.g., `app/services/example_service.rb:42`)
+- **Include relevant institutional learnings** from `docs/solutions/` (key insights, gotchas to avoid)
+- Note external documentation URLs and best practices (if external research was done)
+- List related issues or PRs discovered
+- Capture CLAUDE.md conventions
+
+**Optional validation:** Briefly summarize findings and ask if anything looks off or missing before proceeding to planning.
+
+### 2. Issue Planning & Structure
+
+<thinking>
+Think like a product manager - what would make this issue clear and actionable? Consider multiple perspectives
+</thinking>
+
+**Title & Categorization:**
+
+- [ ] Draft clear, searchable issue title using conventional format (e.g., `feat: Add user authentication`, `fix: Cart total calculation`)
+- [ ] Determine issue type: enhancement, bug, refactor
+- [ ] Convert title to filename: add today's date prefix, determine daily sequence number, strip prefix colon, kebab-case, add `-plan` suffix
+  - Scan `docs/plans/` for files matching today's date pattern `YYYY-MM-DD-\d{3}-`
+  - Find the highest existing sequence number for today
+  - Increment by 1, zero-padded to 3 digits (001, 002, etc.)
+  - Example: `feat: Add User Authentication` → `2026-01-21-001-feat-add-user-authentication-plan.md`
+  - Keep it descriptive (3-5 words after prefix) so plans are findable by context
+
+**Stakeholder Analysis:**
+
+- [ ] Identify who will be affected by this issue (end users, developers, operations)
+- [ ] Consider implementation complexity and required expertise
+
+**Content Planning:**
+
+- [ ] Choose appropriate detail level based on issue complexity and audience
+- [ ] List all necessary sections for the chosen template
+- [ ] Gather supporting materials (error logs, screenshots, design mockups)
+- [ ] Prepare code examples or reproduction steps if applicable, name the mock filenames in the lists
+
+### 3. SpecFlow Analysis
+
+After planning the issue structure, run SpecFlow Analyzer to validate and refine the feature specification:
+
+- Task compound-engineering:workflow:spec-flow-analyzer(feature_description, research_findings)
+
+**SpecFlow Analyzer Output:**
+
+- [ ] Review SpecFlow analysis results
+- [ ] Incorporate any identified gaps or edge cases into the issue
+- [ ] Update acceptance criteria based on SpecFlow findings
+
+### 4. Choose Implementation Detail Level
+
+Select how comprehensive you want the issue to be, simpler is mostly better.
+
+#### 📄 MINIMAL (Quick Issue)
+
+**Best for:** Simple bugs, small improvements, clear features
+
+**Includes:**
+
+- Problem statement or feature description
+- Basic acceptance criteria
+- Essential context only
+
+**Structure:**
+
+````markdown
+---
+title: [Issue Title]
+type: [feat|fix|refactor]
+status: active
+date: YYYY-MM-DD
+origin: docs/brainstorms/YYYY-MM-DD-<topic>-brainstorm.md  # if originated from brainstorm, otherwise omit
+---
+
+# [Issue Title]
+
+[Brief problem/feature description]
+
+## Acceptance Criteria
+
+- [ ] Core requirement 1
+- [ ] Core requirement 2
+
+## Context
+
+[Any critical information]
+
+## MVP
+
+### test.rb
+
+```ruby
+class Test
+  def initialize
+    @name = "test"
+  end
+end
+```
+
+## Sources
+
+- **Origin brainstorm:** [docs/brainstorms/YYYY-MM-DD-<topic>-brainstorm.md](path) — include if plan originated from a brainstorm
+- Related issue: #[issue_number]
+- Documentation: [relevant_docs_url]
+````
+
+#### 📋 MORE (Standard Issue)
+
+**Best for:** Most features, complex bugs, team collaboration
+
+**Includes everything from MINIMAL plus:**
+
+- Detailed background and motivation
+- Technical considerations
+- Success metrics
+- Dependencies and risks
+- Basic implementation suggestions
+
+**Structure:**
+
+```markdown
+---
+title: [Issue Title]
+type: [feat|fix|refactor]
+status: active
+date: YYYY-MM-DD
+origin: docs/brainstorms/YYYY-MM-DD-<topic>-brainstorm.md  # if originated from brainstorm, otherwise omit
+---
+
+# [Issue Title]
+
+## Overview
+
+[Comprehensive description]
+
+## Problem Statement / Motivation
+
+[Why this matters]
+
+## Proposed Solution
+
+[High-level approach]
+
+## Technical Considerations
+
+- Architecture impacts
+- Performance implications
+- Security considerations
+
+## System-Wide Impact
+
+- **Interaction graph**: [What callbacks/middleware/observers fire when this runs?]
+- **Error propagation**: [How do errors flow across layers? Do retry strategies align?]
+- **State lifecycle risks**: [Can partial failure leave orphaned/inconsistent state?]
+- **API surface parity**: [What other interfaces expose similar functionality and need the same change?]
+- **Integration test scenarios**: [Cross-layer scenarios that unit tests won't catch]
+
+## Acceptance Criteria
+
+- [ ] Detailed requirement 1
+- [ ] Detailed requirement 2
+- [ ] Testing requirements
+
+## Success Metrics
+
+[How we measure success]
+
+## Dependencies & Risks
+
+[What could block or complicate this]
+
+## Sources & References
+
+- **Origin brainstorm:** [docs/brainstorms/YYYY-MM-DD-<topic>-brainstorm.md](path) — include if plan originated from a brainstorm
+- Similar implementations: [file_path:line_number]
+- Best practices: [documentation_url]
+- Related PRs: #[pr_number]
+```
+
+#### 📚 A LOT (Comprehensive Issue)
+
+**Best for:** Major features, architectural changes, complex integrations
+
+**Includes everything from MORE plus:**
+
+- Detailed implementation plan with phases
+- Alternative approaches considered
+- Extensive technical specifications
+- Resource requirements and timeline
+- Future considerations and extensibility
+- Risk mitigation strategies
+- Documentation requirements
+
+**Structure:**
+
+```markdown
+---
+title: [Issue Title]
+type: [feat|fix|refactor]
+status: active
+date: YYYY-MM-DD
+origin: docs/brainstorms/YYYY-MM-DD-<topic>-brainstorm.md  # if originated from brainstorm, otherwise omit
+---
+
+# [Issue Title]
+
+## Overview
+
+[Executive summary]
+
+## Problem Statement
+
+[Detailed problem analysis]
+
+## Proposed Solution
+
+[Comprehensive solution design]
+
+## Technical Approach
+
+### Architecture
+
+[Detailed technical design]
+
+### Implementation Phases
+
+#### Phase 1: [Foundation]
+
+- Tasks and deliverables
+- Success criteria
+- Estimated effort
+
+#### Phase 2: [Core Implementation]
+
+- Tasks and deliverables
+- Success criteria
+- Estimated effort
+
+#### Phase 3: [Polish & Optimization]
+
+- Tasks and deliverables
+- Success criteria
+- Estimated effort
+
+## Alternative Approaches Considered
+
+[Other solutions evaluated and why rejected]
+
+## System-Wide Impact
+
+### Interaction Graph
+
+[Map the chain reaction: what callbacks, middleware, observers, and event handlers fire when this code runs? Trace at least two levels deep. Document: "Action X triggers Y, which calls Z, which persists W."]
+
+### Error & Failure Propagation
+
+[Trace errors from lowest layer up. List specific error classes and where they're handled. Identify retry conflicts, unhandled error types, and silent failure swallowing.]
+
+### State Lifecycle Risks
+
+[Walk through each step that persists state. Can partial failure orphan rows, duplicate records, or leave caches stale? Document cleanup mechanisms or their absence.]
+
+### API Surface Parity
+
+[List all interfaces (classes, DSLs, endpoints) that expose equivalent functionality. Note which need updating and which share the code path.]
+
+### Integration Test Scenarios
+
+[3-5 cross-layer test scenarios that unit tests with mocks would never catch. Include expected behavior for each.]
+
+## Acceptance Criteria
+
+### Functional Requirements
+
+- [ ] Detailed functional criteria
+
+### Non-Functional Requirements
+
+- [ ] Performance targets
+- [ ] Security requirements
+- [ ] Accessibility standards
+
+### Quality Gates
+
+- [ ] Test coverage requirements
+- [ ] Documentation completeness
+- [ ] Code review approval
+
+## Success Metrics
+
+[Detailed KPIs and measurement methods]
+
+## Dependencies & Prerequisites
+
+[Detailed dependency analysis]
+
+## Risk Analysis & Mitigation
+
+[Comprehensive risk assessment]
+
+## Resource Requirements
+
+[Team, time, infrastructure needs]
+
+## Future Considerations
+
+[Extensibility and long-term vision]
+
+## Documentation Plan
+
+[What docs need updating]
+
+## Sources & References
+
+### Origin
+
+- **Brainstorm document:** [docs/brainstorms/YYYY-MM-DD-<topic>-brainstorm.md](path) — include if plan originated from a brainstorm. Key decisions carried forward: [list 2-3 major decisions from brainstorm]
+
+### Internal References
+
+- Architecture decisions: [file_path:line_number]
+- Similar features: [file_path:line_number]
+- Configuration: [file_path:line_number]
+
+### External References
+
+- Framework documentation: [url]
+- Best practices guide: [url]
+- Industry standards: [url]
+
+### Related Work
+
+- Previous PRs: #[pr_numbers]
+- Related issues: #[issue_numbers]
+- Design documents: [links]
+```
+
+### 5. Issue Creation & Formatting
+
+<thinking>
+Apply best practices for clarity and actionability, making the issue easy to scan and understand
+</thinking>
+
+**Content Formatting:**
+
+- [ ] Use clear, descriptive headings with proper hierarchy (##, ###)
+- [ ] Include code examples in triple backticks with language syntax highlighting
+- [ ] Add screenshots/mockups if UI-related (drag & drop or use image hosting)
+- [ ] Use task lists (- [ ]) for trackable items that can be checked off
+- [ ] Add collapsible sections for lengthy logs or optional details using `<details>` tags
+- [ ] Apply appropriate emoji for visual scanning (🐛 bug, ✨ feature, 📚 docs, ♻️ refactor)
+
+**Cross-Referencing:**
+
+- [ ] Link to related issues/PRs using #number format
+- [ ] Reference specific commits with SHA hashes when relevant
+- [ ] Link to code using GitHub's permalink feature (press 'y' for permanent link)
+- [ ] Mention relevant team members with @username if needed
+- [ ] Add links to external resources with descriptive text
+
+**Code & Examples:**
+
+````markdown
+# Good example with syntax highlighting and line references
+
+
+```ruby
+# app/services/user_service.rb:42
+def process_user(user)
+
+# Implementation here
+
+end
+```
+
+# Collapsible error logs
+
+<details>
+<summary>Full error stacktrace</summary>
+
+`Error details here...`
+
+</details>
+````
+
+**AI-Era Considerations:**
+
+- [ ] Account for accelerated development with AI pair programming
+- [ ] Include prompts or instructions that worked well during research
+- [ ] Note which AI tools were used for initial exploration (Claude, Copilot, etc.)
+- [ ] Emphasize comprehensive testing given rapid implementation
+- [ ] Document any AI-generated code that needs human review
+
+### 6. Final Review & Submission
+
+**Brainstorm cross-check (if plan originated from a brainstorm):**
+
+Before finalizing, re-read the brainstorm document and verify:
+- [ ] Every key decision from the brainstorm is reflected in the plan
+- [ ] The chosen approach matches what was decided in the brainstorm
+- [ ] Constraints and requirements from the brainstorm are captured in acceptance criteria
+- [ ] Open questions from the brainstorm are either resolved or flagged
+- [ ] The `origin:` frontmatter field points to the brainstorm file
+- [ ] The Sources section includes the brainstorm with a summary of carried-forward decisions
+
+**Pre-submission Checklist:**
+
+- [ ] Title is searchable and descriptive
+- [ ] Labels accurately categorize the issue
+- [ ] All template sections are complete
+- [ ] Links and references are working
+- [ ] Acceptance criteria are measurable
+- [ ] Add names of files in pseudo code examples and todo lists
+- [ ] Add an ERD mermaid diagram if applicable for new model changes
+
+## Write Plan File
+
+**REQUIRED: Write the plan file to disk before presenting any options.**
+
+```bash
+mkdir -p docs/plans/
+# Determine daily sequence number
+today=$(date +%Y-%m-%d)
+last_seq=$(ls docs/plans/${today}-*-plan.md 2>/dev/null | grep -oP "${today}-\K\d{3}" | sort -n | tail -1)
+next_seq=$(printf "%03d" $(( ${last_seq:-0} + 1 )))
+```
+
+Use the Write tool to save the complete plan to `docs/plans/YYYY-MM-DD-NNN-<type>-<descriptive-name>-plan.md` (where NNN is `$next_seq` from the bash command above). This step is mandatory and cannot be skipped — even when running as part of LFG/SLFG or other automated pipelines.
+
+Confirm: "Plan written to docs/plans/[filename]"
+
+**Pipeline mode:** If invoked from an automated workflow (LFG, SLFG, or any `disable-model-invocation` context), skip all AskUserQuestion calls. Make decisions automatically and proceed to writing the plan without interactive prompts.
+
+## Output Format
+
+**Filename:** Use the date, daily sequence number, and kebab-case filename from Step 2 Title & Categorization.
+
+```
+docs/plans/YYYY-MM-DD-NNN-<type>-<descriptive-name>-plan.md
+```
+
+Examples:
+- ✅ `docs/plans/2026-01-15-001-feat-user-authentication-flow-plan.md`
+- ✅ `docs/plans/2026-02-03-001-fix-checkout-race-condition-plan.md`
+- ✅ `docs/plans/2026-03-10-002-refactor-api-client-extraction-plan.md`
+- ❌ `docs/plans/2026-01-15-feat-thing-plan.md` (missing sequence number, not descriptive)
+- ❌ `docs/plans/2026-01-15-001-feat-new-feature-plan.md` (too vague - what feature?)
+- ❌ `docs/plans/2026-01-15-001-feat: user auth-plan.md` (invalid characters - colon and space)
+- ❌ `docs/plans/feat-user-auth-plan.md` (missing date prefix and sequence number)
+
+## Post-Generation Options
+
+After writing the plan file, use the **AskUserQuestion tool** to present these options:
+
+**Question:** "Plan ready at `docs/plans/YYYY-MM-DD-NNN-<type>-<name>-plan.md`. What would you like to do next?"
+
+**Options:**
+1. **Open plan in editor** - Open the plan file for review
+2. **Run `/deepen-plan`** - Enhance each section with parallel research agents (best practices, performance, UI)
+3. **Review and refine** - Improve the document through structured self-review
+4. **Share to Proof** - Upload to Proof for collaborative review and sharing
+5. **Start `/ce:work`** - Begin implementing this plan locally
+6. **Start `/ce:work` on remote** - Begin implementing in Claude Code on the web (use `&` to run in background)
+7. **Create Issue** - Create issue in project tracker (GitHub/Linear)
+
+Based on selection:
+- **Open plan in editor** → Run `open docs/plans/<plan_filename>.md` to open the file in the user's default editor
+- **`/deepen-plan`** → Call the /deepen-plan command with the plan file path to enhance with research
+- **Review and refine** → Load `document-review` skill.
+- **Share to Proof** → Upload the plan to Proof:
+  ```bash
+  CONTENT=$(cat docs/plans/<plan_filename>.md)
+  TITLE="Plan: <plan title from frontmatter>"
+  RESPONSE=$(curl -s -X POST https://www.proofeditor.ai/share/markdown \
+    -H "Content-Type: application/json" \
+    -d "$(jq -n --arg title "$TITLE" --arg markdown "$CONTENT" --arg by "ai:compound" '{title: $title, markdown: $markdown, by: $by}')")
+  PROOF_URL=$(echo "$RESPONSE" | jq -r '.tokenUrl')
+  ```
+  Display: `View & collaborate in Proof: <PROOF_URL>` — skip silently if curl fails. Then return to options.
+- **`/ce:work`** → Call the /ce:work command with the plan file path
+- **`/ce:work` on remote** → Run `/ce:work docs/plans/<plan_filename>.md &` to start work in background for Claude Code web
+- **Create Issue** → See "Issue Creation" section below
+- **Other** (automatically provided) → Accept free text for rework or specific changes
+
+**Note:** If running `/ce:plan` with ultrathink enabled, automatically run `/deepen-plan` after plan creation for maximum depth and grounding.
+
+Loop back to options after Simplify or Other changes until user selects `/ce:work` or another action.
+
+## Issue Creation
+
+When user selects "Create Issue", detect their project tracker from CLAUDE.md:
+
+1. **Check for tracker preference** in user's CLAUDE.md (global or project):
+   - Look for `project_tracker: github` or `project_tracker: linear`
+   - Or look for mentions of "GitHub Issues" or "Linear" in their workflow section
+
+2. **If GitHub:**
+
+   Use the title and type from Step 2 (already in context - no need to re-read the file):
+
+   ```bash
+   gh issue create --title "<type>: <title>" --body-file <plan_path>
+   ```
+
+3. **If Linear:**
+
+   ```bash
+   linear issue create --title "<title>" --description "$(cat <plan_path>)"
+   ```
+
+4. **If no tracker configured:**
+   Ask user: "Which project tracker do you use? (GitHub/Linear/Other)"
+   - Suggest adding `project_tracker: github` or `project_tracker: linear` to their CLAUDE.md
+
+5. **After creation:**
+   - Display the issue URL
+   - Ask if they want to proceed to `/ce:work`
+
+NEVER CODE! Just research and write the plan.
--- a/plugins/compound-engineering/skills/ce-review/SKILL.md
+++ b/plugins/compound-engineering/skills/ce-review/SKILL.md
@@ -0,0 +1,558 @@
+---
+name: ce:review
+description: Perform exhaustive code reviews using multi-agent analysis, ultra-thinking, and worktrees
+argument-hint: "[PR number, GitHub URL, branch name, or latest] [--serial]"
+---
+
+# Review Command
+
+<command_purpose> Perform exhaustive code reviews using multi-agent analysis, ultra-thinking, and Git worktrees for deep local inspection. </command_purpose>
+
+## Introduction
+
+<role>Senior Code Review Architect with expertise in security, performance, architecture, and quality assurance</role>
+
+## Prerequisites
+
+<requirements>
+- Git repository with GitHub CLI (`gh`) installed and authenticated
+- Clean main/master branch
+- Proper permissions to create worktrees and access the repository
+- For document reviews: Path to a markdown file or document
+</requirements>
+
+## Main Tasks
+
+### 1. Determine Review Target & Setup (ALWAYS FIRST)
+
+<review_target> #$ARGUMENTS </review_target>
+
+<thinking>
+First, I need to determine the review target type and set up the code for analysis.
+</thinking>
+
+#### Immediate Actions:
+
+<task_list>
+
+- [ ] Determine review type: PR number (numeric), GitHub URL, file path (.md), or empty (current branch)
+- [ ] Check current git branch
+- [ ] If ALREADY on the target branch (PR branch, requested branch name, or the branch already checked out for review) → proceed with analysis on current branch
+- [ ] If DIFFERENT branch than the review target → offer to use worktree: "Use git-worktree skill for isolated Call `skill: git-worktree` with branch name"
+- [ ] Fetch PR metadata using `gh pr view --json` for title, body, files, linked issues
+- [ ] Set up language-specific analysis tools
+- [ ] Prepare security scanning environment
+- [ ] Make sure we are on the branch we are reviewing. Use gh pr checkout to switch to the branch or manually checkout the branch.
+
+Ensure that the code is ready for analysis (either in worktree or on current branch). ONLY then proceed to the next step.
+
+</task_list>
+
+#### Protected Artifacts
+
+<protected_artifacts>
+The following paths are compound-engineering pipeline artifacts and must never be flagged for deletion, removal, or gitignore by any review agent:
+
+- `docs/plans/*.md` — Plan files created by `/ce:plan`. These are living documents that track implementation progress (checkboxes are checked off by `/ce:work`).
+- `docs/solutions/*.md` — Solution documents created during the pipeline.
+
+If a review agent flags any file in these directories for cleanup or removal, discard that finding during synthesis. Do not create a todo for it.
+</protected_artifacts>
+
+#### Load Review Agents
+
+Read `compound-engineering.local.md` in the project root. If found, use `review_agents` from YAML frontmatter. If the markdown body contains review context, pass it to each agent as additional instructions.
+
+If no settings file exists, invoke the `setup` skill to create one. Then read the newly created file and continue.
+
+#### Choose Execution Mode
+
+<execution_mode>
+
+Before launching review agents, check for context constraints:
+
+**If `--serial` flag is passed OR conversation is in a long session:**
+
+Run agents ONE AT A TIME in sequence. Wait for each agent to complete before starting the next. This uses less context but takes longer.
+
+**Default (parallel):**
+
+Run all agents simultaneously for speed. If you hit context limits, retry with `--serial` flag.
+
+**Auto-detect:** If more than 5 review agents are configured, automatically switch to serial mode and inform the user:
+"Running review agents in serial mode (6+ agents configured). Use --parallel to override."
+
+</execution_mode>
+
+#### Parallel Agents to review the PR:
+
+<parallel_tasks>
+
+**Parallel mode (default for ≤5 agents):**
+
+Run all configured review agents in parallel using Task tool. For each agent in the `review_agents` list:
+
+```
+Task {agent-name}(PR content + review context from settings body)
+```
+
+**Serial mode (--serial flag, or auto for 6+ agents):**
+
+Run configured review agents ONE AT A TIME. For each agent in the `review_agents` list, wait for it to complete before starting the next:
+
+```
+For each agent in review_agents:
+  1. Task {agent-name}(PR content + review context)
+  2. Wait for completion
+  3. Collect findings
+  4. Proceed to next agent
+```
+
+Always run these last regardless of mode:
+- Task compound-engineering:review:agent-native-reviewer(PR content) - Verify new features are agent-accessible
+- Task compound-engineering:research:learnings-researcher(PR content) - Search docs/solutions/ for past issues related to this PR's modules and patterns
+
+</parallel_tasks>
+
+#### Conditional Agents (Run if applicable):
+
+<conditional_agents>
+
+These agents are run ONLY when the PR matches specific criteria. Check the PR files list to determine if they apply:
+
+**MIGRATIONS: If PR contains database migrations, schema.rb, or data backfills:**
+
+- Task compound-engineering:review:schema-drift-detector(PR content) - Detects unrelated schema.rb changes by cross-referencing against included migrations (run FIRST)
+- Task compound-engineering:review:data-migration-expert(PR content) - Validates ID mappings match production, checks for swapped values, verifies rollback safety
+- Task compound-engineering:review:deployment-verification-agent(PR content) - Creates Go/No-Go deployment checklist with SQL verification queries
+
+**When to run:**
+- PR includes files matching `db/migrate/*.rb` or `db/schema.rb`
+- PR modifies columns that store IDs, enums, or mappings
+- PR includes data backfill scripts or rake tasks
+- PR title/body mentions: migration, backfill, data transformation, ID mapping
+
+**What these agents check:**
+- `schema-drift-detector`: Cross-references schema.rb changes against PR migrations to catch unrelated columns/indexes from local database state
+- `data-migration-expert`: Verifies hard-coded mappings match production reality (prevents swapped IDs), checks for orphaned associations, validates dual-write patterns
+- `deployment-verification-agent`: Produces executable pre/post-deploy checklists with SQL queries, rollback procedures, and monitoring plans
+
+</conditional_agents>
+
+### 2. Ultra-Thinking Deep Dive Phases
+
+<ultrathink_instruction> For each phase below, spend maximum cognitive effort. Think step by step. Consider all angles. Question assumptions. And bring all reviews in a synthesis to the user.</ultrathink_instruction>
+
+<deliverable>
+Complete system context map with component interactions
+</deliverable>
+
+#### Phase 1: Stakeholder Perspective Analysis
+
+<thinking_prompt> ULTRA-THINK: Put yourself in each stakeholder's shoes. What matters to them? What are their pain points? </thinking_prompt>
+
+<stakeholder_perspectives>
+
+1. **Developer Perspective** <questions>
+
+   - How easy is this to understand and modify?
+   - Are the APIs intuitive?
+   - Is debugging straightforward?
+   - Can I test this easily? </questions>
+
+2. **Operations Perspective** <questions>
+
+   - How do I deploy this safely?
+   - What metrics and logs are available?
+   - How do I troubleshoot issues?
+   - What are the resource requirements? </questions>
+
+3. **End User Perspective** <questions>
+
+   - Is the feature intuitive?
+   - Are error messages helpful?
+   - Is performance acceptable?
+   - Does it solve my problem? </questions>
+
+4. **Security Team Perspective** <questions>
+
+   - What's the attack surface?
+   - Are there compliance requirements?
+   - How is data protected?
+   - What are the audit capabilities? </questions>
+
+5. **Business Perspective** <questions>
+   - What's the ROI?
+   - Are there legal/compliance risks?
+   - How does this affect time-to-market?
+   - What's the total cost of ownership? </questions> </stakeholder_perspectives>
+
+#### Phase 2: Scenario Exploration
+
+<thinking_prompt> ULTRA-THINK: Explore edge cases and failure scenarios. What could go wrong? How does the system behave under stress? </thinking_prompt>
+
+<scenario_checklist>
+
+- [ ] **Happy Path**: Normal operation with valid inputs
+- [ ] **Invalid Inputs**: Null, empty, malformed data
+- [ ] **Boundary Conditions**: Min/max values, empty collections
+- [ ] **Concurrent Access**: Race conditions, deadlocks
+- [ ] **Scale Testing**: 10x, 100x, 1000x normal load
+- [ ] **Network Issues**: Timeouts, partial failures
+- [ ] **Resource Exhaustion**: Memory, disk, connections
+- [ ] **Security Attacks**: Injection, overflow, DoS
+- [ ] **Data Corruption**: Partial writes, inconsistency
+- [ ] **Cascading Failures**: Downstream service issues </scenario_checklist>
+
+### 3. Multi-Angle Review Perspectives
+
+#### Technical Excellence Angle
+
+- Code craftsmanship evaluation
+- Engineering best practices
+- Technical documentation quality
+- Tooling and automation assessment
+
+#### Business Value Angle
+
+- Feature completeness validation
+- Performance impact on users
+- Cost-benefit analysis
+- Time-to-market considerations
+
+#### Risk Management Angle
+
+- Security risk assessment
+- Operational risk evaluation
+- Compliance risk verification
+- Technical debt accumulation
+
+#### Team Dynamics Angle
+
+- Code review etiquette
+- Knowledge sharing effectiveness
+- Collaboration patterns
+- Mentoring opportunities
+
+### 4. Simplification and Minimalism Review
+
+Run the Task compound-engineering:review:code-simplicity-reviewer() to see if we can simplify the code.
+
+### 5. Findings Synthesis and Todo Creation Using file-todos Skill
+
+<critical_requirement> ALL findings MUST be stored in the todos/ directory using the file-todos skill. Create todo files immediately after synthesis - do NOT present findings for user approval first. Use the skill for structured todo management. </critical_requirement>
+
+#### Step 1: Synthesize All Findings
+
+<thinking>
+Consolidate all agent reports into a categorized list of findings.
+Remove duplicates, prioritize by severity and impact.
+</thinking>
+
+<synthesis_tasks>
+
+- [ ] Collect findings from all parallel agents
+- [ ] Surface learnings-researcher results: if past solutions are relevant, flag them as "Known Pattern" with links to docs/solutions/ files
+- [ ] Discard any findings that recommend deleting or gitignoring files in `docs/plans/` or `docs/solutions/` (see Protected Artifacts above)
+- [ ] Categorize by type: security, performance, architecture, quality, etc.
+- [ ] Assign severity levels: 🔴 CRITICAL (P1), 🟡 IMPORTANT (P2), 🔵 NICE-TO-HAVE (P3)
+- [ ] Remove duplicate or overlapping findings
+- [ ] Estimate effort for each finding (Small/Medium/Large)
+
+</synthesis_tasks>
+
+#### Step 2: Create Todo Files Using file-todos Skill
+
+<critical_instruction> Use the file-todos skill to create todo files for ALL findings immediately. Do NOT present findings one-by-one asking for user approval. Create all todo files in parallel using the skill, then summarize results to user. </critical_instruction>
+
+**Implementation Options:**
+
+**Option A: Direct File Creation (Fast)**
+
+- Create todo files directly using Write tool
+- All findings in parallel for speed
+- Use standard template from `.claude/skills/file-todos/assets/todo-template.md`
+- Follow naming convention: `{issue_id}-pending-{priority}-{description}.md`
+
+**Option B: Sub-Agents in Parallel (Recommended for Scale)** For large PRs with 15+ findings, use sub-agents to create finding files in parallel:
+
+```bash
+# Launch multiple finding-creator agents in parallel
+Task() - Create todos for first finding
+Task() - Create todos for second finding
+Task() - Create todos for third finding
+etc. for each finding.
+```
+
+Sub-agents can:
+
+- Process multiple findings simultaneously
+- Write detailed todo files with all sections filled
+- Organize findings by severity
+- Create comprehensive Proposed Solutions
+- Add acceptance criteria and work logs
+- Complete much faster than sequential processing
+
+**Execution Strategy:**
+
+1. Synthesize all findings into categories (P1/P2/P3)
+2. Group findings by severity
+3. Launch 3 parallel sub-agents (one per severity level)
+4. Each sub-agent creates its batch of todos using the file-todos skill
+5. Consolidate results and present summary
+
+**Process (Using file-todos Skill):**
+
+1. For each finding:
+
+   - Determine severity (P1/P2/P3)
+   - Write detailed Problem Statement and Findings
+   - Create 2-3 Proposed Solutions with pros/cons/effort/risk
+   - Estimate effort (Small/Medium/Large)
+   - Add acceptance criteria and work log
+
+2. Use file-todos skill for structured todo management:
+
+   ```bash
+   skill: file-todos
+   ```
+
+   The skill provides:
+
+   - Template location: `.claude/skills/file-todos/assets/todo-template.md`
+   - Naming convention: `{issue_id}-{status}-{priority}-{description}.md`
+   - YAML frontmatter structure: status, priority, issue_id, tags, dependencies
+   - All required sections: Problem Statement, Findings, Solutions, etc.
+
+3. Create todo files in parallel:
+
+   ```bash
+   {next_id}-pending-{priority}-{description}.md
+   ```
+
+4. Examples:
+
+   ```
+   001-pending-p1-path-traversal-vulnerability.md
+   002-pending-p1-api-response-validation.md
+   003-pending-p2-concurrency-limit.md
+   004-pending-p3-unused-parameter.md
+   ```
+
+5. Follow template structure from file-todos skill: `.claude/skills/file-todos/assets/todo-template.md`
+
+**Todo File Structure (from template):**
+
+Each todo must include:
+
+- **YAML frontmatter**: status, priority, issue_id, tags, dependencies
+- **Problem Statement**: What's broken/missing, why it matters
+- **Findings**: Discoveries from agents with evidence/location
+- **Proposed Solutions**: 2-3 options, each with pros/cons/effort/risk
+- **Recommended Action**: (Filled during triage, leave blank initially)
+- **Technical Details**: Affected files, components, database changes
+- **Acceptance Criteria**: Testable checklist items
+- **Work Log**: Dated record with actions and learnings
+- **Resources**: Links to PR, issues, documentation, similar patterns
+
+**File naming convention:**
+
+```
+{issue_id}-{status}-{priority}-{description}.md
+
+Examples:
+- 001-pending-p1-security-vulnerability.md
+- 002-pending-p2-performance-optimization.md
+- 003-pending-p3-code-cleanup.md
+```
+
+**Status values:**
+
+- `pending` - New findings, needs triage/decision
+- `ready` - Approved by manager, ready to work
+- `complete` - Work finished
+
+**Priority values:**
+
+- `p1` - Critical (blocks merge, security/data issues)
+- `p2` - Important (should fix, architectural/performance)
+- `p3` - Nice-to-have (enhancements, cleanup)
+
+**Tagging:** Always add `code-review` tag, plus: `security`, `performance`, `architecture`, `rails`, `quality`, etc.
+
+#### Step 3: Summary Report
+
+After creating all todo files, present comprehensive summary:
+
+````markdown
+## ✅ Code Review Complete
+
+**Review Target:** PR #XXXX - [PR Title] **Branch:** [branch-name]
+
+### Findings Summary:
+
+- **Total Findings:** [X]
+- **🔴 CRITICAL (P1):** [count] - BLOCKS MERGE
+- **🟡 IMPORTANT (P2):** [count] - Should Fix
+- **🔵 NICE-TO-HAVE (P3):** [count] - Enhancements
+
+### Created Todo Files:
+
+**P1 - Critical (BLOCKS MERGE):**
+
+- `001-pending-p1-{finding}.md` - {description}
+- `002-pending-p1-{finding}.md` - {description}
+
+**P2 - Important:**
+
+- `003-pending-p2-{finding}.md` - {description}
+- `004-pending-p2-{finding}.md` - {description}
+
+**P3 - Nice-to-Have:**
+
+- `005-pending-p3-{finding}.md` - {description}
+
+### Review Agents Used:
+
+- kieran-rails-reviewer
+- security-sentinel
+- performance-oracle
+- architecture-strategist
+- agent-native-reviewer
+- [other agents]
+
+### Next Steps:
+
+1. **Address P1 Findings**: CRITICAL - must be fixed before merge
+
+   - Review each P1 todo in detail
+   - Implement fixes or request exemption
+   - Verify fixes before merging PR
+
+2. **Triage All Todos**:
+   ```bash
+   ls todos/*-pending-*.md  # View all pending todos
+   /triage                  # Use slash command for interactive triage
+   ```
+
+3. **Work on Approved Todos**:
+
+   ```bash
+   /resolve_todo_parallel  # Fix all approved items efficiently
+   ```
+
+4. **Track Progress**:
+   - Rename file when status changes: pending → ready → complete
+   - Update Work Log as you work
+   - Commit todos: `git add todos/ && git commit -m "refactor: add code review findings"`
+
+### Severity Breakdown:
+
+**🔴 P1 (Critical - Blocks Merge):**
+
+- Security vulnerabilities
+- Data corruption risks
+- Breaking changes
+- Critical architectural issues
+
+**🟡 P2 (Important - Should Fix):**
+
+- Performance issues
+- Significant architectural concerns
+- Major code quality problems
+- Reliability issues
+
+**🔵 P3 (Nice-to-Have):**
+
+- Minor improvements
+- Code cleanup
+- Optimization opportunities
+- Documentation updates
+````
+
+### 6. End-to-End Testing (Optional)
+
+<detect_project_type>
+
+**First, detect the project type from PR files:**
+
+| Indicator | Project Type |
+|-----------|--------------|
+| `*.xcodeproj`, `*.xcworkspace`, `Package.swift` (iOS) | iOS/macOS |
+| `Gemfile`, `package.json`, `app/views/*`, `*.html.*` | Web |
+| Both iOS files AND web files | Hybrid (test both) |
+
+</detect_project_type>
+
+<offer_testing>
+
+After presenting the Summary Report, offer appropriate testing based on project type:
+
+**For Web Projects:**
+```markdown
+**"Want to run browser tests on the affected pages?"**
+1. Yes - run `/test-browser`
+2. No - skip
+```
+
+**For iOS Projects:**
+```markdown
+**"Want to run Xcode simulator tests on the app?"**
+1. Yes - run `/xcode-test`
+2. No - skip
+```
+
+**For Hybrid Projects (e.g., Rails + Hotwire Native):**
+```markdown
+**"Want to run end-to-end tests?"**
+1. Web only - run `/test-browser`
+2. iOS only - run `/xcode-test`
+3. Both - run both commands
+4. No - skip
+```
+
+</offer_testing>
+
+#### If User Accepts Web Testing:
+
+Spawn a subagent to run browser tests (preserves main context):
+
+```
+Task general-purpose("Run /test-browser for PR #[number]. Test all affected pages, check for console errors, handle failures by creating todos and fixing.")
+```
+
+The subagent will:
+1. Identify pages affected by the PR
+2. Navigate to each page and capture snapshots (using Playwright MCP or agent-browser CLI)
+3. Check for console errors
+4. Test critical interactions
+5. Pause for human verification on OAuth/email/payment flows
+6. Create P1 todos for any failures
+7. Fix and retry until all tests pass
+
+**Standalone:** `/test-browser [PR number]`
+
+#### If User Accepts iOS Testing:
+
+Spawn a subagent to run Xcode tests (preserves main context):
+
+```
+Task general-purpose("Run /xcode-test for scheme [name]. Build for simulator, install, launch, take screenshots, check for crashes.")
+```
+
+The subagent will:
+1. Verify XcodeBuildMCP is installed
+2. Discover project and schemes
+3. Build for iOS Simulator
+4. Install and launch app
+5. Take screenshots of key screens
+6. Capture console logs for errors
+7. Pause for human verification (Sign in with Apple, push, IAP)
+8. Create P1 todos for any failures
+9. Fix and retry until all tests pass
+
+**Standalone:** `/xcode-test [scheme]`
+
+### Important: P1 Findings Block Merge
+
+Any **🔴 P1 (CRITICAL)** findings must be addressed before merging the PR. Present these prominently and ensure they're resolved before accepting the PR.
--- a/plugins/compound-engineering/skills/ce-work/SKILL.md
+++ b/plugins/compound-engineering/skills/ce-work/SKILL.md
@@ -0,0 +1,470 @@
+---
+name: ce:work
+description: Execute work plans efficiently while maintaining quality and finishing features
+argument-hint: "[plan file, specification, or todo file path]"
+---
+
+# Work Plan Execution Command
+
+Execute a work plan efficiently while maintaining quality and finishing features.
+
+## Introduction
+
+This command takes a work document (plan, specification, or todo file) and executes it systematically. The focus is on **shipping complete features** by understanding requirements quickly, following existing patterns, and maintaining quality throughout.
+
+## Input Document
+
+<input_document> #$ARGUMENTS </input_document>
+
+## Execution Workflow
+
+### Phase 1: Quick Start
+
+1. **Read Plan and Clarify**
+
+   - Read the work document completely
+   - Review any references or links provided in the plan
+   - If anything is unclear or ambiguous, ask clarifying questions now
+   - Get user approval to proceed
+   - **Do not skip this** - better to ask questions now than build the wrong thing
+
+2. **Setup Environment**
+
+   First, check the current branch:
+
+   ```bash
+   current_branch=$(git branch --show-current)
+   default_branch=$(git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@')
+
+   # Fallback if remote HEAD isn't set
+   if [ -z "$default_branch" ]; then
+     default_branch=$(git rev-parse --verify origin/main >/dev/null 2>&1 && echo "main" || echo "master")
+   fi
+   ```
+
+   **If already on a feature branch** (not the default branch):
+   - Ask: "Continue working on `[current_branch]`, or create a new branch?"
+   - If continuing, proceed to step 3
+   - If creating new, follow Option A or B below
+
+   **If on the default branch**, choose how to proceed:
+
+   **Option A: Create a new branch**
+   ```bash
+   git pull origin [default_branch]
+   git checkout -b feature-branch-name
+   ```
+   Use a meaningful name based on the work (e.g., `feat/user-authentication`, `fix/email-validation`).
+
+   **Option B: Use a worktree (recommended for parallel development)**
+   ```bash
+   skill: git-worktree
+   # The skill will create a new branch from the default branch in an isolated worktree
+   ```
+
+   **Option C: Continue on the default branch**
+   - Requires explicit user confirmation
+   - Only proceed after user explicitly says "yes, commit to [default_branch]"
+   - Never commit directly to the default branch without explicit permission
+
+   **Recommendation**: Use worktree if:
+   - You want to work on multiple features simultaneously
+   - You want to keep the default branch clean while experimenting
+   - You plan to switch between branches frequently
+
+3. **Create Todo List**
+   - Use TodoWrite to break plan into actionable tasks
+   - Include dependencies between tasks
+   - Prioritize based on what needs to be done first
+   - Include testing and quality check tasks
+   - Keep tasks specific and completable
+
+### Phase 2: Execute
+
+1. **Task Execution Loop**
+
+   For each task in priority order:
+
+   ```
+   while (tasks remain):
+     - Mark task as in_progress in TodoWrite
+     - Read any referenced files from the plan
+     - Look for similar patterns in codebase
+     - Implement following existing conventions
+     - Write tests for new functionality
+     - Run System-Wide Test Check (see below)
+     - Run tests after changes
+     - Mark task as completed in TodoWrite
+     - Mark off the corresponding checkbox in the plan file ([ ] → [x])
+     - Evaluate for incremental commit (see below)
+   ```
+
+   **System-Wide Test Check** — Before marking a task done, pause and ask:
+
+   | Question | What to do |
+   |----------|------------|
+   | **What fires when this runs?** Callbacks, middleware, observers, event handlers — trace two levels out from your change. | Read the actual code (not docs) for callbacks on models you touch, middleware in the request chain, `after_*` hooks. |
+   | **Do my tests exercise the real chain?** If every dependency is mocked, the test proves your logic works *in isolation* — it says nothing about the interaction. | Write at least one integration test that uses real objects through the full callback/middleware chain. No mocks for the layers that interact. |
+   | **Can failure leave orphaned state?** If your code persists state (DB row, cache, file) before calling an external service, what happens when the service fails? Does retry create duplicates? | Trace the failure path with real objects. If state is created before the risky call, test that failure cleans up or that retry is idempotent. |
+   | **What other interfaces expose this?** Mixins, DSLs, alternative entry points (Agent vs Chat vs ChatMethods). | Grep for the method/behavior in related classes. If parity is needed, add it now — not as a follow-up. |
+   | **Do error strategies align across layers?** Retry middleware + application fallback + framework error handling — do they conflict or create double execution? | List the specific error classes at each layer. Verify your rescue list matches what the lower layer actually raises. |
+
+   **When to skip:** Leaf-node changes with no callbacks, no state persistence, no parallel interfaces. If the change is purely additive (new helper method, new view partial), the check takes 10 seconds and the answer is "nothing fires, skip."
+
+   **When this matters most:** Any change that touches models with callbacks, error handling with fallback/retry, or functionality exposed through multiple interfaces.
+
+   **IMPORTANT**: Always update the original plan document by checking off completed items. Use the Edit tool to change `- [ ]` to `- [x]` for each task you finish. This keeps the plan as a living document showing progress and ensures no checkboxes are left unchecked.
+
+2. **Incremental Commits**
+
+   After completing each task, evaluate whether to create an incremental commit:
+
+   | Commit when... | Don't commit when... |
+   |----------------|---------------------|
+   | Logical unit complete (model, service, component) | Small part of a larger unit |
+   | Tests pass + meaningful progress | Tests failing |
+   | About to switch contexts (backend → frontend) | Purely scaffolding with no behavior |
+   | About to attempt risky/uncertain changes | Would need a "WIP" commit message |
+
+   **Heuristic:** "Can I write a commit message that describes a complete, valuable change? If yes, commit. If the message would be 'WIP' or 'partial X', wait."
+
+   **Commit workflow:**
+   ```bash
+   # 1. Verify tests pass (use project's test command)
+   # Examples: bin/rails test, npm test, pytest, go test, etc.
+
+   # 2. Stage only files related to this logical unit (not `git add .`)
+   git add <files related to this logical unit>
+
+   # 3. Commit with conventional message
+   git commit -m "feat(scope): description of this unit"
+   ```
+
+   **Handling merge conflicts:** If conflicts arise during rebasing or merging, resolve them immediately. Incremental commits make conflict resolution easier since each commit is small and focused.
+
+   **Note:** Incremental commits use clean conventional messages without attribution footers. The final Phase 4 commit/PR includes the full attribution.
+
+3. **Follow Existing Patterns**
+
+   - The plan should reference similar code - read those files first
+   - Match naming conventions exactly
+   - Reuse existing components where possible
+   - Follow project coding standards (see CLAUDE.md)
+   - When in doubt, grep for similar implementations
+
+4. **Test Continuously**
+
+   - Run relevant tests after each significant change
+   - Don't wait until the end to test
+   - Fix failures immediately
+   - Add new tests for new functionality
+   - **Unit tests with mocks prove logic in isolation. Integration tests with real objects prove the layers work together.** If your change touches callbacks, middleware, or error handling — you need both.
+
+5. **Figma Design Sync** (if applicable)
+
+   For UI work with Figma designs:
+
+   - Implement components following design specs
+   - Use figma-design-sync agent iteratively to compare
+   - Fix visual differences identified
+   - Repeat until implementation matches design
+
+6. **Track Progress**
+   - Keep TodoWrite updated as you complete tasks
+   - Note any blockers or unexpected discoveries
+   - Create new tasks if scope expands
+   - Keep user informed of major milestones
+
+### Phase 3: Quality Check
+
+1. **Run Core Quality Checks**
+
+   Always run before submitting:
+
+   ```bash
+   # Run full test suite (use project's test command)
+   # Examples: bin/rails test, npm test, pytest, go test, etc.
+
+   # Run linting (per CLAUDE.md)
+   # Use linting-agent before pushing to origin
+   ```
+
+2. **Consider Reviewer Agents** (Optional)
+
+   Use for complex, risky, or large changes. Read agents from `compound-engineering.local.md` frontmatter (`review_agents`). If no settings file, invoke the `setup` skill to create one.
+
+   Run configured agents in parallel with Task tool. Present findings and address critical issues.
+
+3. **Final Validation**
+   - All TodoWrite tasks marked completed
+   - All tests pass
+   - Linting passes
+   - Code follows existing patterns
+   - Figma designs match (if applicable)
+   - No console errors or warnings
+
+4. **Prepare Operational Validation Plan** (REQUIRED)
+   - Add a `## Post-Deploy Monitoring & Validation` section to the PR description for every change.
+   - Include concrete:
+     - Log queries/search terms
+     - Metrics or dashboards to watch
+     - Expected healthy signals
+     - Failure signals and rollback/mitigation trigger
+     - Validation window and owner
+   - If there is truly no production/runtime impact, still include the section with: `No additional operational monitoring required` and a one-line reason.
+
+### Phase 4: Ship It
+
+1. **Create Commit**
+
+   ```bash
+   git add .
+   git status  # Review what's being committed
+   git diff --staged  # Check the changes
+
+   # Commit with conventional format
+   git commit -m "$(cat <<'EOF'
+   feat(scope): description of what and why
+
+   Brief explanation if needed.
+
+   🤖 Generated with [Claude Code](https://claude.com/claude-code)
+
+   Co-Authored-By: Claude <noreply@anthropic.com>
+   EOF
+   )"
+   ```
+
+2. **Capture and Upload Screenshots for UI Changes** (REQUIRED for any UI work)
+
+   For **any** design changes, new views, or UI modifications, you MUST capture and upload screenshots:
+
+   **Step 1: Start dev server** (if not running)
+   ```bash
+   bin/dev  # Run in background
+   ```
+
+   **Step 2: Capture screenshots with agent-browser CLI**
+   ```bash
+   agent-browser open http://localhost:3000/[route]
+   agent-browser snapshot -i
+   agent-browser screenshot output.png
+   ```
+   See the `agent-browser` skill for detailed usage.
+
+   **Step 3: Upload using imgup skill**
+   ```bash
+   skill: imgup
+   # Then upload each screenshot:
+   imgup -h pixhost screenshot.png  # pixhost works without API key
+   # Alternative hosts: catbox, imagebin, beeimg
+   ```
+
+   **What to capture:**
+   - **New screens**: Screenshot of the new UI
+   - **Modified screens**: Before AND after screenshots
+   - **Design implementation**: Screenshot showing Figma design match
+
+   **IMPORTANT**: Always include uploaded image URLs in PR description. This provides visual context for reviewers and documents the change.
+
+3. **Create Pull Request**
+
+   ```bash
+   git push -u origin feature-branch-name
+
+   gh pr create --title "Feature: [Description]" --body "$(cat <<'EOF'
+   ## Summary
+   - What was built
+   - Why it was needed
+   - Key decisions made
+
+   ## Testing
+   - Tests added/modified
+   - Manual testing performed
+
+   ## Post-Deploy Monitoring & Validation
+   - **What to monitor/search**
+     - Logs:
+     - Metrics/Dashboards:
+   - **Validation checks (queries/commands)**
+     - `command or query here`
+   - **Expected healthy behavior**
+     - Expected signal(s)
+   - **Failure signal(s) / rollback trigger**
+     - Trigger + immediate action
+   - **Validation window & owner**
+     - Window:
+     - Owner:
+   - **If no operational impact**
+     - `No additional operational monitoring required: <reason>`
+
+   ## Before / After Screenshots
+   | Before | After |
+   |--------|-------|
+   | ![before](URL) | ![after](URL) |
+
+   ## Figma Design
+   [Link if applicable]
+
+   ---
+
+   [![Compound Engineered](https://img.shields.io/badge/Compound-Engineered-6366f1)](https://github.com/EveryInc/compound-engineering-plugin) 🤖 Generated with [Claude Code](https://claude.com/claude-code)
+   EOF
+   )"
+   ```
+
+4. **Update Plan Status**
+
+   If the input document has YAML frontmatter with a `status` field, update it to `completed`:
+   ```
+   status: active  →  status: completed
+   ```
+
+5. **Notify User**
+   - Summarize what was completed
+   - Link to PR
+   - Note any follow-up work needed
+   - Suggest next steps if applicable
+
+---
+
+## Swarm Mode (Optional)
+
+For complex plans with multiple independent workstreams, enable swarm mode for parallel execution with coordinated agents.
+
+### When to Use Swarm Mode
+
+| Use Swarm Mode when... | Use Standard Mode when... |
+|------------------------|---------------------------|
+| Plan has 5+ independent tasks | Plan is linear/sequential |
+| Multiple specialists needed (review + test + implement) | Single-focus work |
+| Want maximum parallelism | Simpler mental model preferred |
+| Large feature with clear phases | Small feature or bug fix |
+
+### Enabling Swarm Mode
+
+To trigger swarm execution, say:
+
+> "Make a Task list and launch an army of agent swarm subagents to build the plan"
+
+Or explicitly request: "Use swarm mode for this work"
+
+### Swarm Workflow
+
+When swarm mode is enabled, the workflow changes:
+
+1. **Create Team**
+   ```
+   Teammate({ operation: "spawnTeam", team_name: "work-{timestamp}" })
+   ```
+
+2. **Create Task List with Dependencies**
+   - Parse plan into TaskCreate items
+   - Set up blockedBy relationships for sequential dependencies
+   - Independent tasks have no blockers (can run in parallel)
+
+3. **Spawn Specialized Teammates**
+   ```
+   Task({
+     team_name: "work-{timestamp}",
+     name: "implementer",
+     subagent_type: "general-purpose",
+     prompt: "Claim implementation tasks, execute, mark complete",
+     run_in_background: true
+   })
+
+   Task({
+     team_name: "work-{timestamp}",
+     name: "tester",
+     subagent_type: "general-purpose",
+     prompt: "Claim testing tasks, run tests, mark complete",
+     run_in_background: true
+   })
+   ```
+
+4. **Coordinate and Monitor**
+   - Team lead monitors task completion
+   - Spawn additional workers as phases unblock
+   - Handle plan approval if required
+
+5. **Cleanup**
+   ```
+   Teammate({ operation: "requestShutdown", target_agent_id: "implementer" })
+   Teammate({ operation: "requestShutdown", target_agent_id: "tester" })
+   Teammate({ operation: "cleanup" })
+   ```
+
+See the `orchestrating-swarms` skill for detailed swarm patterns and best practices.
+
+---
+
+## Key Principles
+
+### Start Fast, Execute Faster
+
+- Get clarification once at the start, then execute
+- Don't wait for perfect understanding - ask questions and move
+- The goal is to **finish the feature**, not create perfect process
+
+### The Plan is Your Guide
+
+- Work documents should reference similar code and patterns
+- Load those references and follow them
+- Don't reinvent - match what exists
+
+### Test As You Go
+
+- Run tests after each change, not at the end
+- Fix failures immediately
+- Continuous testing prevents big surprises
+
+### Quality is Built In
+
+- Follow existing patterns
+- Write tests for new code
+- Run linting before pushing
+- Use reviewer agents for complex/risky changes only
+
+### Ship Complete Features
+
+- Mark all tasks completed before moving on
+- Don't leave features 80% done
+- A finished feature that ships beats a perfect feature that doesn't
+
+## Quality Checklist
+
+Before creating PR, verify:
+
+- [ ] All clarifying questions asked and answered
+- [ ] All TodoWrite tasks marked completed
+- [ ] Tests pass (run project's test command)
+- [ ] Linting passes (use linting-agent)
+- [ ] Code follows existing patterns
+- [ ] Figma designs match implementation (if applicable)
+- [ ] Before/after screenshots captured and uploaded (for UI changes)
+- [ ] Commit messages follow conventional format
+- [ ] PR description includes Post-Deploy Monitoring & Validation section (or explicit no-impact rationale)
+- [ ] PR description includes summary, testing notes, and screenshots
+- [ ] PR description includes Compound Engineered badge
+
+## When to Use Reviewer Agents
+
+**Don't use by default.** Use reviewer agents only when:
+
+- Large refactor affecting many files (10+)
+- Security-sensitive changes (authentication, permissions, data access)
+- Performance-critical code paths
+- Complex algorithms or business logic
+- User explicitly requests thorough review
+
+For most features: tests + linting + following patterns is sufficient.
+
+## Common Pitfalls to Avoid
+
+- **Analysis paralysis** - Don't overthink, read the plan and execute
+- **Skipping clarifying questions** - Ask now, not after building wrong thing
+- **Ignoring plan references** - The plan has links for a reason
+- **Testing at the end** - Test continuously or suffer later
+- **Forgetting TodoWrite** - Track progress or lose track of what's done
+- **80% done syndrome** - Finish the feature, don't move on early
+- **Over-reviewing simple changes** - Save reviewer agents for complex work
--- a/plugins/compound-engineering/skills/changelog/SKILL.md
+++ b/plugins/compound-engineering/skills/changelog/SKILL.md
--- a/plugins/compound-engineering/skills/create-agent-skill/SKILL.md
+++ b/plugins/compound-engineering/skills/create-agent-skill/SKILL.md
@@ -2,7 +2,7 @@
 name: create-agent-skill
 description: Create or edit Claude Code skills with expert guidance on structure and best practices
 allowed-tools: Skill(create-agent-skills)
-argument-hint: [skill description or requirements]
+argument-hint: "[skill description or requirements]"
 disable-model-invocation: true
 ---

--- a/plugins/compound-engineering/skills/create-agent-skills/SKILL.md
+++ b/plugins/compound-engineering/skills/create-agent-skills/SKILL.md
@@ -97,22 +97,11 @@ Access individual args: `$ARGUMENTS[0]` or shorthand `$0`, `$1`, `$2`.

 ### Dynamic Context Injection

-The `` !`command` `` syntax runs shell commands before content is sent to Claude:
+Skills support dynamic context injection: prefix a backtick-wrapped shell command with an exclamation mark, and the preprocessor executes it at load time, replacing the directive with stdout. Write an exclamation mark immediately before the opening backtick of the command you want executed (for example, to inject the current git branch, write the exclamation mark followed by `git branch --show-current` wrapped in backticks).

-```yaml
---
-name: pr-summary
-description: Summarize changes in a pull request
-context: fork
-agent: Explore
---
+**Important:** The preprocessor scans the entire SKILL.md as plain text — it does not parse markdown. Directives inside fenced code blocks or inline code spans are still executed. If a skill documents this syntax with literal examples, the preprocessor will attempt to run them, causing load failures. To safely document this feature, describe it in prose (as done here) or place examples in a reference file, which is loaded on-demand by Claude and not preprocessed.

-## Context
- PR diff: !`gh pr diff`
- Changed files: !`gh pr diff --name-only`
-
-Summarize this pull request...
-```
+For a concrete example of dynamic context injection in a skill, see [official-spec.md](references/official-spec.md) § "Dynamic Context Injection".

 ### Running in a Subagent

--- a/plugins/compound-engineering/skills/create-agent-skills/workflows/add-workflow.md
+++ b/plugins/compound-engineering/skills/create-agent-skills/workflows/add-workflow.md
@@ -1,5 +1,11 @@
 # Workflow: Add a Workflow to Existing Skill

+## Interaction Method
+
+If `AskUserQuestion` is available, use it for all prompts below.
+
+If not, present each question as a numbered list and wait for a reply before proceeding to the next step. Never skip or auto-configure.
+
 <required_reading>
 **Read these reference files NOW:**
 1. references/recommended-structure.md
--- a/plugins/compound-engineering/skills/create-agent-skills/workflows/create-new-skill.md
+++ b/plugins/compound-engineering/skills/create-agent-skills/workflows/create-new-skill.md
@@ -1,5 +1,11 @@
 # Workflow: Create a New Skill

+## Interaction Method
+
+If `AskUserQuestion` is available, use it for all prompts below.
+
+If not, present each question as a numbered list and wait for a reply before proceeding to the next step. For multiSelect questions, accept comma-separated numbers (e.g. `1, 3`). Never skip or auto-configure.
+
 <required_reading>
 **Read these reference files NOW:**
 1. references/recommended-structure.md
--- a/plugins/compound-engineering/skills/deepen-plan/SKILL.md
+++ b/plugins/compound-engineering/skills/deepen-plan/SKILL.md
@@ -10,7 +10,7 @@ argument-hint: "[path to plan file]"

 **Note: The current year is 2026.** Use this when searching for recent documentation and best practices.

-This command takes an existing plan (from `/workflows:plan`) and enhances each section with parallel research agents. Each major element gets its own dedicated research sub-agent to find:
+This command takes an existing plan (from `/ce:plan`) and enhances each section with parallel research agents. Each major element gets its own dedicated research sub-agent to find:
 - Best practices and industry patterns
 - Performance optimizations
 - UI/UX improvements (if applicable)
@@ -145,13 +145,13 @@ Task general-purpose: "Use the security-patterns skill at ~/.claude/skills/secur
 ### 3. Discover and Apply Learnings/Solutions

 <thinking>
-Check for documented learnings from /workflows:compound. These are solved problems stored as markdown files. Spawn a sub-agent for each learning to check if it's relevant.
+Check for documented learnings from /ce:compound. These are solved problems stored as markdown files. Spawn a sub-agent for each learning to check if it's relevant.
 </thinking>

 **LEARNINGS LOCATION - Check these exact folders:**

 ```
-docs/solutions/           <-- PRIMARY: Project-level learnings (created by /workflows:compound)
+docs/solutions/           <-- PRIMARY: Project-level learnings (created by /ce:compound)
 ├── performance-issues/
 │   └── *.md
 ├── debugging-patterns/
@@ -370,7 +370,7 @@ Wait for ALL parallel agents to complete - skills, research agents, review agent
 **Collect outputs from ALL sources:**

 1. **Skill-based sub-agents** - Each skill's full output (code examples, patterns, recommendations)
-2. **Learnings/Solutions sub-agents** - Relevant documented learnings from /workflows:compound
+2. **Learnings/Solutions sub-agents** - Relevant documented learnings from /ce:compound
 3. **Research agents** - Best practices, documentation, real-world examples
 4. **Review agents** - All feedback from every reviewer (architecture, security, performance, simplicity, etc.)
 5. **Context7 queries** - Framework documentation and patterns
@@ -480,15 +480,13 @@ After writing the enhanced plan, use the **AskUserQuestion tool** to present the

 **Options:**
 1. **View diff** - Show what was added/changed
-2. **Run `/technical_review`** - Get feedback from reviewers on enhanced plan
-3. **Start `/workflows:work`** - Begin implementing this enhanced plan
-4. **Deepen further** - Run another round of research on specific sections
-5. **Revert** - Restore original plan (if backup exists)
+2. **Start `/ce:work`** - Begin implementing this enhanced plan
+3. **Deepen further** - Run another round of research on specific sections
+4. **Revert** - Restore original plan (if backup exists)

 Based on selection:
 - **View diff** → Run `git diff [plan_path]` or show before/after
- **`/technical_review`** → Call the /technical_review command with the plan file path
- **`/workflows:work`** → Call the /workflows:work command with the plan file path
+- **`/ce:work`** → Call the /ce:work command with the plan file path
 - **Deepen further** → Ask which sections need more research, then re-run those agents
 - **Revert** → Restore from git or backup

--- a/plugins/compound-engineering/skills/deploy-docs/SKILL.md
+++ b/plugins/compound-engineering/skills/deploy-docs/SKILL.md
@@ -15,7 +15,6 @@ Run these checks:
 ```bash
 # Count components
 echo "Agents: $(ls plugins/compound-engineering/agents/*.md | wc -l)"
-echo "Commands: $(ls plugins/compound-engineering/commands/*.md | wc -l)"
 echo "Skills: $(ls -d plugins/compound-engineering/skills/*/ 2>/dev/null | wc -l)"

 # Validate JSON
@@ -109,5 +108,5 @@ Provide a summary:
 - [ ] Commit any pending changes
 - [ ] Push to main branch
 - [ ] Verify GitHub Pages workflow exists
- [ ] Check deployment at https://everyinc.github.io/every-marketplace/
+- [ ] Check deployment at https://everyinc.github.io/compound-engineering-plugin/
 ```
--- a/plugins/compound-engineering/skills/document-review/SKILL.md
+++ b/plugins/compound-engineering/skills/document-review/SKILL.md
@@ -36,7 +36,7 @@ Score the document against these criteria:
 | **Specificity** | Concrete enough for next step (brainstorm → can plan, plan → can implement) |
 | **YAGNI** | No hypothetical features, simplest approach chosen |

-If invoked within a workflow (after `/workflows:brainstorm` or `/workflows:plan`), also check:
+If invoked within a workflow (after `/ce:brainstorm` or `/ce:plan`), also check:
 - **User intent fidelity** — Document reflects what was discussed, assumptions validated

 ## Step 4: Identify the Critical Improvement
--- a/plugins/compound-engineering/skills/feature-video/SKILL.md
+++ b/plugins/compound-engineering/skills/feature-video/SKILL.md
@@ -26,6 +26,7 @@ This command creates professional video walkthroughs of features for PR document
 - Git repository with a PR to document
 - `ffmpeg` installed (for video conversion)
 - `rclone` configured (optional, for cloud upload - see rclone skill)
+- Public R2 base URL known (for example, `https://<public-domain>.r2.dev`)
 </requirements>

 ## Setup
@@ -212,6 +213,9 @@ ffmpeg -y -framerate 0.5 -pattern_type glob -i 'tmp/screenshots/*.png' \
 # Check rclone is configured
 rclone listremotes

+# Set your public base URL (NO trailing slash)
+PUBLIC_BASE_URL="https://<your-public-r2-domain>.r2.dev"
+
 # Upload video, preview GIF, and screenshots to cloud storage
 # Use --s3-no-check-bucket to avoid permission errors
 rclone copy tmp/videos/ r2:kieran-claude/pr-videos/pr-[number]/ --s3-no-check-bucket --progress
@@ -219,12 +223,17 @@ rclone copy tmp/screenshots/ r2:kieran-claude/pr-videos/pr-[number]/screenshots/

 # List uploaded files
 rclone ls r2:kieran-claude/pr-videos/pr-[number]/
-```

-Public URLs (R2 with public access):
-```
-Video: https://pub-4047722ebb1b4b09853f24d3b61467f1.r2.dev/pr-videos/pr-[number]/feature-demo.mp4
-Preview: https://pub-4047722ebb1b4b09853f24d3b61467f1.r2.dev/pr-videos/pr-[number]/feature-demo-preview.gif
+# Build and validate public URLs BEFORE updating PR
+VIDEO_URL="$PUBLIC_BASE_URL/pr-videos/pr-[number]/feature-demo.mp4"
+PREVIEW_URL="$PUBLIC_BASE_URL/pr-videos/pr-[number]/feature-demo-preview.gif"
+
+curl -I "$VIDEO_URL"
+curl -I "$PREVIEW_URL"
+
+# Require HTTP 200 for both URLs; stop if either fails
+curl -I "$VIDEO_URL" | head -n 1 | grep -q ' 200 ' || exit 1
+curl -I "$PREVIEW_URL" | head -n 1 | grep -q ' 200 ' || exit 1
 ```

 </upload_video>
@@ -254,7 +263,7 @@ If the PR already has a video section, replace it. Otherwise, append:

 Example:
 ```markdown
-[![Feature Demo](https://pub-4047722ebb1b4b09853f24d3b61467f1.r2.dev/pr-videos/pr-137/feature-demo-preview.gif)](https://pub-4047722ebb1b4b09853f24d3b61467f1.r2.dev/pr-videos/pr-137/feature-demo.mp4)
+[![Feature Demo](https://<your-public-r2-domain>.r2.dev/pr-videos/pr-137/feature-demo-preview.gif)](https://<your-public-r2-domain>.r2.dev/pr-videos/pr-137/feature-demo.mp4)
 ```

 **Update the PR:**
--- a/plugins/compound-engineering/skills/file-todos/SKILL.md
+++ b/plugins/compound-engineering/skills/file-todos/SKILL.md
@@ -192,7 +192,7 @@ Work logs serve as:

 | Trigger | Flow | Tool |
 |---------|------|------|
-| Code review | `/workflows:review` → Findings → `/triage` → Todos | Review agent + skill |
+| Code review | `/ce:review` → Findings → `/triage` → Todos | Review agent + skill |
 | PR comments | `/resolve_pr_parallel` → Individual fixes → Todos | gh CLI + skill |
 | Code TODOs | `/resolve_todo_parallel` → Fixes + Complex todos | Agent + skill |
 | Planning | Brainstorm → Create todo → Work → Complete | Skill |
--- a/plugins/compound-engineering/skills/generate_command/SKILL.md
+++ b/plugins/compound-engineering/skills/generate_command/SKILL.md
@@ -7,7 +7,7 @@ disable-model-invocation: true

 # Create a Custom Claude Code Command

-Create a new slash command in `.claude/commands/` for the requested task.
+Create a new skill in `.claude/skills/` for the requested task.

 ## Goal

@@ -128,10 +128,10 @@ Implement #$ARGUMENTS following these steps:

 ## Creating the Command File

-1. **Create the file** at `.claude/commands/[name].md` (subdirectories like `workflows/` supported)
+1. **Create the directory** at `.claude/skills/[name]/SKILL.md`
 2. **Start with YAML frontmatter** (see section above)
-3. **Structure the command** using the template above
-4. **Test the command** by using it with appropriate arguments
+3. **Structure the skill** using the template above
+4. **Test the skill** by using it with appropriate arguments

 ## Command File Template

--- a/plugins/compound-engineering/skills/git-worktree/SKILL.md
+++ b/plugins/compound-engineering/skills/git-worktree/SKILL.md
@@ -38,8 +38,8 @@ git worktree add .worktrees/feature-name -b feature-name main

 Use this skill in these scenarios:

-1. **Code Review (`/workflows:review`)**: If NOT already on the target branch (PR branch or requested branch), offer worktree for isolated review
-2. **Feature Work (`/workflows:work`)**: Always ask if user wants parallel worktree or live branch work
+1. **Code Review (`/ce:review`)**: If NOT already on the target branch (PR branch or requested branch), offer worktree for isolated review
+2. **Feature Work (`/ce:work`)**: Always ask if user wants parallel worktree or live branch work
 3. **Parallel Development**: When working on multiple features simultaneously
 4. **Cleanup**: After completing work in a worktree

@@ -47,7 +47,7 @@ Use this skill in these scenarios:

 ### In Claude Code Workflows

-The skill is automatically called from `/workflows:review` and `/workflows:work` commands:
+The skill is automatically called from `/ce:review` and `/ce:work` commands:

 ```
 # For review: offers worktree if not on PR branch
@@ -204,7 +204,7 @@ bash ${CLAUDE_PLUGIN_ROOT}/skills/git-worktree/scripts/worktree-manager.sh clean

 ## Integration with Workflows

-### `/workflows:review`
+### `/ce:review`

 Instead of always creating a worktree:

@@ -217,7 +217,7 @@ Instead of always creating a worktree:
   - no → proceed with PR diff on current branch
 ```

-### `/workflows:work`
+### `/ce:work`

 Always offer choice:

--- a/plugins/compound-engineering/skills/heal-skill/SKILL.md
+++ b/plugins/compound-engineering/skills/heal-skill/SKILL.md
@@ -1,7 +1,7 @@
 ---
 name: heal-skill
 description: Fix incorrect SKILL.md files when a skill has wrong instructions or outdated API references
-argument-hint: [optional: specific issue to fix]
+argument-hint: "[optional: specific issue to fix]"
 allowed-tools: [Read, Edit, Bash(ls:*), Bash(git:*)]
 disable-model-invocation: true
 ---
--- a/plugins/compound-engineering/skills/lfg/SKILL.md
+++ b/plugins/compound-engineering/skills/lfg/SKILL.md
@@ -0,0 +1,34 @@
+---
+name: lfg
+description: Full autonomous engineering workflow
+argument-hint: "[feature description]"
+disable-model-invocation: true
+---
+
+CRITICAL: You MUST execute every step below IN ORDER. Do NOT skip any step. Do NOT jump ahead to coding or implementation. The plan phase (steps 2-3) MUST be completed and verified BEFORE any work begins. Violating this order produces bad output.
+
+1. **Optional:** If the `ralph-wiggum` skill is available, run `/ralph-wiggum:ralph-loop "finish all slash commands" --completion-promise "DONE"`. If not available or it fails, skip and continue to step 2 immediately.
+
+2. `/ce:plan $ARGUMENTS`
+
+   GATE: STOP. Verify that `/ce:plan` produced a plan file in `docs/plans/`. If no plan file was created, run `/ce:plan $ARGUMENTS` again. Do NOT proceed to step 3 until a written plan exists.
+
+3. `/compound-engineering:deepen-plan`
+
+   GATE: STOP. Confirm the plan has been deepened and updated. The plan file in `docs/plans/` should now contain additional detail. Do NOT proceed to step 4 without a deepened plan.
+
+4. `/ce:work`
+
+   GATE: STOP. Verify that implementation work was performed - files were created or modified beyond the plan. Do NOT proceed to step 5 if no code changes were made.
+
+5. `/ce:review`
+
+6. `/compound-engineering:resolve_todo_parallel`
+
+7. `/compound-engineering:test-browser`
+
+8. `/compound-engineering:feature-video`
+
+9. Output `<promise>DONE</promise>` when video is in PR
+
+Start with step 2 now (or step 1 if ralph-wiggum is available). Remember: plan FIRST, then work. Never skip the plan.
--- a/plugins/compound-engineering/skills/proof/SKILL.md
+++ b/plugins/compound-engineering/skills/proof/SKILL.md
@@ -0,0 +1,185 @@
+---
+name: proof
+description: Create, edit, comment on, and share markdown documents via Proof's web API and local bridge. Use when asked to "proof", "share a doc", "create a proof doc", "comment on a document", "suggest edits", "review in proof", or when given a proofeditor.ai URL.
+allowed-tools:
+  - Bash
+  - Read
+  - Write
+  - WebFetch
+---
+
+# Proof - Collaborative Markdown Editor
+
+Proof is a collaborative document editor for humans and agents. It supports two modes:
+
+1. **Web API** - Create and edit shared documents via HTTP (no install needed)
+2. **Local Bridge** - Drive the macOS Proof app via localhost:9847
+
+## Web API (Primary for Sharing)
+
+### Create a Shared Document
+
+No authentication required. Returns a shareable URL with access token.
+
+```bash
+curl -X POST https://www.proofeditor.ai/share/markdown \
+  -H "Content-Type: application/json" \
+  -d '{"title":"My Doc","markdown":"# Hello\n\nContent here."}'
+```
+
+**Response format:**
+```json
+{
+  "slug": "abc123",
+  "tokenUrl": "https://www.proofeditor.ai/d/abc123?token=xxx",
+  "accessToken": "xxx",
+  "ownerSecret": "yyy",
+  "_links": {
+    "state": "https://www.proofeditor.ai/api/agent/abc123/state",
+    "ops": "https://www.proofeditor.ai/api/agent/abc123/ops"
+  }
+}
+```
+
+Use the `tokenUrl` as the shareable link. The `_links` give you the exact API paths.
+
+### Read a Shared Document
+
+```bash
+curl -s "https://www.proofeditor.ai/api/agent/{slug}/state" \
+  -H "x-share-token: <token>"
+```
+
+### Edit a Shared Document
+
+All operations go to `POST https://www.proofeditor.ai/api/agent/{slug}/ops`
+
+**Note:** Use the `/api/agent/{slug}/ops` path (from `_links` in create response), NOT `/api/documents/{slug}/ops`.
+
+**Authentication for protected docs:**
+- Header: `x-share-token: <token>` or `Authorization: Bearer <token>`
+- Token comes from the URL parameter: `?token=xxx` or the `accessToken` from create response
+
+**Comment on text:**
+```json
+{"op": "comment.add", "quote": "text to comment on", "by": "ai:<agent-name>", "text": "Your comment here"}
+```
+
+**Reply to a comment:**
+```json
+{"op": "comment.reply", "markId": "<id>", "by": "ai:<agent-name>", "text": "Reply text"}
+```
+
+**Resolve a comment:**
+```json
+{"op": "comment.resolve", "markId": "<id>", "by": "ai:<agent-name>"}
+```
+
+**Suggest a replacement:**
+```json
+{"op": "suggestion.add", "kind": "replace", "quote": "original text", "by": "ai:<agent-name>", "content": "replacement text"}
+```
+
+**Suggest a deletion:**
+```json
+{"op": "suggestion.add", "kind": "delete", "quote": "text to delete", "by": "ai:<agent-name>"}
+```
+
+**Bulk rewrite:**
+```json
+{"op": "rewrite.apply", "content": "full new markdown", "by": "ai:<agent-name>"}
+```
+
+### Known Limitations (Web API)
+
+- `suggestion.add` with `kind: "insert"` returns Bad Request on the web ops endpoint. Use `kind: "replace"` with a broader quote instead, or use `rewrite.apply` for insertions.
+- Bridge-style endpoints (`/d/{slug}/bridge/*`) require client version headers (`x-proof-client-version`, `x-proof-client-build`, `x-proof-client-protocol`) and return 426 CLIENT_UPGRADE_REQUIRED without them. Use the `/api/agent/{slug}/ops` endpoint instead.
+
+## Local Bridge (macOS App)
+
+Requires Proof.app running. Bridge at `http://localhost:9847`.
+
+**Required headers:**
+- `X-Agent-Id: claude` (identity for presence)
+- `Content-Type: application/json`
+- `X-Window-Id: <uuid>` (when multiple docs open)
+
+### Key Endpoints
+
+| Method | Endpoint | Purpose |
+|--------|----------|---------|
+| GET | `/windows` | List open documents |
+| GET | `/state` | Read markdown, cursor, word count |
+| GET | `/marks` | List all suggestions and comments |
+| POST | `/marks/suggest-replace` | `{"quote":"old","by":"ai:<agent-name>","content":"new"}` |
+| POST | `/marks/suggest-insert` | `{"quote":"after this","by":"ai:<agent-name>","content":"insert"}` |
+| POST | `/marks/suggest-delete` | `{"quote":"delete this","by":"ai:<agent-name>"}` |
+| POST | `/marks/comment` | `{"quote":"text","by":"ai:<agent-name>","text":"comment"}` |
+| POST | `/marks/reply` | `{"markId":"<id>","by":"ai:<agent-name>","text":"reply"}` |
+| POST | `/marks/resolve` | `{"markId":"<id>","by":"ai:<agent-name>"}` |
+| POST | `/marks/accept` | `{"markId":"<id>"}` |
+| POST | `/marks/reject` | `{"markId":"<id>"}` |
+| POST | `/rewrite` | `{"content":"full markdown","by":"ai:<agent-name>"}` |
+| POST | `/presence` | `{"status":"reading","summary":"..."}` |
+| GET | `/events/pending` | Poll for user actions |
+
+### Presence Statuses
+
+`thinking`, `reading`, `idle`, `acting`, `waiting`, `completed`
+
+## Workflow: Review a Shared Document
+
+When given a Proof URL like `https://www.proofeditor.ai/d/abc123?token=xxx`:
+
+1. Extract the slug (`abc123`) and token from the URL
+2. Read the document state via the API
+3. Add comments or suggest edits using the ops endpoint
+4. The author sees changes in real-time
+
+```bash
+# Read
+curl -s "https://www.proofeditor.ai/api/agent/abc123/state" \
+  -H "x-share-token: xxx"
+
+# Comment
+curl -X POST "https://www.proofeditor.ai/api/agent/abc123/ops" \
+  -H "Content-Type: application/json" \
+  -H "x-share-token: xxx" \
+  -d '{"op":"comment.add","quote":"text","by":"ai:compound","text":"comment"}'
+
+# Suggest edit
+curl -X POST "https://www.proofeditor.ai/api/agent/abc123/ops" \
+  -H "Content-Type: application/json" \
+  -H "x-share-token: xxx" \
+  -d '{"op":"suggestion.add","kind":"replace","quote":"old","by":"ai:compound","content":"new"}'
+```
+
+## Workflow: Create and Share a New Document
+
+```bash
+# 1. Create
+RESPONSE=$(curl -s -X POST https://www.proofeditor.ai/share/markdown \
+  -H "Content-Type: application/json" \
+  -d '{"title":"My Doc","markdown":"# Title\n\nContent here."}')
+
+# 2. Extract URL and token
+URL=$(echo "$RESPONSE" | jq -r '.tokenUrl')
+SLUG=$(echo "$RESPONSE" | jq -r '.slug')
+TOKEN=$(echo "$RESPONSE" | jq -r '.accessToken')
+
+# 3. Share the URL
+echo "$URL"
+
+# 4. Make edits using the ops endpoint
+curl -X POST "https://www.proofeditor.ai/api/agent/$SLUG/ops" \
+  -H "Content-Type: application/json" \
+  -H "x-share-token: $TOKEN" \
+  -d '{"op":"comment.add","quote":"Content here","by":"ai:compound","text":"Added a note"}'
+```
+
+## Safety
+
+- Use `/state` content as source of truth before editing
+- Prefer suggest-replace over full rewrite for small changes
+- Don't span table cells in a single replace
+- Always include `by` field for attribution tracking
--- a/plugins/compound-engineering/skills/report-bug/SKILL.md
+++ b/plugins/compound-engineering/skills/report-bug/SKILL.md
--- a/plugins/compound-engineering/skills/reproduce-bug/SKILL.md
+++ b/plugins/compound-engineering/skills/reproduce-bug/SKILL.md
--- a/plugins/compound-engineering/skills/resolve-pr-parallel/SKILL.md
+++ b/plugins/compound-engineering/skills/resolve-pr-parallel/SKILL.md
@@ -1,5 +1,5 @@
 ---
-name: resolve_pr_parallel
+name: resolve-pr-parallel
 description: Resolve all PR comments using parallel processing. Use when addressing PR review feedback, resolving review threads, or batch-fixing PR comments.
 argument-hint: "[optional: PR number or current PR]"
 disable-model-invocation: true
--- a/plugins/compound-engineering/skills/resolve_parallel/SKILL.md
+++ b/plugins/compound-engineering/skills/resolve_parallel/SKILL.md
--- a/plugins/compound-engineering/skills/resolve_todo_parallel/SKILL.md
+++ b/plugins/compound-engineering/skills/resolve_todo_parallel/SKILL.md
@@ -0,0 +1,37 @@
+---
+name: resolve_todo_parallel
+description: Resolve all pending CLI todos using parallel processing
+argument-hint: "[optional: specific todo ID or pattern]"
+---
+
+Resolve all TODO comments using parallel processing.
+
+## Workflow
+
+### 1. Analyze
+
+Get all unresolved TODOs from the /todos/\*.md directory
+
+If any todo recommends deleting, removing, or gitignoring files in `docs/plans/` or `docs/solutions/`, skip it and mark it as `wont_fix`. These are compound-engineering pipeline artifacts that are intentional and permanent.
+
+### 2. Plan
+
+Create a TodoWrite list of all unresolved items grouped by type.Make sure to look at dependencies that might occur and prioritize the ones needed by others. For example, if you need to change a name, you must wait to do the others. Output a mermaid flow diagram showing how we can do this. Can we do everything in parallel? Do we need to do one first that leads to others in parallel? I'll put the to-dos in the mermaid diagram flow‑wise so the agent knows how to proceed in order.
+
+### 3. Implement (PARALLEL)
+
+Spawn a pr-comment-resolver agent for each unresolved item in parallel.
+
+So if there are 3 comments, it will spawn 3 pr-comment-resolver agents in parallel. liek this
+
+1. Task pr-comment-resolver(comment1)
+2. Task pr-comment-resolver(comment2)
+3. Task pr-comment-resolver(comment3)
+
+Always run all in parallel subagents/Tasks for each Todo item.
+
+### 4. Commit & Resolve
+
+- Commit changes
+- Remove the TODO from the file, and mark it as resolved.
+- Push to remote
--- a/plugins/compound-engineering/skills/setup/SKILL.md
+++ b/plugins/compound-engineering/skills/setup/SKILL.md
@@ -6,7 +6,13 @@ disable-model-invocation: true

 # Compound Engineering Setup

-Interactive setup for `compound-engineering.local.md` — configures which agents run during `/workflows:review` and `/workflows:work`.
+## Interaction Method
+
+If `AskUserQuestion` is available, use it for all prompts below.
+
+If not, present each question as a numbered list and wait for a reply before proceeding to the next step. For multiSelect questions, accept comma-separated numbers (e.g. `1, 3`). Never skip or auto-configure.
+
+Interactive setup for `compound-engineering.local.md` — configures which agents run during `/ce:review` and `/ce:work`.

 ## Step 1: Check Existing Config

@@ -145,7 +151,7 @@ plan_review_agents: [{computed plan agent list}]
 # Review Context

 Add project-specific review instructions here.
-These notes are passed to all review agents during /workflows:review and /workflows:work.
+These notes are passed to all review agents during /ce:review and /ce:work.

 Examples:
 - "We use Turbo Frames heavily — check for frame-busting issues"
--- a/plugins/compound-engineering/skills/skill-creator/SKILL.md
+++ b/plugins/compound-engineering/skills/skill-creator/SKILL.md
@@ -1,210 +0,0 @@
---
-name: skill-creator
-description: Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
-license: Complete terms in LICENSE.txt
-disable-model-invocation: true
---
-
-# Skill Creator
-
-This skill provides guidance for creating effective skills.
-
-## About Skills
-
-Skills are modular, self-contained packages that extend Claude's capabilities by providing
-specialized knowledge, workflows, and tools. Think of them as "onboarding guides" for specific
-domains or tasks—they transform Claude from a general-purpose agent into a specialized agent
-equipped with procedural knowledge that no model can fully possess.
-
-### What Skills Provide
-
-1. Specialized workflows - Multi-step procedures for specific domains
-2. Tool integrations - Instructions for working with specific file formats or APIs
-3. Domain expertise - Company-specific knowledge, schemas, business logic
-4. Bundled resources - Scripts, references, and assets for complex and repetitive tasks
-
-### Anatomy of a Skill
-
-Every skill consists of a required SKILL.md file and optional bundled resources:
-
-```
-skill-name/
-├── SKILL.md (required)
-│   ├── YAML frontmatter metadata (required)
-│   │   ├── name: (required)
-│   │   └── description: (required)
-│   └── Markdown instructions (required)
-└── Bundled Resources (optional)
-    ├── scripts/          - Executable code (Python/Bash/etc.)
-    ├── references/       - Documentation intended to be loaded into context as needed
-    └── assets/           - Files used in output (templates, icons, fonts, etc.)
-```
-
-#### SKILL.md (required)
-
-**Metadata Quality:** The `name` and `description` in YAML frontmatter determine when Claude will use the skill. Be specific about what the skill does and when to use it. Use the third-person (e.g. "This skill should be used when..." instead of "Use this skill when...").
-
-#### Bundled Resources (optional)
-
-##### Scripts (`scripts/`)
-
-Executable code (Python/Bash/etc.) for tasks that require deterministic reliability or are repeatedly rewritten.
-
- **When to include**: When the same code is being rewritten repeatedly or deterministic reliability is needed
- **Example**: `scripts/rotate_pdf.py` for PDF rotation tasks
- **Benefits**: Token efficient, deterministic, may be executed without loading into context
- **Note**: Scripts may still need to be read by Claude for patching or environment-specific adjustments
-
-##### References (`references/`)
-
-Documentation and reference material intended to be loaded as needed into context to inform Claude's process and thinking.
-
- **When to include**: For documentation that Claude should reference while working
- **Examples**: `references/finance.md` for financial schemas, `references/mnda.md` for company NDA template, `references/policies.md` for company policies, `references/api_docs.md` for API specifications
- **Use cases**: Database schemas, API documentation, domain knowledge, company policies, detailed workflow guides
- **Benefits**: Keeps SKILL.md lean, loaded only when Claude determines it's needed
- **Best practice**: If files are large (>10k words), include grep search patterns in SKILL.md
- **Avoid duplication**: Information should live in either SKILL.md or references files, not both. Prefer references files for detailed information unless it's truly core to the skill—this keeps SKILL.md lean while making information discoverable without hogging the context window. Keep only essential procedural instructions and workflow guidance in SKILL.md; move detailed reference material, schemas, and examples to references files.
-
-##### Assets (`assets/`)
-
-Files not intended to be loaded into context, but rather used within the output Claude produces.
-
- **When to include**: When the skill needs files that will be used in the final output
- **Examples**: `assets/logo.png` for brand assets, `assets/slides.pptx` for PowerPoint templates, `assets/frontend-template/` for HTML/React boilerplate, `assets/font.ttf` for typography
- **Use cases**: Templates, images, icons, boilerplate code, fonts, sample documents that get copied or modified
- **Benefits**: Separates output resources from documentation, enables Claude to use files without loading them into context
-
-### Progressive Disclosure Design Principle
-
-Skills use a three-level loading system to manage context efficiently:
-
-1. **Metadata (name + description)** - Always in context (~100 words)
-2. **SKILL.md body** - When skill triggers (<5k words)
-3. **Bundled resources** - As needed by Claude (Unlimited*)
-
-*Unlimited because scripts can be executed without reading into context window.
-
-## Skill Creation Process
-
-To create a skill, follow the "Skill Creation Process" in order, skipping steps only if there is a clear reason why they are not applicable.
-
-### Step 1: Understanding the Skill with Concrete Examples
-
-Skip this step only when the skill's usage patterns are already clearly understood. It remains valuable even when working with an existing skill.
-
-To create an effective skill, clearly understand concrete examples of how the skill will be used. This understanding can come from either direct user examples or generated examples that are validated with user feedback.
-
-For example, when building an image-editor skill, relevant questions include:
-
- "What functionality should the image-editor skill support? Editing, rotating, anything else?"
- "Can you give some examples of how this skill would be used?"
- "I can imagine users asking for things like 'Remove the red-eye from this image' or 'Rotate this image'. Are there other ways you imagine this skill being used?"
- "What would a user say that should trigger this skill?"
-
-To avoid overwhelming users, avoid asking too many questions in a single message. Start with the most important questions and follow up as needed for better effectiveness.
-
-Conclude this step when there is a clear sense of the functionality the skill should support.
-
-### Step 2: Planning the Reusable Skill Contents
-
-To turn concrete examples into an effective skill, analyze each example by:
-
-1. Considering how to execute on the example from scratch
-2. Identifying what scripts, references, and assets would be helpful when executing these workflows repeatedly
-
-Example: When building a `pdf-editor` skill to handle queries like "Help me rotate this PDF," the analysis shows:
-
-1. Rotating a PDF requires re-writing the same code each time
-2. A `scripts/rotate_pdf.py` script would be helpful to store in the skill
-
-Example: When designing a `frontend-webapp-builder` skill for queries like "Build me a todo app" or "Build me a dashboard to track my steps," the analysis shows:
-
-1. Writing a frontend webapp requires the same boilerplate HTML/React each time
-2. An `assets/hello-world/` template containing the boilerplate HTML/React project files would be helpful to store in the skill
-
-Example: When building a `big-query` skill to handle queries like "How many users have logged in today?" the analysis shows:
-
-1. Querying BigQuery requires re-discovering the table schemas and relationships each time
-2. A `references/schema.md` file documenting the table schemas would be helpful to store in the skill
-
-To establish the skill's contents, analyze each concrete example to create a list of the reusable resources to include: scripts, references, and assets.
-
-### Step 3: Initializing the Skill
-
-At this point, it is time to actually create the skill.
-
-Skip this step only if the skill being developed already exists, and iteration or packaging is needed. In this case, continue to the next step.
-
-When creating a new skill from scratch, always run the `init_skill.py` script. The script conveniently generates a new template skill directory that automatically includes everything a skill requires, making the skill creation process much more efficient and reliable.
-
-Usage:
-
-```bash
-scripts/init_skill.py <skill-name> --path <output-directory>
-```
-
-The script:
-
- Creates the skill directory at the specified path
- Generates a SKILL.md template with proper frontmatter and TODO placeholders
- Creates example resource directories: `scripts/`, `references/`, and `assets/`
- Adds example files in each directory that can be customized or deleted
-
-After initialization, customize or remove the generated SKILL.md and example files as needed.
-
-### Step 4: Edit the Skill
-
-When editing the (newly-generated or existing) skill, remember that the skill is being created for another instance of Claude to use. Focus on including information that would be beneficial and non-obvious to Claude. Consider what procedural knowledge, domain-specific details, or reusable assets would help another Claude instance execute these tasks more effectively.
-
-#### Start with Reusable Skill Contents
-
-To begin implementation, start with the reusable resources identified above: `scripts/`, `references/`, and `assets/` files. Note that this step may require user input. For example, when implementing a `brand-guidelines` skill, the user may need to provide brand assets or templates to store in `assets/`, or documentation to store in `references/`.
-
-Also, delete any example files and directories not needed for the skill. The initialization script creates example files in `scripts/`, `references/`, and `assets/` to demonstrate structure, but most skills won't need all of them.
-
-#### Update SKILL.md
-
-**Writing Style:** Write the entire skill using **imperative/infinitive form** (verb-first instructions), not second person. Use objective, instructional language (e.g., "To accomplish X, do Y" rather than "You should do X" or "If you need to do X"). This maintains consistency and clarity for AI consumption.
-
-To complete SKILL.md, answer the following questions:
-
-1. What is the purpose of the skill, in a few sentences?
-2. When should the skill be used?
-3. In practice, how should Claude use the skill? All reusable skill contents developed above should be referenced so that Claude knows how to use them.
-
-### Step 5: Packaging a Skill
-
-Once the skill is ready, it should be packaged into a distributable zip file that gets shared with the user. The packaging process automatically validates the skill first to ensure it meets all requirements:
-
-```bash
-scripts/package_skill.py <path/to/skill-folder>
-```
-
-Optional output directory specification:
-
-```bash
-scripts/package_skill.py <path/to/skill-folder> ./dist
-```
-
-The packaging script will:
-
-1. **Validate** the skill automatically, checking:
-   - YAML frontmatter format and required fields
-   - Skill naming conventions and directory structure
-   - Description completeness and quality
-   - File organization and resource references
-
-2. **Package** the skill if validation passes, creating a zip file named after the skill (e.g., `my-skill.zip`) that includes all files and maintains the proper directory structure for distribution.
-
-If validation fails, the script will report the errors and exit without creating a package. Fix any validation errors and run the packaging command again.
-
-### Step 6: Iterate
-
-After testing the skill, users may request improvements. Often this happens right after using the skill, with fresh context of how the skill performed.
-
-**Iteration workflow:**
-1. Use the skill on real tasks
-2. Notice struggles or inefficiencies
-3. Identify how SKILL.md or bundled resources should be updated
-4. Implement changes and test again
--- a/plugins/compound-engineering/skills/skill-creator/scripts/init_skill.py
+++ b/plugins/compound-engineering/skills/skill-creator/scripts/init_skill.py
@@ -1,303 +0,0 @@
-#!/usr/bin/env python3
-"""
-Skill Initializer - Creates a new skill from template
-
-Usage:
-    init_skill.py <skill-name> --path <path>
-
-Examples:
-    init_skill.py my-new-skill --path skills/public
-    init_skill.py my-api-helper --path skills/private
-    init_skill.py custom-skill --path /custom/location
-"""
-
-import sys
-from pathlib import Path
-
-
-SKILL_TEMPLATE = """---
-name: {skill_name}
-description: [TODO: Complete and informative explanation of what the skill does and when to use it. Include WHEN to use this skill - specific scenarios, file types, or tasks that trigger it.]
---
-
-# {skill_title}
-
-## Overview
-
-[TODO: 1-2 sentences explaining what this skill enables]
-
-## Structuring This Skill
-
-[TODO: Choose the structure that best fits this skill's purpose. Common patterns:
-
-**1. Workflow-Based** (best for sequential processes)
- Works well when there are clear step-by-step procedures
- Example: DOCX skill with "Workflow Decision Tree" → "Reading" → "Creating" → "Editing"
- Structure: ## Overview → ## Workflow Decision Tree → ## Step 1 → ## Step 2...
-
-**2. Task-Based** (best for tool collections)
- Works well when the skill offers different operations/capabilities
- Example: PDF skill with "Quick Start" → "Merge PDFs" → "Split PDFs" → "Extract Text"
- Structure: ## Overview → ## Quick Start → ## Task Category 1 → ## Task Category 2...
-
-**3. Reference/Guidelines** (best for standards or specifications)
- Works well for brand guidelines, coding standards, or requirements
- Example: Brand styling with "Brand Guidelines" → "Colors" → "Typography" → "Features"
- Structure: ## Overview → ## Guidelines → ## Specifications → ## Usage...
-
-**4. Capabilities-Based** (best for integrated systems)
- Works well when the skill provides multiple interrelated features
- Example: Product Management with "Core Capabilities" → numbered capability list
- Structure: ## Overview → ## Core Capabilities → ### 1. Feature → ### 2. Feature...
-
-Patterns can be mixed and matched as needed. Most skills combine patterns (e.g., start with task-based, add workflow for complex operations).
-
-Delete this entire "Structuring This Skill" section when done - it's just guidance.]
-
-## [TODO: Replace with the first main section based on chosen structure]
-
-[TODO: Add content here. See examples in existing skills:
- Code samples for technical skills
- Decision trees for complex workflows
- Concrete examples with realistic user requests
- References to scripts/templates/references as needed]
-
-## Resources
-
-This skill includes example resource directories that demonstrate how to organize different types of bundled resources:
-
-### scripts/
-Executable code (Python/Bash/etc.) that can be run directly to perform specific operations.
-
-**Examples from other skills:**
- PDF skill: `fill_fillable_fields.py`, `extract_form_field_info.py` - utilities for PDF manipulation
- DOCX skill: `document.py`, `utilities.py` - Python modules for document processing
-
-**Appropriate for:** Python scripts, shell scripts, or any executable code that performs automation, data processing, or specific operations.
-
-**Note:** Scripts may be executed without loading into context, but can still be read by Claude for patching or environment adjustments.
-
-### references/
-Documentation and reference material intended to be loaded into context to inform Claude's process and thinking.
-
-**Examples from other skills:**
- Product management: `communication.md`, `context_building.md` - detailed workflow guides
- BigQuery: API reference documentation and query examples
- Finance: Schema documentation, company policies
-
-**Appropriate for:** In-depth documentation, API references, database schemas, comprehensive guides, or any detailed information that Claude should reference while working.
-
-### assets/
-Files not intended to be loaded into context, but rather used within the output Claude produces.
-
-**Examples from other skills:**
- Brand styling: PowerPoint template files (.pptx), logo files
- Frontend builder: HTML/React boilerplate project directories
- Typography: Font files (.ttf, .woff2)
-
-**Appropriate for:** Templates, boilerplate code, document templates, images, icons, fonts, or any files meant to be copied or used in the final output.
-
---
-
-**Any unneeded directories can be deleted.** Not every skill requires all three types of resources.
-"""
-
-EXAMPLE_SCRIPT = '''#!/usr/bin/env python3
-"""
-Example helper script for {skill_name}
-
-This is a placeholder script that can be executed directly.
-Replace with actual implementation or delete if not needed.
-
-Example real scripts from other skills:
- pdf/scripts/fill_fillable_fields.py - Fills PDF form fields
- pdf/scripts/convert_pdf_to_images.py - Converts PDF pages to images
-"""
-
-def main():
-    print("This is an example script for {skill_name}")
-    # TODO: Add actual script logic here
-    # This could be data processing, file conversion, API calls, etc.
-
-if __name__ == "__main__":
-    main()
-'''
-
-EXAMPLE_REFERENCE = """# Reference Documentation for {skill_title}
-
-This is a placeholder for detailed reference documentation.
-Replace with actual reference content or delete if not needed.
-
-Example real reference docs from other skills:
- product-management/references/communication.md - Comprehensive guide for status updates
- product-management/references/context_building.md - Deep-dive on gathering context
- bigquery/references/ - API references and query examples
-
-## When Reference Docs Are Useful
-
-Reference docs are ideal for:
- Comprehensive API documentation
- Detailed workflow guides
- Complex multi-step processes
- Information too lengthy for main SKILL.md
- Content that's only needed for specific use cases
-
-## Structure Suggestions
-
-### API Reference Example
- Overview
- Authentication
- Endpoints with examples
- Error codes
- Rate limits
-
-### Workflow Guide Example
- Prerequisites
- Step-by-step instructions
- Common patterns
- Troubleshooting
- Best practices
-"""
-
-EXAMPLE_ASSET = """# Example Asset File
-
-This placeholder represents where asset files would be stored.
-Replace with actual asset files (templates, images, fonts, etc.) or delete if not needed.
-
-Asset files are NOT intended to be loaded into context, but rather used within
-the output Claude produces.
-
-Example asset files from other skills:
- Brand guidelines: logo.png, slides_template.pptx
- Frontend builder: hello-world/ directory with HTML/React boilerplate
- Typography: custom-font.ttf, font-family.woff2
- Data: sample_data.csv, test_dataset.json
-
-## Common Asset Types
-
- Templates: .pptx, .docx, boilerplate directories
- Images: .png, .jpg, .svg, .gif
- Fonts: .ttf, .otf, .woff, .woff2
- Boilerplate code: Project directories, starter files
- Icons: .ico, .svg
- Data files: .csv, .json, .xml, .yaml
-
-Note: This is a text placeholder. Actual assets can be any file type.
-"""
-
-
-def title_case_skill_name(skill_name):
-    """Convert hyphenated skill name to Title Case for display."""
-    return ' '.join(word.capitalize() for word in skill_name.split('-'))
-
-
-def init_skill(skill_name, path):
-    """
-    Initialize a new skill directory with template SKILL.md.
-
-    Args:
-        skill_name: Name of the skill
-        path: Path where the skill directory should be created
-
-    Returns:
-        Path to created skill directory, or None if error
-    """
-    # Determine skill directory path
-    skill_dir = Path(path).resolve() / skill_name
-
-    # Check if directory already exists
-    if skill_dir.exists():
-        print(f"❌ Error: Skill directory already exists: {skill_dir}")
-        return None
-
-    # Create skill directory
-    try:
-        skill_dir.mkdir(parents=True, exist_ok=False)
-        print(f"✅ Created skill directory: {skill_dir}")
-    except Exception as e:
-        print(f"❌ Error creating directory: {e}")
-        return None
-
-    # Create SKILL.md from template
-    skill_title = title_case_skill_name(skill_name)
-    skill_content = SKILL_TEMPLATE.format(
-        skill_name=skill_name,
-        skill_title=skill_title
-    )
-
-    skill_md_path = skill_dir / 'SKILL.md'
-    try:
-        skill_md_path.write_text(skill_content)
-        print("✅ Created SKILL.md")
-    except Exception as e:
-        print(f"❌ Error creating SKILL.md: {e}")
-        return None
-
-    # Create resource directories with example files
-    try:
-        # Create scripts/ directory with example script
-        scripts_dir = skill_dir / 'scripts'
-        scripts_dir.mkdir(exist_ok=True)
-        example_script = scripts_dir / 'example.py'
-        example_script.write_text(EXAMPLE_SCRIPT.format(skill_name=skill_name))
-        example_script.chmod(0o755)
-        print("✅ Created scripts/example.py")
-
-        # Create references/ directory with example reference doc
-        references_dir = skill_dir / 'references'
-        references_dir.mkdir(exist_ok=True)
-        example_reference = references_dir / 'api_reference.md'
-        example_reference.write_text(EXAMPLE_REFERENCE.format(skill_title=skill_title))
-        print("✅ Created references/api_reference.md")
-
-        # Create assets/ directory with example asset placeholder
-        assets_dir = skill_dir / 'assets'
-        assets_dir.mkdir(exist_ok=True)
-        example_asset = assets_dir / 'example_asset.txt'
-        example_asset.write_text(EXAMPLE_ASSET)
-        print("✅ Created assets/example_asset.txt")
-    except Exception as e:
-        print(f"❌ Error creating resource directories: {e}")
-        return None
-
-    # Print next steps
-    print(f"\n✅ Skill '{skill_name}' initialized successfully at {skill_dir}")
-    print("\nNext steps:")
-    print("1. Edit SKILL.md to complete the TODO items and update the description")
-    print("2. Customize or delete the example files in scripts/, references/, and assets/")
-    print("3. Run the validator when ready to check the skill structure")
-
-    return skill_dir
-
-
-def main():
-    if len(sys.argv) < 4 or sys.argv[2] != '--path':
-        print("Usage: init_skill.py <skill-name> --path <path>")
-        print("\nSkill name requirements:")
-        print("  - Hyphen-case identifier (e.g., 'data-analyzer')")
-        print("  - Lowercase letters, digits, and hyphens only")
-        print("  - Max 40 characters")
-        print("  - Must match directory name exactly")
-        print("\nExamples:")
-        print("  init_skill.py my-new-skill --path skills/public")
-        print("  init_skill.py my-api-helper --path skills/private")
-        print("  init_skill.py custom-skill --path /custom/location")
-        sys.exit(1)
-
-    skill_name = sys.argv[1]
-    path = sys.argv[3]
-
-    print(f"🚀 Initializing skill: {skill_name}")
-    print(f"   Location: {path}")
-    print()
-
-    result = init_skill(skill_name, path)
-
-    if result:
-        sys.exit(0)
-    else:
-        sys.exit(1)
-
-
-if __name__ == "__main__":
-    main()
--- a/plugins/compound-engineering/skills/skill-creator/scripts/package_skill.py
+++ b/plugins/compound-engineering/skills/skill-creator/scripts/package_skill.py
@@ -1,110 +0,0 @@
-#!/usr/bin/env python3
-"""
-Skill Packager - Creates a distributable zip file of a skill folder
-
-Usage:
-    python utils/package_skill.py <path/to/skill-folder> [output-directory]
-
-Example:
-    python utils/package_skill.py skills/public/my-skill
-    python utils/package_skill.py skills/public/my-skill ./dist
-"""
-
-import sys
-import zipfile
-from pathlib import Path
-from quick_validate import validate_skill
-
-
-def package_skill(skill_path, output_dir=None):
-    """
-    Package a skill folder into a zip file.
-
-    Args:
-        skill_path: Path to the skill folder
-        output_dir: Optional output directory for the zip file (defaults to current directory)
-
-    Returns:
-        Path to the created zip file, or None if error
-    """
-    skill_path = Path(skill_path).resolve()
-
-    # Validate skill folder exists
-    if not skill_path.exists():
-        print(f"❌ Error: Skill folder not found: {skill_path}")
-        return None
-
-    if not skill_path.is_dir():
-        print(f"❌ Error: Path is not a directory: {skill_path}")
-        return None
-
-    # Validate SKILL.md exists
-    skill_md = skill_path / "SKILL.md"
-    if not skill_md.exists():
-        print(f"❌ Error: SKILL.md not found in {skill_path}")
-        return None
-
-    # Run validation before packaging
-    print("🔍 Validating skill...")
-    valid, message = validate_skill(skill_path)
-    if not valid:
-        print(f"❌ Validation failed: {message}")
-        print("   Please fix the validation errors before packaging.")
-        return None
-    print(f"✅ {message}\n")
-
-    # Determine output location
-    skill_name = skill_path.name
-    if output_dir:
-        output_path = Path(output_dir).resolve()
-        output_path.mkdir(parents=True, exist_ok=True)
-    else:
-        output_path = Path.cwd()
-
-    zip_filename = output_path / f"{skill_name}.zip"
-
-    # Create the zip file
-    try:
-        with zipfile.ZipFile(zip_filename, 'w', zipfile.ZIP_DEFLATED) as zipf:
-            # Walk through the skill directory
-            for file_path in skill_path.rglob('*'):
-                if file_path.is_file():
-                    # Calculate the relative path within the zip
-                    arcname = file_path.relative_to(skill_path.parent)
-                    zipf.write(file_path, arcname)
-                    print(f"  Added: {arcname}")
-
-        print(f"\n✅ Successfully packaged skill to: {zip_filename}")
-        return zip_filename
-
-    except Exception as e:
-        print(f"❌ Error creating zip file: {e}")
-        return None
-
-
-def main():
-    if len(sys.argv) < 2:
-        print("Usage: python utils/package_skill.py <path/to/skill-folder> [output-directory]")
-        print("\nExample:")
-        print("  python utils/package_skill.py skills/public/my-skill")
-        print("  python utils/package_skill.py skills/public/my-skill ./dist")
-        sys.exit(1)
-
-    skill_path = sys.argv[1]
-    output_dir = sys.argv[2] if len(sys.argv) > 2 else None
-
-    print(f"📦 Packaging skill: {skill_path}")
-    if output_dir:
-        print(f"   Output directory: {output_dir}")
-    print()
-
-    result = package_skill(skill_path, output_dir)
-
-    if result:
-        sys.exit(0)
-    else:
-        sys.exit(1)
-
-
-if __name__ == "__main__":
-    main()
--- a/plugins/compound-engineering/skills/skill-creator/scripts/quick_validate.py
+++ b/plugins/compound-engineering/skills/skill-creator/scripts/quick_validate.py
@@ -1,65 +0,0 @@
-#!/usr/bin/env python3
-"""
-Quick validation script for skills - minimal version
-"""
-
-import sys
-import os
-import re
-from pathlib import Path
-
-def validate_skill(skill_path):
-    """Basic validation of a skill"""
-    skill_path = Path(skill_path)
-    
-    # Check SKILL.md exists
-    skill_md = skill_path / 'SKILL.md'
-    if not skill_md.exists():
-        return False, "SKILL.md not found"
-    
-    # Read and validate frontmatter
-    content = skill_md.read_text()
-    if not content.startswith('---'):
-        return False, "No YAML frontmatter found"
-    
-    # Extract frontmatter
-    match = re.match(r'^---\n(.*?)\n---', content, re.DOTALL)
-    if not match:
-        return False, "Invalid frontmatter format"
-    
-    frontmatter = match.group(1)
-    
-    # Check required fields
-    if 'name:' not in frontmatter:
-        return False, "Missing 'name' in frontmatter"
-    if 'description:' not in frontmatter:
-        return False, "Missing 'description' in frontmatter"
-    
-    # Extract name for validation
-    name_match = re.search(r'name:\s*(.+)', frontmatter)
-    if name_match:
-        name = name_match.group(1).strip()
-        # Check naming convention (hyphen-case: lowercase with hyphens)
-        if not re.match(r'^[a-z0-9-]+$', name):
-            return False, f"Name '{name}' should be hyphen-case (lowercase letters, digits, and hyphens only)"
-        if name.startswith('-') or name.endswith('-') or '--' in name:
-            return False, f"Name '{name}' cannot start/end with hyphen or contain consecutive hyphens"
-
-    # Extract and validate description
-    desc_match = re.search(r'description:\s*(.+)', frontmatter)
-    if desc_match:
-        description = desc_match.group(1).strip()
-        # Check for angle brackets
-        if '<' in description or '>' in description:
-            return False, "Description cannot contain angle brackets (< or >)"
-
-    return True, "Skill is valid!"
-
-if __name__ == "__main__":
-    if len(sys.argv) != 2:
-        print("Usage: python quick_validate.py <skill_directory>")
-        sys.exit(1)
-    
-    valid, message = validate_skill(sys.argv[1])
-    print(message)
-    sys.exit(0 if valid else 1)
--- a/plugins/compound-engineering/skills/slfg/SKILL.md
+++ b/plugins/compound-engineering/skills/slfg/SKILL.md
@@ -5,20 +5,20 @@ argument-hint: "[feature description]"
 disable-model-invocation: true
 ---

-Swarm-enabled LFG. Run these steps in order, parallelizing where indicated.
+Swarm-enabled LFG. Run these steps in order, parallelizing where indicated. Do not stop between steps — complete every step through to the end.

 ## Sequential Phase

-1. `/ralph-wiggum:ralph-loop "finish all slash commands" --completion-promise "DONE"`
-2. `/workflows:plan $ARGUMENTS`
+1. **Optional:** If the `ralph-wiggum` skill is available, run `/ralph-wiggum:ralph-loop "finish all slash commands" --completion-promise "DONE"`. If not available or it fails, skip and continue to step 2 immediately.
+2. `/ce:plan $ARGUMENTS`
 3. `/compound-engineering:deepen-plan`
-4. `/workflows:work` — **Use swarm mode**: Make a Task list and launch an army of agent swarm subagents to build the plan
+4. `/ce:work` — **Use swarm mode**: Make a Task list and launch an army of agent swarm subagents to build the plan

 ## Parallel Phase

 After work completes, launch steps 5 and 6 as **parallel swarm agents** (both only need code to be written):

-5. `/workflows:review` — spawn as background Task agent
+5. `/ce:review` — spawn as background Task agent
 6. `/compound-engineering:test-browser` — spawn as background Task agent

 Wait for both to complete before continuing.
--- a/plugins/compound-engineering/skills/test-browser/SKILL.md
+++ b/plugins/compound-engineering/skills/test-browser/SKILL.md
@@ -1,7 +1,7 @@
 ---
 name: test-browser
 description: Run browser tests on pages affected by current PR or branch
-argument-hint: "[PR number, branch name, or 'current' for current branch]"
+argument-hint: "[PR number, branch name, 'current', or --port PORT]"
 ---

 # Browser Test Command
@@ -122,31 +122,82 @@ Build a list of URLs to test based on the mapping.

 </file_to_route_mapping>

-### 4. Verify Server is Running
+### 4. Detect Dev Server Port
+
+<detect_port>
+
+Determine the dev server port using this priority order:
+
+**Priority 1: Explicit argument**
+If the user passed a port number (e.g., `/test-browser 5000` or `/test-browser --port 5000`), use that port directly.
+
+**Priority 2: CLAUDE.md / project instructions**
+```bash
+# Check CLAUDE.md for port references
+grep -Eio '(port\s*[:=]\s*|localhost:)([0-9]{4,5})' CLAUDE.md 2>/dev/null | grep -Eo '[0-9]{4,5}' | head -1
+```
+
+**Priority 3: package.json scripts**
+```bash
+# Check dev/start scripts for --port flags
+grep -Eo '\-\-port[= ]+[0-9]{4,5}' package.json 2>/dev/null | grep -Eo '[0-9]{4,5}' | head -1
+```
+
+**Priority 4: Environment files**
+```bash
+# Check .env, .env.local, .env.development for PORT=
+grep -h '^PORT=' .env .env.local .env.development 2>/dev/null | tail -1 | cut -d= -f2
+```
+
+**Priority 5: Default fallback**
+If none of the above yields a port, default to `3000`.
+
+Store the result in a `PORT` variable for use in all subsequent steps.
+
+```bash
+# Combined detection (run this)
+PORT="${EXPLICIT_PORT:-}"
+if [ -z "$PORT" ]; then
+  PORT=$(grep -Eio '(port\s*[:=]\s*|localhost:)([0-9]{4,5})' CLAUDE.md 2>/dev/null | grep -Eo '[0-9]{4,5}' | head -1)
+fi
+if [ -z "$PORT" ]; then
+  PORT=$(grep -Eo '\-\-port[= ]+[0-9]{4,5}' package.json 2>/dev/null | grep -Eo '[0-9]{4,5}' | head -1)
+fi
+if [ -z "$PORT" ]; then
+  PORT=$(grep -h '^PORT=' .env .env.local .env.development 2>/dev/null | tail -1 | cut -d= -f2)
+fi
+PORT="${PORT:-3000}"
+echo "Using dev server port: $PORT"
+```
+
+</detect_port>
+
+### 5. Verify Server is Running

 <check_server>

-Before testing, verify the local server is accessible:
+Before testing, verify the local server is accessible using the detected port:

 ```bash
-agent-browser open http://localhost:3000
+agent-browser open http://localhost:${PORT}
 agent-browser snapshot -i
 ```

 If server is not running, inform user:
 ```markdown
-**Server not running**
+**Server not running on port ${PORT}**

 Please start your development server:
 - Rails: `bin/dev` or `rails server`
 - Node/Next.js: `npm run dev`
+- Custom port: `/test-browser --port <your-port>`

 Then run `/test-browser` again.
 ```

 </check_server>

-### 5. Test Each Affected Page
+### 6. Test Each Affected Page

 <test_pages>

@@ -154,13 +205,13 @@ For each affected route, use agent-browser CLI commands (NOT Chrome MCP):

 **Step 1: Navigate and capture snapshot**
 ```bash
-agent-browser open "http://localhost:3000/[route]"
+agent-browser open "http://localhost:${PORT}/[route]"
 agent-browser snapshot -i
 ```

 **Step 2: For headed mode (visual debugging)**
 ```bash
-agent-browser --headed open "http://localhost:3000/[route]"
+agent-browser --headed open "http://localhost:${PORT}/[route]"
 agent-browser --headed snapshot -i
 ```

@@ -185,7 +236,7 @@ agent-browser screenshot --full page-name-full.png  # Full page

 </test_pages>

-### 6. Human Verification (When Required)
+### 7. Human Verification (When Required)

 <human_verification>

@@ -214,7 +265,7 @@ Did it work correctly?

 </human_verification>

-### 7. Handle Failures
+### 8. Handle Failures

 <failure_handling>

@@ -253,7 +304,7 @@ When a test fails:

 </failure_handling>

-### 8. Test Summary
+### 9. Test Summary

 <test_summary>

@@ -263,7 +314,7 @@ After all tests complete, present summary:
 ## Browser Test Results

 **Test Scope:** PR #[number] / [branch name]
-**Server:** http://localhost:3000
+**Server:** http://localhost:${PORT}

 ### Pages Tested: [count]

@@ -295,7 +346,7 @@ After all tests complete, present summary:
 ## Quick Usage Examples

 ```bash
-# Test current branch changes
+# Test current branch changes (auto-detects port)
 /test-browser

 # Test specific PR
@@ -303,6 +354,9 @@ After all tests complete, present summary:

 # Test specific branch
 /test-browser feature/new-dashboard
+
+# Test on a specific port
+/test-browser --port 5000
 ```

 ## agent-browser CLI Reference
--- a/plugins/compound-engineering/skills/test-xcode/SKILL.md
+++ b/plugins/compound-engineering/skills/test-xcode/SKILL.md
@@ -323,9 +323,9 @@ mcp__xcodebuildmcp__shutdown_simulator({ simulator_id: "[uuid]" })
 /xcode-test current
 ```

-## Integration with /workflows:review
+## Integration with /ce:review

-When reviewing PRs that touch iOS code, the `/workflows:review` command can spawn this as a subagent:
+When reviewing PRs that touch iOS code, the `/ce:review` command can spawn this as a subagent:

 ```
 Task general-purpose("Run /xcode-test for scheme [name]. Build, install on simulator, test key screens, check for crashes.")
--- a/plugins/compound-engineering/skills/triage/SKILL.md
+++ b/plugins/compound-engineering/skills/triage/SKILL.md
--- a/plugins/compound-engineering/skills/workflows-brainstorm/SKILL.md
+++ b/plugins/compound-engineering/skills/workflows-brainstorm/SKILL.md
@@ -0,0 +1,10 @@
+---
+name: workflows:brainstorm
+description: "[DEPRECATED] Use /ce:brainstorm instead — renamed for clarity."
+argument-hint: "[feature idea or problem to explore]"
+disable-model-invocation: true
+---
+
+NOTE: /workflows:brainstorm is deprecated. Please use /ce:brainstorm instead. This alias will be removed in a future version.
+
+/ce:brainstorm $ARGUMENTS
--- a/plugins/compound-engineering/skills/workflows-compound/SKILL.md
+++ b/plugins/compound-engineering/skills/workflows-compound/SKILL.md
@@ -0,0 +1,10 @@
+---
+name: workflows:compound
+description: "[DEPRECATED] Use /ce:compound instead — renamed for clarity."
+argument-hint: "[optional: brief context about the fix]"
+disable-model-invocation: true
+---
+
+NOTE: /workflows:compound is deprecated. Please use /ce:compound instead. This alias will be removed in a future version.
+
+/ce:compound $ARGUMENTS
--- a/Show More
+++ b/Show More