@rayburst/cc 1.0.30 → 1.0.31

package/commands/rb/discover.md

@@ -334,6 +334,26 @@ For each `existing_feature` with observed behaviors not yet tracked as criteria:
 
 Limit enrichment to 3 new criteria per existing feature to avoid over-loading features with redundant data.
 
+**After enriching each existing feature**, check its current links and add any missing relationships that were evident from the discovery run:
+
+```
+<MCP_PREFIX>list_feature_links({ featureId: "<existing feature ID>" })
+```
+
+For each clear relationship not yet present (limit: at most 3 new links per feature):
+
+```
+<MCP_PREFIX>link_feature_to_feature({
+  sourceFeatureId: "<existing feature ID>",
+  targetFeatureId: "<related feature ID>",
+  linkType: "<depends_on | implements | extends | related_to>"
+})
+```
+
+Apply the same relationship type guide as Step 7. Only link if the relationship is semantically clear from what you observed in the browser. Track the total count for the Step 9 report.
+
+**Also apply this linking check to existing features that were matched but had NO new criteria to add** — if you observed a clear relationship that isn't yet linked, create the link even if no criteria enrichment was needed.
+
 ---
 
 ### Step 9: Summary Report

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rayburst/cc",
-  "version": "1.0.30",
+  "version": "1.0.31",
   "description": "Rayburst slash commands for Claude Code — /rb:init, /rb:plan, /rb:sync, /rb:status, /rb:validate-feature, /rb:validate-card, /rb:implement, /rb:discover",
   "bin": {
     "rayburst-cc": "bin/install.js"