@every-env/compound-plugin 0.9.0 → 0.12.0

package/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)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@every-env/compound-plugin",
-  "version": "0.9.0",
+  "version": "0.12.0",
   "type": "module",
   "private": false,
   "bin": {

package/plans/landing-page-launchkit-refresh.md

@@ -275,5 +275,5 @@ Review and enhance the `/docs/index.html` landing page using LaunchKit elements
 
 - 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`
+- Current Landing Page: `/Users/kieranklaassen/compound-engineering-plugin/docs/index.html`
+- Style CSS: `/Users/kieranklaassen/compound-engineering-plugin/docs/css/style.css`

package/plugins/compound-engineering/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "compound-engineering",
-  "version": "2.35.0",
-  "description": "AI-powered development tools. 29 agents, 22 commands, 19 skills, 1 MCP server for code review, research, design, and workflow automation.",
+  "version": "2.38.0",
+  "description": "AI-powered development tools. 29 agents, 22 commands, 20 skills, 1 MCP server for code review, research, design, and workflow automation.",
   "author": {
     "name": "Kieran Klaassen",
     "email": "kieran@every.to",

package/plugins/compound-engineering/CHANGELOG.md

@@ -5,6 +5,77 @@ 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).
 
+## [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
+
+- **`/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.
+
+---
+
+## [2.35.1] - 2026-02-18
+
+### Changed
+
+- **`/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
@@ -83,7 +154,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

package/plugins/compound-engineering/CLAUDE.md

@@ -35,7 +35,8 @@ agents/
 └── docs/       # Documentation agents
 
 commands/
-├── workflows/  # Core workflow commands (workflows:plan, workflows:review, etc.)
+├── ce/         # Core workflow commands (ce:plan, ce:review, etc.)
+├── workflows/  # Deprecated aliases for ce:* commands
 └── *.md        # Utility commands
 
 skills/
@@ -44,13 +45,14 @@ skills/
 
 ## 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
 

package/plugins/compound-engineering/README.md

@@ -8,7 +8,7 @@ AI-powered development tools that get smarter with every use. Make each unit of
 |-----------|-------|
 | Agents | 29 |
 | Commands | 22 |
-| Skills | 19 |
+| Skills | 20 |
 | MCP Servers | 1 |
 
 ## Agents
@@ -73,15 +73,17 @@ Agents are organized into categories for easier discovery.
 
 ### 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
 
@@ -134,6 +136,7 @@ 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 |
+| `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 |
 

package/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.

package/plugins/compound-engineering/agents/research/learnings-researcher.md

@@ -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