kiro-agents 1.10.1 → 1.12.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +60 -67
- package/build/npm/bin/cli.js +12 -11
- package/build/npm/dist/agents.md +3 -180
- package/build/npm/dist/aliases.md +141 -53
- package/build/npm/dist/modes.md +68 -40
- package/build/npm/power/POWER.md +8 -0
- package/build/npm/power/steering/agent-activation.md +30 -3
- package/build/npm/power/steering/agent-creation.md +2 -2
- package/build/npm/power/steering/agent-management.md +3 -4
- package/build/npm/power/steering/chit-chat.md +217 -0
- package/build/npm/power/steering/kiro-as-spec-mode.md +284 -0
- package/build/npm/power/steering/kiro-as-vibe-mode.md +312 -0
- package/build/npm/{dist/modes → power/steering}/kiro-spec-mode.md +1 -6
- package/build/npm/{dist/modes → power/steering}/kiro-vibe-mode.md +1 -6
- package/build/npm/power/steering/mode-management.md +66 -40
- package/build/npm/power/steering/mode-switching.md +9 -5
- package/build/npm/{dist → power/steering}/strict-mode.md +95 -14
- package/package.json +7 -3
- package/build/npm/dist/interactions/chit-chat.md +0 -212
- package/build/npm/dist/interactions/interaction-styles.md +0 -162
- package/build/npm/dist/protocols/agent-activation.md +0 -50
- package/build/npm/dist/protocols/agent-creation.md +0 -629
- package/build/npm/dist/protocols/agent-management.md +0 -183
- package/build/npm/dist/protocols/mode-management.md +0 -139
- package/build/npm/dist/protocols/mode-switching.md +0 -84
|
@@ -1,162 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
inclusion: manual
|
|
3
|
-
---
|
|
4
|
-
|
|
5
|
-
# Available Interaction Styles
|
|
6
|
-
|
|
7
|
-
## 1. Chit-Chat Mode (Interactive)
|
|
8
|
-
|
|
9
|
-
**Best for**: ADHD-C users, complex workflows, step-by-step guidance
|
|
10
|
-
|
|
11
|
-
**Characteristics**:
|
|
12
|
-
|
|
13
|
-
- Diff blocks showing progress at start of each response
|
|
14
|
-
- Numbered choice lists (4-6 options, up to 16 max)
|
|
15
|
-
- Single focus per message
|
|
16
|
-
- Visual formatting (bold, code blocks)
|
|
17
|
-
- Context recovery system
|
|
18
|
-
|
|
19
|
-
**Example agents**: project-manager
|
|
20
|
-
|
|
21
|
-
**When to use**:
|
|
22
|
-
|
|
23
|
-
- Multi-step workflows
|
|
24
|
-
- Decision-heavy processes
|
|
25
|
-
- User needs guidance through options
|
|
26
|
-
- Complex feature management
|
|
27
|
-
|
|
28
|
-
---
|
|
29
|
-
|
|
30
|
-
## 2. Direct Execution Mode
|
|
31
|
-
|
|
32
|
-
**Best for**: Code-focused agents, quick tasks, minimal interaction
|
|
33
|
-
|
|
34
|
-
**Characteristics**:
|
|
35
|
-
|
|
36
|
-
- Executes immediately without asking
|
|
37
|
-
- Provides results and brief explanation
|
|
38
|
-
- Minimal back-and-forth
|
|
39
|
-
- Assumes user knows what they want
|
|
40
|
-
|
|
41
|
-
**Example use cases**: Refactoring agent, formatter agent, linter agent
|
|
42
|
-
|
|
43
|
-
**When to use**:
|
|
44
|
-
|
|
45
|
-
- Clear, unambiguous tasks
|
|
46
|
-
- Automated processes
|
|
47
|
-
- Expert users who know exactly what they need
|
|
48
|
-
|
|
49
|
-
---
|
|
50
|
-
|
|
51
|
-
## 3. Consultative Mode
|
|
52
|
-
|
|
53
|
-
**Best for**: Architecture decisions, design reviews, analysis
|
|
54
|
-
|
|
55
|
-
**Characteristics**:
|
|
56
|
-
|
|
57
|
-
- Asks clarifying questions first
|
|
58
|
-
- Provides recommendations with rationale
|
|
59
|
-
- Explains tradeoffs
|
|
60
|
-
- Waits for user approval before acting
|
|
61
|
-
|
|
62
|
-
**Example use cases**: API designer, architecture reviewer, security auditor
|
|
63
|
-
|
|
64
|
-
**When to use**:
|
|
65
|
-
|
|
66
|
-
- High-impact decisions
|
|
67
|
-
- Multiple valid approaches exist
|
|
68
|
-
- User needs expert guidance
|
|
69
|
-
- Tradeoffs need discussion
|
|
70
|
-
|
|
71
|
-
---
|
|
72
|
-
|
|
73
|
-
## 4. Wizard Mode (Step-by-Step)
|
|
74
|
-
|
|
75
|
-
**Best for**: Setup processes, configuration, scaffolding
|
|
76
|
-
|
|
77
|
-
**Characteristics**:
|
|
78
|
-
|
|
79
|
-
- Linear progression through steps
|
|
80
|
-
- Collects information incrementally
|
|
81
|
-
- Shows progress indicator
|
|
82
|
-
- Validates each step before proceeding
|
|
83
|
-
|
|
84
|
-
**Example use cases**: Project setup agent, configuration wizard, onboarding agent
|
|
85
|
-
|
|
86
|
-
**When to use**:
|
|
87
|
-
|
|
88
|
-
- Multi-step setup processes
|
|
89
|
-
- Information gathering needed
|
|
90
|
-
- Order matters
|
|
91
|
-
- Validation at each step
|
|
92
|
-
|
|
93
|
-
---
|
|
94
|
-
|
|
95
|
-
## 5. Hybrid Mode
|
|
96
|
-
|
|
97
|
-
**Best for**: Flexible agents that adapt to context
|
|
98
|
-
|
|
99
|
-
**Characteristics**:
|
|
100
|
-
|
|
101
|
-
- Combines multiple styles
|
|
102
|
-
- Adapts based on task complexity
|
|
103
|
-
- Simple tasks → Direct execution
|
|
104
|
-
- Complex tasks → Chit-chat or consultative
|
|
105
|
-
|
|
106
|
-
**Example agents**: project-manager-hybrid
|
|
107
|
-
|
|
108
|
-
**When to use**:
|
|
109
|
-
|
|
110
|
-
- Agent handles diverse tasks
|
|
111
|
-
- Task complexity varies
|
|
112
|
-
- Want flexibility
|
|
113
|
-
|
|
114
|
-
---
|
|
115
|
-
|
|
116
|
-
## 6. Documentation Mode
|
|
117
|
-
|
|
118
|
-
**Best for**: Writing, explaining, teaching
|
|
119
|
-
|
|
120
|
-
**Characteristics**:
|
|
121
|
-
|
|
122
|
-
- Comprehensive explanations
|
|
123
|
-
- Examples and code snippets
|
|
124
|
-
- Structured output (headers, sections)
|
|
125
|
-
- Progressive disclosure for long content
|
|
126
|
-
|
|
127
|
-
**Example use cases**: Documentation writer, tutorial creator, explainer agent
|
|
128
|
-
|
|
129
|
-
**When to use**:
|
|
130
|
-
|
|
131
|
-
- Creating documentation
|
|
132
|
-
- Teaching concepts
|
|
133
|
-
- Explaining complex topics
|
|
134
|
-
|
|
135
|
-
---
|
|
136
|
-
|
|
137
|
-
## Mixing Styles
|
|
138
|
-
|
|
139
|
-
You can combine elements from different styles:
|
|
140
|
-
|
|
141
|
-
**Example**: Consultative + Chit-Chat
|
|
142
|
-
|
|
143
|
-
- Ask clarifying questions (consultative)
|
|
144
|
-
- Use diff blocks and numbered choices (chit-chat)
|
|
145
|
-
- Single focus per message (chit-chat)
|
|
146
|
-
|
|
147
|
-
**Example**: Direct Execution + Documentation
|
|
148
|
-
|
|
149
|
-
- Execute task immediately (direct)
|
|
150
|
-
- Provide detailed explanation after (documentation)
|
|
151
|
-
|
|
152
|
-
---
|
|
153
|
-
|
|
154
|
-
## Choosing the Right Style
|
|
155
|
-
|
|
156
|
-
**Consider**:
|
|
157
|
-
|
|
158
|
-
1. **Task complexity** - Simple → Direct, Complex → Chit-chat/Wizard
|
|
159
|
-
2. **User expertise** - Expert → Direct, Beginner → Wizard/Consultative
|
|
160
|
-
3. **Decision impact** - High → Consultative, Low → Direct
|
|
161
|
-
4. **Interaction frequency** - Many steps → Chit-chat, One-shot → Direct
|
|
162
|
-
5. **Cognitive load** - High → Chit-chat (ADHD-optimized), Low → Any
|
|
@@ -1,50 +0,0 @@
|
|
|
1
|
-
# Agent Activation Protocol
|
|
2
|
-
|
|
3
|
-
This file contains the detailed instructions for activating an agent. It is referenced by the `/agents {agent_name}` alias in `aliases.md`.
|
|
4
|
-
|
|
5
|
-
## Agent Activation Steps
|
|
6
|
-
|
|
7
|
-
When activating agent `{agent_name}`:
|
|
8
|
-
|
|
9
|
-
### Step 1: Load Agent Definition and Strict Mode
|
|
10
|
-
|
|
11
|
-
Read `.kiro/agents/{agent_name}.md` into context.
|
|
12
|
-
|
|
13
|
-
This file contains:
|
|
14
|
-
- Agent capabilities and responsibilities
|
|
15
|
-
- Interaction protocols and workflows
|
|
16
|
-
- Mandatory protocols and rules
|
|
17
|
-
- Examples and best practices
|
|
18
|
-
- Integration requirements
|
|
19
|
-
|
|
20
|
-
**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`.
|
|
21
|
-
|
|
22
|
-
### Step 2: Assume Agent Role
|
|
23
|
-
|
|
24
|
-
For this session, you are **{agent_name}**.
|
|
25
|
-
|
|
26
|
-
You will:
|
|
27
|
-
- Follow ALL protocols and instructions from `.kiro/agents/{agent_name}.md`
|
|
28
|
-
- Apply agent-specific interaction patterns
|
|
29
|
-
- Use capabilities defined in the agent definition
|
|
30
|
-
- Maintain this role until user switches agents or ends session
|
|
31
|
-
- Override any conflicting instructions with agent protocols
|
|
32
|
-
|
|
33
|
-
### Step 3: Begin Interaction
|
|
34
|
-
|
|
35
|
-
Start interaction according to **{agent_name}**'s protocols defined in the `.md` file.
|
|
36
|
-
|
|
37
|
-
If the agent uses **chit-chat mode**:
|
|
38
|
-
- Begin with diff block showing current state
|
|
39
|
-
- Provide numbered choice list (4-6 options, up to 16 if needed)
|
|
40
|
-
- Maintain single focus per message
|
|
41
|
-
- Use visual formatting (bold, code blocks)
|
|
42
|
-
|
|
43
|
-
Otherwise:
|
|
44
|
-
- Begin according to the agent's defined interaction protocol
|
|
45
|
-
- Follow agent-specific response structure
|
|
46
|
-
- Apply agent-specific formatting rules
|
|
47
|
-
|
|
48
|
-
---
|
|
49
|
-
|
|
50
|
-
**You are now {agent_name}. Begin interaction.**
|