[2.9.3] Add "Open plan in editor" option to /plan command

- Added "Open plan in editor" as the first option in post-generation menu
- Opens plan file in user's default editor for review before next steps
- Reordered options: open → review → work → work remote → create issue → simplify

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

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
Kieran Klaassen
2025-12-05 19:43:07 -08:00
parent 6ed1aae8f1
commit 5febbf11d4
3 changed files with 14 additions and 6 deletions

View File

@@ -1,6 +1,6 @@
{ {
"name": "compound-engineering", "name": "compound-engineering",
"version": "2.9.2", "version": "2.9.3",
"description": "AI-powered development tools. 24 agents, 19 commands, 11 skills, 2 MCP servers for code review, research, design, and workflow automation.", "description": "AI-powered development tools. 24 agents, 19 commands, 11 skills, 2 MCP servers for code review, research, design, and workflow automation.",
"author": { "author": {
"name": "Kieran Klaassen", "name": "Kieran Klaassen",

View File

@@ -5,6 +5,12 @@ 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/), 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). and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
## [2.9.3] - 2025-12-05
### Changed
- **`/plan` command** - Added "Open plan in editor" as the first option in post-generation menu. This opens the plan file in the user's default editor for review before deciding on next steps.
## [2.9.2] - 2025-12-04 ## [2.9.2] - 2025-12-04
### Added ### Added

View File

@@ -376,13 +376,15 @@ After writing the plan file, use the **AskUserQuestion tool** to present these o
**Question:** "Plan ready at `plans/<issue_title>.md`. What would you like to do next?" **Question:** "Plan ready at `plans/<issue_title>.md`. What would you like to do next?"
**Options:** **Options:**
1. **Run `/plan_review`** - Get feedback from reviewers (DHH, Kieran, Simplicity) 1. **Open plan in editor** - Open the plan file for review
2. **Start `/work`** - Begin implementing this plan locally 2. **Run `/plan_review`** - Get feedback from reviewers (DHH, Kieran, Simplicity)
3. **Start `/work` on remote** - Begin implementing in Claude Code on the web (use `&` to run in background) 3. **Start `/work`** - Begin implementing this plan locally
4. **Create Issue** - Create issue in project tracker (GitHub/Linear) 4. **Start `/work` on remote** - Begin implementing in Claude Code on the web (use `&` to run in background)
5. **Simplify** - Reduce detail level 5. **Create Issue** - Create issue in project tracker (GitHub/Linear)
6. **Simplify** - Reduce detail level
Based on selection: Based on selection:
- **Open plan in editor** → Run `open plans/<issue_title>.md` to open the file in the user's default editor
- **`/plan_review`** → Call the /plan_review command with the plan file path - **`/plan_review`** → Call the /plan_review command with the plan file path
- **`/work`** → Call the /work command with the plan file path - **`/work`** → Call the /work command with the plan file path
- **`/work` on remote** → Run `/work plans/<issue_title>.md &` to start work in background for Claude Code web - **`/work` on remote** → Run `/work plans/<issue_title>.md &` to start work in background for Claude Code web