flow-cc 0.5.2 → 0.5.4

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 (3) hide show
  1. package/VERSION +1 -1
  2. package/package.json +1 -1
  3. package/skills/flow-status.md +3 -3
package/VERSION CHANGED
@@ -1 +1 @@
1
- 0.5.0
1
+ 0.5.4
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "flow-cc",
3
- "version": "0.5.2",
3
+ "version": "0.5.4",
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-status.md CHANGED
@@ -44,7 +44,7 @@ Use this explicit decision tree:
44
44
  → Alt: `/flow:task` for quick fixes or cleanup (no PRD needed)
45
45
 
46
46
  **IF pending phases exist in ROADMAP BUT no PRD exists for the current milestone:**
47
- → Primary: `/flow:spec [next milestone name]` to create the execution plan
47
+ → Primary: `/flow:spec` to pick a milestone and create its execution plan
48
48
  → Alt: `/flow:task` for quick fixes or cleanup (no PRD needed)
49
49
 
50
50
  **IF all phases are complete AND a next milestone with status "Planned" exists in ROADMAP.md:**
@@ -57,10 +57,10 @@ Use this explicit decision tree:
57
57
  → Alt: `/flow:task` for quick fixes or cleanup (no PRD needed)
58
58
 
59
59
  **IF no phases exist in ROADMAP (milestone defined but not planned):**
60
- → Primary: `/flow:spec [milestone name]` to plan this milestone
60
+ → Primary: `/flow:spec` to pick a milestone and create its execution plan
61
61
  → Alt: `/flow:task` for quick fixes or cleanup (no PRD needed)
62
62
 
63
- **When suggesting `/flow:spec`:** Always include the target milestone name in the suggestion (e.g., `→ /flow:spec v16.0: Conventional Leasing & Email Export`). This lets the user see which milestone will be specced before running the command, and passes the name as an argument so flow:spec can match it directly.
63
+ **When suggesting `/flow:spec`:** Never include a specific milestone name. Always suggest the bare command `/flow:spec` — the milestone picker will handle selection. This avoids confusion when the user has multiple sessions or milestones in flight.
64
64
 
65
65
  ## Step 4 — Print Status Block
66
66