kiro-agents 1.0.2 → 1.2.0

package/README.md

@@ -14,13 +14,29 @@ kiro-agents is a steering document system that extends Kiro IDE with:
 
 ## Installation
 
+### Option 1: Global Installation (npm)
+
 ```bash
 npx kiro-agents
 # or
 bunx kiro-agents
 ```
 
-This installs steering documents to `~/.kiro/steering/` that enhance Kiro's AI capabilities.
+This installs steering documents to `~/.kiro/steering/` (global, available in all workspaces).
+
+### Option 2: Workspace Installation (Kiro Power)
+
+1. Open Kiro IDE
+2. Open Powers panel (Ghosty icon ⚡)
+3. Click "Add power from GitHub"
+4. Enter: `https://github.com/theadd/kiro-agents`
+5. Click Install
+
+This installs to `.kiro/powers/kiro-agents/` (workspace-specific).
+
+**Differences:**
+- **npm**: Global installation, available in all workspaces
+- **Power**: Workspace-specific, auto-updates, better Kiro integration
 
 ## Core Features
 
@@ -34,8 +50,8 @@ Create specialized AI agents for different tasks. Each agent has:
 - Integration with other agents
 
 **Commands:**
-- `/agents` - Interactive agent management (create, activate, manage agents)
-- `/agent {name}` - Activate specific agent directly
+- `/agents` - Interactive agent management (visual menu)
+- `/agents {name}` - Activate specific agent directly
 
 **Example workflow:**
 ```
@@ -68,9 +84,9 @@ Switch between interaction styles based on your needs:
 - Property-based testing focus
 
 **Commands:**
-- `/modes` - Interactive mode management
-- `/mode vibe` - Switch to flexible development
-- `/mode spec` - Switch to structured planning
+- `/modes` - Interactive mode management (visual menu)
+- `/modes vibe` - Switch to flexible development
+- `/modes spec` - Switch to structured planning
 
 ### Strict Mode
 
@@ -82,6 +98,7 @@ Precision mode for experimental or critical development:
 - Ideal for architectural decisions
 
 **Commands:**
+- `/strict` - Interactive control (visual buttons)
 - `/strict on` - Activate precision mode
 - `/strict off` - Return to normal mode
 
@@ -98,33 +115,59 @@ This design reduces decision fatigue and maintains context during long conversat
 
 ## How It Works
 
-kiro-agents installs markdown files to `~/.kiro/steering/` that Kiro loads as steering documents. These documents:
+kiro-agents provides steering documents that Kiro loads to enhance AI capabilities:
 
-1. Define new slash commands (`/agent`, `/mode`, `/strict`, etc.)
-2. Provide protocols for AI behavior
-3. Enable agent and mode systems
-4. Optimize interactions for reduced cognitive load
+**npm installation:**
+- Installs to `~/.kiro/steering/` (global)
+- Available in all workspaces
+- Manual updates via re-running npx/bunx
 
-The system adds minimal overhead to initial context while enabling progressive enhancement through agent creation.
+**Power installation:**
+- Installs to `.kiro/powers/kiro-agents/` (workspace)
+- Auto-updates from GitHub
+- Better integration with Kiro ecosystem
+- Keyword-based activation
+
+Both methods provide:
+1. New slash commands (`/agents`, `/modes`, `/strict`)
+2. Protocols for AI behavior
+3. Agent and mode systems
+4. Optimized interactions for reduced cognitive load
+
+The system adds minimal overhead while enabling progressive enhancement.
 
 ## File Structure After Installation
 
+**npm installation** (`~/.kiro/steering/`):
 ```
 ~/.kiro/steering/
-├── agent-system.md              # Core agent system
-├── modes-system.md              # Mode switching system
+├── agent-system.md
+├── modes-system.md
 └── agent-system/
-    ├── strict-mode.md           # Precision mode
-    ├── kiro-spec-mode.md        # Spec mode protocols
-    ├── kiro-vibe-mode.md        # Vibe mode protocols
+    ├── strict-mode.md
+    ├── kiro-spec-mode.md
+    ├── kiro-vibe-mode.md
     ├── interactions/
-    │   ├── chit-chat.md         # Interactive workflows
-    │   └── interaction-styles.md
     └── tools/
-        └── client-tools.md
 ```
 
-Files are set to read-only after installation to prevent accidental modifications.
+**Power installation** (`.kiro/powers/kiro-agents/`):
+```
+.kiro/powers/kiro-agents/
+├── POWER.md                     # Power metadata
+├── mcp.json                     # MCP server config (empty for now)
+└── steering/
+    ├── agent-system.md          # Core system (always loaded)
+    ├── agents.md                # Interactive menu (manual)
+    ├── modes-system.md          # Core system (always loaded)
+    ├── modes.md                 # Interactive menu (manual)
+    ├── strict-mode.md           # Core system (always loaded)
+    ├── strict.md                # Interactive control (manual)
+    ├── interactions/            # Interaction patterns
+    └── modes/                   # Mode definitions
+```
+
+npm files are read-only after installation. Power files managed by Kiro.
 
 ## Usage Examples
 
@@ -143,7 +186,7 @@ AI: Agent created! Activate now? [Yes/No]
 ### Switching Modes
 
 ```
-User: /mode spec
+User: /modes spec
 AI: [Loads spec mode protocols]
 AI: What feature do you want to work on?
 User: User authentication system
@@ -162,9 +205,9 @@ AI: [Asks clarifying questions about cache strategy, TTL, invalidation, etc.]
 ### Agent Coordination
 
 ```
-User: /mode spec
+User: /modes spec
 [Work on feature planning]
-User: /agent kiro-master
+User: /agents kiro-master
 [Use kiro-master capabilities while in spec mode]
 ```
 

package/{bin → build/npm/bin}/cli.js

@@ -25,16 +25,18 @@ import { existsSync, chmodSync, constants } from "fs";
 import { fileURLToPath } from "url";
 var __filename2 = fileURLToPath(import.meta.url);
 var __dirname2 = dirname(__filename2);
-var INSTALL_DIR = join(homedir(), ".kiro", "steering");
+var INSTALL_DIR = join(homedir(), ".kiro", "steering", "kiro-agents");
 var FILES_TO_INSTALL = [
   "agent-system.md",
   "modes-system.md",
-  "agent-system/strict-mode.md",
-  "agent-system/kiro-spec-mode.md",
-  "agent-system/kiro-vibe-mode.md",
-  "agent-system/interactions/chit-chat.md",
-  "agent-system/interactions/interaction-styles.md",
-  "agent-system/tools/client-tools.md"
+  "strict-mode.md",
+  "agents.md",
+  "modes.md",
+  "strict.md",
+  "interactions/chit-chat.md",
+  "interactions/interaction-styles.md",
+  "modes/kiro-spec-mode.md",
+  "modes/kiro-vibe-mode.md"
 ];
 async function setWritable(filePath) {
   try {
@@ -63,8 +65,14 @@ async function installFile(relativePath) {
   console.log(`✅ Installed: ${relativePath}`);
 }
 async function install() {
-  console.log(`\uD83D\uDCE6 Installing kiro-agents to ~/.kiro/steering/
+  console.log(`\uD83D\uDCE6 Installing kiro-agents to ~/.kiro/steering/kiro-agents/
 `);
+  if (existsSync(INSTALL_DIR)) {
+    console.log(`\uD83D\uDDD1️  Removing existing installation...
+`);
+    const { rmSync } = await import("fs");
+    rmSync(INSTALL_DIR, { recursive: true, force: true });
+  }
   for (const file of FILES_TO_INSTALL) {
     await installFile(file);
   }
@@ -74,6 +82,8 @@ async function install() {
 \uD83D\uDCC1 Files installed to: ${INSTALL_DIR}`);
   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.`);
 }
 install().catch((error) => {
   console.error("❌ Installation failed:", error);

package/{dist → build/npm/dist}/agent-system.md

@@ -7,47 +7,14 @@ description: Generic agent activation system with instruction commands for seaml
 
 Generic agent activation and management system for Kiro using instruction commands with parameter support.
 
-## Instruction Alias with Parameters
-
-### Parameter Substitution Protocol
-
-When processing instructions, if you encounter an XML structure `<alias>` with variables in `{curly_braces}`:
-
-```xml
-<alias>
-  <trigger>COMMAND {param1} {param2}</trigger>
-  <definition>
-    Instructions with {param1} and {param2} placeholders
-  </definition>
-</alias>
-```
-
-**Processing steps:**
-1. **Extract parameter names** from `<trigger>` (e.g., `{param1}`, `{param2}`)
-2. **Match user command** - When user types matching command pattern
-3. **Extract parameter values** - Capture actual values from user input
-4. **Replace placeholders** - Substitute all `{param}` in `<definition>` with actual values
-5. **Execute instructions** - Run resulting instructions immediately
-
-### Example
-
-**Alias definition:**
-```xml
-<alias>
-  <trigger>/greet {name}</trigger>
-  <definition>Say hello to {name} enthusiastically!</definition>
-</alias>
-```
-
-**User types:** `/greet Alice`
-**System executes:** "Say hello to Alice enthusiastically!"
-
 ## Agent Commands
 
+**Note:** This system uses the Instruction Alias pattern defined in `aliases.md`. See that document for details on parameter substitution and literal response patterns.
+
 ### Command 1: Activate Specific Agent
 
 <alias>
-  <trigger>/agent {agent_name}</trigger>
+  <trigger>/agents {agent_name}</trigger>
   <definition>
 ## Agent Activation: {agent_name}
 
@@ -100,152 +67,20 @@ Otherwise:
 
 ### Command 2: Interactive Agent Management
 
-<alias>
-  <trigger>/agents</trigger>
-  <definition>
-## Agent Management Mode
-
-You are now in **agent management mode** using chit-chat interaction protocol.
-
-### Step 1: Load Chit-Chat Mode
-
-Apply protocols from `chit-chat.md` steering document:
-- Use diff blocks to show progress
-- Provide numbered choice lists (4-6 options, up to 16 if needed)
-- Maintain single focus per message
-- Use visual formatting (bold, code blocks, lists)
-- Optimize for ADHD-C (minimal cognitive load)
-
-### Step 2: Auto-Setup and Scan Agents Directory
+For interactive agent management, use the `/agents` slash command (without parameters).
+This provides a visual interface for:
+- Viewing all available agents
+- Creating new agents
+- Managing existing agents
+- Viewing agent details
 
-**First, check if `.kiro/agents/` directory exists:**
-
-If directory doesn't exist OR directory is empty:
-1. Create `.kiro/agents/` directory if missing
-2. Create `kiro-master.md` agent automatically using the enhanced description from "Available Agents" section
-3. Show diff block indicating setup completion
-4. Continue to Step 3 with kiro-master as available agent
-
-If directory exists with agents:
-- List all available agents from `.kiro/agents/` directory
-- Find all `*.md` files
-- Extract agent names from filenames
-- Read frontmatter metadata for descriptions
-- Categorize by agent type if metadata available
-
-### Step 3: Present Agent Selection
-
-Use this response structure:
-
-```diff
-  👉 Agent management mode
-  ⏳ Agent selection or management
-```
-
-**Current Focus**: Agent selection and management
-
-**Available agents in `.kiro/agents/`:**
-
-[List each agent with format:]
-- **{agent-name}** - {description from frontmatter or .md}
-
-**What would you like to do?**
-
-1. **Activate agent** - Choose agent to activate immediately
-2. **Create new agent** - Start agent creation wizard
-3. **Manage existing agent** - Modify agent configuration
-4. **View agent details** - Show full agent definition
-5. **List all commands** - Show available slash commands
-6. **Agent system help** - Explain how agents work
-7. **Exit** - Return to normal mode
-
-### Step 4: Handle User Choice
-
-Based on user selection:
-
-**Option 1 - Activate agent:**
-- Show numbered list of available agents
-- User selects agent by number
-- Execute `/agent {selected_agent_name}` command
-- Agent activates immediately
-
-**Option 2 - Create new agent:**
-- Start agent creation workflow (similar to kiro-master)
-- Ask for agent type (code-focused, documentation, testing, etc.)
-- Collect agent name, description, capabilities
-- Generate `.md` file with all agent definition
-- Offer to activate new agent
-
-**Option 3 - Manage existing agent:**
-- Show numbered list of available agents
-- User selects agent to manage
-- Offer management options:
-  - Modify capabilities
-  - Update instructions
-  - Change interaction protocol
-  - Add/remove integrations
-  - Delete agent
-
-**Option 4 - View agent details:**
-- Show numbered list of available agents
-- User selects agent to view
-- Display full `.md` content with formatting
-- Show agent protocols and capabilities summary
-- Offer to activate or manage agent
-
-**Option 5 - List all commands:**
-- Show all available slash commands in the system
-- Display command syntax and brief description
-- Group by category (agents, modes, utilities)
-- Format as table for quick reference:
-
-```
-Available Commands:
-
-AGENT COMMANDS
-  /agent {name}     Activate specific agent
-  /agents           Interactive agent management
-
-MODE COMMANDS (see modes-system.md)
-  /mode {name}      Switch Kiro mode (vibe/spec)
-  /modes            Interactive mode management
-  /strict {state}   Control strict mode (on/off)
-
-Note: Commands are defined in steering documents.
-New commands can be added via Instruction Alias pattern.
-```
-
-**Option 6 - Agent system help:**
-- Explain agent system architecture
-- Show command usage examples
-- Describe agent file structure
-- Explain how to create custom agents
-- Document best practices
-
-**Option 7 - Exit:**
-- Confirm exit from agent management mode
-- Return to normal Kiro interaction
-- Preserve any changes made
-
-### Step 5: Maintain Chit-Chat Mode
-
-Continue using diff blocks and numbered choices throughout agent management session.
-
-After each action:
-- Update diff block with progress
-- Show current focus
-- Provide next action choices
-- Allow going back or canceling
-
----
-
-**Begin agent management mode now.**
-  </definition>
-</alias>
+**Usage:**
+- Interactive: `/agents` (no parameters, loads `agents.md` steering file)
+- Direct: `/agents {name}` (with agent name, uses alias above)
 
 ## Agent Activation Protocol
 
-When `/agent {name}` is executed:
+When `/agents {name}` is executed:
 
 1. **Discover agent file**
    - Check `.kiro/agents/{name}.md` exists
@@ -301,7 +136,7 @@ When `/agents` is executed:
    - Allow exit to normal mode
 
 4. **Handle operations**
-   - Agent activation → Execute `/agent {name}`
+   - Agent activation → Execute `/agents {name}`
    - Agent creation → Start creation wizard
    - Agent management → Modify agent files
    - Agent viewing → Display agent details
@@ -348,19 +183,20 @@ When `/agents` is executed:
 - Error Handling
 - Success Metrics
 
-## Available Agents
+## Initial Agent
+
+When auto-setup detects no agents exist, it creates the initial agent:
 
-Agents are discovered automatically from `.kiro/agents/` directory.
+**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
 
-**Current agents:**
-- **kiro-master** - Interactive Kiro feature management with CRUD operations for MCP servers, hooks, agents, specs, and steering documents. Includes .kiro/ directory maintenance, steering optimization, refactoring, and comprehensive analysis capabilities
+This description is used when creating `.kiro/agents/kiro-master.md` during auto-setup.
 
 ## Usage Examples
 
 ### Activate Specific Agent
 
 ```
-/agent refactor-architect
+/agents refactor-architect
 ```
 
 **Result:** AI immediately assumes refactor-architect role, loads agent files, applies protocols, and begins interaction according to agent's style.
@@ -376,7 +212,7 @@ Agents are discovered automatically from `.kiro/agents/` directory.
 ### Switch Between Agents
 
 ```
-/agent kiro-master
+/agents kiro-master
 ```
 
 **Result:** Switch from current agent (e.g., refactor-architect) to kiro-master. Previous agent context is suspended, new agent context is loaded.
@@ -432,7 +268,7 @@ Agents can specify required steering documents in their `.md` definition file:
 ### For Agent Users
 
 1. **Use `/agents` for discovery** - See what agents are available
-2. **Use `/agent {name}` for direct activation** - When you know which agent you need
+2. **Use `/agents {name}` for direct activation** - When you know which agent you need
 3. **Let agents maintain focus** - Don't switch agents mid-task unless necessary
 4. **Provide clear context** - Help agents understand your needs
 5. **Use agent capabilities** - Leverage agent-specific tools and workflows
@@ -457,7 +293,7 @@ Agents can specify required steering documents in their `.md` definition file:
 
 ### Agent Not Activating
 
-**Problem:** `/agent {name}` doesn't work
+**Problem:** `/agents {name}` doesn't work
 **Solutions:**
 - Check agent files exist in `.kiro/agents/`
 - Verify filename matches command (case-sensitive)
@@ -487,8 +323,8 @@ Agents can specify required steering documents in their `.md` definition file:
 Potential improvements to agent system:
 
 **Agent enhancements:**
-- **Agent parameters** - `/agent refactor-architect --mode=strict`
-- **Agent chaining** - `/agent kiro-master then refactor-architect`
+- **Agent parameters** - `/agents refactor-architect --mode=strict`
+- **Agent chaining** - `/agents kiro-master then refactor-architect`
 - **Agent templates** - Quick agent creation from templates
 - **Agent marketplace** - Share agents with community
 - **Agent versioning** - Track agent changes over time
@@ -509,4 +345,4 @@ Potential improvements to agent system:
 
 ---
 
-**Agent system ready. Use `/agents` to begin or `/agent {name}` to activate specific agent.**
+**Agent system ready. Use `/agents` to begin or `/agents {name}` to activate specific agent.**

package/build/npm/dist/agents.md

@@ -0,0 +1,155 @@
+---
+inclusion: manual
+description: "Interactive agent management interface with visual menu for creating, activating, and managing AI agents"
+keywords: ["agents", "management", "create", "activate", "interactive"]
+---
+
+# Agent Management
+
+You are now in **agent management mode** using chit-chat interaction protocol.
+
+## Step 1: Load Chit-Chat Mode
+
+Apply protocols from `chit-chat.md` steering document:
+- Use diff blocks to show progress
+- Provide numbered choice lists (4-6 options, up to 16 if needed)
+- Maintain single focus per message
+- Use visual formatting (bold, code blocks, lists)
+- Optimize for ADHD-C (minimal cognitive load)
+
+## Step 2: Auto-Setup and Scan Agents Directory
+
+**CRITICAL: You MUST execute `listDirectory` tool on `.kiro/agents/` to get the actual list of agents.**
+
+**DO NOT rely on open editor files or context - always scan the directory explicitly.**
+
+**First, execute `listDirectory` on `.kiro/agents/`:**
+
+If directory doesn't exist OR directory is empty:
+1. Create `.kiro/agents/kiro-master.md` agent automatically using the description from "Initial Agent" section
+2. Show diff block indicating setup completion
+3. Continue to Step 3 with kiro-master as available agent
+
+If directory exists with agents:
+1. **Execute `listDirectory` tool** to get complete list of `.md` files
+2. Extract agent names from filenames (remove `.md` extension)
+3. Read frontmatter metadata for descriptions
+4. Categorize by agent type if metadata available
+5. **List ALL agents found** - do not filter or assume based on context
+
+## Step 3: Present Agent Selection
+
+Use this response structure:
+
+```diff
+  👉 Agent management mode
+  ⏳ Agent selection or management
+```
+
+**Current Focus**: Agent selection and management
+
+**Available agents in `.kiro/agents/`:**
+
+[List each agent with format:]
+- **{agent-name}** - {description from frontmatter or .md}
+
+**What would you like to do?**
+
+1. **Activate agent** - Choose agent to activate immediately
+2. **Create new agent** - Start agent creation wizard
+3. **Manage existing agent** - Modify agent configuration
+4. **View agent details** - Show full agent definition
+5. **List all commands** - Show available slash commands
+6. **Agent system help** - Explain how agents work
+7. **Exit** - Return to normal mode
+
+## Step 4: Handle User Choice
+
+Based on user selection:
+
+**Option 1 - Activate agent:**
+- Show numbered list of available agents
+- User selects agent by number
+- Execute `/agents {selected_agent_name}` command
+- Agent activates immediately
+
+**Option 2 - Create new agent:**
+- Start agent creation workflow
+- Ask for agent type (code-focused, documentation, testing, etc.)
+- Collect agent name, description, capabilities
+- Generate `.md` file with all agent definition
+- Offer to activate new agent
+
+**Option 3 - Manage existing agent:**
+- Show numbered list of available agents
+- User selects agent to manage
+- Offer management options:
+  - Modify capabilities
+  - Update instructions
+  - Change interaction protocol
+  - Add/remove integrations
+  - Delete agent
+
+**Option 4 - View agent details:**
+- Show numbered list of available agents
+- User selects agent to view
+- Display full `.md` content with formatting
+- Show agent protocols and capabilities summary
+- Offer to activate or manage agent
+
+**Option 5 - List all commands:**
+- Show all available slash commands in the system
+- Display command syntax and brief description
+- Group by category (agents, modes, utilities)
+- Format as table for quick reference:
+
+```
+Available Commands:
+
+AGENT COMMANDS
+  /agents {name}    Activate specific agent
+  /agents           Interactive agent management
+
+MODE COMMANDS (see modes-system.md)
+  /modes {name}     Switch Kiro mode (vibe/spec)
+  /modes            Interactive mode management
+  /strict {state}   Control strict mode (on/off)
+  /strict           Interactive strict mode control
+
+Note: Commands are defined in steering documents.
+New commands can be added via Instruction Alias pattern.
+```
+
+**Option 6 - Agent system help:**
+- Explain agent system architecture
+- Show command usage examples
+- Describe agent file structure
+- Explain how to create custom agents
+- Document best practices
+
+**Option 7 - Exit:**
+- Confirm exit from agent management mode
+- Return to normal Kiro interaction
+- Preserve any changes made
+
+## Step 5: Maintain Chit-Chat Mode
+
+Continue using diff blocks and numbered choices throughout agent management session.
+
+After each action:
+- Update diff block with progress
+- Show current focus
+- Provide next action choices
+- Allow going back or canceling
+
+## Initial Agent
+
+When auto-setup detects no agents exist, create the initial agent:
+
+**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
+
+This description is used when creating `.kiro/agents/kiro-master.md` during auto-setup.
+
+---
+
+**Begin agent management mode now.**

package/build/npm/dist/aliases.md

@@ -0,0 +1,77 @@
+---
+inclusion: always
+description: Instruction alias system for creating custom commands with parameter substitution and literal responses
+---
+
+# Instruction Alias System
+
+System for creating custom commands using XML-based alias definitions with parameter support and literal response patterns.
+
+**For complete documentation, examples, and troubleshooting, see `docs/aliases-guide.md`**
+
+## Parameter Substitution
+
+When processing instructions, if you encounter an XML structure `<alias>` with variables in `{curly_braces}`:
+
+```xml
+<alias>
+  <trigger>COMMAND {param1} {param2}</trigger>
+  <definition>
+    Instructions with {param1} and {param2} placeholders
+  </definition>
+</alias>
+```
+
+**Processing steps:**
+1. **Extract parameter names** from `<trigger>` (e.g., `{param1}`, `{param2}`)
+2. **Match user command** - When user types matching command pattern
+3. **Extract parameter values** - Capture actual values from user input
+4. **Replace placeholders** - Substitute all `{param}` in `<definition>` with actual values
+5. **Execute instructions** - Run resulting instructions immediately
+
+### Example
+
+**Alias definition:**
+```xml
+<alias>
+  <trigger>/greet {name}</trigger>
+  <definition>Say hello to {name} enthusiastically!</definition>
+</alias>
+```
+
+User types: `/greet Alice` → Executes: "Say hello to Alice enthusiastically!"
+
+## Literal Response Pattern
+
+For outputting exact text without AI interpretation (e.g., triggering native IDE modes):
+
+````xml
+<alias>
+  <trigger>command</trigger>
+  <definition>
+Respond directly to the user with exactly and only the content of the following code block, AS-IS:
+```
+literal_text
+```
+  </definition>
+</alias>
+````
+
+**CRITICAL:** When you see this pattern, output ONLY the code block content. No explanations, no context, no other text.
+
+### Example
+
+**Alias definition:**
+````xml
+<alias>
+  <trigger>/spec</trigger>
+  <definition>
+Respond directly to the user with exactly and only the content of the following code block, AS-IS:
+```
+spec
+```
+  </definition>
+</alias>
+````
+
+User types: `/spec` → AI responds: `spec`

package/{dist/agent-system → build/npm/dist/modes}/kiro-spec-mode.md

@@ -216,7 +216,7 @@ When user requests task execution:
 ## Integration with Agent System
 
 Spec mode can be activated via:
-- `/mode spec` command (when mode-switching is enabled)
+- `/modes spec` command (when mode-switching is enabled)
 - Starting new conversation in Spec mode
 - Explicit instruction to assume Spec mode role
 

package/{dist/agent-system → build/npm/dist/modes}/kiro-vibe-mode.md

@@ -217,7 +217,7 @@ User: "Tests are failing"
 ## Integration with Agent System
 
 Vibe mode can be activated via:
-- `/mode vibe` command (when mode-switching enabled)
+- `/modes vibe` command (when mode-switching enabled)
 - Starting new conversation in Vibe mode
 - Explicit instruction to assume Vibe mode role
 
@@ -238,13 +238,13 @@ Vibe mode works alongside:
 ## Switching Between Modes
 
 **From Vibe to Spec:**
-- Use `/mode spec` when structure needed
+- Use `/modes spec` when structure needed
 - Transition to formal planning
 - Create requirements/design/tasks
 - Follow spec workflow
 
 **From Spec to Vibe:**
-- Use `/mode vibe` for flexibility
+- Use `/modes vibe` for flexibility
 - Continue working on same code
 - Drop formal structure
 - Iterate freely

package/{dist → build/npm/dist}/modes-system.md

@@ -17,7 +17,7 @@ Mode switching system for Kiro that enables different interaction styles and wor
 ### Command 1: Switch Kiro Mode
 
 <alias>
-  <trigger>/mode {mode_name}</trigger>
+  <trigger>/modes {mode_name}</trigger>
   <definition>
 ## Mode Switch: {mode_name}
 
@@ -36,8 +36,6 @@ This file contains:
 - File organization rules
 - Integration points
 
-**Also load `strict-mode.md` steering document** to enable `/strict {state}` command for this mode. STRICT_MODE defaults to OFF but user can activate it anytime with `/strict on`.
-
 ### Step 2: Assume Mode Role
 
 For this session, you are in **{mode_name} mode**.
@@ -106,114 +104,23 @@ Start interaction according to **{mode_name} mode**'s protocols.
 
 ### Command 2: Interactive Mode Management
 
-<alias>
-  <trigger>/modes</trigger>
-  <definition>
-## Mode Management
-
-You are now in **mode management** using chit-chat interaction protocol.
-
-### Step 1: Load Chit-Chat Mode
-
-Apply protocols from `chit-chat.md` steering document:
-- Use diff blocks to show progress
-- Provide numbered choice lists (4-6 options)
-- Maintain single focus per message
-- Use visual formatting (bold, code blocks, lists)
-
-### Step 2: Detect Available Modes
-
-Scan agent-system directory for `kiro-*-mode.md` files:
-- Extract mode names from filenames
-- Read frontmatter for descriptions
-- Identify current mode from context
-
-### Step 3: Present Mode Selection
-
-Use this response structure:
-
-```diff
-  👉 Mode management
-  ⏳ Mode selection
-```
-
-**Current mode:** [current_mode]
-
-**Available Kiro modes:**
-
-- **vibe** - Flexible, conversational development assistance
-- **spec** - Structured feature development with requirements, design, and tasks
-
-**What would you like to do?**
-
-1. **Switch to vibe mode** - Flexible development and quick iterations
-2. **Switch to spec mode** - Structured feature planning and implementation
-3. **View mode details** - See full mode capabilities and protocols
-4. **Mode comparison** - Understand differences between modes
-5. **Stay in current mode** - Continue with current mode
-6. **Help** - Learn about mode system
-
-### Step 4: Handle User Choice
-
-Based on user selection:
-
-**Option 1 - Switch to vibe:**
-- Execute `/mode vibe` command
-- Load vibe mode protocols
-- Begin flexible interaction
-
-**Option 2 - Switch to spec:**
-- Execute `/mode spec` command
-- Load spec mode protocols
-- Begin structured workflow
-
-**Option 3 - View mode details:**
-- Show numbered list of modes
-- User selects mode to view
-- Display full mode definition
-- Explain capabilities and use cases
-- Offer to switch to that mode
-
-**Option 4 - Mode comparison:**
-- Show side-by-side comparison
-- Explain when to use each mode
-- Highlight key differences
-- Help user choose appropriate mode
-
-**Option 5 - Stay in current mode:**
-- Confirm staying in current mode
-- Return to normal interaction
-- Preserve current state
+For interactive mode management, use the `/modes` slash command (without parameters).
+This provides a visual interface for:
+- Viewing available modes
+- Comparing modes
+- Switching modes
+- Getting help
 
-**Option 6 - Help:**
-- Explain mode system
-- Show switching commands
-- Describe mode benefits
-- Provide usage examples
-
-### Step 5: Maintain Chit-Chat Mode
-
-Continue using diff blocks and numbered choices throughout mode management.
-
-After each action:
-- Update diff block with progress
-- Show current focus
-- Provide next action choices
-- Allow going back or canceling
-
----
-
-**Begin mode management now.**
-  </definition>
-</alias>
+**Usage:**
+- Interactive: `/modes` (no parameters, loads `modes.md` steering file)
+- Direct: `/modes {name}` (with mode name, uses alias above)
 
 ## Mode Activation Protocol
 
-When `/mode {name}` is executed:
+When `/modes {name}` is executed:
 
 1. **Load mode definition**
    - Read `kiro-{name}-mode.md` from agent-system directory
-   - Load `strict-mode.md` steering document
    - Parse mode configuration
    - Understand mode workflows
 
@@ -256,7 +163,7 @@ When `/modes` is executed:
    - Allow staying in current mode
 
 4. **Handle operations**
-   - Mode switching → Execute `/mode {name}`
+   - Mode switching → Execute `/modes {name}`
    - View details → Show mode definition
    - Comparison → Explain differences
    - Help → Explain mode system
@@ -272,7 +179,7 @@ When `/modes` is executed:
 - Custom agents: Domain-specific expertise
 
 **They work together:**
-- Modes can activate agents: `/mode spec` then `/agent kiro-master`
+- Modes can activate agents: `/modes spec` then `/agents kiro-master`
 - Agents inherit mode protocols: Agent in spec mode follows spec workflow
 - Context preserved: Switch modes/agents without losing work
 - Layered capabilities: Mode + Agent + Strict mode all active simultaneously
@@ -288,13 +195,13 @@ When `/modes` is executed:
 ### Switch Kiro Modes
 
 ```
-/mode vibe
+/modes vibe
 ```
 
 **Result:** AI switches to Vibe mode - flexible, conversational development. No formal workflows, quick iterations, direct changes.
 
 ```
-/mode spec
+/modes spec
 ```
 
 **Result:** AI switches to Spec mode - structured feature development with requirements, design, and task planning.
@@ -310,9 +217,9 @@ When `/modes` is executed:
 ### Combined with Agents
 
 ```
-/mode spec
+/modes spec
 [Work on structured feature planning]
-/agent kiro-master
+/agents kiro-master
 [Use kiro-master agent while in spec mode]
 ```
 
@@ -340,7 +247,7 @@ When `/modes` is executed:
 
 **Mode enhancements:**
 - **Custom modes** - User-defined modes beyond vibe/spec
-- **Mode parameters** - `/mode spec --strict --minimal-tests`
+- **Mode parameters** - `/modes spec --strict --minimal-tests`
 - **Mode presets** - Save mode configurations
 - **Mode history** - Track mode usage patterns
 - **Automated transitions** - Suggest mode switch when appropriate
@@ -363,6 +270,6 @@ When `/modes` is executed:
 **Modes system ready.**
 
 **Quick start:**
-- `/mode vibe` - Flexible development
-- `/mode spec` - Structured planning
+- `/modes vibe` - Flexible development
+- `/modes spec` - Structured planning
 - `/modes` - Interactive mode management

package/build/npm/dist/modes.md

@@ -0,0 +1,101 @@
+---
+inclusion: manual
+description: "Interactive mode management interface for switching between vibe and spec interaction styles"
+keywords: ["modes", "vibe", "spec", "workflow", "interactive"]
+---
+
+# Mode Management
+
+You are now in **mode management** using chit-chat interaction protocol.
+
+## Step 1: Load Chit-Chat Mode
+
+Apply protocols from `chit-chat.md` steering document:
+- Use diff blocks to show progress
+- Provide numbered choice lists (4-6 options)
+- Maintain single focus per message
+- Use visual formatting (bold, code blocks, lists)
+
+## Step 2: Detect Available Modes
+
+Scan agent-system directory for `kiro-*-mode.md` files:
+- Extract mode names from filenames
+- Read frontmatter for descriptions
+- Identify current mode from context
+
+## Step 3: Present Mode Selection
+
+Use this response structure:
+
+```diff
+  👉 Mode management
+  ⏳ Mode selection
+```
+
+**Current mode:** [current_mode]
+
+**Available Kiro modes:**
+
+- **vibe** - Flexible, conversational development assistance
+- **spec** - Structured feature development with requirements, design, and tasks
+
+**What would you like to do?**
+
+1. **Switch to vibe mode** - Flexible development and quick iterations
+2. **Switch to spec mode** - Structured feature planning and implementation
+3. **View mode details** - See full mode capabilities and protocols
+4. **Mode comparison** - Understand differences between modes
+5. **Stay in current mode** - Continue with current mode
+6. **Help** - Learn about mode system
+
+## Step 4: Handle User Choice
+
+Based on user selection:
+
+**Option 1 - Switch to vibe:**
+- Execute `/modes vibe` command
+- Load vibe mode protocols
+- Begin flexible interaction
+
+**Option 2 - Switch to spec:**
+- Execute `/modes spec` command
+- Load spec mode protocols
+- Begin structured workflow
+
+**Option 3 - View mode details:**
+- Show numbered list of modes
+- User selects mode to view
+- Display full mode definition
+- Explain capabilities and use cases
+- Offer to switch to that mode
+
+**Option 4 - Mode comparison:**
+- Show side-by-side comparison
+- Explain when to use each mode
+- Highlight key differences
+- Help user choose appropriate mode
+
+**Option 5 - Stay in current mode:**
+- Confirm staying in current mode
+- Return to normal interaction
+- Preserve current state
+
+**Option 6 - Help:**
+- Explain mode system
+- Show switching commands
+- Describe mode benefits
+- Provide usage examples
+
+## Step 5: Maintain Chit-Chat Mode
+
+Continue using diff blocks and numbered choices throughout mode management.
+
+After each action:
+- Update diff block with progress
+- Show current focus
+- Provide next action choices
+- Allow going back or canceling
+
+---
+
+**Begin mode management now.**

package/{dist/agent-system → build/npm/dist}/strict-mode.md

@@ -46,7 +46,9 @@ This serves dual purpose:
 - File locations not specified
 - Breaking changes implications
 
-## Activation Command
+## Activation Commands
+
+### Command 1: Direct State Change
 
 <alias>
   <trigger>/strict {state}</trigger>
@@ -57,6 +59,19 @@ State changed. Response Protocol now applies.
   </definition>
 </alias>
 
+### Command 2: Interactive Control
+
+For interactive strict mode control, use the `/strict` slash command (without parameters).
+This provides a numbered choice interface to:
+- Enable strict mode
+- Disable strict mode
+- Learn more about strict mode
+- Check current state
+
+**Usage:**
+- Interactive: `/strict` (no parameters, loads `strict.md` steering file with numbered options)
+- Direct: `/strict on` or `/strict off` (with state)
+
 ## Use Case Guidelines
 
 ### When to Activate STRICT_MODE

package/build/npm/dist/strict.md

@@ -0,0 +1,93 @@
+---
+inclusion: manual
+description: "Interactive strict mode control with numbered options for enabling/disabling precision mode"
+keywords: ["strict", "precision", "mode", "control"]
+---
+
+# Strict Mode Control
+
+Interactive control for STRICT_MODE using numbered choice pattern.
+
+## Current State Check
+
+First, determine the current STRICT_MODE state from context.
+
+## Present Interactive Options
+
+Display the question with numbered options:
+
+```markdown
+# Strict Mode Control
+
+**Current State**: STRICT_MODE = ${current_state}
+
+Strict mode blocks execution on ambiguous input and requires explicit clarification. Use it for:
+- Experimental projects with cutting-edge technologies
+- Architectural decisions that propagate throughout codebase
+- Breaking changes affecting multiple files/systems
+- New component creation establishing patterns
+- Debugging propagated errors from incorrect assumptions
+
+**What would you like to do?**
+
+1. **🟢 Enable Strict Mode** - Activate precision mode - blocks execution on ambiguous input, requires explicit clarification
+2. **🔴 Disable Strict Mode** - Return to normal mode - allows reasonable assumptions, faster iteration
+3. **ℹ️ Learn More** - Understand when and how to use strict mode effectively
+4. **📊 Check Current State** - Show current strict mode configuration and status
+```
+
+**Note**: Recommend option 1 when current_state is "OFF", recommend option 2 when current_state is "ON".
+
+## Handle User Selection
+
+Based on user's choice:
+
+**Enable Strict Mode:**
+- Set STRICT_MODE = ON
+- Confirm activation
+- Show brief reminder of strict mode rules
+- Return to conversation with strict mode active
+
+**Disable Strict Mode:**
+- Set STRICT_MODE = OFF
+- Confirm deactivation
+- Return to normal conversation mode
+
+**Learn More:**
+- Explain strict mode purpose and benefits
+- Show examples of when to use it
+- Describe the critical rules (no assumptions, mandatory clarification, block execution)
+- Provide use case guidelines
+- Offer to enable/disable after explanation
+
+**Check Current State:**
+- Display current STRICT_MODE value
+- Show when it was last changed (if tracked)
+- Explain current behavior
+- Offer to change state
+
+## Quick Reference
+
+**Strict Mode Rules (when ON)**:
+1. **NO ASSUMPTIONS** - Stop immediately if input is ambiguous
+2. **MANDATORY CLARIFICATION** - Ask specific questions to resolve ambiguities
+3. **BLOCK EXECUTION** - Do not execute main task until data is confirmed
+4. **EXPLICIT AUTHORIZATION ONLY** - Proceed only with user confirmation
+
+**When to Use**:
+- Experimental/cutting-edge projects
+- Architectural decisions
+- Breaking changes
+- New component patterns
+- Debugging propagated errors
+
+**When Standard Mode is Fine**:
+- Well-established patterns
+- Simple, clear tasks
+- Documentation work
+- Standard refactoring
+- Common web development patterns
+
+---
+
+**Strict mode control ready.**

package/package.json

@@ -1,19 +1,26 @@
 {
   "name": "kiro-agents",
-  "version": "1.0.2",
+  "version": "1.2.0",
   "description": "AI agent system for Kiro IDE",
   "type": "module",
   "bin": {
-    "kiro-agents": "bin/cli.js"
+    "kiro-agents": "build/npm/bin/cli.js"
   },
   "files": [
-    "bin",
-    "dist"
+    "build/npm/bin",
+    "build/npm/dist"
   ],
   "scripts": {
-    "build": "bun run scripts/build.ts",
-    "watch": "bun run scripts/build.ts --watch",
-    "clean": "bun run scripts/clean.ts"
+    "build": "bun run scripts/build.ts npm",
+    "build:power": "bun run scripts/build.ts power",
+    "dev": "bun run scripts/build.ts dev",
+    "test": "bun run scripts/test.ts",
+    "clean": "bun run scripts/clean.ts",
+    "snapshot": "bun run scripts/snapshot.ts",
+    "finalize": "bun run scripts/finalize.ts analyze",
+    "finalize:analyze": "bun run scripts/finalize.ts analyze",
+    "finalize:commit": "bun run scripts/finalize.ts commit",
+    "release": "bun run scripts/release.ts"
   },
   "keywords": [
     "kiro",
@@ -22,6 +29,7 @@
   "author": "R. Beltran",
   "license": "MIT",
   "devDependencies": {
+    "@changesets/cli": "^2.29.8",
     "@types/bun": "latest"
   },
   "peerDependencies": {

package/bin/cli.ts

@@ -1,85 +0,0 @@
-#!/usr/bin/env node
-import { join, dirname } from "path";
-import { homedir } from "os";
-import { existsSync, chmodSync, constants } from "fs";
-import { fileURLToPath } from "url";
-
-const __filename = fileURLToPath(import.meta.url);
-const __dirname = dirname(__filename);
-
-const INSTALL_DIR = join(homedir(), ".kiro", "steering");
-
-// Files to install (relative to dist/ in package)
-const FILES_TO_INSTALL = [
-  "agent-system.md",
-  "modes-system.md",
-  "agent-system/strict-mode.md",
-  "agent-system/kiro-spec-mode.md",
-  "agent-system/kiro-vibe-mode.md",
-  "agent-system/interactions/chit-chat.md",
-  "agent-system/interactions/interaction-styles.md",
-  "agent-system/tools/client-tools.md",
-] as const;
-
-async function setWritable(filePath: string): Promise<void> {
-  try {
-    chmodSync(filePath, constants.S_IRUSR | constants.S_IWUSR | constants.S_IRGRP | constants.S_IROTH);
-  } catch (error) {
-    // Ignore errors if file doesn't exist
-  }
-}
-
-async function setReadOnly(filePath: string): Promise<void> {
-  try {
-    chmodSync(filePath, constants.S_IRUSR | constants.S_IRGRP | constants.S_IROTH);
-  } catch (error) {
-    console.warn(`⚠️  Could not set read-only: ${filePath}`);
-  }
-}
-
-async function installFile(relativePath: string): Promise<void> {
-  const destPath = join(INSTALL_DIR, relativePath);
-  
-  // Restore write permissions if file exists
-  if (existsSync(destPath)) {
-    await setWritable(destPath);
-  }
-  
-  // Get source file from package dist/
-  const srcPath = join(__dirname, "..", "dist", relativePath);
-  
-  // Read file using fs for Node.js compatibility
-  const { readFile, writeFile, mkdir } = await import("fs/promises");
-  const content = await readFile(srcPath);
-  
-  // Ensure directory exists
-  const destDir = dirname(destPath);
-  await mkdir(destDir, { recursive: true });
-  
-  // Write file
-  await writeFile(destPath, content);
-  
-  // Set read-only
-  await setReadOnly(destPath);
-  
-  console.log(`✅ Installed: ${relativePath}`);
-}
-
-async function install(): Promise<void> {
-  console.log("📦 Installing kiro-agents to ~/.kiro/steering/\n");
-  
-  // Install all files
-  for (const file of FILES_TO_INSTALL) {
-    await installFile(file);
-  }
-  
-  console.log("\n✨ Installation completed successfully!");
-  console.log(`\n📁 Files installed to: ${INSTALL_DIR}`);
-  console.log("\n💡 Files are set to read-only. To modify them, change permissions first.");
-}
-
-// Main execution
-install().catch((error) => {
-  console.error("❌ Installation failed:", error);
-  process.exit(1);
-});

package/dist/agent-system/tools/client-tools.md

@@ -1,21 +0,0 @@
----
-inclusion: manual
----
-
-# Client Tools
-
-## userInput Tool
-
-```typescript
-userInput({
-  question: "# Markdown works here! 🚀",
-  options: [
-    {
-      title: "🎯 Emoji + text only",  // NO markdown
-      description: "## Full markdown here!",  // YES markdown
-      recommended: true
-    }
-  ],
-  reason: "fix-pbt"  // REQUIRED
-})
-```