kiro-agents 1.4.0 → 1.6.0

package/README.md

@@ -93,3 +93,13 @@ Traditional AI assistants overwhelm you with context and options. kiro-agents:
 ## License
 
 MIT
+
+## Contributing
+
+We welcome contributions! Please see [CONTRIBUTING.md](CONTRIBUTING.md) for guidelines.
+
+**Important**: Do not modify files in `power/` directory. This is auto-generated during release. See contributing guide for details.
+
+## License
+
+MIT

package/build/npm/bin/cli.js

@@ -27,8 +27,6 @@ var __filename2 = fileURLToPath(import.meta.url);
 var __dirname2 = dirname(__filename2);
 var INSTALL_DIR = join(homedir(), ".kiro", "steering", "kiro-agents");
 var FILES_TO_INSTALL = [
-  "agent-system.md",
-  "modes-system.md",
   "strict-mode.md",
   "agents.md",
   "modes.md",

package/build/npm/dist/agents.md

@@ -37,7 +37,7 @@ Begin with a diff block showing:
 Execute `listDirectory` on `.kiro/agents/`:
 
 **If directory doesn't exist OR directory is empty:**
-1. **Read `{{{PROTOCOLS_PATH}}}/agent-creation.mdx` into context** - Load agent creation protocol
+1. **Read `~/.kiro/steering/kiro-agents/protocols/agent-creation.mdx` into context** - Load agent creation protocol
 2. Create `.kiro/agents/kiro-master.md` agent automatically using the description from "Initial Agent" section
 3. Follow the agent definition structure from agent-creation.mdx protocol
 4. Show diff block indicating setup completion
@@ -89,7 +89,7 @@ Based on user selection:
 
 #### Option 2 - Create New Agent
 
-- **Read `{{{PROTOCOLS_PATH}}}/agent-creation.mdx` into context** - Load agent creation protocol
+- **Read `~/.kiro/steering/kiro-agents/protocols/agent-creation.mdx` into context** - Load agent creation protocol
 - Follow all steps from the "Agent Creation Steps" section in agent-creation.mdx
 - Start agent creation workflow with interactive wizard
 - Ask for agent type (code-focused, documentation, testing, etc.)
@@ -100,7 +100,7 @@ Based on user selection:
 
 #### Option 3 - Manage Existing Agent
 
-- **Read `{{{PROTOCOLS_PATH}}}/agent-creation.mdx` into context** - Load agent structure reference
+- **Read `~/.kiro/steering/kiro-agents/protocols/agent-creation.mdx` into context** - Load agent structure reference
 - Show numbered list of available agents
 - User selects agent to manage
 - Offer management options:
@@ -133,7 +133,11 @@ AGENT COMMANDS
   /agents {name}    Activate specific agent
   /agents           Interactive agent management
 
-{{{MODE_COMMANDS}}}
+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.
@@ -151,7 +155,7 @@ Explain agent system:
 #### Option 7 - Exit
 
 - Confirm exit from agent management mode
-- Return to normal Kiro interaction
+- Return to normal interaction
 - Preserve any changes made
 
 ### Step 5: Maintain Chit-Chat Mode
@@ -185,4 +189,16 @@ This description is used when creating `.kiro/agents/kiro-master.md` during auto
 
 ---
 
-**Begin agent management mode now.**
+**Quick Commands:**
+
+```
+/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.

package/build/npm/dist/aliases.md

@@ -75,3 +75,45 @@ spec
 ````
 
 User types: `/spec` → AI responds: `spec`
+
+## Agent System Alias
+
+The agent activation command uses parameter substitution to load agent definitions dynamically:
+
+<alias>
+  <trigger>/agents {agent_name}</trigger>
+  <definition>
+## Agent Activation: {agent_name}
+
+You are now activating the **{agent_name}** agent.
+
+**Load and execute activation protocol:**
+1. Read `.kiro/agents/{agent_name}.md` into context
+2. Read `~/.kiro/steering/kiro-agents/protocols/agent-activation.mdx` into context
+3. Follow all steps from the "Agent Activation Steps" section in agent-activation.mdx
+4. Use `{agent_name}` as the agent identifier throughout the protocol
+  </definition>
+</alias>
+
+This alias enables users to activate any agent with `/agents {name}` syntax.
+
+## Mode System Alias
+
+The mode switching command uses parameter substitution to load mode definitions dynamically:
+
+<alias>
+  <trigger>/modes {mode_name}</trigger>
+  <definition>
+## Mode Switch: {mode_name}
+
+You are now switching to **{mode_name} mode**.
+
+**Load and execute mode switching protocol:**
+1. Read `kiro-{mode_name}-mode.md` from agent-system directory into context
+2. Read `~/.kiro/steering/kiro-agents/protocols/mode-switching.mdx` into context
+3. Follow all steps from the "Mode Switch Steps" section in mode-switching.mdx
+4. Use `{mode_name}` as the mode identifier throughout the protocol
+  </definition>
+</alias>
+
+This alias enables users to switch modes with `/modes {name}` syntax.

package/build/npm/dist/interactions/interaction-styles.md

@@ -16,7 +16,7 @@ inclusion: manual
 - Visual formatting (bold, code blocks)
 - Context recovery system
 
-**Example agents**: kiro-manager
+**Example agents**: project-manager
  
 **When to use**:
 
@@ -103,7 +103,7 @@ inclusion: manual
 - Simple tasks → Direct execution
 - Complex tasks → Chit-chat or consultative
 
-**Example agents**: kiro-manager-hybrid
+**Example agents**: project-manager-hybrid
  
 **When to use**:
 

package/build/npm/dist/modes.md

@@ -8,93 +8,142 @@ keywords: ["modes", "vibe", "spec", "workflow", "interactive"]
 
 You are now in **mode management** using chit-chat interaction protocol.
 
-## Step 1: Load Chit-Chat Mode
+## Mode Management Steps
+
+When entering mode management:
+
+### 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)
+
+Begin with a diff block showing:
+```diff
+  👉 Mode management
+  ⏳ Mode selection
+```
+
+### Step 2: Detect Available Modes
+
+Scan agent-system directory for `kiro-*-mode.md` files:
+- Extract mode names from filenames (remove `kiro-` prefix and `-mode.md` suffix)
+- Read frontmatter for descriptions
+- Identify current mode from context (if any)
+
+**Available Kiro modes:**
+- **vibe** - Flexible, conversational development assistance
+- **spec** - Structured feature development with requirements, design, and tasks
+
+### Step 3: Present Mode Selection
+
+Use this response structure:
+
+```diff
+  👉 Mode management
+  ⏳ Mode selection
+```
+
+**Current mode:** [current_mode or "none"]
+
+**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:
+  - **Vibe Mode**: Flexible, conversational, quick iterations, no formal workflow
+  - **Spec Mode**: Structured workflow with requirements → design → tasks, approval gates
+- Explain when to use each mode:
+  - Use vibe for: Quick fixes, exploration, prototyping, iterative development
+  - Use spec for: Complex features, team collaboration, formal planning, documentation
+- Highlight key differences:
+  - Workflow: None vs. Structured phases
+  - Approval: Direct changes vs. Approval gates
+  - Documentation: Minimal vs. Comprehensive
+- 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:
+- **What are modes?** - Different interaction styles for different workflows
+- **How to switch?** - Use `/modes {name}` or `/modes` for interactive menu
+- **Mode benefits:**
+  - Vibe: Fast iteration, flexible approach
+  - Spec: Structured planning, comprehensive documentation
+- **Mode coordination:**
+  - Modes can be combined with agents
+  - File changes preserved when switching
+  - Workflow state resets when switching
+- **Usage examples:**
+  - Quick bug fix → Use vibe mode
+  - New feature with requirements → Use spec mode
+  - Refactoring existing code → Use vibe mode
+  - Team feature with documentation → Use spec mode
+
+### Step 5: Maintain Chit-Chat Mode
+
+Continue using diff blocks and numbered choices throughout mode management session.
+
+After each action:
+- Update diff block with progress
+- Show current focus
+- Provide next action choices
+- Allow going back or canceling
+
+**Context Preservation:**
+- Use diff blocks to show progress
+- Preserve user decisions
+- Allow going back to previous step
+- Enable canceling operations
+
+---
+
+**Mode management active. Present choices to user.**
 
-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
 
 ---
 

package/build/npm/dist/protocols/agent-activation.mdx

@@ -1,6 +1,6 @@
 # Agent Activation Protocol
 
-This file contains the detailed instructions for activating an agent. It is referenced by the `/agents {agent_name}` alias in `agent-system.md`.
+This file contains the detailed instructions for activating an agent. It is referenced by the `/agents {agent_name}` alias in `aliases.md`.
 
 ## Agent Activation Steps
 

package/build/npm/dist/protocols/mode-management.mdx

@@ -0,0 +1,139 @@
+# Mode Management Protocol
+
+This file contains the detailed instructions for interactive mode management. It is referenced when `/modes` is executed without parameters.
+
+## Mode Management Steps
+
+When entering mode management:
+
+### 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)
+
+Begin with a diff block showing:
+```diff
+  👉 Mode management
+  ⏳ Mode selection
+```
+
+### Step 2: Detect Available Modes
+
+Scan agent-system directory for `kiro-*-mode.md` files:
+- Extract mode names from filenames (remove `kiro-` prefix and `-mode.md` suffix)
+- Read frontmatter for descriptions
+- Identify current mode from context (if any)
+
+**Available Kiro modes:**
+- **vibe** - Flexible, conversational development assistance
+- **spec** - Structured feature development with requirements, design, and tasks
+
+### Step 3: Present Mode Selection
+
+Use this response structure:
+
+```diff
+  👉 Mode management
+  ⏳ Mode selection
+```
+
+**Current mode:** [current_mode or "none"]
+
+**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:
+  - **Vibe Mode**: Flexible, conversational, quick iterations, no formal workflow
+  - **Spec Mode**: Structured workflow with requirements → design → tasks, approval gates
+- Explain when to use each mode:
+  - Use vibe for: Quick fixes, exploration, prototyping, iterative development
+  - Use spec for: Complex features, team collaboration, formal planning, documentation
+- Highlight key differences:
+  - Workflow: None vs. Structured phases
+  - Approval: Direct changes vs. Approval gates
+  - Documentation: Minimal vs. Comprehensive
+- 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:
+- **What are modes?** - Different interaction styles for different workflows
+- **How to switch?** - Use `/modes {name}` or `/modes` for interactive menu
+- **Mode benefits:**
+  - Vibe: Fast iteration, flexible approach
+  - Spec: Structured planning, comprehensive documentation
+- **Mode coordination:**
+  - Modes can be combined with agents
+  - File changes preserved when switching
+  - Workflow state resets when switching
+- **Usage examples:**
+  - Quick bug fix → Use vibe mode
+  - New feature with requirements → Use spec mode
+  - Refactoring existing code → Use vibe mode
+  - Team feature with documentation → Use spec mode
+
+### Step 5: Maintain Chit-Chat Mode
+
+Continue using diff blocks and numbered choices throughout mode management session.
+
+After each action:
+- Update diff block with progress
+- Show current focus
+- Provide next action choices
+- Allow going back or canceling
+
+**Context Preservation:**
+- Use diff blocks to show progress
+- Preserve user decisions
+- Allow going back to previous step
+- Enable canceling operations
+
+---
+
+**Mode management active. Present choices to user.**

package/build/npm/dist/protocols/mode-switching.mdx

@@ -1,84 +1,84 @@
-# Mode Switching Protocol
-
-This file contains the detailed instructions for switching Kiro modes. It is referenced by the `/modes {mode_name}` alias in `modes-system.md`.
-
-## Mode Switch Steps
-
-When switching to mode `{mode_name}`:
-
-### Step 1: Load Mode Definition
-
-Read `kiro-{mode_name}-mode.md` from agent-system directory into context.
-
-This file contains:
-- Mode identity and purpose
-- Interaction protocols
-- Workflow patterns (if any)
-- Response style guidelines
-- Testing approaches
-- File organization rules
-- Integration points
-
-### Step 2: Assume Mode Role
-
-For this session, you are in **{mode_name} mode**.
-
-You will:
-- Follow ALL protocols and instructions from `kiro-{mode_name}-mode.md`
-- Apply mode-specific interaction patterns
-- Use capabilities defined in the mode definition
-- Maintain this mode until user switches modes or ends session
-- Override any conflicting instructions with mode protocols
-
-### Step 3: Preserve Context and Check State
-
-**IMPORTANT:** Mode switching preserves:
-- All file changes made in previous mode
-- Conversation history and context
-- Current working state
-- User preferences and settings
-
-**WARNING:** Mode switching does NOT preserve:
-- Workflow state (e.g., which phase you're in)
-- Approval gate status
-- Phase-specific context
-
-**If switching FROM spec mode:**
-Before switching, display warning:
-```
-⚠️ Switching from Spec mode will reset workflow state.
-
-Current Spec state:
-- Phase: [current phase]
-- Requirements: [approved/not approved]
-- Design: [approved/not approved]
-- Tasks: [approved/not approved]
-
-If you return to Spec mode later, you'll need to re-approve documents.
-
-Continue switching to {mode_name} mode? [Yes] [No, stay in Spec mode]
-```
-
-Wait for user confirmation before proceeding.
-
-You are simply changing HOW you interact, not WHAT you're working on.
-
-### Step 4: Begin Interaction
-
-Start interaction according to **{mode_name} mode**'s protocols.
-
-**If switching to spec mode:**
-- Ask user what they want to work on
-- Offer to create new spec or update existing
-- Follow structured workflow (requirements → design → tasks)
-- Use approval gates between phases
-
-**If switching to vibe mode:**
-- Continue with flexible, conversational interaction
-- No formal workflow required
-- Make changes directly when clear
-- Iterate quickly on feedback
-
----
-
-**You are now in {mode_name} mode. Begin interaction.**
+# Mode Switching Protocol
+
+This file contains the detailed instructions for switching Kiro modes. It is referenced by the `/modes {mode_name}` alias in `modes-system.md`.
+
+## Mode Switch Steps
+
+When switching to mode `{mode_name}`:
+
+### Step 1: Load Mode Definition
+
+Read `kiro-{mode_name}-mode.md` from agent-system directory into context.
+
+This file contains:
+- Mode identity and purpose
+- Interaction protocols
+- Workflow patterns (if any)
+- Response style guidelines
+- Testing approaches
+- File organization rules
+- Integration points
+
+### Step 2: Assume Mode Role
+
+For this session, you are in **{mode_name} mode**.
+
+You will:
+- Follow ALL protocols and instructions from `kiro-{mode_name}-mode.md`
+- Apply mode-specific interaction patterns
+- Use capabilities defined in the mode definition
+- Maintain this mode until user switches modes or ends session
+- Override any conflicting instructions with mode protocols
+
+### Step 3: Preserve Context and Check State
+
+**IMPORTANT:** Mode switching preserves:
+- All file changes made in previous mode
+- Conversation history and context
+- Current working state
+- User preferences and settings
+
+**WARNING:** Mode switching does NOT preserve:
+- Workflow state (e.g., which phase you're in)
+- Approval gate status
+- Phase-specific context
+
+**If switching FROM spec mode:**
+Before switching, display warning:
+```
+⚠️ Switching from Spec mode will reset workflow state.
+
+Current Spec state:
+- Phase: [current phase]
+- Requirements: [approved/not approved]
+- Design: [approved/not approved]
+- Tasks: [approved/not approved]
+
+If you return to Spec mode later, you'll need to re-approve documents.
+
+Continue switching to {mode_name} mode? [Yes] [No, stay in Spec mode]
+```
+
+Wait for user confirmation before proceeding.
+
+You are simply changing HOW you interact, not WHAT you're working on.
+
+### Step 4: Begin Interaction
+
+Start interaction according to **{mode_name} mode**'s protocols.
+
+**If switching to spec mode:**
+- Ask user what they want to work on
+- Offer to create new spec or update existing
+- Follow structured workflow (requirements → design → tasks)
+- Use approval gates between phases
+
+**If switching to vibe mode:**
+- Continue with flexible, conversational interaction
+- No formal workflow required
+- Make changes directly when clear
+- Iterate quickly on feedback
+
+---
+
+**You are now in {mode_name} mode. Begin interaction.**

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "kiro-agents",
-  "version": "1.4.0",
+  "version": "1.6.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": {
@@ -52,7 +52,7 @@
   "author": "R. Beltran",
   "license": "MIT",
   "devDependencies": {
-    "@changesets/cli": "^2.29.8",
+    "@changesets/cli": "2.27.9",
     "@types/bun": "latest"
   },
   "peerDependencies": {

package/build/npm/dist/agent-system.md

@@ -1,111 +0,0 @@
----
-inclusion: always
-description: Generic agent activation system with instruction commands for seamless agent management
----
-
-# Agent System
-
-Generic agent activation and management system for Kiro using instruction commands with parameter support.
-
-**For complete documentation, examples, and troubleshooting, see `docs/agent-system-guide.md`**
-
-## Agent Commands
-
-**Note:** This system uses the Instruction Alias pattern defined in `aliases.md`.
-
-### Command 1: Activate Specific Agent
-
-<alias>
-  <trigger>/agents {agent_name}</trigger>
-  <definition>
-## Agent Activation: {agent_name}
-
-You are now activating the **{agent_name}** agent.
-
-**Load and execute activation protocol:**
-1. Read `.kiro/agents/{agent_name}.md` into context
-2. Read `~/.kiro/steering/kiro-agents/protocols/agent-activation.mdx` into context
-3. Follow all steps from the "Agent Activation Steps" section in agent-activation.mdx
-4. Use `{agent_name}` as the agent identifier throughout the protocol
-  </definition>
-</alias>
-
-### Command 2: Interactive Agent Management
-
-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
-
-**Usage:**
-- Interactive: `/agents` (no parameters, loads `agents.md` steering file)
-- Direct: `/agents {name}` (with agent name, uses alias above)
-
-## Quick Reference
-
-### Activation Protocol Summary
-
-When `/agents {name}` is executed:
-
-1. **Discover** - Check `.kiro/agents/{name}.md` exists
-2. **Load** - Read agent definition and `strict-mode.md`
-3. **Apply** - Follow mandatory protocols, load required steering
-4. **Assume** - Become agent completely, maintain role
-5. **Begin** - Start interaction per agent's protocol
-
-### Management Protocol Summary
-
-When `/agents` is executed:
-
-1. **Activate chit-chat** - Load chit-chat.md, use diff blocks
-2. **Scan directory** - List `.md` files in `.kiro/agents/`
-3. **Present choices** - Show agents, offer operations
-4. **Handle operations** - Activation, creation, management, viewing
-5. **Maintain context** - Track progress, preserve decisions
-
-## Agent Definition Requirements
-
-**File location:** `.kiro/agents/{agent-name}.md`
-
-**Required sections:**
-- Frontmatter (name, type, description, version)
-- Core Responsibilities
-- Capabilities
-- Interaction Protocol
-- Mandatory Protocols
-- Workflows
-- Examples
-
-**Recommended sections:**
-- Integration Points
-- Conflict Priorities
-- Best Practices
-- Advanced Features
-- Error Handling
-- Success Metrics
-
-## Initial Agent
-
-When auto-setup detects no agents exist, it creates:
-
-**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
-
-## Integration Notes
-
-- Works alongside steering documents
-- Compatible with chit-chat mode
-- Preserves ADHD-C optimizations
-- **Mode system** - Works seamlessly with modes (see `modes-system.md`)
-- **Context preservation** - File changes and conversation history persist across agent switches
-
-## System Notes
-
-- Prototype system using Instruction Alias pattern
-- Relies on AI understanding and following instructions
-- May need iteration based on actual usage
-
----
-
-**Agent system ready. Use `/agents` to begin or `/agents {name}` to activate specific agent.**

package/build/npm/dist/modes-system.md

@@ -1,98 +0,0 @@
----
-inclusion: always
-description: Kiro mode switching system for flexible interaction styles (vibe/spec modes)
----
-
-# Modes System
-
-Mode switching system for Kiro that enables different interaction styles and workflows.
-
-**For complete documentation, examples, and troubleshooting, see `docs/modes-system-guide.md`**
-
-## Available Modes
-
-- **vibe** - Flexible, conversational development assistance
-- **spec** - Structured feature development with requirements, design, and tasks
-
-## Mode Commands
-
-### Command 1: Switch Kiro Mode
-
-<alias>
-  <trigger>/modes {mode_name}</trigger>
-  <definition>
-## Mode Switch: {mode_name}
-
-You are now switching to **{mode_name} mode**.
-
-**Load and execute mode switching protocol:**
-1. Read `kiro-{mode_name}-mode.md` from agent-system directory into context
-2. Read `~/.kiro/steering/kiro-agents/protocols/mode-switching.mdx` into context
-3. Follow all steps from the "Mode Switch Steps" section in mode-switching.mdx
-4. Use `{mode_name}` as the mode identifier throughout the protocol
-  </definition>
-</alias>
-
-### Command 2: Interactive Mode Management
-
-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
-
-**Usage:**
-- Interactive: `/modes` (no parameters, loads `modes.md` steering file)
-- Direct: `/modes {name}` (with mode name, uses alias above)
-
-## Quick Reference
-
-### Activation Protocol Summary
-
-When `/modes {name}` is executed:
-
-1. **Load** - Read mode definition and parse configuration
-2. **Check** - If from spec mode, show warning and confirm
-3. **Apply** - Follow mode protocols, set up context
-4. **Begin** - Start interaction per mode's protocol
-
-### Management Protocol Summary
-
-When `/modes` is executed:
-
-1. **Activate chit-chat** - Load chit-chat.md, use diff blocks
-2. **Detect modes** - Scan for `kiro-*-mode.md` files
-3. **Present choices** - Show modes, offer operations
-4. **Handle operations** - Switching, viewing, comparison, help
-
-## Mode and Agent Coordination
-
-**Modes provide the framework:**
-- Vibe mode: Flexible, conversational interaction
-- Spec mode: Structured workflow with approval gates
-
-**Agents provide specialized capabilities:**
-- kiro-master: Feature management and .kiro/ operations
-- Custom agents: Domain-specific expertise
-
-**They work together:**
-- 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
-
-## System Notes
-
-- Prototype system using Instruction Alias pattern
-- Relies on AI understanding and following instructions
-- Works seamlessly with agent system
-
----
-
-**Modes system ready.**
-
-**Quick start:**
-- `/modes vibe` - Flexible development
-- `/modes spec` - Structured planning
-- `/modes` - Interactive mode management