[2.9.0] Rename plugin to compound-engineering

BREAKING: Plugin renamed from compounding-engineering to compound-engineering.
Users will need to reinstall with the new name:

  claude /plugin install compound-engineering

Changes:
- Renamed plugin directory and all references
- Updated documentation counts (24 agents, 19 commands)
- Added julik-frontend-races-reviewer to docs

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

.claude-plugin/marketplace.json

@@ -10,17 +10,17 @@
   },
   "plugins": [
     {
-      "name": "compounding-engineering",
-      "description": "AI-powered development tools that get smarter with every use. Make each unit of engineering work easier than the last. Includes 24 specialized agents, 16 commands, and 11 skills.",
-      "version": "2.8.0",
+      "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 24 specialized agents, 19 commands, and 11 skills.",
+      "version": "2.9.0",
       "author": {
         "name": "Kieran Klaassen",
         "url": "https://github.com/kieranklaassen",
         "email": "kieran@every.to"
       },
-      "homepage": "https://github.com/EveryInc/compounding-engineering-plugin",
-      "tags": ["ai-powered", "compounding-engineering", "workflow-automation", "code-review", "quality", "knowledge-management", "image-generation"],
-      "source": "./plugins/compounding-engineering"
+      "homepage": "https://github.com/EveryInc/compound-engineering-plugin",
+      "tags": ["ai-powered", "compound-engineering", "workflow-automation", "code-review", "quality", "knowledge-management", "image-generation"],
+      "source": "./plugins/compound-engineering"
     }
   ]
 }

.github/workflows/deploy-docs.yml

@@ -4,7 +4,7 @@ on:
   push:
     branches: [main]
     paths:
-      - 'plugins/compounding-engineering/docs/**'
+      - 'plugins/compound-engineering/docs/**'
   workflow_dispatch:
 
 permissions:
@@ -32,7 +32,7 @@ jobs:
       - name: Upload artifact
         uses: actions/upload-pages-artifact@v3
         with:
-          path: 'plugins/compounding-engineering/docs'
+          path: 'plugins/compound-engineering/docs'
 
       - name: Deploy to GitHub Pages
         id: deployment

CLAUDE.md

@@ -1,6 +1,6 @@
 # Every Marketplace - Claude Code Plugin Marketplace
 
-This repository is a Claude Code plugin marketplace that distributes the `compounding-engineering` plugin to developers building with AI-powered tools.
+This repository is a Claude Code plugin marketplace that distributes the `compound-engineering` plugin to developers building with AI-powered tools.
 
 ## Repository Structure
 
@@ -14,7 +14,7 @@ every-marketplace/
 │   ├── js/                       # JavaScript
 │   └── pages/                    # Reference pages
 └── plugins/
-    └── compounding-engineering/   # The actual plugin
+    └── compound-engineering/   # The actual plugin
         ├── .claude-plugin/
         │   └── plugin.json        # Plugin metadata
         ├── agents/                # 24 specialized AI agents
@@ -60,22 +60,22 @@ When agents, commands, or skills are added/removed, follow this checklist:
 
 ```bash
 # Count agents
-ls plugins/compounding-engineering/agents/*.md | wc -l
+ls plugins/compound-engineering/agents/*.md | wc -l
 
 # Count commands
-ls plugins/compounding-engineering/commands/*.md | wc -l
+ls plugins/compound-engineering/commands/*.md | wc -l
 
 # Count skills
-ls -d plugins/compounding-engineering/skills/*/ 2>/dev/null | wc -l
+ls -d plugins/compound-engineering/skills/*/ 2>/dev/null | wc -l
 ```
 
 #### 2. Update ALL description strings with correct counts
 
 The description appears in multiple places and must match everywhere:
 
-- [ ] `plugins/compounding-engineering/.claude-plugin/plugin.json` → `description` field
+- [ ] `plugins/compound-engineering/.claude-plugin/plugin.json` → `description` field
 - [ ] `.claude-plugin/marketplace.json` → plugin `description` field
-- [ ] `plugins/compounding-engineering/README.md` → intro paragraph
+- [ ] `plugins/compound-engineering/README.md` → intro paragraph
 
 Format: `"Includes X specialized agents, Y commands, and Z skill(s)."`
 
@@ -83,13 +83,13 @@ Format: `"Includes X specialized agents, Y commands, and Z skill(s)."`
 
 When adding new functionality, bump the version in:
 
-- [ ] `plugins/compounding-engineering/.claude-plugin/plugin.json` → `version`
+- [ ] `plugins/compound-engineering/.claude-plugin/plugin.json` → `version`
 - [ ] `.claude-plugin/marketplace.json` → plugin `version`
 
 #### 4. Update documentation
 
-- [ ] `plugins/compounding-engineering/README.md` → list all components
-- [ ] `plugins/compounding-engineering/CHANGELOG.md` → document changes
+- [ ] `plugins/compound-engineering/README.md` → list all components
+- [ ] `plugins/compound-engineering/CHANGELOG.md` → document changes
 - [ ] `CLAUDE.md` → update structure diagram if needed
 
 #### 5. Rebuild documentation site
@@ -110,15 +110,15 @@ This will:
 
 ```bash
 cat .claude-plugin/marketplace.json | jq .
-cat plugins/compounding-engineering/.claude-plugin/plugin.json | jq .
+cat plugins/compound-engineering/.claude-plugin/plugin.json | jq .
 ```
 
 #### 6. Verify before committing
 
 ```bash
 # Ensure counts in descriptions match actual files
-grep -o "Includes [0-9]* specialized agents" plugins/compounding-engineering/.claude-plugin/plugin.json
-ls plugins/compounding-engineering/agents/*.md | wc -l
+grep -o "Includes [0-9]* specialized agents" plugins/compound-engineering/.claude-plugin/plugin.json
+ls plugins/compound-engineering/agents/*.md | wc -l
 ```
 
 ### Marketplace.json Structure
@@ -267,7 +267,7 @@ python -m http.server 8000
 2. Install the plugin:
 
    ```bash
-   claude /plugin install compounding-engineering
+   claude /plugin install compound-engineering
    ```
 
 3. Test agents and commands:
@@ -282,28 +282,28 @@ Before committing, ensure JSON files are valid:
 
 ```bash
 cat .claude-plugin/marketplace.json | jq .
-cat plugins/compounding-engineering/.claude-plugin/plugin.json | jq .
+cat plugins/compound-engineering/.claude-plugin/plugin.json | jq .
 ```
 
 ## Common Tasks
 
 ### Adding a New Agent
 
-1. Create `plugins/compounding-engineering/agents/new-agent.md`
+1. Create `plugins/compound-engineering/agents/new-agent.md`
 2. Update plugin.json agent count and agent list
 3. Update README.md agent list
 4. Test with `claude agent new-agent "test"`
 
 ### Adding a New Command
 
-1. Create `plugins/compounding-engineering/commands/new-command.md`
+1. Create `plugins/compound-engineering/commands/new-command.md`
 2. Update plugin.json command count and command list
 3. Update README.md command list
 4. Test with `claude /new-command`
 
 ### Adding a New Skill
 
-1. Create skill directory: `plugins/compounding-engineering/skills/skill-name/`
+1. Create skill directory: `plugins/compound-engineering/skills/skill-name/`
 2. Add skill structure:
    ```
    skills/skill-name/
@@ -332,7 +332,7 @@ Detailed documentation...
 
 Tags should reflect the compounding engineering philosophy:
 
-- Use: `ai-powered`, `compounding-engineering`, `workflow-automation`, `knowledge-management`
+- Use: `ai-powered`, `compound-engineering`, `workflow-automation`, `knowledge-management`
 - Avoid: Framework-specific tags unless the plugin is framework-specific
 
 ## Commit Conventions

README.md

@@ -14,14 +14,14 @@ Run Claude and add the marketplace:
 Then install the plugin:
 
 ```bash
-/plugin install compounding-engineering
+/plugin install compound-engineering
 ```
 
 ### One-Command Installation
 Use the [Claude Plugins CLI](https://claude-plugins.dev) to skip the marketplace setup:
 
 ```bash
-npx claude-plugins install @EveryInc/every-marketplace/compounding-engineering
+npx claude-plugins install @EveryInc/every-marketplace/compound-engineering
 ```
 
 This automatically adds the marketplace and installs the plugin in a single step.
@@ -81,7 +81,7 @@ The plugin follows a three-step workflow that makes development compound:
 
 ### 1. Plan: Turn Ideas Into Structured Issues
 
-Use `/compounding-engineering:plan` to transform feature descriptions into comprehensive GitHub issues.
+Use `/compound-engineering:plan` to transform feature descriptions into comprehensive GitHub issues.
 
 **What it does:**
 - Researches your codebase to find similar patterns and conventions
@@ -93,7 +93,7 @@ Use `/compounding-engineering:plan` to transform feature descriptions into compr
 
 ### 2. Work: Execute Plans Systematically
 
-Use `/compounding-engineering:work` to execute work plans with isolated worktrees and systematic task tracking.
+Use `/compound-engineering:work` to execute work plans with isolated worktrees and systematic task tracking.
 
 **What it does:**
 - Creates isolated git worktrees for clean development
@@ -105,7 +105,7 @@ Use `/compounding-engineering:work` to execute work plans with isolated worktree
 
 ### 3. Review: Ensure Quality Before Merging
 
-Use `/compounding-engineering:review` to perform exhaustive multi-agent code reviews.
+Use `/compound-engineering:review` to perform exhaustive multi-agent code reviews.
 
 **What it does:**
 - Checks out your PR in an isolated worktree for deep analysis
@@ -121,7 +121,7 @@ Use `/compounding-engineering:review` to perform exhaustive multi-agent code rev
 
 ```bash
 # Create a detailed GitHub issue from a feature description
-claude /compounding-engineering:plan "Add user profile avatars with S3 upload and automatic resizing"
+claude /compound-engineering:plan "Add user profile avatars with S3 upload and automatic resizing"
 ```
 
 The command will:
@@ -139,7 +139,7 @@ You can choose detail levels:
 
 ```bash
 # Execute a plan document systematically
-claude /compounding-engineering:work path/to/plan.md
+claude /compound-engineering:work path/to/plan.md
 ```
 
 The command will:
@@ -153,13 +153,13 @@ The command will:
 
 ```bash
 # Review the latest PR
-claude /compounding-engineering:review
+claude /compound-engineering:review
 
 # Review a specific PR
-claude /compounding-engineering:review 123
+claude /compound-engineering:review 123
 
 # Review from a GitHub URL
-claude /compounding-engineering:review https://github.com/user/repo/pull/123
+claude /compound-engineering:review https://github.com/user/repo/pull/123
 ```
 
 The command will:
@@ -177,22 +177,22 @@ The command will:
 
 The plugin includes six commands for different stages of development:
 
-### `/compounding-engineering:plan [feature description]`
+### `/compound-engineering:plan [feature description]`
 Creates detailed GitHub issues from feature descriptions. Includes research, acceptance criteria, and implementation guidance.
 
-### `/compounding-engineering:work [plan file]`
+### `/compound-engineering:work [plan file]`
 Executes work plans systematically with worktrees, todos, and continuous validation.
 
-### `/compounding-engineering:review [PR number or URL]`
+### `/compound-engineering:review [PR number or URL]`
 Performs exhaustive multi-agent code reviews with security, performance, and architecture analysis.
 
-### `/compounding-engineering:triage`
+### `/compound-engineering:triage`
 Presents findings one by one for review and converts approved items into trackable todos.
 
-### `/compounding-engineering:resolve_todo_parallel`
+### `/compound-engineering:resolve_todo_parallel`
 Resolves multiple todos in parallel with systematic execution and quality checks.
 
-### `/compounding-engineering:generate_command`
+### `/compound-engineering:generate_command`
 Generates new Claude Code commands from descriptions.
 
 ## All Agents
@@ -230,17 +230,17 @@ The plugin includes 17 specialized agents that provide expertise in different ar
 
 Traditional development tools help you work faster. Compounding engineering tools make future work easier.
 
-**Every `/compounding-engineering:plan` you create:**
+**Every `/compound-engineering:plan` you create:**
 - Documents patterns that inform the next plan
 - Establishes conventions that reduce planning time
 - Builds institutional knowledge
 
-**Every `/compounding-engineering:work` execution:**
+**Every `/compound-engineering:work` execution:**
 - Creates reusable components
 - Refines your testing approach
 - Improves your development process
 
-**Every `/compounding-engineering:review` you run:**
+**Every `/compound-engineering:review` you run:**
 - Catches issues earlier
 - Documents learnings for the team
 - Raises the quality bar systematically
@@ -257,16 +257,16 @@ The plugin embodies these compounding engineering principles:
 
 **Quality compounds:** High-quality code is easier to modify. The multi-agent review system ensures every change meets your quality bar.
 
-**Systematic beats heroic:** Consistent processes beat individual heroics. The `/compounding-engineering:work` command executes plans systematically, with continuous validation.
+**Systematic beats heroic:** Consistent processes beat individual heroics. The `/compound-engineering:work` command executes plans systematically, with continuous validation.
 
 **Knowledge should be codified:** Learnings should be captured and reused. The research agents analyze your codebase to apply your own patterns back to you.
 
 ## Getting Started
 
 1. Install the plugin using one of the methods above
-2. Run `/compounding-engineering:plan` on your next feature idea
-3. Use `/compounding-engineering:work` to execute the plan
-4. Run `/compounding-engineering:review` before merging
+2. Run `/compound-engineering:plan` on your next feature idea
+3. Use `/compound-engineering:work` to execute the plan
+4. Run `/compound-engineering:review` before merging
 5. Repeat, and watch your development process compound
 
 Each cycle makes the next cycle easier. That's compounding engineering.

docs/index.html

@@ -4,7 +4,7 @@
 <head>
   <meta charset="utf-8" />
   <title>Compounding Engineering - AI-Powered Development Tools for Claude Code</title>
-  <meta content="Your code reviews just got 12 expert opinions in 30 seconds. 23 specialized agents, 18 workflow commands, and 11 skills that make today's work easier than yesterday's." name="description" />
+  <meta content="Your code reviews just got 12 expert opinions in 30 seconds. 24 specialized agents, 19 workflow commands, and 11 skills that make today's work easier than yesterday's." name="description" />
   <meta content="width=device-width, initial-scale=1" name="viewport" />
 
   <!-- Open Graph -->
@@ -12,7 +12,7 @@
   <meta property="og:site_name" content="Compounding Engineering" />
   <meta property="og:locale" content="en_US" />
   <meta property="og:title" content="Compounding Engineering - AI Development Tools" />
-  <meta property="og:description" content="Get 12 expert code reviews in 30 seconds. 23 specialized agents that make today's work easier than yesterday's." />
+  <meta property="og:description" content="Get 12 expert code reviews in 30 seconds. 24 specialized agents that make today's work easier than yesterday's." />
   <meta name="twitter:card" content="summary_large_image" />
   <meta name="twitter:title" content="Compounding Engineering" />
   <meta name="twitter:description" content="12 expert code reviews in 30 seconds. Make today's work easier than yesterday's." />
@@ -161,7 +161,7 @@
             Your Code Reviews Just Got 12 Expert Opinions. In 30 Seconds.
           </h1>
           <p class="paragraph m secondary balanced" style="margin-bottom: 32px;">
-            Here's what happened when we shipped yesterday: security audit, performance analysis, architectural review, pattern detection, and eight more specialized checks—all running in parallel. No meetings. No waiting. Just answers. That's compounding engineering: 23 specialized agents, 18 workflow commands, and 11 skills that make today's work easier than yesterday's.
+            Here's what happened when we shipped yesterday: security audit, performance analysis, architectural review, pattern detection, and eight more specialized checks—all running in parallel. No meetings. No waiting. Just answers. That's compounding engineering: 24 specialized agents, 19 workflow commands, and 11 skills that make today's work easier than yesterday's.
           </p>
           <div class="button-group margin-paragraph centered">
             <a href="#install" class="button primary">
@@ -179,12 +179,12 @@
         <div class="stats-container">
           <div class="stat-card">
             <div class="stat-icon"><i class="fa-solid fa-users-gear"></i></div>
-            <div class="stat-number">23</div>
+            <div class="stat-number">24</div>
             <div class="stat-label">Specialized Agents</div>
           </div>
           <div class="stat-card">
             <div class="stat-icon"><i class="fa-solid fa-terminal"></i></div>
-            <div class="stat-number">18</div>
+            <div class="stat-number">19</div>
             <div class="stat-label">Slash Commands</div>
           </div>
           <div class="stat-card">
@@ -244,7 +244,7 @@
                 The <code>security-sentinel</code> has checked 10,000 PRs for SQL injection. The <code>kieran-rails-reviewer</code> never approves a controller with business logic. They don't get tired, don't skip Friday afternoon reviews, don't forget the conventions you agreed on in March. Run <code>/work</code> and watch your plan execute with quality gates that actually enforce your standards—every single time.
               </p>
               <div class="pillar-tools">
-                <span class="tool-tag">23 specialized agents</span>
+                <span class="tool-tag">24 specialized agents</span>
                 <span class="tool-tag">/work</span>
                 <span class="tool-tag">dhh-ruby-style skill</span>
                 <span class="tool-tag">git-worktree skill</span>
@@ -292,7 +292,7 @@
       <section id="agents">
         <div class="heading">
           <h2 class="no-top-margin">
-            <i class="fa-solid fa-users-gear color-accent"></i> 23 Specialized Agents
+            <i class="fa-solid fa-users-gear color-accent"></i> 24 Specialized Agents
           </h2>
           <p class="paragraph m secondary">
             Think of them as coworkers who never quit. The security-sentinel has seen every SQL injection variant. The kieran-rails-reviewer enforces conventions with zero compromise. The performance-oracle spots N+1 queries while you're still reading the PR. Run them solo or launch twelve in parallel—your choice.
@@ -301,7 +301,7 @@
 
         <!-- Review Agents -->
         <div class="agent-category">
-          <h3><i class="fa-solid fa-code-pull-request"></i> Review Agents (10)</h3>
+          <h3><i class="fa-solid fa-code-pull-request"></i> Review Agents (11)</h3>
           <div class="grid columns-2">
             <div class="agent-card">
               <div class="agent-header">
@@ -383,6 +383,14 @@
               <p class="agent-description">Final pass for simplicity and minimalism. Remove unnecessary complexity, improve readability.</p>
               <code class="agent-usage">claude agent code-simplicity-reviewer</code>
             </div>
+            <div class="agent-card">
+              <div class="agent-header">
+                <span class="agent-name">julik-frontend-races-reviewer</span>
+                <span class="agent-badge">JavaScript</span>
+              </div>
+              <p class="agent-description">Review JavaScript and Stimulus code for race conditions, DOM event handling, promise management, and timer cleanup.</p>
+              <code class="agent-usage">claude agent julik-frontend-races-reviewer</code>
+            </div>
           </div>
         </div>
 
@@ -523,7 +531,7 @@
       <section id="commands">
         <div class="heading">
           <h2 class="no-top-margin">
-            <i class="fa-solid fa-terminal color-accent"></i> 18 Powerful Commands
+            <i class="fa-solid fa-terminal color-accent"></i> 19 Powerful Commands
           </h2>
           <p class="paragraph m secondary">
             Slash commands that replace entire workflows. <code>/review</code> is your code review committee. <code>/plan</code> is your research team. <code>/triage</code> sorts 50 todos in the time it takes you to read five. Each one automates hours of work into a single line.
@@ -885,7 +893,7 @@
             <div class="step-content">
               <h3>Install the Plugin</h3>
               <div class="card-code-block">
-                <pre><code>claude /plugin install compounding-engineering</code></pre>
+                <pre><code>claude /plugin install compound-engineering</code></pre>
               </div>
             </div>
           </div>
@@ -981,7 +989,7 @@ skill: gemini-imagegen</code></pre>
           <span class="cta-badge"><i class="fa-solid fa-bolt"></i> Free & Open Source</span>
           <h2>Install Once. Compound Forever.</h2>
           <p class="paragraph m cta-subheading">
-            <strong>Your next code review takes 30 seconds.</strong> The one after that? Even faster. That's compounding. Get 23 expert agents, 18 workflow commands, and 11 specialized skills working for you right now.
+            <strong>Your next code review takes 30 seconds.</strong> The one after that? Even faster. That's compounding. Get 24 expert agents, 19 workflow commands, and 11 specialized skills working for you right now.
           </p>
           <div class="button-group margin-paragraph centered">
             <a href="#install" class="button primary cta-primary">

docs/pages/changelog.html

@@ -81,7 +81,7 @@
       <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 compounding-engineering plugin. This project follows
+          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>
@@ -116,7 +116,7 @@
             <ul>
               <li>
                 <strong><code>/report-bug</code> command</strong> - New slash command for reporting bugs in the
-                compounding-engineering plugin. Provides a structured workflow that gathers bug information
+                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/every-marketplace repository.
               </li>
@@ -428,7 +428,7 @@
           </div>
 
           <p class="version-description">
-            Initial release of the compounding-engineering plugin.
+            Initial release of the compound-engineering plugin.
           </p>
 
           <div class="changelog-category added">

docs/pages/getting-started.html

@@ -103,7 +103,7 @@
           <h3>Step 2: Install the Plugin</h3>
           <p>Now grab the plugin itself:</p>
           <div class="card-code-block">
-            <pre><code>claude /plugin install compounding-engineering</code></pre>
+            <pre><code>claude /plugin install compound-engineering</code></pre>
           </div>
 
           <h3>Step 3: Verify Installation</h3>
@@ -111,7 +111,7 @@
           <div class="card-code-block">
             <pre><code>claude /plugin list</code></pre>
           </div>
-          <p>You'll see <code>compounding-engineering</code> in the list. If you do, you're ready.</p>
+          <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>

docs/solutions/plugin-versioning-requirements.md

@@ -11,7 +11,7 @@ component: plugin-development
 
 ## Problem
 
-When making changes to the compounding-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.
+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.
 
 ## Solution
 
@@ -36,7 +36,7 @@ When making changes to the compounding-engineering plugin, documentation can get
 ## Checklist for Plugin Changes
 
 ```markdown
-Before committing changes to compounding-engineering plugin:
+Before committing changes to compound-engineering plugin:
 
 - [ ] Version bumped in `.claude-plugin/plugin.json`
 - [ ] CHANGELOG.md updated with changes
@@ -72,6 +72,6 @@ This documentation serves as a reminder. When Claude Code works on this plugin,
 
 ## Related Files
 
-- `/Users/kieranklaassen/every-marketplace/plugins/compounding-engineering/.claude-plugin/plugin.json`
-- `/Users/kieranklaassen/every-marketplace/plugins/compounding-engineering/CHANGELOG.md`
-- `/Users/kieranklaassen/every-marketplace/plugins/compounding-engineering/README.md`
+- `/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`

plans/grow-your-own-garden-plugin-architecture.md

@@ -1,6 +1,6 @@
 # Grow Your Own Garden: Adaptive Agent Ecosystem
 
-> **Issue:** https://github.com/EveryInc/compounding-engineering-plugin/issues/20
+> **Issue:** https://github.com/EveryInc/compound-engineering-plugin/issues/20
 
 ## The Idea
 
@@ -58,7 +58,7 @@ plugin/agents/        → From installed plugins
 
 ### Phase 1: Split the Plugin
 - Create `agent-library/` with framework-specific agents (Rails, Python, TypeScript, Frontend)
-- Keep `compounding-engineering` as core with universal agents
+- Keep `compound-engineering` as core with universal agents
 - No breaking changes—existing users unaffected
 
 ### Phase 2: Agent Discovery

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

@@ -1,7 +1,7 @@
 {
-  "name": "compounding-engineering",
-  "version": "2.8.3",
-  "description": "AI-powered development tools. 24 agents, 16 commands, 11 skills, 2 MCP servers for code review, research, design, and workflow automation.",
+  "name": "compound-engineering",
+  "version": "2.9.0",
+  "description": "AI-powered development tools. 24 agents, 19 commands, 11 skills, 2 MCP servers for code review, research, design, and workflow automation.",
   "author": {
     "name": "Kieran Klaassen",
     "email": "kieran@every.to",
@@ -12,7 +12,7 @@
   "license": "MIT",
   "keywords": [
     "ai-powered",
-    "compounding-engineering",
+    "compound-engineering",
     "workflow-automation",
     "code-review",
     "rails",

plugins/compound-engineering/CHANGELOG.md

@@ -1,10 +1,20 @@
 # Changelog
 
-All notable changes to the compounding-engineering plugin will be documented in this file.
+All notable changes to the compound-engineering plugin will be documented in this file.
 
 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.9.0] - 2025-12-02
+
+### Changed
+
+- **Plugin renamed** from `compounding-engineering` to `compound-engineering`. Shorter name, same philosophy. Users will need to reinstall with the new name.
+
+### Fixed
+
+- **Documentation counts** - Updated all documentation to reflect actual component counts (24 agents, 19 commands).
+
 ## [2.8.3] - 2025-11-29
 
 ### Fixed
@@ -63,7 +73,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Added
 
-- **`/report-bug` command** - New slash command for reporting bugs in the compounding-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/every-marketplace repository. Designed to be user-friendly for anyone using the plugin.
+- **`/report-bug` command** - 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/every-marketplace repository. Designed to be user-friendly for anyone using the plugin.
 
 ## [2.4.1] - 2024-11-24
 
@@ -209,7 +219,7 @@ Major reorganization consolidating agents, commands, and skills from multiple so
 
 ## [1.0.0] - 2024-10-09
 
-Initial release of the compounding-engineering plugin.
+Initial release of the compound-engineering plugin.
 
 ### Added
 

plugins/compound-engineering/README.md

@@ -6,8 +6,8 @@ AI-powered development tools that get smarter with every use. Make each unit of
 
 | Component | Count |
 |-----------|-------|
-| Agents | 23 |
-| Commands | 16 |
+| Agents | 24 |
+| Commands | 19 |
 | Skills | 11 |
 | MCP Servers | 2 |
 
@@ -15,7 +15,7 @@ AI-powered development tools that get smarter with every use. Make each unit of
 
 Agents are organized into categories for easier discovery.
 
-### Review (10)
+### Review (11)
 
 | Agent | Description |
 |-------|-------------|
@@ -29,6 +29,7 @@ Agents are organized into categories for easier discovery.
 | `pattern-recognition-specialist` | Analyze code for patterns and anti-patterns |
 | `performance-oracle` | Performance analysis and optimization |
 | `security-sentinel` | Security audits and vulnerability assessments |
+| `julik-frontend-races-reviewer` | Review JavaScript/Stimulus code for race conditions |
 
 ### Research (4)
 
@@ -86,7 +87,7 @@ Core workflow commands (use the short form for autocomplete):
 | `/heal-skill` | Fix skill documentation issues |
 | `/plan_review` | Multi-agent plan review in parallel |
 | `/prime` | Prime/setup command |
-| `/report-bug` | Report a bug in the compounding-engineering plugin |
+| `/report-bug` | Report a bug in the compound-engineering plugin |
 | `/reproduce-bug` | Reproduce bugs using logs and console |
 | `/resolve_parallel` | Resolve TODO comments in parallel |
 | `/resolve_pr_parallel` | Resolve PR comments in parallel |
@@ -161,7 +162,7 @@ MCP servers start automatically when the plugin is enabled.
 ## Installation
 
 ```bash
-claude /plugin install compounding-engineering
+claude /plugin install compound-engineering
 ```
 
 ## Known Issues

plugins/compound-engineering/commands/deploy-docs.md

@@ -13,17 +13,17 @@ Run these checks:
 
 ```bash
 # Count components
-echo "Agents: $(ls plugins/compounding-engineering/agents/*.md | wc -l)"
-echo "Commands: $(ls plugins/compounding-engineering/commands/*.md | wc -l)"
-echo "Skills: $(ls -d plugins/compounding-engineering/skills/*/ 2>/dev/null | wc -l)"
+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
 cat .claude-plugin/marketplace.json | jq . > /dev/null && echo "✓ marketplace.json valid"
-cat plugins/compounding-engineering/.claude-plugin/plugin.json | jq . > /dev/null && echo "✓ plugin.json valid"
+cat plugins/compound-engineering/.claude-plugin/plugin.json | jq . > /dev/null && echo "✓ plugin.json valid"
 
 # Check all HTML files exist
 for page in index agents commands skills mcp-servers changelog getting-started; do
-  if [ -f "plugins/compounding-engineering/docs/pages/${page}.html" ] || [ -f "plugins/compounding-engineering/docs/${page}.html" ]; then
+  if [ -f "plugins/compound-engineering/docs/pages/${page}.html" ] || [ -f "plugins/compound-engineering/docs/${page}.html" ]; then
     echo "✓ ${page}.html exists"
   else
     echo "✗ ${page}.html MISSING"
@@ -34,7 +34,7 @@ done
 ## Step 2: Check for Uncommitted Changes
 
 ```bash
-git status --porcelain plugins/compounding-engineering/docs/
+git status --porcelain plugins/compound-engineering/docs/
 ```
 
 If there are uncommitted changes, warn the user to commit first.
@@ -66,7 +66,7 @@ on:
   push:
     branches: [main]
     paths:
-      - 'plugins/compounding-engineering/docs/**'
+      - 'plugins/compound-engineering/docs/**'
   workflow_dispatch:
 
 permissions:
@@ -89,7 +89,7 @@ jobs:
       - uses: actions/configure-pages@v4
       - uses: actions/upload-pages-artifact@v3
         with:
-          path: 'plugins/compounding-engineering/docs'
+          path: 'plugins/compound-engineering/docs'
       - uses: actions/deploy-pages@v4
 ```
 

plugins/compound-engineering/commands/release-docs.md

@@ -6,7 +6,7 @@ argument-hint: "[optional: --dry-run to preview changes without writing]"
 
 # Release Documentation Command
 
-You are a documentation generator for the compounding-engineering plugin. Your job is to ensure the documentation site at `plugins/compounding-engineering/docs/` is always up-to-date with the actual plugin components.
+You are a documentation generator for the compound-engineering plugin. Your job is to ensure the documentation site at `plugins/compound-engineering/docs/` is always up-to-date with the actual plugin components.
 
 ## Overview
 
@@ -23,38 +23,38 @@ First, count and list all current components:
 
 ```bash
 # Count agents
-ls plugins/compounding-engineering/agents/*.md | wc -l
+ls plugins/compound-engineering/agents/*.md | wc -l
 
 # Count commands
-ls plugins/compounding-engineering/commands/*.md | wc -l
+ls plugins/compound-engineering/commands/*.md | wc -l
 
 # Count skills
-ls -d plugins/compounding-engineering/skills/*/ 2>/dev/null | wc -l
+ls -d plugins/compound-engineering/skills/*/ 2>/dev/null | wc -l
 
 # Count MCP servers
-ls -d plugins/compounding-engineering/mcp-servers/*/ 2>/dev/null | wc -l
+ls -d plugins/compound-engineering/mcp-servers/*/ 2>/dev/null | wc -l
 ```
 
 Read all component files to get their metadata:
 
 ### Agents
-For each agent file in `plugins/compounding-engineering/agents/*.md`:
+For each agent file in `plugins/compound-engineering/agents/*.md`:
 - Extract the frontmatter (name, description)
 - Note the category (Review, Research, Workflow, Design, Docs)
 - Get key responsibilities from the content
 
 ### Commands
-For each command file in `plugins/compounding-engineering/commands/*.md`:
+For each command file in `plugins/compound-engineering/commands/*.md`:
 - Extract the frontmatter (name, description, argument-hint)
 - Categorize as Workflow or Utility command
 
 ### Skills
-For each skill directory in `plugins/compounding-engineering/skills/*/`:
+For each skill directory in `plugins/compound-engineering/skills/*/`:
 - Read the SKILL.md file for frontmatter (name, description)
 - Note any scripts or supporting files
 
 ### MCP Servers
-For each MCP server in `plugins/compounding-engineering/mcp-servers/*/`:
+For each MCP server in `plugins/compound-engineering/mcp-servers/*/`:
 - Read the configuration and README
 - List the tools provided
 
@@ -117,7 +117,7 @@ Regenerate the MCP servers reference page:
 
 Ensure counts are consistent across:
 
-1. **`plugins/compounding-engineering/.claude-plugin/plugin.json`**
+1. **`plugins/compound-engineering/.claude-plugin/plugin.json`**
    - Update `description` with correct counts
    - Update `components` object with counts
    - Update `agents`, `commands` arrays with current items
@@ -125,7 +125,7 @@ Ensure counts are consistent across:
 2. **`.claude-plugin/marketplace.json`**
    - Update plugin `description` with correct counts
 
-3. **`plugins/compounding-engineering/README.md`**
+3. **`plugins/compound-engineering/README.md`**
    - Update intro paragraph with counts
    - Update component lists
 
@@ -136,14 +136,14 @@ Run validation checks:
 ```bash
 # Validate JSON files
 cat .claude-plugin/marketplace.json | jq .
-cat plugins/compounding-engineering/.claude-plugin/plugin.json | jq .
+cat plugins/compound-engineering/.claude-plugin/plugin.json | jq .
 
 # Verify counts match
-echo "Agents in files: $(ls plugins/compounding-engineering/agents/*.md | wc -l)"
-grep -o "[0-9]* specialized agents" plugins/compounding-engineering/docs/index.html
+echo "Agents in files: $(ls plugins/compound-engineering/agents/*.md | wc -l)"
+grep -o "[0-9]* specialized agents" plugins/compound-engineering/docs/index.html
 
-echo "Commands in files: $(ls plugins/compounding-engineering/commands/*.md | wc -l)"
-grep -o "[0-9]* slash commands" plugins/compounding-engineering/docs/index.html
+echo "Commands in files: $(ls plugins/compound-engineering/commands/*.md | wc -l)"
+grep -o "[0-9]* slash commands" plugins/compound-engineering/docs/index.html
 ```
 
 ## Step 5: Report Changes

plugins/compound-engineering/commands/report-bug.md

@@ -1,12 +1,12 @@
 ---
 name: report-bug
-description: Report a bug in the compounding-engineering plugin
+description: Report a bug in the compound-engineering plugin
 argument-hint: "[optional: brief description of the bug]"
 ---
 
 # Report a Compounding Engineering Plugin Bug
 
-Report bugs encountered while using the compounding-engineering plugin. This command gathers structured information and creates a GitHub issue for the maintainer.
+Report bugs encountered while using the compound-engineering plugin. This command gathers structured information and creates a GitHub issue for the maintainer.
 
 ## Step 1: Gather Bug Information
 
@@ -41,7 +41,7 @@ Use the AskUserQuestion tool to collect the following information:
 Automatically gather:
 ```bash
 # Get plugin version
-cat ~/.claude/plugins/installed_plugins.json 2>/dev/null | grep -A5 "compounding-engineering" | head -10 || echo "Plugin info not found"
+cat ~/.claude/plugins/installed_plugins.json 2>/dev/null | grep -A5 "compound-engineering" | head -10 || echo "Plugin info not found"
 
 # Get Claude Code version
 claude --version 2>/dev/null || echo "Claude CLI version unknown"
@@ -101,16 +101,16 @@ Use the GitHub CLI to create the issue:
 ```bash
 gh issue create \
   --repo EveryInc/every-marketplace \
-  --title "[compounding-engineering] Bug: [Brief description]" \
+  --title "[compound-engineering] Bug: [Brief description]" \
   --body "[Formatted bug report from Step 3]" \
-  --label "bug,compounding-engineering"
+  --label "bug,compound-engineering"
 ```
 
 **Note:** If labels don't exist, create without labels:
 ```bash
 gh issue create \
   --repo EveryInc/every-marketplace \
-  --title "[compounding-engineering] Bug: [Brief description]" \
+  --title "[compound-engineering] Bug: [Brief description]" \
   --body "[Formatted bug report]"
 ```
 
@@ -127,9 +127,9 @@ After the issue is created:
 ✅ Bug report submitted successfully!
 
 Issue: https://github.com/EveryInc/every-marketplace/issues/[NUMBER]
-Title: [compounding-engineering] Bug: [description]
+Title: [compound-engineering] Bug: [description]
 
-Thank you for helping improve the compounding-engineering plugin!
+Thank you for helping improve the compound-engineering plugin!
 The maintainer will review your report and respond as soon as possible.
 ```