flow-cc 0.5.3 → 0.5.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 (3) hide show
  1. package/VERSION +1 -1
  2. package/package.json +1 -1
  3. package/skills/flow-status.md +9 -5
package/VERSION CHANGED
@@ -1 +1 @@
1
- 0.5.3
1
+ 0.5.5
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "flow-cc",
3
- "version": "0.5.3",
3
+ "version": "0.5.5",
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,8 +44,8 @@ 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
48
- → Alt: `/flow:task` for quick fixes or cleanup (no PRD needed)
47
+ → `/flow:spec` — select a milestone and build its execution plan
48
+ → `/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:**
51
51
  → Primary: `/flow:done` to finalize this milestone (will auto-transition to next milestone)
@@ -57,10 +57,14 @@ 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
61
- → Alt: `/flow:task` for quick fixes or cleanup (no PRD needed)
60
+ → `/flow:spec` — select a milestone and build its execution plan
61
+ → `/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
+ **CRITICAL — `/flow:spec` suggestion format:** When printing routing recommendations, output EXACTLY this text for /flow:spec suggestions:
64
+ ```
65
+ → /flow:spec — select a milestone and build its execution plan
66
+ ```
67
+ Do NOT append a milestone name, do NOT say "for v16" or "to plan v16" or any variation. The milestone picker inside /flow:spec handles selection. Adding a name here confuses users who may have multiple milestones in flight across terminals. Print the line EXACTLY as shown above — no modifications.
64
68
 
65
69
  ## Step 4 — Print Status Block
66
70