planflow-ai 1.0.3 → 1.0.5

package/.claude/commands/create-plan.md

@@ -147,17 +147,38 @@ Plan Created!
 - X phases created
 - Total complexity: XX/XX
 - Highest complexity: Phase X at Y/10
+```
+
+**CRITICAL — Check autopilot mode BEFORE presenting next steps:**
+
+1. **Check if `flow/.autopilot` exists**
+2. **If autopilot is ON**: Do NOT show "Next Steps" or "invoke manually". Instead, use `AskUserQuestion` to ask for plan approval, then **immediately auto-proceed** to `/execute-plan` with the plan file. Do NOT stop. Do NOT wait for the user to manually invoke `/execute-plan`.
+
+```typescript
+// When autopilot is ON, ask for approval then auto-proceed:
+AskUserQuestion({
+  questions: [{
+    question: "Plan is ready. Approve to proceed with execution?",
+    header: "Plan",
+    options: [
+      { label: "Approve and execute", description: "Start executing the plan now" },
+      { label: "Refine first", description: "Let me suggest changes to the plan before executing" }
+    ],
+    multiSelect: false
+  }]
+})
+// If approved → immediately invoke /execute-plan (do NOT stop)
+```
+
+3. **If autopilot is OFF**: Show next steps and stop:
 
-**Next Steps** (user must invoke manually):
+```markdown
+**Next Steps**:
 1. Review the plan above
 2. Request any refinements
 3. When ready, invoke `/execute-plan @flow/plans/plan_<feature>_v<version>.md`
 ```
 
-**CRITICAL**: If autopilot mode is OFF (`flow/.autopilot` does not exist), this command is now complete. Do NOT auto-invoke `/execute-plan`. Wait for the user to explicitly invoke it.
-
-**If autopilot mode is ON** (`flow/.autopilot` exists): Auto-proceed to `/execute-plan` with the plan file after the user approves the plan.
-
 ---
 
 ## Flow Diagram

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "planflow-ai",
-  "version": "1.0.3",
+  "version": "1.0.5",
   "description": "Structured AI-assisted development workflows for discovery, planning, execution, code reviews, and testing",
   "type": "module",
   "main": "dist/cli/index.js",

package/rules/core/autopilot-mode.mdc

@@ -71,7 +71,7 @@ Check `flow/contracts/` for any relevant integration contracts. If found, note t
 
 ### Step 2: Discovery
 
-1. **Read** the discovery command to load discovery context
+1. **Read** the file `.cursor/commands/discovery-plan.md` to load discovery context
 2. Execute the discovery skill following that command's instructions
 3. **PAUSE**: Ask user discovery questions as needed (mandatory checkpoint)
 4. Produce the discovery document in `flow/discovery/`
@@ -83,7 +83,7 @@ Check `flow/contracts/` for any relevant integration contracts. If found, note t
 **GATE CHECK**: Before proceeding, verify that Step 2 produced a discovery document in `flow/discovery/`. If no discovery document exists, **DO NOT proceed** — go back to Step 2. A plan cannot be created without a discovery document. This is a hard requirement with no exceptions.
 
 1. **Verify** discovery document exists in `flow/discovery/` (created in Step 2)
-2. **Read** the create-plan command to load planning context
+2. **Read** the file `.cursor/commands/create-plan.md` to load planning context
 3. Execute the create-plan skill with the discovery document as input
 4. **PAUSE**: Present the plan for user approval (mandatory checkpoint)
 5. Wait for user to approve the plan before proceeding
@@ -93,7 +93,7 @@ Check `flow/contracts/` for any relevant integration contracts. If found, note t
 
 ### Step 4: Execute Plan
 
-1. **Read** the execute-plan command to load execution context
+1. **Read** the file `.cursor/commands/execute-plan.md` to load execution context
 2. Execute the plan following complexity-based grouping strategy
 3. Update the plan file with progress
 4. Run build + test verification at the end
@@ -102,7 +102,7 @@ Check `flow/contracts/` for any relevant integration contracts. If found, note t
 
 ### Step 5: Review Code
 
-1. **Read** the review-code command to load review context
+1. **Read** the file `.cursor/commands/review-code.md` to load review context
 2. Review all uncommitted changes
 3. Present the review summary
 
@@ -174,10 +174,10 @@ All other transitions happen automatically.
 
 When autopilot is ON, the following rules in individual commands are **suspended**:
 
-- Discovery command: "Ask Before Proceeding" and "No Auto-Execution" rules
-- Create-plan command: "No Auto-Chaining" and "Complete and Stop" rules
-- Execute-plan command: "Complete and Stop" rule
-- Review-code command: completion stop behavior
+- `.cursor/commands/discovery-plan.md`: "Ask Before Proceeding" and "No Auto-Execution" rules
+- `.cursor/commands/create-plan.md`: "No Auto-Chaining" and "Complete and Stop" rules
+- `.cursor/commands/execute-plan.md`: "Complete and Stop" rule
+- `.cursor/commands/review-code.md`: completion stop behavior
 
 These rules remain fully active when autopilot is OFF.