kiro-agents 1.15.3 → 2.0.0

package/README.md

@@ -78,7 +78,7 @@ Automatically installed alongside kiro-agents, this Power provides protocols (ag
 Protocols load only when needed, keeping your context clean. Base system uses just 1.35K tokens.
 
 **Your Agents, Your Files**
-Agents you create are saved as `.md` files in `.kiro/agents/`. Edit them like any document, version control them with git, reuse them across projects.
+Agents you create are saved as `.md` files in `.kiro/kiro-agents/`. Edit them like any document, version control them with git, reuse them across projects.
 
 ## Documentation
 

package/build/npm/bin/cli.js

@@ -28,7 +28,8 @@ var __dirname2 = dirname(__filename2);
 var STEERING_INSTALL_DIR = join(homedir(), ".kiro", "steering", "kiro-agents");
 var POWER_INSTALL_DIR = join(homedir(), ".kiro", "powers", "kiro-protocols");
 var POWER_INSTALLED_DIR = join(homedir(), ".kiro", "powers", "installed", "kiro-protocols");
-var REGISTRY_PATH = join(homedir(), ".kiro", "powers", "registry.json");
+var INSTALLED_JSON_PATH = join(homedir(), ".kiro", "powers", "installed.json");
+var USER_ADDED_JSON_PATH = join(homedir(), ".kiro", "powers", "registries", "user-added.json");
 var STEERING_FILES = [
   "aliases.md",
   "agents.md",
@@ -69,32 +70,6 @@ async function setReadOnly(filePath) {
     console.warn(`⚠️  Could not set read-only: ${filePath}`);
   }
 }
-async function extractPowerMetadata(powerMdPath) {
-  const { readFile } = await import("fs/promises");
-  const content = await readFile(powerMdPath, "utf-8");
-  const frontmatterMatch = content.match(/^---\n([\s\S]*?)\n---/);
-  if (!frontmatterMatch || !frontmatterMatch[1]) {
-    throw new Error("No frontmatter found in POWER.md");
-  }
-  const frontmatter = frontmatterMatch[1];
-  const extractField = (pattern, defaultValue) => {
-    const match = frontmatter.match(pattern);
-    return match && match[1] ? match[1].trim() : defaultValue;
-  };
-  const extractKeywords = () => {
-    const match = frontmatter.match(/^keywords:\s*\[(.*?)\]$/m);
-    if (!match || !match[1])
-      return [];
-    return match[1].split(",").map((k) => k.trim().replace(/["']/g, ""));
-  };
-  return {
-    name: extractField(/^name:\s*["']?([^"'\n]+)["']?$/m, "kiro-protocols"),
-    displayName: extractField(/^displayName:\s*["']?([^"'\n]+)["']?$/m, "Kiro Protocols"),
-    description: extractField(/^description:\s*["']?([^"'\n]+)["']?$/m, ""),
-    keywords: extractKeywords(),
-    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);
@@ -108,90 +83,73 @@ async function copyRecursive(src, dest) {
     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;
+async function installPowerFiles() {
+  const { readdir, mkdir, rm, stat, copyFile } = await import("fs/promises");
   if (existsSync(POWER_INSTALLED_DIR)) {
     await rm(POWER_INSTALLED_DIR, { recursive: true, force: true });
   }
   await mkdir(POWER_INSTALLED_DIR, { recursive: true });
   const entries = await readdir(POWER_INSTALL_DIR);
   for (const entry of entries) {
-    const sourcePath = join(POWER_INSTALL_DIR, entry);
-    const targetPath = join(POWER_INSTALLED_DIR, entry);
-    try {
-      const stats = await stat(sourcePath);
-      const isDirectory = stats.isDirectory();
-      if (platform() === "win32") {
-        await symlink(sourcePath, targetPath, isDirectory ? "junction" : "file");
-      } else {
-        await symlink(sourcePath, targetPath);
-      }
-      console.log(`✅ Linked: ${entry}`);
-    } catch (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++;
+    if (entry === "icon.png")
+      continue;
+    const srcPath = join(POWER_INSTALL_DIR, entry);
+    const destPath = join(POWER_INSTALLED_DIR, entry);
+    const stats = await stat(srcPath);
+    if (stats.isDirectory()) {
+      await copyRecursive(srcPath, destPath);
+      const subEntries = await readdir(destPath);
+      for (const subEntry of subEntries) {
+        await setReadOnly(join(destPath, subEntry));
       }
+    } else {
+      await copyFile(srcPath, destPath);
+      await setReadOnly(destPath);
     }
+    console.log(`✅ Installed: ${entry}`);
   }
-  return warningCount;
 }
-async function registerPowerInRegistry() {
+async function registerPower() {
   const { readFile, writeFile, mkdir } = await import("fs/promises");
-  const registryDir = dirname(REGISTRY_PATH);
-  await mkdir(registryDir, { recursive: true });
-  let registry;
-  if (existsSync(REGISTRY_PATH)) {
-    const content = await readFile(REGISTRY_PATH, "utf-8");
-    registry = JSON.parse(content);
+  await mkdir(dirname(USER_ADDED_JSON_PATH), { recursive: true });
+  let installed;
+  if (existsSync(INSTALLED_JSON_PATH)) {
+    const content = await readFile(INSTALLED_JSON_PATH, "utf-8");
+    installed = JSON.parse(content);
+  } else {
+    installed = { version: "1.0.0", installedPowers: [], dismissedAutoInstalls: [] };
+  }
+  const alreadyInstalled = installed.installedPowers.some((p) => p.name === "kiro-protocols");
+  if (!alreadyInstalled) {
+    installed.installedPowers.push({ name: "kiro-protocols", registryId: "user-added" });
+  }
+  await writeFile(INSTALLED_JSON_PATH, JSON.stringify(installed, null, 2), "utf-8");
+  let userAdded;
+  if (existsSync(USER_ADDED_JSON_PATH)) {
+    const content = await readFile(USER_ADDED_JSON_PATH, "utf-8");
+    userAdded = JSON.parse(content);
   } else {
-    registry = {
-      version: "1.0.0",
-      powers: {},
-      repoSources: {},
-      lastUpdated: new Date().toISOString()
-    };
+    userAdded = { powers: [] };
   }
-  const powerMdPath = join(POWER_INSTALL_DIR, "POWER.md");
-  const metadata = await extractPowerMetadata(powerMdPath);
-  const repoId = "local-kiro-protocols";
-  registry.powers[metadata.name] = {
-    name: metadata.name,
-    displayName: metadata.displayName,
-    description: metadata.description,
-    mcpServers: [],
-    author: metadata.author,
-    keywords: metadata.keywords,
-    installed: true,
-    installedAt: new Date().toISOString(),
-    installPath: POWER_INSTALLED_DIR,
+  const existingIdx = userAdded.powers.findIndex((p) => p.name === "kiro-protocols");
+  const entry = {
+    name: "kiro-protocols",
+    description: `Custom power from ${POWER_INSTALL_DIR}`,
     source: {
-      type: "repo",
-      repoId,
-      repoName: POWER_INSTALL_DIR
-    },
-    sourcePath: POWER_INSTALL_DIR
-  };
-  registry.repoSources[repoId] = {
-    name: POWER_INSTALL_DIR,
-    type: "local",
-    enabled: true,
-    addedAt: new Date().toISOString(),
-    path: POWER_INSTALL_DIR,
-    lastSync: new Date().toISOString(),
-    powerCount: 1
+      type: "local",
+      path: POWER_INSTALL_DIR
+    }
   };
-  registry.lastUpdated = new Date().toISOString();
-  await writeFile(REGISTRY_PATH, JSON.stringify(registry, null, 2), "utf-8");
+  if (existingIdx >= 0) {
+    userAdded.powers[existingIdx] = entry;
+  } else {
+    userAdded.powers.push(entry);
+  }
+  await writeFile(USER_ADDED_JSON_PATH, JSON.stringify(userAdded, null, 2), "utf-8");
   console.log("✅ Power registered in Kiro registry");
   return true;
 }
-async function installFile(relativePath, installDir, sourceDir) {
+async function installFile(relativePath, installDir, sourceDir, readOnly = true) {
   const destPath = join(installDir, relativePath);
   if (existsSync(destPath)) {
     await setWritable(destPath);
@@ -202,13 +160,14 @@ async function installFile(relativePath, installDir, sourceDir) {
   const destDir = dirname(destPath);
   await mkdir(destDir, { recursive: true });
   await writeFile(destPath, content);
-  await setReadOnly(destPath);
+  if (readOnly) {
+    await setReadOnly(destPath);
+  }
   console.log(`✅ Installed: ${relativePath}`);
 }
 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)) {
@@ -220,45 +179,36 @@ async function install() {
     await installFile(file, STEERING_INSTALL_DIR, "dist");
   }
   console.log(`
-⚡ Installing kiro-protocols power to ~/.kiro/powers/kiro-protocols/`);
+⚡ Installing kiro-protocols source to ~/.kiro/powers/kiro-protocols/`);
   if (existsSync(POWER_INSTALL_DIR)) {
-    console.log("\uD83D\uDDD1️  Removing existing power installation...");
+    console.log("\uD83D\uDDD1️  Removing existing power source...");
     const { rmSync } = await import("fs");
     rmSync(POWER_INSTALL_DIR, { recursive: true, force: true });
   }
   for (const file of POWER_FILES) {
-    await installFile(file, POWER_INSTALL_DIR, "power");
+    await installFile(file, POWER_INSTALL_DIR, "power", false);
   }
   console.log(`
-\uD83D\uDD17 Creating symbolic links in installed/ directory...`);
+\uD83D\uDCCB Copying power files to ~/.kiro/powers/installed/kiro-protocols/`);
   try {
-    const symlinkWarnings = await createSymbolicLinks();
-    if (symlinkWarnings > 0) {
-      hasWarnings = true;
-    }
+    await installPowerFiles();
   } catch (error) {
-    console.warn("⚠️  Warning: Could not create symbolic links:", error instanceof Error ? error.message : error);
+    console.warn("⚠️  Warning: Could not copy power files to installed/:", 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 {
-    const registrySuccess = await registerPowerInRegistry();
-    if (!registrySuccess) {
-      hasWarnings = true;
-    }
+    await registerPower();
   } catch (error) {
-    console.warn("⚠️  Warning: Could not register power in registry:", error instanceof Error ? error.message : error);
+    console.warn("⚠️  Warning: Could not register power:", 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("   You can manually add the power via: Powers panel → Add Custom Power → Local Directory");
     console.warn(`   Path: ${POWER_INSTALL_DIR}`);
     hasWarnings = true;
   }
-  if (hasErrors) {
-    console.log(`
-❌ Installation completed with errors!`);
-  } else if (hasWarnings) {
+  if (hasWarnings) {
     console.log(`
 ⚠️  Installation completed with warnings!`);
     console.log("   Core files installed successfully, but some optional features may not work.");
@@ -267,12 +217,11 @@ async function install() {
 ✨ Installation completed successfully!`);
   }
   console.log(`
-\uD83D\uDCC1 Steering files: ${STEERING_INSTALL_DIR}`);
-  console.log(`\uD83D\uDCC1 Power files: ${POWER_INSTALL_DIR}`);
-  console.log(`\uD83D\uDCC1 Installed links: ${POWER_INSTALLED_DIR}`);
+\uD83D\uDCC1 Steering files:  ${STEERING_INSTALL_DIR}`);
+  console.log(`\uD83D\uDCC1 Power source:    ${POWER_INSTALL_DIR}`);
+  console.log(`\uD83D\uDCC1 Power installed: ${POWER_INSTALLED_DIR}`);
   console.log(`
 \uD83D\uDCA1 The kiro-protocols power should now appear as installed in Kiro Powers UI.`);
-  console.log("\uD83D\uDCA1 Files are set to read-only. To modify them, change permissions first.");
   console.log(`
 \uD83D\uDD04 To update, simply run 'npx kiro-agents' again.`);
 }

package/build/npm/dist/agents.md

@@ -40,7 +40,7 @@ When auto-setup detects no agents exist:
    /only-read-protocols agent-creation.md
    ```
 
-2. **Create `.kiro/agents/kiro-master.md`** using the agent definition structure from agent-creation.md Step 3, with:
+2. **Create `.kiro/kiro-agents/kiro-master.md`** using the agent definition structure from agent-creation.md Step 3, with:
    
    **kiro-master** - Interactive Kiro feature management with CRUD operations for MCP servers, hooks, agents, specs, powers, and steering documents. Includes .kiro/ directory maintenance, steering optimization, refactoring, and comprehensive analysis capabilities
 

package/build/npm/dist/aliases.md

@@ -71,7 +71,7 @@ The agent activation command uses parameter substitution to load agent definitio
 You are now activating the **{agent_name}** agent.
 
 **Load and execute activation protocol:**
-1. Read `.kiro/agents/{agent_name}.md` into context
+1. Read `.kiro/kiro-agents/{agent_name}.md` into context
 2. /only-read-protocols agent-activation.md
 3. Follow all steps from the "Agent Activation Steps" section in agent-activation.md protocol file
 4. Use `{agent_name}` as the agent identifier throughout the protocol

package/build/npm/dist/reflect.md

@@ -20,7 +20,7 @@ Enables reflection system for the currently active agent for this session.
 
 **Step 1: Check if agent has Reflections section**
 
-Read the agent definition file: `.kiro/agents/{agent-name}.md`
+Read the agent definition file: `.kiro/kiro-agents/{agent-name}.md`
 
 **If agent already has `## Reflections` section:**
 - Load capture protocol: `/only-read-protocols reflect-agent-insights.md`
@@ -32,7 +32,7 @@ Read the agent definition file: `.kiro/agents/{agent-name}.md`
 
 **Step 2: Add Reflections section to agent file**
 
-Use `fsAppend` to add the following section to `.kiro/agents/{agent-name}.md`:
+Use `fsAppend` to add the following section to `.kiro/kiro-agents/{agent-name}.md`:
 
 ````markdown
 
@@ -243,7 +243,7 @@ No initialization required! Files created automatically when:
 
 ## Learn More
 
-- **Curator Agent:** `.kiro/agents/reflection-curator.md`
+- **Curator Agent:** `.kiro/kiro-agents/reflection-curator.md`
 
 ---
 

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/build/npm/power/steering/agent-activation.md

@@ -8,7 +8,7 @@ When activating agent `{agent_name}`:
 
 ### Step 1: Load Agent Definition and Strict Mode
 
-Read `.kiro/agents/{agent_name}.md` into context.
+Read `.kiro/kiro-agents/{agent_name}.md` into context.
 
 This file contains:
 - Agent capabilities and responsibilities
@@ -49,7 +49,7 @@ If chit-chat.md is in context from a previous session, its patterns do not apply
 For this session, you are **{agent_name}**.
 
 You will:
-- Follow ALL protocols and instructions from `.kiro/agents/{agent_name}.md`
+- Follow ALL protocols and instructions from `.kiro/kiro-agents/{agent_name}.md`
 - Apply agent-specific interaction patterns
 - Use capabilities defined in the agent definition
 - Maintain this role until user switches agents or ends session

package/build/npm/power/steering/agent-creation.md

@@ -328,7 +328,7 @@ Requirements:
 - Lowercase with hyphens (e.g., `refactor-architect`)
 - No spaces or special characters
 - Descriptive of agent's purpose
-- Must be unique (check `.kiro/agents/` directory)
+- Must be unique (check `.kiro/kiro-agents/` directory)
 
 #### 2.3: Agent Description
 
@@ -487,7 +487,7 @@ Once confirmed, generate complete agent definition using the AI-analyzed capabil
 
 ## Step 3: Generate Agent Definition File
 
-Create `.kiro/agents/{agent-name}.md` with this structure:
+Create `.kiro/kiro-agents/{agent-name}.md` with this structure:
 
 ```markdown
 ---
@@ -612,7 +612,7 @@ Show summary to user:
 
 **Agent Created:** `{agent-name}`
 
-**Location:** `.kiro/agents/{agent-name}.md`
+**Location:** `.kiro/kiro-agents/{agent-name}.md`
 
 **Summary:**
 - Type: {type}

package/build/npm/power/steering/agent-management.md

@@ -26,16 +26,16 @@ Begin with a diff block showing:
 
 ### Step 2: Scan Agents Directory
 
-**CRITICAL: You MUST execute `listDirectory` tool on `.kiro/agents/` to get the actual list of agents.**
+**CRITICAL: You MUST execute `listDirectory` tool on `.kiro/kiro-agents/` to get the actual list of agents.**
 
 **DO NOT rely on open editor files or context - always scan the directory explicitly.**
 
-Execute `listDirectory` on `.kiro/agents/`:
+Execute `listDirectory` on `.kiro/kiro-agents/`:
 
 **If directory doesn't exist OR directory is empty:**
 1. **Load agent creation protocol**:
    - Call `kiroPowers` with action="readSteering", powerName="kiro-protocols", steeringFile="agent-creation.md"
-2. Create `.kiro/agents/kiro-master.md` agent automatically using the description from "Initial Agent" section
+2. Create `.kiro/kiro-agents/kiro-master.md` agent automatically using the description from "Initial Agent" section
 3. Follow the agent definition structure from agent-creation.md protocol
 4. Show diff block indicating setup completion
 5. Continue to Step 3 with kiro-master as available agent
@@ -58,7 +58,7 @@ Use this response structure:
 
 **Current Focus**: Agent selection and management
 
-**Available agents in `.kiro/agents/`:**
+**Available agents in `.kiro/kiro-agents/`:**
 
 [List each agent with format:]
 - **{agent-name}** - {description from frontmatter or .md}

package/build/npm/power/steering/reflect-manager-workflow.md

@@ -16,7 +16,7 @@ This protocol enables batch enablement of reflection system across multiple agen
 **Scan agent directory:**
 
 ```
-.kiro/agents/
+.kiro/kiro-agents/
 ├── agent-1.md
 ├── agent-2.md
 ├── agent-3.md
@@ -107,7 +107,7 @@ For each selected agent:
 #### 5a. Read Agent Definition
 
 ```
-Read: .kiro/agents/{agent-name}.md
+Read: .kiro/kiro-agents/{agent-name}.md
 ```
 
 #### 5b. Check Current State
@@ -166,9 +166,9 @@ Processed: {total} agents
 └─ Skipped: {skipped-count}
 
 Modified agent definitions:
-- .kiro/agents/{agent-1}.md
-- .kiro/agents/{agent-2}.md
-- .kiro/agents/{agent-3}.md
+- .kiro/kiro-agents/{agent-1}.md
+- .kiro/kiro-agents/{agent-2}.md
+- .kiro/kiro-agents/{agent-3}.md
 ...
 
 Next steps:

package/build/npm/power/steering/strict-mode.md

@@ -142,7 +142,7 @@ ACTIVE_AGENT: none | {agent-name}
 
 **Agent activation:**
 - Triggered by `/agents {agent-name}` command
-- Loads `.kiro/agents/{agent-name}.md` into context
+- Loads `.kiro/kiro-agents/{agent-name}.md` into context
 - Executes agent-activation protocol
 - Sets ACTIVE_AGENT = {agent-name}
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "kiro-agents",
-  "version": "1.15.3",
+  "version": "2.0.0",
   "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": {