kiro-agents 1.7.1 → 1.8.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 +8 -9
- package/build/npm/bin/cli.js +35 -13
- package/build/npm/dist/agents.md +9 -5
- package/build/npm/dist/aliases.md +27 -0
- package/build/npm/dist/protocols/agent-creation.md +356 -9
- package/build/npm/dist/protocols/agent-management.md +9 -5
- package/build/npm/power/POWER.md +266 -0
- package/build/npm/power/icon.png +0 -0
- package/build/npm/power/mcp.json +3 -0
- package/build/npm/power/steering/agent-activation.md +50 -0
- package/build/npm/power/steering/agent-creation.md +282 -0
- package/build/npm/power/steering/agent-management.md +179 -0
- package/build/npm/power/steering/mode-management.md +139 -0
- package/build/npm/power/steering/mode-switching.md +84 -0
- package/package.json +3 -3
|
@@ -0,0 +1,266 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: "kiro-protocols"
|
|
3
|
+
displayName: "Kiro Protocols"
|
|
4
|
+
description: "Reusable protocol library for AI agents - Load step-by-step workflows on-demand for agent management, mode switching, and interactive patterns"
|
|
5
|
+
keywords: ["protocols", "workflows", "agents", "modes", "procedures", "instructions"]
|
|
6
|
+
author: "R. Beltran"
|
|
7
|
+
version: "1.0.0"
|
|
8
|
+
---
|
|
9
|
+
|
|
10
|
+
# Kiro Protocols
|
|
11
|
+
|
|
12
|
+
## Overview
|
|
13
|
+
|
|
14
|
+
A comprehensive library of reusable protocols (step-by-step workflows) that can be loaded on-demand by AI agents, steering documents, and other Kiro Powers. Each protocol provides detailed instructions for specific tasks like agent management, mode switching, and interactive patterns.
|
|
15
|
+
|
|
16
|
+
**What are Protocols?**
|
|
17
|
+
|
|
18
|
+
Protocols are detailed, step-by-step instruction documents that guide AI through complex workflows. Instead of embedding these instructions directly in every steering document, protocols are loaded dynamically only when needed, reducing context overhead and improving maintainability.
|
|
19
|
+
|
|
20
|
+
**Key Benefits:**
|
|
21
|
+
- **On-Demand Loading** - Protocols load only when needed, minimizing context
|
|
22
|
+
- **Single Source of Truth** - One protocol, many consumers
|
|
23
|
+
- **Reusable Across Powers** - Any power can reference these protocols
|
|
24
|
+
- **Maintainable** - Update once, affects all consumers
|
|
25
|
+
- **Extensible** - Easy to add new protocols
|
|
26
|
+
|
|
27
|
+
## Available Protocols
|
|
28
|
+
|
|
29
|
+
This power provides the following protocols as steering files:
|
|
30
|
+
|
|
31
|
+
### Agent System Protocols
|
|
32
|
+
|
|
33
|
+
- **agent-activation** - Protocol for activating and assuming agent roles
|
|
34
|
+
- Loads agent definition
|
|
35
|
+
- Applies agent protocols
|
|
36
|
+
- Begins agent interaction
|
|
37
|
+
|
|
38
|
+
- **agent-management** - Interactive agent management workflow
|
|
39
|
+
- Chit-chat mode interface
|
|
40
|
+
- Agent directory scanning
|
|
41
|
+
- Create, activate, manage, and view agents
|
|
42
|
+
|
|
43
|
+
- **agent-creation** - Step-by-step agent creation wizard
|
|
44
|
+
- Gather agent information
|
|
45
|
+
- Generate agent definition
|
|
46
|
+
- Validate and finalize
|
|
47
|
+
|
|
48
|
+
### Mode System Protocols
|
|
49
|
+
|
|
50
|
+
- **mode-switching** - Protocol for switching between Kiro modes
|
|
51
|
+
- Load mode definition
|
|
52
|
+
- Preserve context
|
|
53
|
+
- Handle workflow state transitions
|
|
54
|
+
|
|
55
|
+
- **mode-management** - Interactive mode management workflow
|
|
56
|
+
- Mode selection interface
|
|
57
|
+
- Mode comparison
|
|
58
|
+
- Help and documentation
|
|
59
|
+
|
|
60
|
+
## How to Use Protocols
|
|
61
|
+
|
|
62
|
+
### Method 1: Direct Steering File Load (Recommended)
|
|
63
|
+
|
|
64
|
+
Use Kiro's built-in power tools to load protocols on-demand:
|
|
65
|
+
|
|
66
|
+
```markdown
|
|
67
|
+
**Load protocol:**
|
|
68
|
+
1. Call kiroPowers action="activate" with powerName="kiro-protocols"
|
|
69
|
+
2. Call kiroPowers action="readSteering" with powerName="kiro-protocols", steeringFile="agent-activation.md"
|
|
70
|
+
3. Follow all steps from the loaded protocol
|
|
71
|
+
```
|
|
72
|
+
|
|
73
|
+
**Example in steering document:**
|
|
74
|
+
```markdown
|
|
75
|
+
When user activates agent:
|
|
76
|
+
1. Load agent-activation protocol from kiro-protocols power
|
|
77
|
+
2. Execute protocol steps with agent name as parameter
|
|
78
|
+
3. Agent assumes role and begins interaction
|
|
79
|
+
```
|
|
80
|
+
|
|
81
|
+
### Method 2: Instruction Alias Pattern
|
|
82
|
+
|
|
83
|
+
Create reusable aliases that load protocols:
|
|
84
|
+
|
|
85
|
+
```markdown
|
|
86
|
+
<alias>
|
|
87
|
+
<trigger>/protocol {protocol_name}</trigger>
|
|
88
|
+
<definition>
|
|
89
|
+
## Load Protocol: {protocol_name}
|
|
90
|
+
|
|
91
|
+
**Execute protocol loading:**
|
|
92
|
+
1. Call kiroPowers action="activate" with powerName="kiro-protocols"
|
|
93
|
+
2. Call kiroPowers action="readSteering" with powerName="kiro-protocols", steeringFile="{protocol_name}.md"
|
|
94
|
+
3. Follow all steps from the loaded protocol
|
|
95
|
+
</definition>
|
|
96
|
+
</alias>
|
|
97
|
+
```
|
|
98
|
+
|
|
99
|
+
### Method 3: Programmatic Reference
|
|
100
|
+
|
|
101
|
+
Reference protocols in your steering documents:
|
|
102
|
+
|
|
103
|
+
```markdown
|
|
104
|
+
**When creating new agent:**
|
|
105
|
+
- Load `agent-creation.md` protocol from kiro-protocols power
|
|
106
|
+
- Follow wizard steps to gather information
|
|
107
|
+
- Generate agent definition file
|
|
108
|
+
- Validate and offer activation
|
|
109
|
+
```
|
|
110
|
+
|
|
111
|
+
## Protocol Structure
|
|
112
|
+
|
|
113
|
+
Each protocol follows a consistent structure:
|
|
114
|
+
|
|
115
|
+
```markdown
|
|
116
|
+
# Protocol Name
|
|
117
|
+
|
|
118
|
+
Brief description of what this protocol does.
|
|
119
|
+
|
|
120
|
+
## Protocol Steps
|
|
121
|
+
|
|
122
|
+
### Step 1: [Action Name]
|
|
123
|
+
|
|
124
|
+
Detailed instructions for this step...
|
|
125
|
+
|
|
126
|
+
### Step 2: [Action Name]
|
|
127
|
+
|
|
128
|
+
Detailed instructions for this step...
|
|
129
|
+
|
|
130
|
+
[Additional steps...]
|
|
131
|
+
|
|
132
|
+
---
|
|
133
|
+
|
|
134
|
+
**Protocol complete. [Next action guidance]**
|
|
135
|
+
```
|
|
136
|
+
|
|
137
|
+
## Best Practices
|
|
138
|
+
|
|
139
|
+
### For Protocol Consumers
|
|
140
|
+
|
|
141
|
+
1. **Load on-demand** - Only load protocols when needed
|
|
142
|
+
2. **Follow steps sequentially** - Protocols are designed as ordered workflows
|
|
143
|
+
3. **Preserve context** - Protocols may reference previous steps
|
|
144
|
+
4. **Handle errors gracefully** - Protocols include error handling guidance
|
|
145
|
+
|
|
146
|
+
### For Protocol Authors
|
|
147
|
+
|
|
148
|
+
1. **Keep focused** - One protocol, one workflow
|
|
149
|
+
2. **Be explicit** - Clear, actionable steps
|
|
150
|
+
3. **Include examples** - Show expected inputs/outputs
|
|
151
|
+
4. **Document dependencies** - List required context or prerequisites
|
|
152
|
+
5. **Version carefully** - Breaking changes affect all consumers
|
|
153
|
+
|
|
154
|
+
## Creating Custom Protocols
|
|
155
|
+
|
|
156
|
+
Want to add your own protocols to this power?
|
|
157
|
+
|
|
158
|
+
1. **Fork the repository** - https://github.com/Theadd/kiro-agents
|
|
159
|
+
2. **Add protocol file** - Create `.md` file in `src/core/protocols/`
|
|
160
|
+
3. **Follow structure** - Use existing protocols as templates
|
|
161
|
+
4. **Build and test** - Run build script and test in Kiro IDE
|
|
162
|
+
5. **Submit PR** - Contribute back to the community
|
|
163
|
+
|
|
164
|
+
## Integration Examples
|
|
165
|
+
|
|
166
|
+
### Example 1: Agent System
|
|
167
|
+
|
|
168
|
+
```markdown
|
|
169
|
+
# agents.md (steering document)
|
|
170
|
+
|
|
171
|
+
When user types `/agents {name}`:
|
|
172
|
+
1. Load agent-activation protocol
|
|
173
|
+
2. Pass agent name as parameter
|
|
174
|
+
3. Execute protocol steps
|
|
175
|
+
4. Agent activates and assumes role
|
|
176
|
+
```
|
|
177
|
+
|
|
178
|
+
### Example 2: Mode System
|
|
179
|
+
|
|
180
|
+
```markdown
|
|
181
|
+
# modes.md (steering document)
|
|
182
|
+
|
|
183
|
+
When user types `/modes {mode}`:
|
|
184
|
+
1. Load mode-switching protocol
|
|
185
|
+
2. Pass mode name as parameter
|
|
186
|
+
3. Check for workflow state preservation
|
|
187
|
+
4. Execute mode switch
|
|
188
|
+
```
|
|
189
|
+
|
|
190
|
+
### Example 3: Custom Power
|
|
191
|
+
|
|
192
|
+
```markdown
|
|
193
|
+
# my-custom-power/steering/workflow.md
|
|
194
|
+
|
|
195
|
+
When complex workflow needed:
|
|
196
|
+
1. Load agent-management protocol from kiro-protocols
|
|
197
|
+
2. Use interactive chit-chat pattern
|
|
198
|
+
3. Guide user through multi-step process
|
|
199
|
+
4. Apply custom power logic
|
|
200
|
+
```
|
|
201
|
+
|
|
202
|
+
## Troubleshooting
|
|
203
|
+
|
|
204
|
+
### Protocol Not Found
|
|
205
|
+
|
|
206
|
+
**Problem:** Error loading protocol file
|
|
207
|
+
|
|
208
|
+
**Solutions:**
|
|
209
|
+
1. Verify kiro-protocols power is installed
|
|
210
|
+
2. Check protocol name spelling (case-sensitive)
|
|
211
|
+
3. Ensure protocol exists in available list above
|
|
212
|
+
4. Try reloading power: Kiro Powers panel → Reload
|
|
213
|
+
|
|
214
|
+
### Protocol Outdated
|
|
215
|
+
|
|
216
|
+
**Problem:** Protocol references old paths or commands
|
|
217
|
+
|
|
218
|
+
**Solutions:**
|
|
219
|
+
1. Update kiro-protocols power to latest version
|
|
220
|
+
2. Check GitHub releases for breaking changes
|
|
221
|
+
3. Review protocol changelog in repository
|
|
222
|
+
|
|
223
|
+
### Context Overflow
|
|
224
|
+
|
|
225
|
+
**Problem:** Too many protocols loaded at once
|
|
226
|
+
|
|
227
|
+
**Solutions:**
|
|
228
|
+
1. Load protocols only when needed (not upfront)
|
|
229
|
+
2. Use on-demand loading pattern
|
|
230
|
+
3. Consider splitting complex workflows
|
|
231
|
+
4. Unload unused protocols from context
|
|
232
|
+
|
|
233
|
+
## Version Compatibility
|
|
234
|
+
|
|
235
|
+
This power follows semantic versioning:
|
|
236
|
+
|
|
237
|
+
- **Major version** - Breaking changes to protocol structure
|
|
238
|
+
- **Minor version** - New protocols added
|
|
239
|
+
- **Patch version** - Bug fixes and clarifications
|
|
240
|
+
|
|
241
|
+
**Current Version:** 1.0.0
|
|
242
|
+
|
|
243
|
+
**Compatibility:**
|
|
244
|
+
- Kiro IDE: All versions with Powers support
|
|
245
|
+
- kiro-agents: v1.6.0+
|
|
246
|
+
|
|
247
|
+
## Contributing
|
|
248
|
+
|
|
249
|
+
Contributions welcome! See repository for guidelines:
|
|
250
|
+
- https://github.com/Theadd/kiro-agents
|
|
251
|
+
|
|
252
|
+
**Ways to contribute:**
|
|
253
|
+
1. Report issues with existing protocols
|
|
254
|
+
2. Suggest new protocols
|
|
255
|
+
3. Improve protocol documentation
|
|
256
|
+
4. Submit protocol enhancements
|
|
257
|
+
|
|
258
|
+
## License
|
|
259
|
+
|
|
260
|
+
MIT License - See repository for full license text
|
|
261
|
+
|
|
262
|
+
---
|
|
263
|
+
|
|
264
|
+
**Power:** kiro-protocols
|
|
265
|
+
**Repository:** https://github.com/Theadd/kiro-agents
|
|
266
|
+
**Version:** 1.0.0
|
|
Binary file
|
|
@@ -0,0 +1,50 @@
|
|
|
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.**
|
|
@@ -0,0 +1,282 @@
|
|
|
1
|
+
# Agent Creation Protocol
|
|
2
|
+
|
|
3
|
+
This file contains the detailed instructions for creating new agents. It is referenced during agent creation workflow in agent management mode.
|
|
4
|
+
|
|
5
|
+
## Agent Creation Steps
|
|
6
|
+
|
|
7
|
+
When creating a new agent:
|
|
8
|
+
|
|
9
|
+
### Step 1: Initialize Creation Wizard
|
|
10
|
+
|
|
11
|
+
Use chit-chat mode for the creation process:
|
|
12
|
+
|
|
13
|
+
```diff
|
|
14
|
+
👉 Agent creation wizard
|
|
15
|
+
⏳ Gathering agent information
|
|
16
|
+
```
|
|
17
|
+
|
|
18
|
+
**Current Focus**: Creating new agent
|
|
19
|
+
|
|
20
|
+
### Step 2: Collect Agent Information
|
|
21
|
+
|
|
22
|
+
Guide user through agent definition with numbered choices:
|
|
23
|
+
|
|
24
|
+
#### 2.1: Agent Type Selection
|
|
25
|
+
|
|
26
|
+
**What type of agent would you like to create?**
|
|
27
|
+
|
|
28
|
+
1. **Specialist** - Focused on specific domain (e.g., refactoring, testing)
|
|
29
|
+
- Deep expertise in narrow area
|
|
30
|
+
- Clear boundaries of responsibility
|
|
31
|
+
- Best for: Specialized tasks requiring domain expertise
|
|
32
|
+
|
|
33
|
+
2. **Generalist** - Broad capabilities across domains
|
|
34
|
+
- Flexible and adaptable
|
|
35
|
+
- Good for exploration and discovery
|
|
36
|
+
- Best for: General-purpose assistance
|
|
37
|
+
|
|
38
|
+
3. **Coordinator** - Manages other agents
|
|
39
|
+
- Orchestrates complex workflows
|
|
40
|
+
- Handles agent handoffs
|
|
41
|
+
- Best for: Multi-agent workflows
|
|
42
|
+
|
|
43
|
+
#### 2.2: Agent Name
|
|
44
|
+
|
|
45
|
+
**What should we name this agent?**
|
|
46
|
+
|
|
47
|
+
Requirements:
|
|
48
|
+
- Lowercase with hyphens (e.g., `refactor-architect`)
|
|
49
|
+
- No spaces or special characters
|
|
50
|
+
- Descriptive of agent's purpose
|
|
51
|
+
- Must be unique (check `.kiro/agents/` directory)
|
|
52
|
+
|
|
53
|
+
#### 2.3: Agent Description
|
|
54
|
+
|
|
55
|
+
**Provide a brief description (1-2 sentences):**
|
|
56
|
+
|
|
57
|
+
This will be shown in agent listings and help users understand when to use this agent.
|
|
58
|
+
|
|
59
|
+
Example: "Specialized in code refactoring with focus on design patterns, SOLID principles, and maintainability improvements."
|
|
60
|
+
|
|
61
|
+
#### 2.4: Core Responsibilities
|
|
62
|
+
|
|
63
|
+
**What are the agent's primary responsibilities? (3-5 items)**
|
|
64
|
+
|
|
65
|
+
Example:
|
|
66
|
+
- Analyze code structure and identify refactoring opportunities
|
|
67
|
+
- Apply design patterns appropriately
|
|
68
|
+
- Improve code maintainability and readability
|
|
69
|
+
- Ensure SOLID principles compliance
|
|
70
|
+
|
|
71
|
+
#### 2.5: Capabilities
|
|
72
|
+
|
|
73
|
+
**What specific capabilities should this agent have?**
|
|
74
|
+
|
|
75
|
+
Group by category. Example:
|
|
76
|
+
|
|
77
|
+
**Code Analysis:**
|
|
78
|
+
- Detect code smells and anti-patterns
|
|
79
|
+
- Identify coupling and cohesion issues
|
|
80
|
+
- Analyze complexity metrics
|
|
81
|
+
|
|
82
|
+
**Refactoring:**
|
|
83
|
+
- Extract methods and classes
|
|
84
|
+
- Apply design patterns
|
|
85
|
+
- Simplify conditional logic
|
|
86
|
+
|
|
87
|
+
#### 2.6: Interaction Protocol
|
|
88
|
+
|
|
89
|
+
**How should this agent interact with users?**
|
|
90
|
+
|
|
91
|
+
1. **Formal** - Professional, structured responses
|
|
92
|
+
2. **Casual** - Conversational, friendly tone
|
|
93
|
+
3. **Technical** - Precise, detailed explanations
|
|
94
|
+
4. **Chit-chat mode** - Interactive with diff blocks and numbered choices
|
|
95
|
+
|
|
96
|
+
**Confirmation requirements:**
|
|
97
|
+
- Always confirm before changes
|
|
98
|
+
- Never confirm (trusted operations)
|
|
99
|
+
- Confirm only risky operations
|
|
100
|
+
|
|
101
|
+
#### 2.7: Mandatory Protocols
|
|
102
|
+
|
|
103
|
+
**What rules MUST this agent follow?**
|
|
104
|
+
|
|
105
|
+
Example:
|
|
106
|
+
1. **Always analyze before refactoring** - Never refactor without understanding impact
|
|
107
|
+
2. **Preserve functionality** - Ensure tests pass after refactoring
|
|
108
|
+
3. **Document changes** - Explain why refactoring was done
|
|
109
|
+
|
|
110
|
+
#### 2.8: Workflows
|
|
111
|
+
|
|
112
|
+
**Define step-by-step processes for common tasks:**
|
|
113
|
+
|
|
114
|
+
Example workflow:
|
|
115
|
+
|
|
116
|
+
**Refactor Code:**
|
|
117
|
+
1. Analyze current code structure
|
|
118
|
+
2. Identify refactoring opportunities
|
|
119
|
+
3. Propose refactoring plan
|
|
120
|
+
4. Get user confirmation
|
|
121
|
+
5. Apply refactoring
|
|
122
|
+
6. Verify tests pass
|
|
123
|
+
7. Document changes
|
|
124
|
+
|
|
125
|
+
### Step 3: Generate Agent Definition File
|
|
126
|
+
|
|
127
|
+
Create `.kiro/agents/{agent-name}.md` with this structure:
|
|
128
|
+
|
|
129
|
+
```markdown
|
|
130
|
+
---
|
|
131
|
+
name: {agent-name}
|
|
132
|
+
type: {specialist|generalist|coordinator}
|
|
133
|
+
description: {brief description}
|
|
134
|
+
version: 1.0.0
|
|
135
|
+
---
|
|
136
|
+
|
|
137
|
+
# {Agent Name}
|
|
138
|
+
|
|
139
|
+
{Brief overview of agent purpose and capabilities}
|
|
140
|
+
|
|
141
|
+
## Core Responsibilities
|
|
142
|
+
|
|
143
|
+
{List of primary responsibilities}
|
|
144
|
+
|
|
145
|
+
## Capabilities
|
|
146
|
+
|
|
147
|
+
{Detailed list organized by category}
|
|
148
|
+
|
|
149
|
+
## Interaction Protocol
|
|
150
|
+
|
|
151
|
+
{How agent responds to user input}
|
|
152
|
+
|
|
153
|
+
**Response Style:** {formal|casual|technical|chit-chat}
|
|
154
|
+
|
|
155
|
+
**Formatting Preferences:**
|
|
156
|
+
- {Code blocks, lists, tables, etc.}
|
|
157
|
+
|
|
158
|
+
**Confirmation Requirements:**
|
|
159
|
+
- {Always, never, when risky}
|
|
160
|
+
|
|
161
|
+
**Error Handling:**
|
|
162
|
+
- {How agent handles errors}
|
|
163
|
+
|
|
164
|
+
## Mandatory Protocols
|
|
165
|
+
|
|
166
|
+
{Rules agent MUST follow with rationale}
|
|
167
|
+
|
|
168
|
+
## Workflows
|
|
169
|
+
|
|
170
|
+
{Step-by-step processes for common tasks}
|
|
171
|
+
|
|
172
|
+
## Examples
|
|
173
|
+
|
|
174
|
+
### Example 1: {Scenario Name}
|
|
175
|
+
|
|
176
|
+
**User:** {Example user input}
|
|
177
|
+
**Agent:** {Example agent response}
|
|
178
|
+
|
|
179
|
+
### Example 2: {Scenario Name}
|
|
180
|
+
|
|
181
|
+
**User:** {Example user input}
|
|
182
|
+
**Agent:** {Example agent response}
|
|
183
|
+
|
|
184
|
+
## Integration Points
|
|
185
|
+
|
|
186
|
+
### Required Steering Documents
|
|
187
|
+
- `{steering-name}.md` - {Why it's required}
|
|
188
|
+
|
|
189
|
+
### Optional Steering Documents
|
|
190
|
+
- `{steering-name}.md` - {When to load}
|
|
191
|
+
|
|
192
|
+
## Conflict Priorities
|
|
193
|
+
|
|
194
|
+
When conflicts arise, this agent prioritizes:
|
|
195
|
+
|
|
196
|
+
1. User safety and data integrity
|
|
197
|
+
2. Agent mandatory protocols
|
|
198
|
+
3. Project-specific requirements
|
|
199
|
+
4. Performance and efficiency
|
|
200
|
+
5. Code style and conventions
|
|
201
|
+
|
|
202
|
+
## Best Practices
|
|
203
|
+
|
|
204
|
+
- {Best practice 1 for using this agent}
|
|
205
|
+
- {Best practice 2 for using this agent}
|
|
206
|
+
- {Best practice 3 for using this agent}
|
|
207
|
+
|
|
208
|
+
## Advanced Features
|
|
209
|
+
|
|
210
|
+
- {Advanced feature 1 description}
|
|
211
|
+
- {Advanced feature 2 description}
|
|
212
|
+
|
|
213
|
+
## Error Handling
|
|
214
|
+
|
|
215
|
+
- **Syntax errors** - {Approach description}
|
|
216
|
+
- **Logic errors** - {Approach description}
|
|
217
|
+
- **Ambiguous input** - {Approach description}
|
|
218
|
+
|
|
219
|
+
## Success Metrics
|
|
220
|
+
|
|
221
|
+
- {Metric 1 description}
|
|
222
|
+
- {Metric 2 description}
|
|
223
|
+
```
|
|
224
|
+
|
|
225
|
+
### Step 4: Validate Agent Definition
|
|
226
|
+
|
|
227
|
+
Check that the generated agent file:
|
|
228
|
+
|
|
229
|
+
1. **Has valid YAML frontmatter** with required fields
|
|
230
|
+
2. **Contains all required sections**:
|
|
231
|
+
- Core Responsibilities
|
|
232
|
+
- Capabilities
|
|
233
|
+
- Interaction Protocol
|
|
234
|
+
- Mandatory Protocols
|
|
235
|
+
- Workflows
|
|
236
|
+
- Examples
|
|
237
|
+
3. **Has no syntax errors** in markdown
|
|
238
|
+
4. **Follows naming conventions** (lowercase with hyphens)
|
|
239
|
+
5. **Is unique** (no existing agent with same name)
|
|
240
|
+
|
|
241
|
+
### Step 5: Confirm and Finalize
|
|
242
|
+
|
|
243
|
+
Show summary to user:
|
|
244
|
+
|
|
245
|
+
```diff
|
|
246
|
+
👉 Agent creation complete
|
|
247
|
+
✅ Agent definition created
|
|
248
|
+
```
|
|
249
|
+
|
|
250
|
+
**Agent Created:** `{agent-name}`
|
|
251
|
+
|
|
252
|
+
**Location:** `.kiro/agents/{agent-name}.md`
|
|
253
|
+
|
|
254
|
+
**Summary:**
|
|
255
|
+
- Type: {type}
|
|
256
|
+
- Responsibilities: {count} defined
|
|
257
|
+
- Capabilities: {count} defined
|
|
258
|
+
- Workflows: {count} defined
|
|
259
|
+
|
|
260
|
+
**What would you like to do next?**
|
|
261
|
+
|
|
262
|
+
1. **Activate this agent** - Start using it immediately
|
|
263
|
+
2. **View agent definition** - Review the generated file
|
|
264
|
+
3. **Edit agent** - Make modifications
|
|
265
|
+
4. **Create another agent** - Start new creation wizard
|
|
266
|
+
5. **Return to agent management** - Back to main menu
|
|
267
|
+
6. **Exit** - Return to normal mode
|
|
268
|
+
|
|
269
|
+
### Step 6: Post-Creation Actions
|
|
270
|
+
|
|
271
|
+
Based on user choice:
|
|
272
|
+
|
|
273
|
+
- **Activate**: Execute `/agents {agent-name}` command
|
|
274
|
+
- **View**: Display full agent definition with formatting
|
|
275
|
+
- **Edit**: Open agent file for modifications
|
|
276
|
+
- **Create another**: Restart creation wizard
|
|
277
|
+
- **Return**: Go back to agent management menu
|
|
278
|
+
- **Exit**: Return to normal interaction
|
|
279
|
+
|
|
280
|
+
---
|
|
281
|
+
|
|
282
|
+
**Agent creation wizard ready. Begin collecting information.**
|