@rayburst/cc 1.0.28 → 1.0.31

package/.claude-plugin/plugin.json

@@ -0,0 +1,23 @@
+{
+  "name": "rayburst",
+  "description": "AI-native product management for Claude Code. Track features with acceptance criteria, run Playwright browser validation, and manage board cards through the full dev cycle — all via slash commands and MCP.",
+  "version": "1.0.29",
+  "author": {
+    "name": "Rayburst",
+    "email": "hello@rayburst.app"
+  },
+  "homepage": "https://rayburst.app",
+  "repository": "https://github.com/rayburst/rayburst-cc",
+  "license": "MIT",
+  "keywords": [
+    "project-management",
+    "feature-tracking",
+    "qa-validation",
+    "playwright",
+    "mcp",
+    "board",
+    "acceptance-criteria",
+    "product-manager",
+    "browser-testing"
+  ]
+}

package/commands/rb/discover.md

@@ -2,6 +2,8 @@
 name: rb:discover
 description: Feature Atlas discovery — log into the target app with Playwright, crawl all pages, and create/enrich untracked features in the Rayburst atlas
 argument-hint: "[starting URL or page name, e.g. /dashboard]"
+user-invocable: true
+disable-model-invocation: true
 allowed-tools:
   - mcp__playwright__browser_navigate
   - mcp__playwright__browser_snapshot
@@ -265,6 +267,43 @@ Immediately after `create_feature`, add 4–8 acceptance criteria in batches of
 })
 ```
 
+**After creating a feature's criteria**, search for related already-tracked features (both from the existing atlas loaded in Step 2 and from features created earlier in this same discovery run) and link them:
+
+```
+<MCP_PREFIX>list_features({ search: "<keyword from feature title>", limit: 10 })
+```
+
+For each clear relationship found (limit: at most 3 links per newly created feature):
+
+```
+<MCP_PREFIX>link_feature_to_feature({
+  sourceFeatureId: "<new feature ID>",
+  targetFeatureId: "<related feature ID>",
+  linkType: "<depends_on | implements | extends | related_to>"
+})
+```
+
+Relationship type guide:
+- `depends_on` — the new feature cannot work without the related feature
+- `implements` — the new feature is a concrete implementation of the related feature
+- `extends` — the new feature builds on top of the related feature
+- `related_to` — thematically related but not a hard dependency
+
+Only link if the relationship is semantically clear. Prefer `depends_on` and `implements` over `related_to`.
+
+After creating links, embed `[[Feature Name]]` wikilink syntax in the new feature's description for the 1-2 most important connections:
+
+```
+<MCP_PREFIX>update_feature({
+  featureId: "<new feature ID>",
+  description: "<existing description with [[Related Feature Name]] wikilinks added inline>"
+})
+```
+
+Track the total count of feature-to-feature links created across this discovery run (for the Step 9 report).
+
+---
+
 **Tag strategy**:
 - Reuse an existing tag if `tagNameLower` matches the page/area concept (e.g. "board-view", "settings")
 - Create a new tag only if no existing tag fits the page/area context:
@@ -295,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
@@ -309,6 +368,7 @@ Feature Atlas Discovery — Summary
   Existing features enriched : <Y>
   New tags created       : <K>
   Total criteria added   : <total>
+  Feature links created  : <Z>
 ──────────────────────────────────────────
 
 New features:

package/commands/rb/implement.md

@@ -1,5 +1,9 @@
 ---
+name: rb:implement
+description: Implement a Rayburst board card end-to-end — load the card and linked features, plan with a subagent, execute with a subagent, then move the card to validation
 argument-hint: "<cardId or card title>"
+user-invocable: true
+disable-model-invocation: true
 allowed-tools:
   - Read
   - Glob

package/commands/rb/init.md

@@ -2,6 +2,8 @@
 name: rb:init
 description: Initialize project config — set project URL, user credentials, and MCP server role assignments for use by other rb: commands
 argument-hint: ""
+user-invocable: true
+disable-model-invocation: true
 allowed-tools:
   - Bash
   - Read

package/commands/rb/plan.md

@@ -2,6 +2,8 @@
 name: rb:plan
 description: Task-driven PM session — search the feature atlas for a matching feature, enrich or create it, create a board card, and link them together
 argument-hint: "<task description, e.g. 'Feature Validation Tab', 'card drag and drop'>"
+user-invocable: true
+disable-model-invocation: true
 allowed-tools:
   - Read
   - Bash
@@ -134,6 +136,53 @@ Print a summary of the feature + criteria created.
 
 ---
 
+### Step 3.5: Connect Related Features (Wikilinks)
+
+Search the atlas for features that are semantically related to the current feature:
+
+```
+<MCP_PREFIX>list_features({ search: "<1-2 keywords from feature title>", limit: 15 })
+```
+
+For each candidate feature (excluding the current feature itself), decide the relationship type:
+- `depends_on` — the current feature cannot work without the candidate (e.g. "Feature Graph Canvas" depends_on "Feature-to-Feature Link Graph")
+- `implements` — the current feature is a concrete UI/API implementation of the candidate (e.g. "Gherkin Syntax Detection" implements "Cucumber-Style Criteria Display")
+- `extends` — the current feature builds on top of the candidate (e.g. "Feature Graph Canvas" extends "Experimental Features Page Layout")
+- `related_to` — thematically related but not a hard dependency
+
+**Rules for linking:**
+- Only link if the relationship is semantically clear and meaningful
+- Create at most 3-5 links per feature (don't over-connect)
+- Prefer `depends_on` and `implements` over `related_to` when the relationship is directional
+- Skip features that are clearly from a different domain (e.g. billing features when working on a board feature)
+
+For each clear relationship found:
+```
+<MCP_PREFIX>link_feature_to_feature({
+  sourceFeatureId: "<current feature ID>",
+  targetFeatureId: "<related feature ID>",
+  linkType: "<depends_on | implements | extends | related_to>"
+})
+```
+
+**Update the feature description with wikilinks:**
+
+After creating links, update the feature description to embed `[[Feature Name]]` wikilink syntax for the most important 1-3 connections:
+
+```
+<MCP_PREFIX>update_feature({
+  featureId: "<feature-id>",
+  description: "<existing description text, with [[Related Feature Name]] wikilinks added inline where relevant>"
+})
+```
+
+Example description with wikilinks:
+> "Adds a React Flow graph view on the Features page. Nodes represent features colored by status; edges come from [[Feature-to-Feature Link Graph]] typed links. Clicking a node opens the feature detail panel from [[Experimental Feature Detail Overview Tab Layout]]."
+
+Print a brief summary of links created.
+
+---
+
 ### Step 4: Create a Board Card
 
 ```
@@ -164,6 +213,7 @@ Print a summary:
 - **Feature:** title (new or existing), criteria count
 - **Card:** title, full UUID, status (`ready`)
 - **Link:** confirmed
+- **Links:** N feature-to-feature links created (list the linked feature titles)
 
 Then print the next-step prompt:
 

package/commands/rb/status.md

@@ -2,6 +2,8 @@
 name: rb:status
 description: Show feature atlas status — counts by status, draft features ready for planning, and active board cards
 argument-hint: ""
+user-invocable: true
+disable-model-invocation: false
 allowed-tools:
   - Read
   - Bash
@@ -67,6 +69,28 @@ Extract:
 - Cards in `validation` status (awaiting QA)
 - Cards in `in-progress` status (actively being built)
 
+### Step 3.5: Sample Feature Links
+
+Call `list_feature_links` on a sample of 5-10 features from the loaded list to estimate graph density:
+
+```
+<MCP_PREFIX>list_feature_links({ featureId: "<feature ID 1>" })
+<MCP_PREFIX>list_feature_links({ featureId: "<feature ID 2>" })
+<MCP_PREFIX>list_feature_links({ featureId: "<feature ID 3>" })
+<MCP_PREFIX>list_feature_links({ featureId: "<feature ID 4>" })
+<MCP_PREFIX>list_feature_links({ featureId: "<feature ID 5>" })
+```
+
+Pick a representative sample spread across different status groups (draft, active, completed). Call up to 10 features if the atlas is large.
+
+Compute from the results:
+- `features_with_links`: count of sampled features where `list_feature_links` returned > 0 results
+- Extrapolate: `estimated_linked` = (features_with_links / sample_size) × total_feature_count
+- `estimated_isolated` = total_feature_count − estimated_linked
+- Note the feature with the most links as "most connected"
+
+---
+
 ### Step 4: Cross-Reference Features and Cards
 
 For each feature:
@@ -103,6 +127,12 @@ Sorted by criteria count (highest first):
 ### Active Features (in-progress on board)
 - [Feature Title] → card: [card title] ([status])
 
+### Knowledge Graph Health
+- Features with at least 1 link: N
+- Isolated features (no links): N
+- Most connected feature: [Feature Title] (N links)
+- Run `/rb:plan <area>` to connect isolated features
+
 ### Next Actions
 - Run `/rb:plan <area>` to generate more draft features
 - Run `/rb:sync <task>` to track a new task in the atlas

package/commands/rb/sync.md

@@ -2,6 +2,8 @@
 name: rb:sync
 description: Passive feature sync — find or create the matching Rayburst feature for a task description
 argument-hint: "<task description, e.g. add monthly billing toggle>"
+user-invocable: true
+disable-model-invocation: false
 allowed-tools:
   - Read
   - Bash
@@ -113,6 +115,53 @@ Then add 4-8 acceptance criteria:
 
 Coverage: happy path (2-3), empty states (1), error handling (1), edge cases (1).
 
+### Step 4.5: Connect Related Features (Wikilinks)
+
+Search the atlas for features that are semantically related to the current feature:
+
+```
+<MCP_PREFIX>list_features({ search: "<1-2 keywords from feature title>", limit: 15 })
+```
+
+For each candidate feature (excluding the current feature itself), decide the relationship type:
+- `depends_on` — the current feature cannot work without the candidate (e.g. "Feature Graph Canvas" depends_on "Feature-to-Feature Link Graph")
+- `implements` — the current feature is a concrete UI/API implementation of the candidate (e.g. "Gherkin Syntax Detection" implements "Cucumber-Style Criteria Display")
+- `extends` — the current feature builds on top of the candidate (e.g. "Feature Graph Canvas" extends "Experimental Features Page Layout")
+- `related_to` — thematically related but not a hard dependency
+
+**Rules for linking:**
+- Only link if the relationship is semantically clear and meaningful
+- Create at most 3-5 links per feature (don't over-connect)
+- Prefer `depends_on` and `implements` over `related_to` when the relationship is directional
+- Skip features that are clearly from a different domain (e.g. billing features when working on a board feature)
+
+For each clear relationship found:
+```
+<MCP_PREFIX>link_feature_to_feature({
+  sourceFeatureId: "<current feature ID>",
+  targetFeatureId: "<related feature ID>",
+  linkType: "<depends_on | implements | extends | related_to>"
+})
+```
+
+**Update the feature description with wikilinks:**
+
+After creating links, update the feature description to embed `[[Feature Name]]` wikilink syntax for the most important 1-3 connections:
+
+```
+<MCP_PREFIX>update_feature({
+  featureId: "<feature-id>",
+  description: "<existing description text, with [[Related Feature Name]] wikilinks added inline where relevant>"
+})
+```
+
+Example description with wikilinks:
+> "Adds a React Flow graph view on the Features page. Nodes represent features colored by status; edges come from [[Feature-to-Feature Link Graph]] typed links. Clicking a node opens the feature detail panel from [[Experimental Feature Detail Overview Tab Layout]]."
+
+Print a brief summary of links created.
+
+---
+
 ### Step 6: Report
 
 Print a compact summary:
@@ -122,6 +171,7 @@ Feature sync complete:
 - Title: [feature title]
 - ID: [full UUID]
 - Criteria: N
+- Links: N feature-to-feature links created (list the linked feature titles)
 ```
 
 ---

package/commands/rb/validate-card.md

@@ -2,6 +2,8 @@
 name: rb:validate-card
 description: Validate all acceptance criteria of a board card using Playwright browser automation, submit a formal validation report, move the card to done if all criteria pass, or post a failure comment and return the card to in-progress if any criteria fail
 argument-hint: "<cardId or card title>"
+user-invocable: true
+disable-model-invocation: true
 allowed-tools:
   - mcp__playwright__browser_navigate
   - mcp__playwright__browser_snapshot

package/commands/rb/validate-feature.md

@@ -2,6 +2,8 @@
 name: rb:validate-feature
 description: Validate all acceptance criteria of a feature using Playwright browser automation, create bug cards for failures, and submit a formal validation report
 argument-hint: "<featureId or feature title>"
+user-invocable: true
+disable-model-invocation: true
 allowed-tools:
   - mcp__playwright__browser_navigate
   - mcp__playwright__browser_snapshot

package/package.json

@@ -1,13 +1,14 @@
 {
   "name": "@rayburst/cc",
-  "version": "1.0.28",
+  "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"
   },
   "files": [
     "bin",
-    "commands"
+    "commands",
+    ".claude-plugin"
   ],
   "keywords": [
     "claude",