@every-env/compound-plugin 2.36.0 → 2.36.2

package/.claude-plugin/marketplace.json

@@ -11,8 +11,8 @@
   "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 28 specialized agents, 22 commands, and 20 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 28 specialized agents and 47 skills.",
+      "version": "2.40.0",
       "author": {
         "name": "Kieran Klaassen",
         "url": "https://github.com/kieranklaassen",

package/CHANGELOG.md

@@ -7,6 +7,20 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 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.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)
 
 

package/README.md

@@ -158,17 +158,20 @@ Notes:
 ## Workflow
 
 ```
-Plan → Work → Review → Compound → Repeat
+Brainstorm → Plan → Work → Review → Compound → Repeat
 ```
 
 | Command | Purpose |
 |---------|---------|
+| `/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
 

package/package.json

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

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

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

package/plugins/compound-engineering/CLAUDE.md

@@ -34,15 +34,16 @@ agents/
 ├── workflow/   # Workflow automation agents
 └── docs/       # Documentation agents
 
-commands/
-├── ce/         # Core workflow commands (ce:plan, ce:review, etc.)
-├── workflows/  # Deprecated aliases for ce:* commands
-└── *.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 `ce:` prefix to unambiguously identify them as compound-engineering commands:

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

package/plugins/compound-engineering/{commands/ce/plan.md → skills/ce-plan/SKILL.md}

@@ -579,17 +579,15 @@ After writing the plan file, use the **AskUserQuestion tool** to present these o
 **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. **Run `/technical_review`** - Technical feedback from code-focused reviewers (DHH, Kieran, Simplicity)
-4. **Review and refine** - Improve the document through structured self-review
-5. **Share to Proof** - Upload to Proof for collaborative review and sharing
-6. **Start `/ce:work`** - Begin implementing this plan locally
-7. **Start `/ce:work` on remote** - Begin implementing in Claude Code on the web (use `&` to run in background)
-8. **Create Issue** - Create issue in project tracker (GitHub/Linear)
+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
-- **`/technical_review`** → Call the /technical_review command with the plan file path
 - **Review and refine** → Load `document-review` skill.
 - **Share to Proof** → Upload the plan to Proof:
   ```bash
@@ -608,7 +606,7 @@ Based on selection:
 
 **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 `/technical_review`.
+Loop back to options after Simplify or Other changes until user selects `/ce:work` or another action.
 
 ## Issue Creation
 
@@ -638,6 +636,6 @@ When user selects "Create Issue", detect their project tracker from CLAUDE.md:
 
 5. **After creation:**
    - Display the issue URL
-   - Ask if they want to proceed to `/ce:work` or `/technical_review`
+   - Ask if they want to proceed to `/ce:work`
 
 NEVER CODE! Just research and write the plan.

package/plugins/compound-engineering/{commands/deepen-plan.md → skills/deepen-plan/SKILL.md}

@@ -480,14 +480,12 @@ 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 `/ce: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
 - **`/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

package/plugins/compound-engineering/{commands/deploy-docs.md → 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

package/plugins/compound-engineering/{commands/generate_command.md → 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
 

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

package/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/compound-engineering-plugin/docs/index.html`
-- Style CSS: `/Users/kieranklaassen/compound-engineering-plugin/docs/css/style.css`