kiro-agents 1.10.0 → 1.11.0

package/build/npm/dist/protocols/agent-management.md

@@ -1,183 +0,0 @@
-# Agent Management Protocol
-
-This file contains the detailed instructions for interactive agent management. It is referenced when `/agents` is executed without parameters.
-
-## Agent Management Steps
-
-When entering agent management mode:
-
-### Step 1: Activate Chit-Chat Mode
-
-Load and apply protocols from `chit-chat.md` steering document:
-
-- **Use diff blocks** to show progress and current state
-- **Provide numbered choice lists** (4-8 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)
-
-Begin with a diff block showing:
-```diff
-  👉 Agent management mode
-  ⏳ [Current operation]
-```
-
-### Step 2: 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.**
-
-Execute `listDirectory` on `.kiro/agents/`:
-
-**If directory doesn't exist OR directory is empty:**
-1. **Load agent creation protocol**:
-   - Call `kiroPowers` with action="activate", powerName="kiro-protocols"
-   - 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
-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
-
-**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
-
-- **Load agent creation protocol**:
-  - Call `kiroPowers` with action="activate", powerName="kiro-protocols"
-  - Call `kiroPowers` with action="readSteering", powerName="kiro-protocols", steeringFile="agent-creation.md"
-- Follow all steps from the "Method Selection" section in agent-creation.md
-- Present 5 creation methods to user:
-  1. Quick Start (predefined templates)
-  2. Project-Specific (AI analysis)
-  3. Explore Roles (domain browser)
-  4. Guided Wizard (step-by-step)
-  5. Natural Language (describe in plain English)
-- Execute selected method following protocol
-- Generate `.md` file with complete agent definition
-- Validate agent definition per protocol
-- Offer to activate new agent
-
-#### Option 3 - Manage Existing Agent
-
-- **Load agent structure reference**:
-  - Call `kiroPowers` with action="activate", powerName="kiro-protocols"
-  - Call `kiroPowers` with action="readSteering", powerName="kiro-protocols", steeringFile="agent-creation.md"
-- 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
-- Use agent definition structure from protocol as reference for modifications
-- Apply changes to agent `.md` file
-- Validate changes against protocol requirements
-- Reload agent if currently active
-
-#### 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:
-
-```
-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:
-- Agent system architecture
-- Command usage examples
-- Agent file structure
-- How to create custom agents
-- Best practices for agent usage
-
-#### Option 7 - Exit
-
-- Confirm exit from agent management mode
-- Return to normal 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
-
-**Context Preservation:**
-- Use diff blocks to show progress
-- Preserve user decisions
-- Allow going back to previous step
-- Enable canceling operations
-
----
-
-**Agent management mode active. Present choices to user.**

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

@@ -1,139 +0,0 @@
-# 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.md

@@ -1,84 +0,0 @@
-# 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.**