kiro-agents 1.10.1 → 1.12.0

package/build/npm/dist/modes.md

@@ -8,13 +8,17 @@ keywords: ["modes", "vibe", "spec", "workflow", "interactive"]
 
 You are now in **mode management** using chit-chat interaction protocol.
 
+/only-read-protocols chit-chat.md
+
 ## Mode Management Steps
 
 When entering mode management:
 
 ### Step 1: Load Chit-Chat Mode
 
-Apply protocols from `chit-chat.md` steering document:
+/only-read-protocols chit-chat.md
+
+Apply protocols from chit-chat.md:
 - Use diff blocks to show progress
 - Provide numbered choice lists (4-6 options)
 - Maintain single focus per message
@@ -26,18 +30,7 @@ Begin with a diff block showing:
   ⏳ 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
+### Step 2: Present Mode Selection
 
 Use this response structure:
 
@@ -50,19 +43,24 @@ Use this response structure:
 
 **Available Kiro modes:**
 
-- **vibe** - Flexible, conversational development assistance
-- **spec** - Structured feature development with requirements, design, and tasks
+- **vibe** - Flexible, conversational development assistance (with vibe tools)
+- **spec** - Structured feature development with requirements, design, and tasks (with spec tools)
+- **as-vibe** - Vibe interaction style (keeps current tools)
+- **as-spec** - Spec interaction style (keeps current tools)
 
 **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
+1. **Switch to vibe mode** - Flexible development with vibe tools
+2. **Switch to spec mode** - Structured development with spec tools
+3. **Switch to as-vibe mode** - Vibe interaction style (keeps current tools)
+4. **Switch to as-spec mode** - Spec interaction style (keeps current tools)
+5. **Switch to spec-as-vibe mode** - Spec tools with vibe interaction style
+6. **View mode details** - See full mode capabilities and protocols
+7. **Mode comparison** - Understand differences between modes
+8. **Stay in current mode** - Continue with current mode
+9. **Help** - Learn about mode system
 
-### Step 4: Handle User Choice
+### Step 3: Handle User Choice
 
 Based on user selection:
 
@@ -70,15 +68,33 @@ Based on user selection:
 
 - Execute `/modes vibe` command
 - Load vibe mode protocols
-- Begin flexible interaction
+- Begin flexible interaction with vibe tools
 
 #### Option 2 - Switch to spec
 
 - Execute `/modes spec` command
 - Load spec mode protocols
-- Begin structured workflow
+- Begin structured workflow with spec tools
+
+#### Option 3 - Switch to as-vibe
+
+- Execute `/modes as-vibe` command
+- Load as-vibe mode protocols
+- Begin flexible interaction (keeps current tools)
+
+#### Option 4 - Switch to as-spec
+
+- Execute `/modes as-spec` command
+- Load as-spec mode protocols
+- Begin structured interaction (keeps current tools)
+
+#### Option 5 - Switch to spec-as-vibe
+
+- Execute `/spec-as-vibe` command
+- Load spec tools with vibe interaction style
+- Begin flexible interaction with spec capabilities
 
-#### Option 3 - View mode details
+#### Option 6 - View mode details
 
 - Show numbered list of modes
 - User selects mode to view
@@ -86,45 +102,57 @@ Based on user selection:
 - Explain capabilities and use cases
 - Offer to switch to that mode
 
-#### Option 4 - Mode comparison
+#### Option 7 - 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
+- Show comprehensive comparison:
+  - **Vibe Mode**: Flexible, conversational, quick iterations, no formal workflow (with vibe tools)
+  - **Spec Mode**: Structured workflow with requirements → design → tasks, approval gates (with spec tools)
+  - **As-Vibe Mode**: Flexible interaction style but keeps current tools
+  - **As-Spec Mode**: Structured interaction style but keeps current tools
 - 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
+  - Use vibe for: Quick fixes, exploration, prototyping, iterative development (need vibe tools)
+  - Use spec for: Complex features, team collaboration, formal planning, documentation (need spec tools)
+  - Use as-vibe for: Flexible interaction with current tools (agent superpowers + vibe style)
+  - Use as-spec for: Structured interaction with current tools (agent superpowers + spec methodology)
 - Highlight key differences:
-  - Workflow: None vs. Structured phases
-  - Approval: Direct changes vs. Approval gates
-  - Documentation: Minimal vs. Comprehensive
+  - **Tools**: vibe/spec change tools, as-vibe/as-spec keep current tools
+  - **Interaction**: vibe/as-vibe flexible, spec/as-spec structured
+  - **Use case**: Combine agent capabilities with desired interaction style
 - Help user choose appropriate mode
 
-#### Option 5 - Stay in current mode
+#### Option 8 - Stay in current mode
 
 - Confirm staying in current mode
 - Return to normal interaction
 - Preserve current state
 
-#### Option 6 - Help
+#### Option 9 - Help
 
 Explain mode system:
-- **What are modes?** - Different interaction styles for different workflows
+- **What are modes?** - Different interaction styles and tool sets for different workflows
 - **How to switch?** - Use `/modes {name}` or `/modes` for interactive menu
+- **Mode types:**
+  - **Full modes** (vibe/spec): Change both tools and interaction style
+  - **Role modes** (as-vibe/as-spec): Change only interaction style, keep current tools
 - **Mode benefits:**
-  - Vibe: Fast iteration, flexible approach
-  - Spec: Structured planning, comprehensive documentation
+  - Vibe: Fast iteration, flexible approach (with vibe tools)
+  - Spec: Structured planning, comprehensive documentation (with spec tools)
+  - As-Vibe: Flexible interaction with current tools (agent superpowers + vibe style)
+  - As-Spec: Structured interaction with current tools (agent superpowers + spec methodology)
 - **Mode coordination:**
   - Modes can be combined with agents
   - File changes preserved when switching
   - Workflow state resets when switching
+  - Role modes enable "agent superpowers" - specialized tools with preferred interaction style
 - **Usage examples:**
   - Quick bug fix → Use vibe mode
   - New feature with requirements → Use spec mode
+  - Agent with spec tools but want flexibility → Use as-vibe mode
+  - Agent with vibe tools but want structure → Use as-spec mode
   - Refactoring existing code → Use vibe mode
   - Team feature with documentation → Use spec mode
 
-### Step 5: Maintain Chit-Chat Mode
+### Step 4: Maintain Chit-Chat Mode
 
 Continue using diff blocks and numbered choices throughout mode management session.
 

package/build/npm/power/POWER.md

@@ -28,6 +28,14 @@ Protocols are detailed, step-by-step instruction documents that guide AI through
 
 This power provides the following protocols as steering files:
 
+### Core Protocols
+
+- **strict-mode** - Precision mode for experimental/cutting-edge development
+  - Blocks execution on ambiguous input
+  - Mandatory clarification before proceeding
+  - Prevents assumption propagation
+  - Opt-in via `/strict on` command
+
 ### Agent System Protocols
 
 - **agent-activation** - Protocol for activating and assuming agent roles

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

@@ -17,7 +17,32 @@ This file contains:
 - Examples and best practices
 - Integration requirements
 
-**Also load `strict-mode.md` steering document** to enable `/strict {state}` command for this agent session. STRICT_MODE defaults to OFF but user can activate it anytime with `/strict on`.
+This enables `/strict {state}` command for this agent session. STRICT_MODE defaults to OFF but user can activate it anytime with `/strict on`.
+/only-read-protocols strict-mode.md
+
+### Step 1.5: Manage Chit-Chat Protocol
+
+**Scan the agent definition for chit-chat protocol usage indicators:**
+
+Check if the agent definition contains ANY of these patterns (case-insensitive):
+- `**Response Style:** Chit-chat`
+- `**Response Style:** Chit-chat mode`
+- `chit-chat protocol`
+- `chit-chat interaction`
+- Section header containing "Chit-Chat" (e.g., "## Chit-Chat Mode Support")
+
+**If ANY indicator is found:**
+```
+/only-read-protocols chit-chat.md
+```
+
+**Chit-chat protocol is active** for this agent session.
+
+**If NO indicators are found:**
+
+**Chit-chat protocol is inactive** for this agent session.
+
+If chit-chat.md is in context from a previous session, its patterns do not apply. Follow the agent's defined interaction protocol instead.
 
 ### Step 2: Assume Agent Role
 
@@ -34,16 +59,18 @@ You will:
 
 Start interaction according to **{agent_name}**'s protocols defined in the `.md` file.
 
-If the agent uses **chit-chat mode**:
+**If chit-chat protocol is active:**
 - Begin with diff block showing current state
 - Provide numbered choice list (4-6 options, up to 16 if needed)
 - Maintain single focus per message
 - Use visual formatting (bold, code blocks)
+- Follow all chit-chat protocols (STOP system, context references, etc.)
 
-Otherwise:
+**If chit-chat protocol is inactive:**
 - Begin according to the agent's defined interaction protocol
 - Follow agent-specific response structure
 - Apply agent-specific formatting rules
+- Do NOT use chit-chat patterns (diff blocks, numbered choices, etc.)
 
 ---
 

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

@@ -18,7 +18,7 @@ When user initiates agent creation:
 
 ### Step 1: Present Creation Methods
 
-Use chit-chat mode for the creation process:
+Use chit-chat protocol for the creation process:
 
 ```diff
   👉 Agent Creation
@@ -355,7 +355,7 @@ Group by category. Example:
 1. **Formal** - Professional, structured responses
 2. **Casual** - Conversational, friendly tone
 3. **Technical** - Precise, detailed explanations
-4. **Chit-chat mode** - Interactive with diff blocks and numbered choices
+4. **Chit-chat protocol** - Interactive with diff blocks and numbered choices
 
 **Confirmation requirements:**
 - Always confirm before changes

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

@@ -8,7 +8,9 @@ When entering agent management mode:
 
 ### Step 1: Activate Chit-Chat Mode
 
-Load and apply protocols from `chit-chat.md` steering document:
+/only-read-protocols chit-chat.md
+
+Apply protocols from chit-chat.md:
 
 - **Use diff blocks** to show progress and current state
 - **Provide numbered choice lists** (4-8 options, up to 16 if needed)
@@ -32,7 +34,6 @@ 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
@@ -86,7 +87,6 @@ Based on user selection:
 #### 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:
@@ -103,7 +103,6 @@ Based on user selection:
 #### 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

package/build/npm/power/steering/chit-chat.md

@@ -0,0 +1,217 @@
+---
+inclusion: manual
+---
+
+# Interactive Chat Mode for ADHD Users
+
+Conversational mode optimized for users with ADHD (in particular, ADHD-C). While designed primarily for ADHD, these patterns benefit many neurodivergent users including those with autism, dyslexia, executive function disorders, and processing differences. See `docs/neurodivergent-accessibility.md` for details.
+
+Throughout this document, "ADHD" refers to the primary design target, though benefits extend more broadly.
+
+## Core Protocol: Three-Part Response Structure
+
+**MANDATORY format for every response:**
+
+1. **Diff Block** - Progress tracker showing workflow status
+2. **Single Topic** - Current focus (one concept only)
+3. **Numbered Choices** - 6-8 options (up to 16 when necessary)
+
+**Example:**
+```diff
+- ✅ Authentication bug fixed → *password validation corrected*
+  👉 Write tests for auth flow
+  ⏳ Update documentation
+```
+
+**Current Focus:** Test strategy for authentication
+
+**What would you like to do?**
+1. Write unit tests for password validation
+2. Write integration tests for full auth flow
+3. Skip tests, move to documentation
+4. Explain testing approach first
+
+---
+
+## Protocol 1: Diff Block (Progress Tracker)
+
+Provide persistent visual reference of workflow state that survives context switches.
+
+**Format:**
+```diff
+[💤 suspended_task] ← (+N)
+- ✅ completed_step → *brief_outcome*
+  👉 current_step
+  ⏳ next_step
++ 🆕 new_step ← (+N_remaining)
+```
+
+**Symbols:** `✅` completed | `👉` current | `⏳` upcoming | `💤` suspended | `🆕` new
+
+**Rules:**
+- Same step text across all diff blocks (never rename steps)
+- Steps move down as completed (linear progression)
+- Context switches: suspend current, mark with `💤`, resume later
+- Not a diff replacement format (don't remove/replace lines)
+
+---
+
+## Protocol 2: Single-Point Focus
+
+Minimize cognitive load by addressing one topic per message.
+
+**Rules:**
+- Address ONE concept, task, or decision point per message
+- Break complex tasks into discrete steps
+- Only combine tightly coupled concepts or when separation creates confusion
+
+**Example:**
+
+User: "Fix the bug and add tests"
+
+✅ **Good:** Address bug first, then offer tests as next step
+❌ **Bad:** Explain both bug fix and test strategy in same message
+
+---
+
+## Protocol 3: Response Length Management (STOP System)
+
+Prevent information overload by breaking long responses at natural boundaries.
+
+**Counting (starts after diff block + 3 lines):**
+- Text: 1 line = 1 point
+- Code/Lists: 3 lines = 1 point
+- Headers/formatting: 0 points
+
+**Thresholds (enter stopping mode):**
+- 20 points: Dense explanations
+- 15 points: Multi-concept content
+- 12 points: Abstract theory
+
+**At threshold:**
+1. Continue to natural break (paragraph/code/list end)
+2. Never stop mid-sentence/list/code/explanation
+3. Offer navigation: Continue | Skip to summary | Ask | Implement
+
+**Counter resets to 0:**
+- Tool invocations (protects work-in-progress)
+- File operations
+- Sequential corrections
+
+---
+
+## Protocol 4: Multi-Part Explanations
+
+Structure long explanations into digestible chunks with user-controlled navigation.
+
+**Rules:**
+- Label as 1A, 1B, 1C, etc.
+- ONE concept per part
+- Each part ends with navigation: Continue | Skip to summary | Ask | Implement
+- After final part: Recap (3-5 bullets) + concrete next steps
+
+---
+
+## Protocol 5: Choice-Based Interaction
+
+Reduce decision fatigue with structured options.
+
+**Rules:**
+- 6-8 options (up to 16 maximum)
+- 180 characters max per option
+- Format: `1. **Action** - Brief description`
+- If >16 options: Group related, add "Show more options"
+
+---
+
+## Protocol 6: Context References
+
+Prevent users from needing to scroll back to understand references.
+
+**Rules:**
+- Use *italics* for clarification
+- Include file paths and line numbers
+- No orphaned references (e.g., "as mentioned earlier")
+- Format: `function` *in file.ts line 42* or `[functionName](path/to/file.ts:42)`
+
+---
+
+## Protocol 7: Visual Formatting
+
+Use visual hierarchy to reduce cognitive load.
+
+**Use:** **Bold** for emphasis | `Code blocks` for technical | Lists for structure | Whitespace
+
+**Avoid:** Dense text blocks | Long paragraphs (>5 lines) | Walls of code | Nested complexity
+
+---
+
+## Protocol 8: Language Adaptation
+
+Adapt to user's language while maintaining technical consistency.
+
+**Rules:**
+- Navigation in user's language (detect from messages)
+- Technical terms in English (function names, APIs, libraries, code)
+
+---
+
+## Conflict Resolution
+
+**Priority hierarchy:**
+1. ADHD Support (overrides all)
+2. Chit-Chat Protocols
+3. Core AI Protocols
+4. System Identity
+
+**Principles:** User cognitive load > System efficiency | Fragmented > Complete dumps | Context maintenance > Brevity | User control > AI autonomy
+
+---
+
+## Anti-Patterns
+
+❌ Massive text covering 3+ concepts
+❌ No sections or breaks
+❌ Options only at end (violates STOP system)
+❌ No navigation in multi-part
+❌ Responses >80 lines without parts
+❌ Different step text for same concept (breaks tracking)
+❌ Non-linear step progression (steps should move down)
+
+---
+
+## Activation
+
+**Auto-activated when loaded.**
+
+Can be deactivated or reactivated at any time by:
+- Explicit user request
+- Protocol instructions stating "chit-chat is inactive" or "deactivate chit-chat"
+- Agent definitions specifying different interaction protocols
+
+When deactivated, chit-chat patterns do not apply until reactivated.
+
+---
+
+## Quick Reference
+
+**Every Response Must Have:**
+1. ✅ Diff block (progress tracker)
+2. ✅ Single topic (current focus)
+3. ✅ Numbered choices (6-8 options)
+
+**STOP System Triggers:**
+- 20 points: Dense explanations
+- 15 points: Multi-concept content
+- 12 points: Abstract theory
+
+**Counting:**
+- Text: 1 line = 1 point
+- Code/Lists: 3 lines = 1 point
+- Tools: Reset to 0
+
+**Navigation (always include):**
+1. Continue
+2. Skip to summary
+3. Ask about this
+4. Go implement