fix(ai-workflow): Stop plan-phases from auto-implementing and fix implement-phases plan reading

- Add explicit Instructions and Important sections to workflow-plan-phases to stop after planning
- Add plan-only enforcement to plan-phases SKILL.md
- Fix workflow-implement-phases to read plan file argument and auto-discover plans in docs/plans/
- Update all command references from /plan-phases to /workflow-plan-phases format in README
- Bump ai-workflow to v1.0.2 and marketplace to v1.6.2

Author: charlesjones-dev

.claude-plugin/marketplace.json

@@ -6,7 +6,7 @@
   },
   "metadata": {
     "description": "A curated list of custom Claude Code plugins, agents, and skills for developers.",
-    "version": "1.6.1",
+    "version": "1.6.2",
     "pluginRoot": "./plugins"
   },
   "plugins": [
@@ -142,7 +142,7 @@
       "name": "ai-workflow",
       "source": "./plugins/ai-workflow",
       "description": "AI-powered development workflow automation - Phase-based planning, implementation orchestration, and preflight code quality checks for efficient sub-agent execution",
-      "version": "1.0.1",
+      "version": "1.0.2",
       "keywords": [
         "ai",
         "workflow",

CHANGELOG.md

@@ -7,6 +7,24 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [1.6.2] - 2025-12-12
+
+### Fixed
+
+#### AI-Workflow Plugin (v1.0.2)
+
+- **Fixed `/workflow-plan-phases` proceeding to implementation after creating plan**
+  - Added explicit "Instructions" section with step-by-step workflow
+  - Added "Important" section emphasizing planning-only scope
+  - Command now stops after presenting the plan and directs users to `/workflow-implement-phases` for execution
+  - Updated skill file with "IMPORTANT: Planning Only — Do Not Implement" section
+
+- **Fixed `/workflow-implement-phases` not reading the plan file argument**
+  - Added explicit "Instructions" section telling Claude to read the plan file
+  - Added automatic plan discovery: if no file provided, searches `docs/plans/` and lets user pick
+  - Plan file argument is now optional (defaults to searching `docs/plans/`)
+  - Updated workflow step 1 to explicitly use Read tool for plan document
+
 ## [1.6.1] - 2025-12-10
 
 ### Changed
@@ -389,7 +407,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 - README.md, CLAUDE.md, individual plugin READMEs, and MIT license
 
-[Unreleased]: https://github.com/charlesjones-dev/claude-code-plugins-dev/compare/v1.6.1...HEAD
+[Unreleased]: https://github.com/charlesjones-dev/claude-code-plugins-dev/compare/v1.6.2...HEAD
+[1.6.2]: https://github.com/charlesjones-dev/claude-code-plugins-dev/compare/v1.6.1...v1.6.2
 [1.6.1]: https://github.com/charlesjones-dev/claude-code-plugins-dev/compare/v1.6.0...v1.6.1
 [1.6.0]: https://github.com/charlesjones-dev/claude-code-plugins-dev/compare/v1.5.4...v1.6.0
 [1.5.4]: https://github.com/charlesjones-dev/claude-code-plugins-dev/compare/v1.5.3...v1.5.4

README.md

@@ -1,6 +1,6 @@
 # Claude Code Plugins for Developers
 
-[![Version](https://img.shields.io/badge/version-1.6.1-blue.svg)](https://github.com/charlesjones-dev/claude-code-plugins-dev/releases)
+[![Version](https://img.shields.io/badge/version-1.6.2-blue.svg)](https://github.com/charlesjones-dev/claude-code-plugins-dev/releases)
 [![License](https://img.shields.io/badge/license-MIT-green.svg)](LICENSE)
 [![GitHub Issues](https://img.shields.io/github/issues/charlesjones-dev/claude-code-plugins-dev.svg)](https://github.com/charlesjones-dev/claude-code-plugins-dev/issues)
 [![GitHub Stars](https://img.shields.io/github/stars/charlesjones-dev/claude-code-plugins-dev.svg)](https://github.com/charlesjones-dev/claude-code-plugins-dev/stargazers)

plugins/ai-workflow/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "ai-workflow",
-  "version": "1.0.1",
+  "version": "1.0.2",
   "description": "AI-powered development workflow automation - Phase-based planning, implementation orchestration, and preflight code quality checks for efficient sub-agent execution",
   "author": {
     "name": "Charles Jones",

plugins/ai-workflow/README.md

@@ -18,7 +18,7 @@ Provides tools for managing complex development workflows including breaking fea
 
 ## Available Commands
 
-### `/plan-phases`
+### `/workflow-plan-phases`
 
 Create structured implementation plans from feature descriptions, optimized for context-efficient sub-agent execution.
 
@@ -35,8 +35,8 @@ Create structured implementation plans from feature descriptions, optimized for
 **Usage:**
 
 ```
-/plan-phases "Build a user authentication system with OAuth, MFA, and session management"
-/plan-phases --output=docs/plans/auth-system.md "Build authentication system..."
+/workflow-plan-phases "Build a user authentication system with OAuth, MFA, and session management"
+/workflow-plan-phases --output=docs/plans/auth-system.md "Build authentication system..."
 ```
 
 **Before (manual planning):**
@@ -51,15 +51,15 @@ Create structured implementation plans from feature descriptions, optimized for
 **After (with ai-workflow plugin):**
 
 ```
-/plan-phases "Build user authentication"
+/workflow-plan-phases "Build user authentication"
 # Answers clarifying questions
 # AI creates optimally-sized phases
 # Dependencies clearly mapped
 # Execution strategy recommended
 # Plan saved to docs/plans/
 ```
 
-### `/implement-phases`
+### `/workflow-implement-phases`
 
 Orchestrate multi-phase implementation from a plan document using intelligent parallel/sequential execution.
 
@@ -76,9 +76,9 @@ Orchestrate multi-phase implementation from a plan document using intelligent pa
 **Usage:**
 
 ```
-/implement-phases @docs/plans/user-authentication.md
-/implement-phases @docs/plans/feature.md --phases=1,2,3
-/implement-phases @docs/plans/feature.md --strategy=parallel
+/workflow-implement-phases @docs/plans/user-authentication.md
+/workflow-implement-phases @docs/plans/feature.md --phases=1,2,3
+/workflow-implement-phases @docs/plans/feature.md --strategy=parallel
 ```
 
 **Execution Strategies:**
@@ -89,7 +89,7 @@ Orchestrate multi-phase implementation from a plan document using intelligent pa
 | **Sequential** | Linear dependency chain | Safest execution, full context from prior phases |
 | **Mixed** | Some independent, some dependent | Best of both worlds |
 
-### `/preflight`
+### `/workflow-preflight`
 
 Run comprehensive code quality checks before commits, PRs, or deployments.
 
@@ -104,10 +104,10 @@ Run comprehensive code quality checks before commits, PRs, or deployments.
 **Usage:**
 
 ```
-/preflight                  # Interactive mode (default)
-/preflight --fix            # Auto-fix all fixable issues
-/preflight --check-only     # Report only, no fixes
-/preflight --verbose        # Show detailed output
+/workflow-preflight                  # Interactive mode (default)
+/workflow-preflight --fix            # Auto-fix all fixable issues
+/workflow-preflight --check-only     # Report only, no fixes
+/workflow-preflight --verbose        # Show detailed output
 ```
 
 **Supported Ecosystems:**
@@ -133,7 +133,7 @@ Run comprehensive code quality checks before commits, PRs, or deployments.
 **After (with ai-workflow plugin):**
 
 ```
-/preflight
+/workflow-preflight
 # AI discovers configured tools
 # Runs all checks in optimal order
 # Shows clear summary
@@ -169,7 +169,7 @@ Methodology for analyzing plan documents and coordinating phase implementation.
 - Error handling patterns
 - Results aggregation templates
 
-**Auto-loads when:** Implementing phases from a plan, orchestrating sub-agents, or when `/implement-phases` is invoked.
+**Auto-loads when:** Implementing phases from a plan, orchestrating sub-agents, or when `/workflow-implement-phases` is invoked.
 
 ### `preflight-checks`
 
@@ -197,16 +197,16 @@ Comprehensive reference for code quality tools across ecosystems. Provides:
 
 ```
 # Plan a new feature
-/plan-phases "Add user profile editing with avatar upload"
+/workflow-plan-phases "Add user profile editing with avatar upload"
 
 # Review the generated plan
 # Located at: docs/plans/user-profile-editing.md
 
 # Implement the phases
-/implement-phases @docs/plans/user-profile-editing.md
+/workflow-implement-phases @docs/plans/user-profile-editing.md
 
 # Run preflight checks before committing
-/preflight
+/workflow-preflight
 ```
 
 ---
@@ -309,7 +309,7 @@ Verify Fixes
 
 ### Preflight Integration
 
-- Run `/preflight` before every commit
+- Run `/workflow-preflight` before every commit
 - Use `--fix` in CI for automated formatting
 - Use `--check-only` in CI for validation gates
 - Align local checks with CI configuration
@@ -344,7 +344,7 @@ Plus improved code quality, fewer context overflows, and more efficient sub-agen
 - **Version:** 1.0.0
 - **Type:** Development Workflow Automation
 - **Features:**
-  - Commands: `/plan-phases`, `/implement-phases`, `/preflight`
+  - Commands: `/workflow-plan-phases`, `/workflow-implement-phases`, `/workflow-preflight`
   - Skills: `plan-phases`, `implement-phases`, `preflight-checks`
 - **License:** MIT
 - **Author:** Charles Jones

plugins/ai-workflow/commands/workflow-implement-phases.md

@@ -9,23 +9,35 @@ Analyzes phases from a plan document and orchestrates implementation using sub-a
 
 ## Usage
 
-```
-/implement-phases @path/to/plan.md
-/implement-phases @path/to/plan.md --phases=1,2,3
-/implement-phases @path/to/plan.md --strategy=parallel|sequential|auto
+```bash
+/workflow-implement-phases                    # Search docs/plans/ and pick one
+/workflow-implement-phases @path/to/plan.md
+/workflow-implement-phases @path/to/plan.md --phases=1,2,3
+/workflow-implement-phases @path/to/plan.md --strategy=parallel|sequential|auto
 ```
 
 ## Arguments
 
-- `plan_file` (required): Path to the plan document containing phase definitions
+- `plan_file` (optional): Path to the plan document. If omitted, searches `docs/plans/` for existing plans
 - `--phases`: Comma-separated list of specific phases to implement (default: all)
 - `--strategy`: Force execution strategy. Default is `auto` (analyzed)
 
+## Instructions
+
+### If a plan file is provided:
+Read the plan file passed as an argument (e.g., `@docs/plans/my-plan.md`) and proceed with the workflow.
+
+### If no plan file is provided:
+1. Search for existing plan files in `docs/plans/` directory
+2. If plans are found, present them to the user and ask which one to implement
+3. If no plans are found, inform the user and suggest using `/workflow-plan-phases` to create one first
+
 ## Workflow
 
-1. Parse plan document and extract phases
-2. Analyze dependencies (explicit and implicit)
-3. Determine optimal execution strategy (parallel/sequential/mixed)
-4. Present execution plan to user for confirmation
-5. Execute via Task() sub-agents with coordination directory
-6. Aggregate results and report
+1. **Read the plan file** — Use the Read tool to load the plan document
+2. Parse plan document and extract phases
+3. Analyze dependencies (explicit and implicit)
+4. Determine optimal execution strategy (parallel/sequential/mixed)
+5. Present execution plan to user for confirmation
+6. Execute via Task() sub-agents with coordination directory
+7. Aggregate results and report

plugins/ai-workflow/commands/workflow-plan-phases.md

@@ -9,17 +9,27 @@ Creates a phased implementation plan from a feature description, optimized for c
 
 ## Usage
 
-```
-/plan-phases <description>
-/plan-phases "Build a user authentication system with OAuth, MFA, and session management"
-/plan-phases --output=docs/plans/auth-system.md "Build authentication system..."
+```bash
+/workflow-plan-phases <description>
+/workflow-plan-phases "Build a user authentication system with OAuth, MFA, and session management"
+/workflow-plan-phases --output=docs/plans/auth-system.md "Build authentication system..."
 ```
 
 ## Arguments
 
 - `description` (required): What the user wants to build
 - `--output`: Custom output path (default: `docs/plans/{slugified-name}.md`)
 
+## Instructions
+
+1. **Read the user's description** from the command argument
+2. **Ask clarifying questions** before creating the plan — never skip this step
+3. **Wait for user responses** before proceeding
+4. **Create the plan document** following the plan-phases skill methodology
+5. **Save to `docs/plans/`** (create directory if needed) using a slugified filename
+6. **Present the plan** and ask if changes are needed
+7. **Stop** — do not implement
+
 ## Workflow
 
 1. Ask clarifying questions (always — never skip)
@@ -28,3 +38,15 @@ Creates a phased implementation plan from a feature description, optimized for c
 4. Define clear acceptance criteria per phase
 5. Map dependencies and recommend execution strategy
 6. Output structured markdown to docs/plans/
+7. **STOP** — do not implement the plan
+
+## Important
+
+**This command only creates the plan. Do NOT proceed to implement any phases.**
+
+After the plan is written:
+- Present the plan document to the user
+- Ask if they want to make any changes
+- Inform them they can use `/workflow-implement-phases` when ready to execute
+
+**Never start writing code or implementing phases after creating the plan.**

plugins/ai-workflow/skills/implement-phases/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: implement-phases
-description: "Use when implementing phases from a plan document, executing phased implementations, orchestrating sub-agents for phase work, or when /implement-phases command is invoked. Provides dependency analysis and parallel/sequential execution strategies."
+description: "Use when implementing phases from a plan document, executing phased implementations, orchestrating sub-agents for phase work, or when /workflow-implement-phases command is invoked. Provides dependency analysis and parallel/sequential execution strategies."
 ---
 
 # Phase Implementation Orchestration Skill

plugins/ai-workflow/skills/plan-phases/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: plan-phases
-description: "Use when creating implementation plans, phase planning documents, breaking features into phases, or when /plan-phases command is invoked. Provides methodology for context-efficient phase sizing and dependency analysis."
+description: "Use when creating implementation plans, phase planning documents, breaking features into phases, or when /workflow-plan-phases command is invoked. Provides methodology for context-efficient phase sizing and dependency analysis."
 ---
 
 # Phase Planning Skill
@@ -410,3 +410,22 @@ Before delivering plan:
 - [ ] Dependencies are explicit and acyclic
 - [ ] Specifications are detailed enough to implement without guessing
 - [ ] File saved to docs/plans/{feature-name}.md
+
+---
+
+## IMPORTANT: Planning Only — Do Not Implement
+
+**This skill is for planning only. After creating the plan, STOP.**
+
+Do NOT:
+- Start implementing any phases
+- Write any code
+- Create any files other than the plan document
+- Begin execution automatically
+
+After the plan is complete:
+1. Present the plan document to the user
+2. Ask if they want to make any revisions
+3. Inform them to use `/workflow-implement-phases` or the `implement-phases` skill when ready to execute
+
+The user decides when to proceed with implementation.