project-iris 0.1.1 → 0.2.0

package/flows/aidlc/agents/inception-agent.md

@@ -116,25 +116,25 @@ Only stop at designated checkpoints (1-5 above).
 ## Artifacts Created
 
 - **Requirements** → `{intent}/requirements.md`
-  Template: `templates/inception/requirements-template.md`
+  Template: `.iris/aidlc/templates/inception/requirements-template.md`
 
 - **Risks** → `{intent}/risks.md`
-  Template: `templates/inception/risks-template.md`
+  Template: `.iris/aidlc/templates/inception/risks-template.md`
 
 - **System Context** → `{intent}/system-context.md`
-  Template: `templates/inception/system-context-template.md`
+  Template: `.iris/aidlc/templates/inception/system-context-template.md`
 
 - **Units** → `{intent}/units.md`
-  Template: `templates/inception/units-template.md`
+  Template: `.iris/aidlc/templates/inception/units-template.md`
 
 - **Unit Brief** → `{intent}/units/{unit}/unit-brief.md`
-  Template: `templates/inception/unit-brief-template.md`
+  Template: `.iris/aidlc/templates/inception/unit-brief-template.md`
 
 - **Stories** → `{intent}/units/{unit}/stories/`
-  Template: `templates/inception/stories-template.md`
+  Template: `.iris/aidlc/templates/inception/stories-template.md`
 
 - **Bolt Instances** → `memory-bank/bolts/bolt-{unit}-{N}/bolt.md`
-  Template: `templates/construction/bolt-template.md`
+  Template: `.iris/aidlc/templates/construction/bolt-template.md`
 
 ---
 

package/flows/aidlc/skills/construction/bolt-replan.md

@@ -355,8 +355,8 @@ After splitting 002-auth-service:
 
 After replanning:
 
-- → **Bolt Start** (`.iris/skills/construction/bolt-start.md`) - continue execution
-- → **Bolt Status** (`.iris/skills/construction/bolt-status.md`) - verify changes
+- → **Bolt Start** (`.iris/aidlc/skills/construction/bolt-start.md`) - continue execution
+- → **Bolt Status** (`.iris/aidlc/skills/construction/bolt-status.md`) - verify changes
 - → **Inception Agent** - if major scope change requires new stories
 
 ---

package/flows/aidlc/skills/construction/bolt-status.md

@@ -195,8 +195,8 @@ All {n} stories implemented and tested.
 
 After viewing status:
 
-- → **Bolt Start** (`.iris/skills/construction/bolt-start.md`) - continue the bolt
-- → **Bolt List** (`.iris/skills/construction/bolt-list.md`) - view other bolts
+- → **Bolt Start** (`.iris/aidlc/skills/construction/bolt-start.md`) - continue the bolt
+- → **Bolt List** (`.iris/aidlc/skills/construction/bolt-list.md`) - view other bolts
 - → **Operations Agent** - if all bolts for unit are complete
 
 ---

package/flows/aidlc/skills/master/analyze-context.md

@@ -254,8 +254,8 @@ Provide a structured analysis:
 
 After analysis, either:
 
-- → **Route Request** (`.iris/skills/master/route-request.md`) - to direct user to specialist agent
-- → **Answer Question** (`.iris/skills/master/answer-question.md`) - if user has questions about state
+- → **Route Request** (`.iris/aidlc/skills/master/route-request.md`) - to direct user to specialist agent
+- → **Answer Question** (`.iris/aidlc/skills/master/answer-question.md`) - if user has questions about state
 
 ---
 

package/flows/aidlc/skills/master/answer-question.md

@@ -150,8 +150,8 @@ I couldn't find information about "{topic}" in the memory bank.
 
 After answering:
 
-- → **Route Request** (`.iris/skills/master/route-request.md`) - if user wants to take action
-- → **Analyze Context** (`.iris/skills/master/analyze-context.md`) - if user wants overall status
+- → **Route Request** (`.iris/aidlc/skills/master/route-request.md`) - if user wants to take action
+- → **Analyze Context** (`.iris/aidlc/skills/master/analyze-context.md`) - if user wants overall status
 - → Stay in Q&A mode if user has more questions
 
 ---

package/flows/aidlc/skills/master/explain-flow.md

@@ -168,8 +168,8 @@ Provide a tailored explanation based on the user's question:
 
 After explanation:
 
-- → **Route Request** (`.iris/skills/master/route-request.md`) - if user wants to proceed
-- → **Answer Question** (`.iris/skills/master/answer-question.md`) - if user has more questions
+- → **Route Request** (`.iris/aidlc/skills/master/route-request.md`) - if user wants to proceed
+- → **Answer Question** (`.iris/aidlc/skills/master/answer-question.md`) - if user has more questions
 
 ---
 

package/flows/aidlc/skills/master/project-init.md

@@ -196,7 +196,7 @@ Before creating new standards, check if any exist:
 
 For each required/recommended standard:
 
-1. **Load the facilitation guide** from `templates/standards/{standard}.guide.md`
+1. **Load the facilitation guide** from `.iris/aidlc/templates/standards/{standard}.guide.md`
 2. **Follow the guide's discovery process** - don't invent your own questions
 3. **Adapt to user expertise** - be concise with experts, explanatory with newcomers
 4. **Confirm before saving** - summarize choices, get approval
@@ -389,8 +389,8 @@ If trying to create a standard before its dependency:
 
 After project initialization:
 
-- → **Inception Agent** (`.iris/agents/inception-agent.md`) - to create first intent
-- → **Analyze Context** (`.iris/skills/master/analyze-context.md`) - if user wants to see project state
+- → **Inception Agent** (`.iris/aidlc/agents/inception-agent.md`) - to create first intent
+- → **Analyze Context** (`.iris/aidlc/skills/master/analyze-context.md`) - if user wants to see project state
 - → **Project Init** again - to add optional standards later
 
 ---

package/flows/aidlc/skills/master/route-request.md

@@ -136,8 +136,8 @@ After routing:
 
 If user declines routing:
 
-- → **Answer Question** (`.iris/skills/master/answer-question.md`) - clarify their needs
-- → **Explain Flow** (`.iris/skills/master/explain-flow.md`) - explain the methodology
+- → **Answer Question** (`.iris/aidlc/skills/master/answer-question.md`) - clarify their needs
+- → **Explain Flow** (`.iris/aidlc/skills/master/explain-flow.md`) - explain the methodology
 
 ---
 

package/flows/aidlc/skills/operations/verify.md

@@ -234,8 +234,8 @@ On failure:
 
 After verification:
 
-- → **Monitor** (`.iris/skills/operations/monitor.md`) - if verified and final environment
-- → **Deploy** (`.iris/skills/operations/deploy.md`) - to next environment if verified
+- → **Monitor** (`.iris/aidlc/skills/operations/monitor.md`) - if verified and final environment
+- → **Deploy** (`.iris/aidlc/skills/operations/deploy.md`) - to next environment if verified
 - → **Rollback** - if verification fails (deploy previous version)
 
 ---

package/lib/installer.js

@@ -2,6 +2,7 @@ const fs = require('fs-extra');
 const path = require('path');
 const prompts = require('prompts');
 const yaml = require('js-yaml');
+const { execSync } = require('child_process');
 const CLIUtils = require('./cli-utils');
 const InstallerFactory = require('./InstallerFactory');
 const { FLOWS } = require('./constants');
@@ -67,6 +68,73 @@ async function detectTools() {
   return detected;
 }
 
+// VS Code-based tools that can use the iris Dashboard extension
+const VSCODE_TOOLS = ['claude', 'cursor', 'copilot', 'windsurf', 'cline', 'roo', 'antigravity'];
+
+/**
+ * Install VS Code extension if any VS Code-based tool is selected
+ * @param {string[]} selectedToolKeys - Selected tool keys
+ * @returns {boolean} Whether extension was installed
+ */
+async function installVSCodeExtension(selectedToolKeys) {
+  // Check if any VS Code-based tool is selected
+  const hasVSCodeTool = selectedToolKeys.some(key => VSCODE_TOOLS.includes(key));
+  if (!hasVSCodeTool) {
+    return false;
+  }
+
+  const extensionPath = path.join(__dirname, '..', 'extensions', 'iris-dashboard-0.0.1.vsix');
+
+  // Check if extension file exists
+  if (!await fs.pathExists(extensionPath)) {
+    console.log(theme.dim('  VS Code extension not found, skipping...'));
+    return false;
+  }
+
+  console.log(theme.dim('  Installing iris Dashboard VS Code extension...'));
+
+  try {
+    // Try 'code' command first (VS Code), then 'cursor' for Cursor
+    let installed = false;
+
+    // Try VS Code
+    try {
+      execSync(`code --install-extension "${extensionPath}" --force`, {
+        stdio: 'pipe',
+        timeout: 30000
+      });
+      installed = true;
+      CLIUtils.displayStatus('', 'Installed iris Dashboard extension for VS Code', 'success');
+    } catch {
+      // VS Code not available or failed
+    }
+
+    // Try Cursor if selected
+    if (selectedToolKeys.includes('cursor')) {
+      try {
+        execSync(`cursor --install-extension "${extensionPath}" --force`, {
+          stdio: 'pipe',
+          timeout: 30000
+        });
+        installed = true;
+        CLIUtils.displayStatus('', 'Installed iris Dashboard extension for Cursor', 'success');
+      } catch {
+        // Cursor not available or failed
+      }
+    }
+
+    if (!installed) {
+      console.log(theme.dim('  Could not auto-install extension. Install manually:'));
+      console.log(theme.dim(`    code --install-extension "${extensionPath}"`));
+    }
+
+    return installed;
+  } catch (error) {
+    console.log(theme.dim(`  Extension install skipped: ${error.message}`));
+    return false;
+  }
+}
+
 async function install() {
   // Initialize analytics (respects opt-out env vars)
   analytics.init();
@@ -153,6 +221,9 @@ async function install() {
   try {
     const filesCreated = await installFlow(selectedFlow, selectedToolKeys);
 
+    // Install VS Code extension if applicable
+    await installVSCodeExtension(selectedToolKeys);
+
     // Track successful installation for each tool
     const durationMs = Date.now() - installStartTime;
     for (const toolKey of selectedToolKeys) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "project-iris",
-  "version": "0.1.1",
+  "version": "0.2.0",
   "description": "Multi-agent orchestration system for AI-native software development. Delivers AI-DLC, Agile, and custom SDLC flows as markdown-based agent systems.",
   "main": "lib/installer.js",
   "bin": {
@@ -34,6 +34,7 @@
   },
   "files": [
     "bin/",
+    "extensions/",
     "flows/",
     "lib/",
     "scripts/",