kiro-agents 1.15.2 → 1.15.4

package/build/npm/bin/cli.js

@@ -45,12 +45,17 @@ var POWER_FILES = [
   "steering/reflect-manager-workflow.md",
   "steering/reflect-curator-checklist.md",
   "steering/reflect-agent-insights.md",
+  "steering/mode-switching.md",
+  "steering/mode-management.md",
   "steering/kiro-vibe-mode.md",
   "steering/kiro-spec-mode.md",
   "steering/kiro-as-vibe-mode.md",
   "steering/kiro-as-spec-mode.md",
   "steering/explainability-protocol.md",
-  "steering/chit-chat.md"
+  "steering/chit-chat.md",
+  "steering/agent-management.md",
+  "steering/agent-creation.md",
+  "steering/agent-activation.md"
 ];
 async function setWritable(filePath) {
   try {
@@ -90,9 +95,23 @@ async function extractPowerMetadata(powerMdPath) {
     author: extractField(/^author:\s*["']?([^"'\n]+)["']?$/m, "")
   };
 }
+async function copyRecursive(src, dest) {
+  const { stat, readdir, mkdir, copyFile } = await import("fs/promises");
+  const stats = await stat(src);
+  if (stats.isDirectory()) {
+    await mkdir(dest, { recursive: true });
+    const entries = await readdir(src);
+    for (const entry of entries) {
+      await copyRecursive(join(src, entry), join(dest, entry));
+    }
+  } else {
+    await copyFile(src, dest);
+  }
+}
 async function createSymbolicLinks() {
   const { readdir, mkdir, symlink, rm, stat } = await import("fs/promises");
   const { platform } = await import("os");
+  let warningCount = 0;
   if (existsSync(POWER_INSTALLED_DIR)) {
     await rm(POWER_INSTALLED_DIR, { recursive: true, force: true });
   }
@@ -111,9 +130,16 @@ async function createSymbolicLinks() {
       }
       console.log(`✅ Linked: ${entry}`);
     } catch (error) {
-      console.warn(`⚠️  Could not link ${entry}:`, error instanceof Error ? error.message : error);
+      try {
+        await copyRecursive(sourcePath, targetPath);
+        console.log(`\uD83D\uDCCB Copied: ${entry} (symlink not available)`);
+      } catch (copyError) {
+        console.warn(`⚠️  Could not link or copy ${entry}:`, error instanceof Error ? error.message : error);
+        warningCount++;
+      }
     }
   }
+  return warningCount;
 }
 async function registerPowerInRegistry() {
   const { readFile, writeFile, mkdir } = await import("fs/promises");
@@ -163,6 +189,7 @@ async function registerPowerInRegistry() {
   registry.lastUpdated = new Date().toISOString();
   await writeFile(REGISTRY_PATH, JSON.stringify(registry, null, 2), "utf-8");
   console.log("✅ Power registered in Kiro registry");
+  return true;
 }
 async function installFile(relativePath, installDir, sourceDir) {
   const destPath = join(installDir, relativePath);
@@ -181,6 +208,8 @@ async function installFile(relativePath, installDir, sourceDir) {
 async function install() {
   console.log(`\uD83D\uDE80 Installing kiro-agents system...
 `);
+  let hasErrors = false;
+  let hasWarnings = false;
   console.log("\uD83D\uDCC4 Installing steering files to ~/.kiro/steering/kiro-agents/");
   if (existsSync(STEERING_INSTALL_DIR)) {
     console.log("\uD83D\uDDD1️  Removing existing steering installation...");
@@ -203,23 +232,40 @@ async function install() {
   console.log(`
 \uD83D\uDD17 Creating symbolic links in installed/ directory...`);
   try {
-    await createSymbolicLinks();
+    const symlinkWarnings = await createSymbolicLinks();
+    if (symlinkWarnings > 0) {
+      hasWarnings = true;
+    }
   } catch (error) {
     console.warn("⚠️  Warning: Could not create symbolic links:", error instanceof Error ? error.message : error);
     console.warn("   Power may not appear correctly in Kiro Powers UI.");
+    hasWarnings = true;
   }
   console.log(`
 \uD83D\uDCDD Registering power in Kiro registry...`);
   try {
-    await registerPowerInRegistry();
+    const registrySuccess = await registerPowerInRegistry();
+    if (!registrySuccess) {
+      hasWarnings = true;
+    }
   } catch (error) {
     console.warn("⚠️  Warning: Could not register power in registry:", error instanceof Error ? error.message : error);
     console.warn("   The power files are installed but may not appear in Kiro Powers UI.");
     console.warn("   You can manually add the power via: Powers panel → Add Repository → Local Directory");
     console.warn(`   Path: ${POWER_INSTALL_DIR}`);
+    hasWarnings = true;
   }
-  console.log(`
+  if (hasErrors) {
+    console.log(`
+❌ Installation completed with errors!`);
+  } else if (hasWarnings) {
+    console.log(`
+⚠️  Installation completed with warnings!`);
+    console.log("   Core files installed successfully, but some optional features may not work.");
+  } else {
+    console.log(`
 ✨ Installation completed successfully!`);
+  }
   console.log(`
 \uD83D\uDCC1 Steering files: ${STEERING_INSTALL_DIR}`);
   console.log(`\uD83D\uDCC1 Power files: ${POWER_INSTALL_DIR}`);

package/build/npm/power/POWER.md

@@ -1,274 +1,33 @@
 ---
 name: "kiro-protocols"
 displayName: "Kiro Protocols"
-description: "Reusable protocol library for AI agents - Load step-by-step workflows on-demand for agent management, mode switching, and interactive patterns"
-keywords: ["protocols", "workflows", "agents", "modes", "procedures", "instructions"]
+description: "Steering file library - Reusable content loaded on-demand to minimize context overhead"
+keywords: ["protocol-library", "steering-library", "lazy-loading"]
 author: "R. Beltran"
 version: "1.0.0"
 ---
 
 # Kiro Protocols
 
-## Overview
+Steering file library providing reusable content loaded on-demand to minimize context overhead.
 
-A comprehensive library of reusable protocols (step-by-step workflows) that can be loaded on-demand by AI agents, steering documents, and other Kiro Powers. Each protocol provides detailed instructions for specific tasks like agent management, mode switching, and interactive patterns.
+## Usage
 
-**What are Protocols?**
-
-Protocols are detailed, step-by-step instruction documents that guide AI through complex workflows. Instead of embedding these instructions directly in every steering document, protocols are loaded dynamically only when needed, reducing context overhead and improving maintainability.
-
-**Key Benefits:**
-- **On-Demand Loading** - Protocols load only when needed, minimizing context
-- **Single Source of Truth** - One protocol, many consumers
-- **Reusable Across Powers** - Any power can reference these protocols
-- **Maintainable** - Update once, affects all consumers
-- **Extensible** - Easy to add new protocols
-
-## Available Protocols
-
-This power provides the following protocols as steering files:
-
-### Core Protocols
-
-- **strict-mode** - Precision mode for experimental/cutting-edge development
-  - Blocks execution on ambiguous input
-  - Mandatory clarification before proceeding
-  - Prevents assumption propagation
-  - Opt-in via `/strict on` command
-
-### Agent System Protocols
-
-- **agent-activation** - Protocol for activating and assuming agent roles
-  - Loads agent definition
-  - Applies agent protocols
-  - Begins agent interaction
-
-- **agent-management** - Interactive agent management workflow
-  - Chit-chat mode interface
-  - Agent directory scanning
-  - Create, activate, manage, and view agents
-
-- **agent-creation** - Step-by-step agent creation wizard
-  - Gather agent information
-  - Generate agent definition
-  - Validate and finalize
-
-### Mode System Protocols
-
-- **mode-switching** - Protocol for switching between Kiro modes
-  - Load mode definition
-  - Preserve context
-  - Handle workflow state transitions
-
-- **mode-management** - Interactive mode management workflow
-  - Mode selection interface
-  - Mode comparison
-  - Help and documentation
-
-## How to Use Protocols
-
-### Method 1: Direct Steering File Load (Recommended)
-
-Use Kiro's built-in power tools to load protocols on-demand:
-
-```markdown
-**Load protocol:**
-1. Call kiroPowers action="activate" with powerName="kiro-protocols"
-2. Call kiroPowers action="readSteering" with powerName="kiro-protocols", steeringFile="agent-activation.md"
-3. Follow all steps from the loaded protocol
-```
-
-**Example in steering document:**
-```markdown
-When user activates agent:
-1. Load agent-activation protocol from kiro-protocols power
-2. Execute protocol steps with agent name as parameter
-3. Agent assumes role and begins interaction
-```
-
-### Method 2: Instruction Alias Pattern
-
-Create reusable aliases that load protocols:
-
-```markdown
-<alias>
-  <trigger>/protocol {protocol_name}</trigger>
-  <definition>
-## Load Protocol: {protocol_name}
-
-**Execute protocol loading:**
-1. Call kiroPowers action="activate" with powerName="kiro-protocols"
-2. Call kiroPowers action="readSteering" with powerName="kiro-protocols", steeringFile="{protocol_name}.md"
-3. Follow all steps from the loaded protocol
-  </definition>
-</alias>
-```
-
-### Method 3: Programmatic Reference
-
-Reference protocols in your steering documents:
-
-```markdown
-**When creating new agent:**
-- Load `agent-creation.md` protocol from kiro-protocols power
-- Follow wizard steps to gather information
-- Generate agent definition file
-- Validate and offer activation
-```
-
-## Protocol Structure
-
-Each protocol follows a consistent structure:
-
-```markdown
-# Protocol Name
-
-Brief description of what this protocol does.
-
-## Protocol Steps
-
-### Step 1: [Action Name]
-
-Detailed instructions for this step...
-
-### Step 2: [Action Name]
-
-Detailed instructions for this step...
-
-[Additional steps...]
-
----
-
-**Protocol complete. [Next action guidance]**
-```
-
-## Best Practices
-
-### For Protocol Consumers
-
-1. **Load on-demand** - Only load protocols when needed
-2. **Follow steps sequentially** - Protocols are designed as ordered workflows
-3. **Preserve context** - Protocols may reference previous steps
-4. **Handle errors gracefully** - Protocols include error handling guidance
-
-### For Protocol Authors
-
-1. **Keep focused** - One protocol, one workflow
-2. **Be explicit** - Clear, actionable steps
-3. **Include examples** - Show expected inputs/outputs
-4. **Document dependencies** - List required context or prerequisites
-5. **Version carefully** - Breaking changes affect all consumers
-
-## Creating Custom Protocols
-
-Want to add your own protocols to this power?
-
-1. **Fork the repository** - https://github.com/Theadd/kiro-agents
-2. **Add protocol file** - Create `.md` file in `src/core/protocols/`
-3. **Follow structure** - Use existing protocols as templates
-4. **Build and test** - Run build script and test in Kiro IDE
-5. **Submit PR** - Contribute back to the community
-
-## Integration Examples
-
-### Example 1: Agent System
-
-```markdown
-# agents.md (steering document)
-
-When user types `/agents {name}`:
-1. Load agent-activation protocol
-2. Pass agent name as parameter
-3. Execute protocol steps
-4. Agent activates and assumes role
-```
-
-### Example 2: Mode System
+Load steering files on-demand via instruction aliases or direct kiroPowers calls:
 
 ```markdown
-# modes.md (steering document)
-
-When user types `/modes {mode}`:
-1. Load mode-switching protocol
-2. Pass mode name as parameter
-3. Check for workflow state preservation
-4. Execute mode switch
+/protocols agent-activation.md
+/only-read-protocols chit-chat.md
 ```
 
-### Example 3: Custom Power
+Or directly:
 
 ```markdown
-# my-custom-power/steering/workflow.md
-
-When complex workflow needed:
-1. Load agent-management protocol from kiro-protocols
-2. Use interactive chit-chat pattern
-3. Guide user through multi-step process
-4. Apply custom power logic
+kiroPowers action="readSteering" powerName="kiro-protocols" steeringFile="agent-activation.md"
 ```
 
-## Troubleshooting
-
-### Protocol Not Found
-
-**Problem:** Error loading protocol file
-
-**Solutions:**
-1. Verify kiro-protocols power is installed
-2. Check protocol name spelling (case-sensitive)
-3. Ensure protocol exists in available list above
-4. Try reloading power: Kiro Powers panel → Reload
-
-### Protocol Outdated
-
-**Problem:** Protocol references old paths or commands
-
-**Solutions:**
-1. Update kiro-protocols power to latest version
-2. Check GitHub releases for breaking changes
-3. Review protocol changelog in repository
-
-### Context Overflow
-
-**Problem:** Too many protocols loaded at once
-
-**Solutions:**
-1. Load protocols only when needed (not upfront)
-2. Use on-demand loading pattern
-3. Consider splitting complex workflows
-4. Unload unused protocols from context
-
-## Version Compatibility
-
-This power follows semantic versioning:
-
-- **Major version** - Breaking changes to protocol structure
-- **Minor version** - New protocols added
-- **Patch version** - Bug fixes and clarifications
-
-**Current Version:** 1.0.0
-
-**Compatibility:**
-- Kiro IDE: All versions with Powers support
-- kiro-agents: v1.6.0+
-
-## Contributing
-
-Contributions welcome! See repository for guidelines:
-- https://github.com/Theadd/kiro-agents
-
-**Ways to contribute:**
-1. Report issues with existing protocols
-2. Suggest new protocols
-3. Improve protocol documentation
-4. Submit protocol enhancements
-
-## License
-
-MIT License - See repository for full license text
+**Note:** No activation needed - protocols are steering files, not MCP tools.
 
 ---
 
-**Power:** kiro-protocols  
-**Repository:** https://github.com/Theadd/kiro-agents  
-**Version:** 1.0.0
+**Repository:** https://github.com/Theadd/kiro-agents

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "kiro-agents",
-  "version": "1.15.2",
+  "version": "1.15.4",
   "description": "Advanced AI agent system for Kiro IDE - Create specialized AI agents, switch interaction modes, and enhance development workflows with minimal cognitive overhead",
   "homepage": "https://github.com/Theadd/kiro-agents#readme",
   "repository": {