flow-cc 0.5.7 → 0.5.8

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.
package/CHANGELOG.md CHANGED
@@ -5,6 +5,13 @@ All notable changes to this project will be documented in this file.
5
5
  The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
6
6
  and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
7
7
 
8
+ ## [0.5.8] - 2026-02-14
9
+
10
+ ### Fixed
11
+ - `/flow:go` Step 7 now enforces mandatory `/flow:done` suggestion in every phase completion output
12
+ - Added STOP RULE to prevent autonomous post-phase work (PR creation, comment resolution, cleanup)
13
+ - Separated "next flow commands" from project-specific actions so `/flow:done` never gets dropped
14
+
8
15
  ## [0.5.0] - 2026-02-13
9
16
 
10
17
  ### Added
package/VERSION CHANGED
@@ -1 +1 @@
1
- 0.5.7
1
+ 0.5.8
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "flow-cc",
3
- "version": "0.5.7",
3
+ "version": "0.5.8",
4
4
  "description": "Structured workflow system for Claude Code — spec interviews, agent-team execution, session handoffs, compounding knowledge",
5
5
  "author": "Troy Hoffman",
6
6
  "license": "MIT",
package/skills/flow-go.md CHANGED
@@ -163,18 +163,35 @@ Create an atomic commit for this phase:
163
163
 
164
164
  **ROADMAP.md:** Mark this phase as "Complete ([today's date])"
165
165
 
166
- ## Step 7 — Route Next Action
166
+ ## Step 7 — Route Next Action (MANDATORY — FINAL STEP)
167
+
168
+ **STOP RULE:** This is the LAST thing you do. After printing the output below, STOP IMMEDIATELY. Do NOT:
169
+ - Review or resolve code review comments
170
+ - Create or update pull requests
171
+ - Run additional cleanup or refactoring
172
+ - Do any work beyond printing this summary
173
+
174
+ Any post-phase work belongs in a SEPARATE `/flow:go` invocation or `/flow:task`.
175
+
176
+ Print this EXACT structure (fill in values):
167
177
 
168
- Print phase summary:
169
178
  ```
170
- Phase [N]: [Name] — Complete
179
+ Phase [N]: [Name] — Complete
171
180
  - [X] files created, [Y] modified
172
181
  - Commit: [SHA]
173
- - Verification: passed
182
+ - Verification: [passed/failed]
183
+
184
+ Next flow command:
185
+ → /flow:go — execute Phase [N+1]: [Next Phase Name]
186
+ → /flow:done — end session, update docs, generate handoff prompt
187
+ ```
188
+
189
+ If this was the last phase, replace the flow commands block with:
190
+
191
+ ```
192
+ All phases complete — milestone done!
174
193
 
175
- Next:
176
- - /flow:go for Phase [N+1]: [Next Phase Name]
177
- - /flow:done to end session
194
+ → /flow:done — finalize session (REQUIRED before ending)
178
195
  ```
179
196
 
180
- If this was the last phase: "All phases complete! Run `/flow:done` to finalize."
197
+ **CRITICAL:** The `→ /flow:done` line MUST appear in EVERY phase completion output, whether or not more phases remain. This is non-negotiable. `/flow:done` is how session-end documentation happens.