[2.8.1] Add GitHub/Linear issue creation to /plan command

- Add "Create Issue" option to post-generation menu in /plan
- Detect project tracker from user's CLAUDE.md (project_tracker: github or linear)
- Use gh issue create for GitHub, linear CLI for Linear
- Show issue URL after creation and offer to continue to /work or /plan_review

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

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

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

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

plugins/compounding-engineering/CHANGELOG.md

@@ -5,6 +5,12 @@ All notable changes to the compounding-engineering plugin will be documented in
 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.8.1] - 2025-11-27
+
+### Added
+
+- **`/plan` command** - Added "Create Issue" option to post-generation menu. Detects project tracker (GitHub or Linear) from user's CLAUDE.md (`project_tracker: github` or `project_tracker: linear`) and creates issues using `gh issue create` or Linear CLI.
+
 ## [2.8.0] - 2025-11-27
 
 ### Added

plugins/compounding-engineering/commands/workflows/plan.md

@@ -378,16 +378,47 @@ After writing the plan file, use the **AskUserQuestion tool** to present these o
 **Options:**
 1. **Start `/work`** - Begin implementing this plan
 2. **Run `/plan_review`** - Get feedback from reviewers (DHH, Kieran, Simplicity)
-3. **Simplify** - Reduce detail level
-4. **Rework** - Change approach or request specific changes
+3. **Create Issue** - Create issue in project tracker (GitHub/Linear)
+4. **Simplify** - Reduce detail level
+5. **Rework** - Change approach or request specific changes
 
 Based on selection:
 - **`/work`** → Call the /work command with the plan file path
 - **`/plan_review`** → Call the /plan_review command with the plan file path
+- **Create Issue** → See "Issue Creation" section below
 - **Simplify** → Ask "What should I simplify?" then regenerate simpler version
 - **Rework** → Ask "What would you like changed?" then regenerate with changes
 - **Other** (automatically provided) → Accept free text, act on it
 
 Loop back to options after Simplify/Rework until user selects `/work` or `/plan_review`.
 
+## Issue Creation
+
+When user selects "Create Issue", detect their project tracker from CLAUDE.md:
+
+1. **Check for tracker preference** in user's CLAUDE.md (global or project):
+   - Look for `project_tracker: github` or `project_tracker: linear`
+   - Or look for mentions of "GitHub Issues" or "Linear" in their workflow section
+
+2. **If GitHub:**
+   ```bash
+   # Extract title from plan filename (kebab-case to Title Case)
+   # Read plan content for body
+   gh issue create --title "feat: [Plan Title]" --body-file plans/<issue_title>.md
+   ```
+
+3. **If Linear:**
+   ```bash
+   # Use linear CLI if available, or provide instructions
+   # linear issue create --title "[Plan Title]" --description "$(cat plans/<issue_title>.md)"
+   ```
+
+4. **If no tracker configured:**
+   Ask user: "Which project tracker do you use? (GitHub/Linear/Other)"
+   - Suggest adding `project_tracker: github` or `project_tracker: linear` to their CLAUDE.md
+
+5. **After creation:**
+   - Display the issue URL
+   - Ask if they want to proceed to `/work` or `/plan_review`
+
 NEVER CODE! Just research and write the plan.