feat: add OpenCode/Codex outputs and update changelog (#104)

* Add OpenCode converter coverage and specs

* Add Codex target support and spec docs

* Generate Codex command skills and refresh spec docs

* Add global Codex install path

* fix: harden plugin path loading and codex descriptions

* feat: ensure codex agents block on convert/install

* docs: clarify target branch usage for review

* chore: prep npm package metadata and release notes

* docs: mention opencode and codex in changelog

* docs: update CLI usage and remove stale todos

* feat: install from GitHub with global outputs

plugins/compound-engineering/CHANGELOG.md

@@ -5,6 +5,34 @@ 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.28.0] - 2026-01-21
+
+### Added
+
+- **`/workflows:brainstorm` command** - Guided ideation flow to expand options quickly (#101)
+
+### Changed
+
+- **`/workflows:plan` command** - Smarter research decision logic before deep dives (#100)
+- **Research checks** - Mandatory API deprecation validation in research flows (#102)
+- **Docs** - Call out experimental OpenCode/Codex providers and install defaults
+- **CLI defaults** - `install` pulls from GitHub by default and writes OpenCode/Codex output to global locations
+
+### Merged PRs
+
+- [#102](https://github.com/EveryInc/compound-engineering-plugin/pull/102) feat(research): add mandatory API deprecation validation
+- [#101](https://github.com/EveryInc/compound-engineering-plugin/pull/101) feat: Add /workflows:brainstorm command and skill
+- [#100](https://github.com/EveryInc/compound-engineering-plugin/pull/100) feat(workflows:plan): Add smart research decision logic
+
+### Contributors
+
+Huge thanks to the community contributors who made this release possible! 🙌
+
+- **[@tmchow](https://github.com/tmchow)** - Brainstorm workflow, research decision logic (2 PRs)
+- **[@jaredmorgenstern](https://github.com/jaredmorgenstern)** - API deprecation validation
+
+---
+
 ## [2.27.0] - 2026-01-20
 
 ### Added

plugins/compound-engineering/commands/workflows/review.md

@@ -37,8 +37,8 @@ First, I need to determine the review target type and set up the code for analys
 
 - [ ] Determine review type: PR number (numeric), GitHub URL, file path (.md), or empty (current branch)
 - [ ] Check current git branch
-- [ ] If ALREADY on the PR branch → proceed with analysis on current branch
-- [ ] If DIFFERENT branch → offer to use worktree: "Use git-worktree skill for isolated Call `skill: git-worktree` with branch name
+- [ ] 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

plugins/compound-engineering/skills/git-worktree/SKILL.md

@@ -38,7 +38,7 @@ 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 PR branch, offer worktree for isolated review
+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
 3. **Parallel Development**: When working on multiple features simultaneously
 4. **Cleanup**: After completing work in a worktree
@@ -210,8 +210,8 @@ Instead of always creating a worktree:
 
 ```
 1. Check current branch
-2. If ALREADY on PR branch → stay there, no worktree needed
-3. If DIFFERENT branch → offer worktree:
+2. If ALREADY on target branch (PR branch or requested branch) → stay there, no worktree needed
+3. If DIFFERENT branch than the review target → offer worktree:
    "Use worktree for isolated review? (y/n)"
    - yes → call git-worktree skill
    - no → proceed with PR diff on current branch