kiro-agents 1.1.0 → 1.2.0

package/README.md

@@ -186,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
@@ -205,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/build/npm/dist/agent-system.md

@@ -7,43 +7,10 @@ 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>
@@ -113,7 +80,7 @@ This provides a visual interface for:
 
 ## Agent Activation Protocol
 
-When `/agent {name}` is executed:
+When `/agents {name}` is executed:
 
 1. **Discover agent file**
    - Check `.kiro/agents/{name}.md` exists
@@ -169,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
@@ -229,7 +196,7 @@ This description is used when creating `.kiro/agents/kiro-master.md` during auto
 ### 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.
@@ -245,7 +212,7 @@ This description is used when creating `.kiro/agents/kiro-master.md` during auto
 ### 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.
@@ -301,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
@@ -326,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)
@@ -356,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
@@ -378,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/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/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/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/build/npm/dist/modes-system.md

@@ -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**.
@@ -119,11 +117,10 @@ This provides a visual interface for:
 
 ## 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
 
@@ -166,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
@@ -182,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
@@ -198,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.
@@ -220,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]
 ```
 
@@ -250,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
@@ -273,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/strict-mode.md

@@ -62,13 +62,14 @@ State changed. Response Protocol now applies.
 ### Command 2: Interactive Control
 
 For interactive strict mode control, use the `/strict` slash command (without parameters).
-This provides a visual interface with buttons to:
+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 userInput buttons)
+- Interactive: `/strict` (no parameters, loads `strict.md` steering file with numbered options)
 - Direct: `/strict on` or `/strict off` (with state)
 
 ## Use Case Guidelines

package/build/npm/dist/strict.md

@@ -1,12 +1,12 @@
 ---
 inclusion: manual
-description: "Interactive strict mode control with visual buttons for enabling/disabling precision mode"
+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 userInput tool.
+Interactive control for STRICT_MODE using numbered choice pattern.
 
 ## Current State Check
 
@@ -14,11 +14,10 @@ First, determine the current STRICT_MODE state from context.
 
 ## Present Interactive Options
 
-Use userInput tool to show interactive buttons:
+Display the question with numbered options:
 
-```typescript
-userInput({
-  question: `# Strict Mode Control
+```markdown
+# Strict Mode Control
 
 **Current State**: STRICT_MODE = ${current_state}
 
@@ -29,31 +28,16 @@ Strict mode blocks execution on ambiguous input and requires explicit clarificat
 - New component creation establishing patterns
 - Debugging propagated errors from incorrect assumptions
 
-**What would you like to do?**`,
-  options: [
-    {
-      title: "🟢 Enable Strict Mode",
-      description: "Activate precision mode - blocks execution on ambiguous input, requires explicit clarification",
-      recommended: current_state === "OFF"
-    },
-    {
-      title: "🔴 Disable Strict Mode",
-      description: "Return to normal mode - allows reasonable assumptions, faster iteration",
-      recommended: current_state === "ON"
-    },
-    {
-      title: "ℹ️ Learn More",
-      description: "Understand when and how to use strict mode effectively"
-    },
-    {
-      title: "📊 Check Current State",
-      description: "Show current strict mode configuration and status"
-    }
-  ],
-  reason: "strict-mode-control"
-})
+**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:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "kiro-agents",
-  "version": "1.1.0",
+  "version": "1.2.0",
   "description": "AI agent system for Kiro IDE",
   "type": "module",
   "bin": {
@@ -17,7 +17,9 @@
     "test": "bun run scripts/test.ts",
     "clean": "bun run scripts/clean.ts",
     "snapshot": "bun run scripts/snapshot.ts",
-    "finalize": "bun run scripts/finalize.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": [