flow-cc 0.5.1 → 0.5.2

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/package.json +1 -1
  2. package/skills/flow-spec.md +1 -1
  3. package/skills/flow-status.md +4 -2
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "flow-cc",
3
- "version": "0.5.1",
3
+ "version": "0.5.2",
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-spec.md CHANGED
@@ -43,7 +43,7 @@ Before starting the interview, determine which milestone this PRD targets:
43
43
 
44
44
  1. **If the user passed an argument** (e.g., `/flow:spec v3: Payments`) — match against ROADMAP.md milestones. If no match, print available milestones and ask which one.
45
45
 
46
- 2. **If no argument** — read ROADMAP.md and list all incomplete milestones. Use AskUserQuestion to let the user pick which milestone to spec. Pre-select the current milestone from STATE.md as the first option (marked as "current"). If only one incomplete milestone exists, skip the prompt and use it directly.
46
+ 2. **If no argument** — read ROADMAP.md and list all incomplete milestones. Use AskUserQuestion to let the user pick which milestone to spec. Pre-select the next unspecced milestone as the first option. Always show the picker, even if only one milestone is listed — the user may want to confirm or choose "Other" to define a new milestone first.
47
47
 
48
48
  3. **Derive the PRD slug:** Take the milestone's version prefix and name (e.g., "v3: Dashboard Analytics"), lowercase it, replace spaces and special characters with hyphens, collapse consecutive hyphens. Result: `v3-dashboard-analytics`. The PRD path is `.planning/prds/{slug}.md`.
49
49
 
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` to create the execution plan
47
+ → Primary: `/flow:spec [next milestone name]` to create the 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,9 +57,11 @@ 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` to plan this milestone
60
+ → Primary: `/flow:spec [milestone name]` to plan this milestone
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.
64
+
63
65
  ## Step 4 — Print Status Block
64
66
 
65
67
  ```