ma-agents 3.1.0 → 3.3.0

package/lib/bmad-extension/workflows/add-to-sprint/workflow.md

@@ -1,206 +1,4 @@
-# Add-to-Sprint Workflow
+<!-- This workflow has been superseded by lib/bmad-extension/skills/add-to-sprint/SKILL.md -->
+<!-- Resolved via skill:add-to-sprint in module-help.csv -->
 
-Guided workflow to assign backlog items (stories + bugs) to a sprint using multi-criteria prioritization.
-
-<workflow>
-
-<step n="1a" goal="Discover user story backlog items from sprint-status.yaml">
-  <action>Read `_bmad-output/implementation-artifacts/sprint-status.yaml` — authoritative source for user story execution status</action>
-  <action>Parse the development_status section. For each entry:
-    - Skip epic keys (keys matching `epic-*`)
-    - Skip retrospective keys (keys ending with `-retrospective`)
-    - Collect story keys and their current status (backlog, ready-for-dev, in-progress, review, done)
-  </action>
-  <action>Store as {{user_stories}} — list of objects with: key, status</action>
-  <action>Infer story title from key (e.g., `12-1-add-sprint-workflow` → "Add Sprint Workflow")</action>
-</step>
-
-<step n="1b" goal="Discover bug story backlog items">
-  <action>Glob `_bmad-output/implementation-artifacts/bug-*.md` to discover all bug story files</action>
-  <check if="no bug files found">
-    <action>Set {{bug_stories}} = [] (empty list)</action>
-  </check>
-  <check if="bug files found">
-    <action>For each bug file, parse YAML frontmatter to extract: `type`, `severity`, `title`</action>
-    <action>Store as {{bug_stories}} — list of objects with: file, type (bug), severity, title</action>
-  </check>
-</step>
-
-<step n="1c" goal="Filter out items already assigned to any sprint">
-  <action>Glob `_bmad-output/implementation-artifacts/sprint-plan-*.yaml` to discover all existing sprint artifact files</action>
-  <action>For each sprint file found, read its assigned_items list</action>
-  <action>Build {{all_assigned_items}} = flat set of every item identifier (story keys and bug basenames) across ALL sprint plans</action>
-  <action>Filter {{user_stories}}: remove any story whose key is present in {{all_assigned_items}}</action>
-  <action>Filter {{bug_stories}}: remove any bug whose file basename is present in {{all_assigned_items}}</action>
-  <action>Items already assigned to any sprint will NOT appear in the backlog — this prevents duplicate assignment</action>
-  <check if="no sprint files found">
-    <action>Set {{all_assigned_items}} = [] — no filtering needed when no sprints exist yet</action>
-  </check>
-</step>
-
-<step n="2" goal="Present flat backlog combining stories and bugs">
-  <action>Combine {{user_stories}} and {{bug_stories}} into a flat backlog list</action>
-  <action>Stories and bugs are peers — no epic grouping (FR65)</action>
-  <output>
-## 📋 Backlog Items
-
-| # | ID / File | Title | Type | Status/Severity |
-|---|---|---|---|---|
-{{#each backlog_items}}
-| {{@index+1}} | {{id}} | {{title}} | {{type}} | {{status_or_severity}} |
-{{/each}}
-
-*Total: {{story_count}} stories, {{bug_count}} bugs*
-  </output>
-</step>
-
-<step n="3" goal="List available sprints and select target sprint">
-  <action>Glob `_bmad-output/implementation-artifacts/sprint-plan-*.yaml` to discover all sprint artifact files</action>
-  <check if="no sprint files found">
-    <output>❌ No sprint plans found. Run `/add-sprint` first to create a sprint before assigning items.</output>
-    <action>Exit workflow</action>
-  </check>
-  <action>For each sprint file found, read and extract: sprint_number, sprint_name, capacity, assigned_items count, status</action>
-  <output>
-## 🏃 Available Sprints
-
-| # | Sprint | Status | Capacity | Assigned | Remaining |
-|---|---|---|---|---|---|
-{{#each sprints}}
-| {{@index+1}} | {{sprint_name}} | {{status}} | {{capacity}} | {{assigned_count}} | {{remaining}} |
-{{/each}}
-  </output>
-  <ask>Select target sprint (enter number):</ask>
-  <action>Store selected sprint data as {{target_sprint}}</action>
-</step>
-
-<step n="4" goal="Display current sprint capacity usage">
-  <action>Calculate: {{assigned_count}} = length of {{target_sprint.assigned_items}}</action>
-  <action>Calculate: {{remaining_capacity}} = {{target_sprint.capacity}} - {{assigned_count}}</action>
-  <output>
-## Sprint Capacity: {{target_sprint.sprint_name}}
-
-- **Capacity:** {{target_sprint.capacity}} items
-- **Assigned:** {{assigned_count}} items
-- **Remaining:** {{remaining_capacity}} slots
-
-{{#if remaining_capacity <= 0}}
-⚠️ This sprint is **at or over capacity**. Adding items will exceed the limit.
-{{/if}}
-  </output>
-</step>
-
-<step n="5" goal="Select candidate items for this sprint">
-  <ask>Which backlog items do you want to consider for this sprint? Enter item numbers (comma-separated), or "all" to evaluate the full backlog:</ask>
-  <check if="user enters 'all'">
-    <action>Set {{candidate_items}} = all items in {{backlog_items}} (the full filtered backlog list from step 2)</action>
-  </check>
-  <check if="user enters item numbers">
-    <action>Resolve the entered numbers against the backlog table from step 2 and set {{candidate_items}} = those specific items</action>
-  </check>
-</step>
-
-<step n="6" goal="Multi-criteria prioritization guidance">
-  <action>For each item in {{candidate_items}}, evaluate and score across criteria:
-    - **Business value:** High (H) / Medium (M) / Low (L) — impact on users or project goals
-    - **Dependency status:** Blocked (blocked by another item) / Blocking (blocks other items) / Independent
-    - **Severity** (bugs only): Critical / High / Medium / Low — N/A for stories
-    - **Effort estimation:** Small (S ≤ 1 day) / Medium (M 2–3 days) / Large (L 4+ days)
-  </action>
-  <action>Generate a ranked ordering recommendation, factoring in:
-    1. Blocking dependencies first (items that unlock others)
-    2. High business value + low/medium effort (quick wins)
-    3. Critical/High bugs ahead of Medium/Low bugs
-    4. Avoid blocked items unless capacity allows waiting
-  </action>
-  <output>
-## 🎯 Prioritization Analysis
-
-| Rank | ID / File | Title | Type | Business Value | Dependencies | Severity | Effort | Rationale |
-|---|---|---|---|---|---|---|---|---|
-{{#each ranked_items}}
-| {{rank}} | {{id}} | {{title}} | {{type}} | {{business_value}} | {{dependency_status}} | {{severity}} | {{effort}} | {{rationale}} |
-{{/each}}
-
-**Recommended selection** (up to {{remaining_capacity}} items to stay within capacity): {{recommended_selection}}
-  </output>
-</step>
-
-<step n="7" goal="User confirms or adjusts ranking">
-  <ask>Review the ranking above. Options:
-- [c] Confirm recommended selection as-is
-- [m] Modify selection (specify item numbers to include)
-- [r] Re-rank items (provide new priority order)
-- [x] Cancel without assigning
-
-Choice:</ask>
-  <check if="user selects 'x'">
-    <output>❌ Assignment cancelled — no changes made.</output>
-    <action>Exit workflow</action>
-  </check>
-  <check if="user selects 'm'">
-    <ask>Enter item numbers to assign (comma-separated):</ask>
-    <action>Update {{confirmed_items}} with user selection</action>
-  </check>
-  <check if="user selects 'r'">
-    <ask>Enter item numbers in your preferred priority order (comma-separated). Only items you include will be assigned — items not listed will be excluded from this session and remain in the unassigned backlog:</ask>
-    <action>Set {{confirmed_items}} = only the items matching the user-provided numbers, in the order provided. Items from {{candidate_items}} NOT mentioned are excluded from assignment in this session (they remain available in the backlog for future sprints).</action>
-  </check>
-  <check if="user selects 'c'">
-    <action>Set {{confirmed_items}} = recommended selection</action>
-  </check>
-  <action>Store confirmed ranking in {{confirmed_ranking}} for auditability (included in workflow output)</action>
-</step>
-
-<step n="8" goal="Assign selected items to sprint with capacity enforcement">
-  <action>For each item in {{confirmed_items}}, in confirmed ranking order:</action>
-  <action>Re-calculate current assigned count (in case multiple items are being added)</action>
-  <check if="assigning this item would exceed capacity">
-    <output>⚠️ **Capacity Warning:** Adding "{{item.title}}" would bring assigned items to {{new_count}}/{{target_sprint.capacity}} — exceeding sprint capacity by {{overage}}.</output>
-    <ask>Options:
-- [a] Add anyway (over-capacity acknowledged)
-- [s] Skip this item
-- [m] Modify sprint capacity first via `/modify-sprint`
-
-Choice:</ask>
-    <check if="user selects 's'">
-      <action>Skip this item — do not add to sprint. Continue to next item in the {{confirmed_items}} loop.</action>
-    </check>
-    <check if="user selects 'm'">
-      <output>💡 Run `/modify-sprint` to increase capacity for {{target_sprint.sprint_name}}, then re-run `/add-to-sprint`.</output>
-      <action>Exit workflow</action>
-    </check>
-  </check>
-  <action>Add item identifier to {{target_sprint.assigned_items}} list in the sprint-plan-{{target_sprint.sprint_number}}.yaml artifact</action>
-  <action>Item identifier format: story key for user stories (e.g., `12-1-add-sprint-workflow`), file basename for bugs (e.g., `bug-login-crash`)</action>
-</step>
-
-<step n="9" goal="Persist changes and display confirmed ranking for auditability">
-  <action>Update `_bmad-output/implementation-artifacts/sprint-plan-{{target_sprint.sprint_number}}.yaml`:
-    - Update `assigned_items` list with all newly assigned item identifiers
-    - Update `last_modified` to current ISO timestamp
-  </action>
-  <action>**Do NOT modify sprint-status.yaml** — sprint membership is exclusively tracked in sprint-plan-{n}.yaml</action>
-  <output>
-## ✅ Assignment Complete
-
-**Sprint:** {{target_sprint.sprint_name}}
-**Items assigned this session:** {{assigned_this_session}}
-
-### Confirmed Ranking (Audit Record)
-
-| Rank | ID | Title | Type | Business Value | Dependencies | Severity | Effort |
-|---|---|---|---|---|---|---|---|
-{{#each confirmed_ranking}}
-| {{rank}} | {{id}} | {{title}} | {{type}} | {{business_value}} | {{dependency_status}} | {{severity}} | {{effort}} |
-{{/each}}
-
-**Updated Capacity:** {{new_assigned_count}}/{{target_sprint.capacity}} items used ({{new_remaining}} remaining)
-
-**Next Steps:**
-- Use `/modify-sprint` to adjust capacity or remove items
-- Use `/sprint-status-view` to view the full sprint with all assigned items
-  </output>
-</step>
-
-</workflow>
+See `lib/bmad-extension/skills/add-to-sprint/SKILL.md` for the current workflow.

package/lib/bmad-extension/workflows/modify-sprint/workflow.md

@@ -1,3 +1,8 @@
+<!-- DEPRECATED: This workflow references the old sprint-plan-{n}.yaml format.
+     It will be reworked in Story 17.4. Use /add-sprint to create sprints in the new format. -->
+
+> **DEPRECATED:** This workflow references the old `sprint-plan-{n}.yaml` format. It will be reworked in Story 17.4. Use `/add-sprint` to create sprints in the new format.
+
 # Modify Sprint Workflow
 
 Guided workflow to modify an existing sprint — add/remove items, change capacity, update metadata.

package/lib/bmad-extension/workflows/sprint-status-view/workflow.md

@@ -1,193 +1,4 @@
-# Sprint Status View Workflow
+<!-- This workflow has been superseded by lib/bmad-extension/skills/sprint-status-view/SKILL.md -->
+<!-- Resolved via skill:sprint-status-view in module-help.csv -->
 
-Extension workflow that displays sprint progress with assigned items (stories + bugs), type distinction, and remaining capacity.
-
-> **Architecture mandate:** This workflow is a NEW extension at `lib/bmad-extension/workflows/sprint-status-view/`. It does NOT modify any files under `_bmad/bmm/workflows/`.
-
-<workflow>
-
-<step n="1" goal="Discover all sprint artifact files">
-  <action>Glob `_bmad-output/implementation-artifacts/sprint-plan-*.yaml` to discover all sprint artifact files</action>
-  <check if="no sprint files found">
-    <output>
-ℹ️ **No Sprints Found**
-
-No sprint plan files exist yet (`sprint-plan-*.yaml`).
-
-**To get started:**
-- Run `/add-sprint` to create your first sprint
-- Run `/add-to-sprint` to assign backlog items to it
-    </output>
-    <action>Exit workflow</action>
-  </check>
-  <action>For each sprint file found, read the full YAML content and store as {{sprint_plans}} list</action>
-  <action>Sort {{sprint_plans}} by sprint_number ascending</action>
-</step>
-
-<step n="2" goal="Load sprint-status.yaml for user story execution statuses">
-  <action>Read `_bmad-output/implementation-artifacts/sprint-status.yaml`</action>
-  <check if="file not found">
-    <output>⚠️ `sprint-status.yaml` not found. User story execution statuses will not be available. Run `/sprint-planning` to initialize.</output>
-    <action>Set {{story_status_map}} = {} (empty — will show data integrity warnings per missing item)</action>
-  </check>
-  <check if="file found">
-    <action>Parse development_status section into {{story_status_map}} — key: story key, value: status</action>
-    <action>Exclude epic-* keys and *-retrospective keys from the map</action>
-  </check>
-</step>
-
-<step n="3" goal="Discover bug stories for type/severity data">
-  <action>Glob `_bmad-output/implementation-artifacts/bug-*.md` to discover all bug story files</action>
-  <check if="no bug files found">
-    <action>Set {{bug_metadata_map}} = {} (empty)</action>
-  </check>
-  <check if="bug files found">
-    <action>For each bug file, parse YAML frontmatter to extract: type, severity, title</action>
-    <action>Build {{bug_metadata_map}} — key: file basename (e.g., `bug-login-crash`), value: {severity, title}</action>
-  </check>
-</step>
-
-<step n="4" goal="Display sprint status for each sprint">
-  <action>For each sprint in {{sprint_plans}} (in order):</action>
-  <action>Calculate: {{assigned_count}} = length(sprint.assigned_items)</action>
-  <action>Calculate: {{remaining_capacity}} = sprint.capacity - {{assigned_count}}</action>
-
-  <action>For each item identifier in sprint.assigned_items, resolve item details:
-
-    **If item is a story (key matches regex `^\d+-\d+-.+`):**
-    - Look up status in {{story_status_map}}[item_key]
-    - If NOT found in {{story_status_map}}:
-      → Record as DATA INTEGRITY WARNING: "Item {item_key} has no status entry in sprint-status.yaml — run /sprint-planning to initialize status tracking for this item."
-      → Display item with marker: ⚠️ [status unknown]
-    - If found: display with current status label
-
-    **If item is a bug (key matches regex `^bug-.+`):**
-    - Look up in {{bug_metadata_map}}[item_key]
-    - If NOT found: display with title as item_key, severity as "unknown"
-    - If found: display with title and severity from frontmatter
-    - Bug execution status: use `status` from bug file frontmatter if present; otherwise "not-started"
-
-    **If item matches neither pattern:** display as type "Unknown" with raw identifier as title
-  </action>
-
-  <output>
----
-
-## 🏃 {{sprint.sprint_name}} (Sprint {{sprint.sprint_number}})
-
-**Status:** {{sprint.status}} | **Capacity:** {{sprint.capacity}} items | **Assigned:** {{assigned_count}} | **Remaining:** {{remaining_capacity}}
-{{#if sprint.start_context}}**Start:** {{sprint.start_context}}{{/if}} {{#if sprint.end_context}}| **End:** {{sprint.end_context}}{{/if}}
-
-{{#if over_capacity}}
-⚠️ **Over capacity by {{overage}} item(s)**
-{{/if}}
-
-### Assigned Items
-
-| Item | Title | Type | Status / Severity |
-|---|---|---|---|
-{{#each resolved_items}}
-{{#if is_story}}
-| {{item_key}} | {{title}} | 📋 Story | {{status}} |
-{{/if}}
-{{#if is_bug}}
-| {{item_key}} | {{title}} | 🐛 Bug | Severity: {{severity}} / {{bug_status}} |
-{{/if}}
-{{/each}}
-
-{{#if data_integrity_warnings}}
-**⚠️ Data Integrity Warnings:**
-{{#each data_integrity_warnings}}
-- {{this}}
-{{/each}}
-{{/if}}
-
-{{#if assigned_items_empty}}
-*(No items assigned to this sprint)*
-{{/if}}
-  </output>
-</step>
-
-<step n="5" goal="Display unassigned backlog summary">
-  <action>Collect all item keys from {{story_status_map}} that are NOT in any sprint's assigned_items list — these are unassigned user stories</action>
-  <action>Collect all bug basenames from {{bug_metadata_map}} that are NOT in any sprint's assigned_items list — these are unassigned bugs</action>
-  <action>Count unassigned stories by status: {{unassigned_by_status}}</action>
-  <output>
----
-
-## 📦 Unassigned Backlog
-
-### 📋 Unassigned Stories
-
-| Status | Count |
-|---|---|
-| backlog | {{count_backlog}} |
-| ready-for-dev | {{count_ready}} |
-| in-progress | {{count_in_progress}} |
-| review | {{count_review}} |
-| done | {{count_done}} |
-
-*Total unassigned stories: {{total_unassigned}}*
-
-### 🐛 Unassigned Bugs
-
-{{#if unassigned_bugs}}
-| ID / File | Title | Severity |
-|---|---|---|
-{{#each unassigned_bugs}}
-| {{id}} | {{title}} | {{severity}} |
-{{/each}}
-{{else}}
-*(No unassigned bugs)*
-{{/if}}
-
-**Tip:** Use `/add-to-sprint` to assign unassigned items to a sprint.
-  </output>
-</step>
-
-<step n="6" goal="Offer next actions">
-  <ask>Options:
-1. Show full unassigned backlog item list (IDs + titles + statuses)
-2. Add items to a sprint — run `/add-to-sprint`
-3. Modify a sprint — run `/modify-sprint`
-4. Create a new sprint — run `/add-sprint`
-5. Exit
-
-Choice:</ask>
-  <check if="choice == 1">
-    <action>For each unassigned story key in {{story_status_map}} not assigned to any sprint, display: key, inferred title, status</action>
-    <action>For each unassigned bug in {{bug_metadata_map}} not assigned to any sprint, display: id, title, severity</action>
-    <output>
-### Full Unassigned Backlog
-
-**Stories:**
-| Key | Title | Status |
-|---|---|---|
-{{#each unassigned_story_items}}
-| {{key}} | {{title}} | {{status}} |
-{{/each}}
-
-**Bugs:**
-| ID | Title | Severity |
-|---|---|---|
-{{#each unassigned_bugs}}
-| {{id}} | {{title}} | {{severity}} |
-{{/each}}
-    </output>
-    <goto step="6" />
-  </check>
-  <check if="choice == 2">
-    <output>▶️ Run `/add-to-sprint` to assign backlog items to a sprint.</output>
-  </check>
-  <check if="choice == 3">
-    <output>▶️ Run `/modify-sprint` to add/remove items or change sprint settings.</output>
-  </check>
-  <check if="choice == 4">
-    <output>▶️ Run `/add-sprint` to create a new sprint.</output>
-  </check>
-  <check if="choice == 5">
-    <action>Exit workflow</action>
-  </check>
-</step>
-
-</workflow>
+See `lib/bmad-extension/skills/sprint-status-view/SKILL.md` for the current workflow.

package/package.json

@@ -1,14 +1,14 @@
 {
   "name": "ma-agents",
-  "version": "3.1.0",
-  "description": "NPX tool to install skills for AI coding agents (Claude Code, Gemini, Copilot, Kilocode, Cline, Cursor)",
+  "version": "3.3.0",
+  "description": "NPX tool to install skills for AI coding agents (Claude Code, Gemini, Copilot, Kilocode, Cline, Cursor, Roo Code)",
   "main": "index.js",
   "bin": {
     "ma-agents": "bin/cli.js"
   },
   "scripts": {
     "start": "node bin/cli.js",
-    "test": "node test/yes-flag.test.js && node test/skill-authoring.test.js && node test/skill-validation.test.js && node test/skill-mandatory.test.js && node test/skill-customize-agent.test.js && node test/create-agent.test.js && node test/generate-project-context.test.js && node test/build-bmad-args.test.js && node test/bmad-version-bump.test.js && node test/extension-module-restructure.test.js && node test/convert-agents-to-skills.test.js && node test/migration.test.js && node test/migration-validation.test.js && node test/story-15-5-workflow-skills.test.js && node test/repo-layout.test.js && node test/config-storage.test.js && node test/cross-repo-validation.test.js && node test/config-lost-on-update.test.js && node test/portable-paths.test.js && node test/cicd-remote-mode.test.js && node test/config-layout.test.js",
+    "test": "node test/yes-flag.test.js && node test/skill-authoring.test.js && node test/skill-validation.test.js && node test/skill-mandatory.test.js && node test/skill-customize-agent.test.js && node test/create-agent.test.js && node test/generate-project-context.test.js && node test/build-bmad-args.test.js && node test/bmad-version-bump.test.js && node test/extension-module-restructure.test.js && node test/convert-agents-to-skills.test.js && node test/migration.test.js && node test/migration-validation.test.js && node test/story-15-5-workflow-skills.test.js && node test/repo-layout.test.js && node test/config-storage.test.js && node test/cross-repo-validation.test.js && node test/config-lost-on-update.test.js && node test/portable-paths.test.js && node test/cicd-remote-mode.test.js && node test/config-layout.test.js && node test/roo-code-agent.test.js && node test/roo-code-injection.test.js",
     "build:bmad-cache": "node scripts/build-bmad-cache.js"
   },
   "keywords": [
@@ -21,6 +21,7 @@
     "kilocode",
     "cline",
     "cursor",
+    "roo-code",
     "npx"
   ],
   "author": "",

package/test/roo-code-agent.test.js

@@ -0,0 +1,166 @@
+#!/usr/bin/env node
+/**
+ * Tests for Story 18.1: Register Roo Code Agent in Registry
+ *
+ * Validates that the roo-code agent entry conforms to the required schema
+ * and resolves correctly through the existing config-driven registry pattern.
+ */
+'use strict';
+
+const assert = require('assert');
+
+let passed = 0;
+let failed = 0;
+const errors = [];
+
+function test(name, fn) {
+  try {
+    fn();
+    console.log(`  \u2713 ${name}`);
+    passed++;
+  } catch (err) {
+    console.error(`  \u2717 ${name}: ${err.message}`);
+    failed++;
+    errors.push({ name, error: err.message });
+  }
+}
+
+const { getAllAgents, getAgent, getAgentsByCategory } = require('../lib/agents');
+const allAgents = getAllAgents();
+const rooCode = getAgent('roo-code');
+
+// --- Schema validation ---
+
+console.log('\nRoo Code agent schema validation');
+
+test('roo-code agent exists in registry', () => {
+  assert.ok(rooCode, 'roo-code agent should exist in the registry');
+});
+
+test('id is "roo-code"', () => {
+  assert.strictEqual(rooCode.id, 'roo-code');
+});
+
+test('name is "Roo Code"', () => {
+  assert.strictEqual(rooCode.name, 'Roo Code');
+});
+
+test('category is "ide"', () => {
+  assert.strictEqual(rooCode.category, 'ide');
+});
+
+test('getProjectPath is a function', () => {
+  assert.strictEqual(typeof rooCode.getProjectPath, 'function',
+    'getProjectPath should be a function');
+});
+
+test('getGlobalPath is a function', () => {
+  assert.strictEqual(typeof rooCode.getGlobalPath, 'function',
+    'getGlobalPath should be a function');
+});
+
+test('getProjectPath returns path ending in .roo/skills', () => {
+  const projectPath = rooCode.getProjectPath();
+  assert.ok(
+    projectPath.endsWith('.roo/skills') || projectPath.endsWith('.roo\\skills'),
+    `Expected path ending in .roo/skills, got: ${projectPath}`
+  );
+});
+
+test('getGlobalPath returns a non-empty string', () => {
+  const globalPath = rooCode.getGlobalPath();
+  assert.strictEqual(typeof globalPath, 'string');
+  assert.ok(globalPath.length > 0, 'getGlobalPath should return a non-empty string');
+});
+
+test('getGlobalPath contains roo-cline (VS Code extension storage convention)', () => {
+  const globalPath = rooCode.getGlobalPath();
+  assert.ok(
+    globalPath.includes('roo-cline'),
+    `Expected global path to contain 'roo-cline', got: ${globalPath}`
+  );
+});
+
+test('fileExtension is ".md"', () => {
+  assert.strictEqual(rooCode.fileExtension, '.md');
+});
+
+test('description is a non-empty string', () => {
+  assert.strictEqual(typeof rooCode.description, 'string',
+    'description should be a string');
+  assert.ok(rooCode.description.length > 0, 'description should not be empty');
+});
+
+test('description mentions Cline fork lineage', () => {
+  assert.ok(rooCode.description.includes('Cline'),
+    `description should mention Cline fork lineage, got: ${rooCode.description}`);
+});
+
+test('template is "generic"', () => {
+  assert.strictEqual(rooCode.template, 'generic');
+});
+
+test('skillsDir is ".roo/skills"', () => {
+  assert.strictEqual(rooCode.skillsDir, '.roo/skills');
+});
+
+test('instructionFiles is a non-empty array', () => {
+  assert.ok(Array.isArray(rooCode.instructionFiles),
+    'instructionFiles should be an array');
+  assert.ok(rooCode.instructionFiles.length > 0,
+    'instructionFiles should not be empty');
+});
+
+test('instructionFiles targets .roo/rules/ directory', () => {
+  const hasRooRules = rooCode.instructionFiles.some(f =>
+    f.includes('.roo/rules/') || f.includes('.roo\\rules\\')
+  );
+  assert.ok(hasRooRules,
+    `instructionFiles should target .roo/rules/ directory, got: ${rooCode.instructionFiles}`);
+});
+
+test('injectionStrategy is an object', () => {
+  assert.ok(rooCode.injectionStrategy && typeof rooCode.injectionStrategy === 'object',
+    'injectionStrategy should be an object');
+});
+
+test('injectionStrategy.position is "top"', () => {
+  assert.strictEqual(rooCode.injectionStrategy.position, 'top');
+});
+
+// --- Registry resolution ---
+
+console.log('\nRoo Code agent resolution');
+
+test('getAgent("roo-code") returns the agent', () => {
+  const resolved = getAgent('roo-code');
+  assert.ok(resolved, 'getAgent("roo-code") should return an agent object');
+  assert.strictEqual(resolved.id, 'roo-code');
+});
+
+test('roo-code appears in getAllAgents()', () => {
+  const ids = allAgents.map(a => a.id);
+  assert.ok(ids.includes('roo-code'), 'roo-code should appear in getAllAgents()');
+});
+
+test('roo-code is in the ide category', () => {
+  const ideAgents = getAgentsByCategory('ide');
+  const ids = ideAgents.map(a => a.id);
+  assert.ok(ids.includes('roo-code'), 'roo-code should be in ide category');
+});
+
+test('roo-code is distinct from cline', () => {
+  const cline = getAgent('cline');
+  assert.ok(cline, 'cline agent should still exist');
+  assert.notStrictEqual(cline.id, rooCode.id, 'roo-code and cline should be different agents');
+  assert.notStrictEqual(cline.skillsDir, rooCode.skillsDir,
+    'roo-code and cline should use different skills directories');
+});
+
+// Print summary
+console.log(`\n${passed} passed, ${failed} failed`);
+if (errors.length > 0) {
+  console.log('\nFailed tests:');
+  errors.forEach(e => console.log(`  - ${e.name}: ${e.error}`));
+}
+if (failed > 0) process.exit(1);