planflow-ai 1.0.4 → 1.0.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/rules/core/autopilot-mode.mdc +8 -8
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "planflow-ai",
3
- "version": "1.0.4",
3
+ "version": "1.0.5",
4
4
  "description": "Structured AI-assisted development workflows for discovery, planning, execution, code reviews, and testing",
5
5
  "type": "module",
6
6
  "main": "dist/cli/index.js",
package/rules/core/autopilot-mode.mdc CHANGED
@@ -71,7 +71,7 @@ Check `flow/contracts/` for any relevant integration contracts. If found, note t
71
71
 
72
72
  ### Step 2: Discovery
73
73
 
74
- 1. **Read** the discovery command to load discovery context
74
+ 1. **Read** the file `.cursor/commands/discovery-plan.md` to load discovery context
75
75
  2. Execute the discovery skill following that command's instructions
76
76
  3. **PAUSE**: Ask user discovery questions as needed (mandatory checkpoint)
77
77
  4. Produce the discovery document in `flow/discovery/`
@@ -83,7 +83,7 @@ Check `flow/contracts/` for any relevant integration contracts. If found, note t
83
83
  **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.
84
84
 
85
85
  1. **Verify** discovery document exists in `flow/discovery/` (created in Step 2)
86
- 2. **Read** the create-plan command to load planning context
86
+ 2. **Read** the file `.cursor/commands/create-plan.md` to load planning context
87
87
  3. Execute the create-plan skill with the discovery document as input
88
88
  4. **PAUSE**: Present the plan for user approval (mandatory checkpoint)
89
89
  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
93
93
 
94
94
  ### Step 4: Execute Plan
95
95
 
96
- 1. **Read** the execute-plan command to load execution context
96
+ 1. **Read** the file `.cursor/commands/execute-plan.md` to load execution context
97
97
  2. Execute the plan following complexity-based grouping strategy
98
98
  3. Update the plan file with progress
99
99
  4. Run build + test verification at the end
@@ -102,7 +102,7 @@ Check `flow/contracts/` for any relevant integration contracts. If found, note t
102
102
 
103
103
  ### Step 5: Review Code
104
104
 
105
- 1. **Read** the review-code command to load review context
105
+ 1. **Read** the file `.cursor/commands/review-code.md` to load review context
106
106
  2. Review all uncommitted changes
107
107
  3. Present the review summary
108
108
 
@@ -174,10 +174,10 @@ All other transitions happen automatically.
174
174
 
175
175
  When autopilot is ON, the following rules in individual commands are **suspended**:
176
176
 
177
- - Discovery command: "Ask Before Proceeding" and "No Auto-Execution" rules
178
- - Create-plan command: "No Auto-Chaining" and "Complete and Stop" rules
179
- - Execute-plan command: "Complete and Stop" rule
180
- - Review-code command: completion stop behavior
177
+ - `.cursor/commands/discovery-plan.md`: "Ask Before Proceeding" and "No Auto-Execution" rules
178
+ - `.cursor/commands/create-plan.md`: "No Auto-Chaining" and "Complete and Stop" rules
179
+ - `.cursor/commands/execute-plan.md`: "Complete and Stop" rule
180
+ - `.cursor/commands/review-code.md`: completion stop behavior
181
181
 
182
182
  These rules remain fully active when autopilot is OFF.
183
183