flow-cc 0.8.2 → 0.8.3

package/CHANGELOG.md

@@ -5,6 +5,15 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.8.3] - 2026-02-15
+
+### Fixed
+- `/flow:spec` now writes `**Linear Project:**` field to PRD header — downstream skills (`flow:go`, `flow:done`) depend on it
+- `/flow:spec` now sets `projectMilestoneId` on every Linear issue — fixes milestone progress showing 0% despite issues existing
+- `/flow:spec` PRD template includes `**Linear Project:**` field (was missing, causing silent Linear skips)
+- `/flow:go` Step 6 now moves completed milestone issues to "Done" in Linear (were stuck at "In Progress" forever)
+- `/flow:done` Step 5.5 now handles interim milestone completion — moves completed milestone issues to "Done" before checking PR/project status
+
 ## [0.8.2] - 2026-02-14
 
 ### Fixed

package/VERSION

@@ -1 +1 @@
-0.8.2
+0.8.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "flow-cc",
-  "version": "0.8.2",
+  "version": "0.8.3",
   "description": "Structured workflow system for Claude Code — spec interviews, agent-team execution, session handoffs, compounding knowledge",
   "author": "Troy Hoffman",
   "license": "MIT",

package/skills/flow-done.md

@@ -148,14 +148,18 @@ Runs when 5.25 created a PR (or one already exists for this branch).
 
 - Check if Linear MCP tools are available; skip silently if not
 - Parse active PRD for `**Linear Project:**` field
-- If found and open PR exists (`gh pr list --head [branch] --state open`):
-  - Move all "In Progress" issues to "In Review" via `mcp__linear__update_issue`
-  - Print: "Linear: [N] issues → In Review (PR open)"
-- If no PR: issues stay In Progress (normal mid-project session end)
-- **If project complete** (all milestones done):
-  - Find project via `mcp__linear__list_projects`, match by name from PRD `**Linear Project:**` field
-  - Move project to Completed: `mcp__linear__update_project` with `state: "Completed"`
-  - Print: "Linear: project → Completed"
+- If found:
+  - Find project, list milestones via `mcp__linear__list_milestones`
+  - Cross-reference ROADMAP.md: for each milestone marked "Complete", find matching Linear milestone
+  - For each completed milestone: list its issues, move non-Done issues to "Done" via `mcp__linear__update_issue`
+  - Print: "Linear: [N] issues → Done ([milestone name])" per milestone; if 0 issues: "Linear: [milestone name] — no issues to update"
+  - If open PR exists (`gh pr list --head [branch] --state open`):
+    - Move remaining "In Progress" issues to "In Review" via `mcp__linear__update_issue`
+    - Print: "Linear: [N] issues → In Review (PR open)"
+  - If no PR: remaining in-progress issues stay (normal mid-project session end)
+  - **If project complete** (all milestones done):
+    - Move project to Completed: `mcp__linear__update_project` with `state: "Completed"`
+    - Print: "Linear: project → Completed"
 - Post progress comment on any branch-linked Linear issue
 
 ### 6. Route Next Action
@@ -188,7 +192,7 @@ Session complete.
 - Committed: [SHA | nothing to commit]
 - PR: [created #N | skipped (milestones remain)]
 - Review: [N comments addressed | pending | skipped]
-- Linear: [N issues → In Review, project → Completed | N issues → In Review | skipped]
+- Linear: [N issues → Done (milestone) | N → In Review (PR) | project → Completed | skipped]
 
 Next: [routing from Step 6]
 ```

package/skills/flow-go.md

@@ -137,6 +137,8 @@ Atomic commit for this milestone. Stage only files from this milestone's agents.
 
 **ROADMAP.md (ALWAYS):** Mark milestone as "Complete ([date])"
 
+**Linear milestone (ALWAYS):** If `**Linear Project:**` in PRD and Linear MCP available: find completed milestone in Linear via `mcp__linear__list_milestones`, list its issues, move non-Done issues to "Done" via `mcp__linear__update_issue`. Print: "Linear: [N] issues → Done ([milestone name])". If 0 issues: print "Linear: [milestone name] — no issues to update". Skip silently if no Linear Project or MCP unavailable.
+
 **STATE.md (LAST MILESTONE ONLY):** Update only if this was the LAST milestone (project complete): files created/modified count, commit SHA, milestone completion note. Keep "Active PRD" pointing to resolved path. Skip STATE.md for non-final milestones.
 
 ## Step 7 — Route Next Action (MANDATORY — FINAL STEP)

package/skills/flow-spec.md

@@ -94,6 +94,7 @@ Write to `.planning/prds/{slug}.md` (create dir if needed) with this structure:
 **Branch:** feat/{project-slug}
 **Created:** [date]
 **Assigned To:** [developer or "unassigned"]
+**Linear Project:** [Linear project name if linked, or blank]
 
 ## Overview
 [One paragraph summary]
@@ -161,10 +162,13 @@ After writing the PRD:
 4. **Linear Integration (optional):**
    - Check if Linear MCP tools are available (`mcp__linear__list_teams`)
    - If available: search for matching Linear project (`mcp__linear__list_projects`)
-     - Found: create one **Linear milestone** per implementation milestone, one **Linear issue** per user story/task (not per milestone)
-     - Not found: AskUserQuestion to pick project or skip
+     - Found: use it. Not found: AskUserQuestion to pick existing project or skip Linear
+   - Add `**Linear Project:** [project name]` to the PRD header (after `**Assigned To:**`)
+   - For each implementation milestone: create a **Linear milestone** (`mcp__linear__create_milestone`) under the project
+   - For each user story: create a **Linear issue** (`mcp__linear__create_issue`) with BOTH `projectId` AND `projectMilestoneId` set — assign to the milestone whose `**Acceptance:**` field references that story. Title: "US-N: [story name]"
+   - **Critical:** Every issue MUST have `projectMilestoneId` set. Issues without milestone assignment break downstream status tracking.
    - If MCP unavailable: skip silently
-   - Print: "[N] milestones + [M] issues created under project [name]"
+   - Print: "[N] milestones + [M] issues created under [project name]"
 
 5. Print handoff prompt in a fenced code block.