kiro-agent-team 1.0.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/.kiro/README.md +228 -0
- package/.kiro/agents/backend-engineer.json +6 -0
- package/.kiro/agents/backend-engineer.md +643 -0
- package/.kiro/agents/database-specialist.json +6 -0
- package/.kiro/agents/database-specialist.md +390 -0
- package/.kiro/agents/development-logger.json +6 -0
- package/.kiro/agents/development-logger.md +265 -0
- package/.kiro/agents/devops-engineer.json +6 -0
- package/.kiro/agents/devops-engineer.md +287 -0
- package/.kiro/agents/frontend-architect.json +6 -0
- package/.kiro/agents/frontend-architect.md +1032 -0
- package/.kiro/agents/hooks/backend-engineer-hooks.yaml +540 -0
- package/.kiro/agents/hooks/database-specialist-hooks.yaml +488 -0
- package/.kiro/agents/hooks/development-logger-hooks.yaml +361 -0
- package/.kiro/agents/hooks/devops-engineer-hooks.yaml +345 -0
- package/.kiro/agents/hooks/frontend-architect-hooks.yaml +521 -0
- package/.kiro/agents/hooks/project-manager-hooks.yaml +513 -0
- package/.kiro/agents/hooks/security-specialist-hooks.yaml +358 -0
- package/.kiro/agents/hooks/test-orchestrator-hooks.yaml +380 -0
- package/.kiro/agents/hooks/ui-ux-designer-hooks.yaml +353 -0
- package/.kiro/agents/project-manager.json +6 -0
- package/.kiro/agents/project-manager.md +344 -0
- package/.kiro/agents/prompts/backend-engineer-system.md +815 -0
- package/.kiro/agents/prompts/database-specialist-system.md +332 -0
- package/.kiro/agents/prompts/development-logger-system.md +232 -0
- package/.kiro/agents/prompts/devops-engineer-system.md +260 -0
- package/.kiro/agents/prompts/frontend-architect-system.md +305 -0
- package/.kiro/agents/prompts/project-manager-system.md +285 -0
- package/.kiro/agents/prompts/security-specialist-system.md +231 -0
- package/.kiro/agents/prompts/test-orchestrator-system.md +214 -0
- package/.kiro/agents/prompts/ui-ux-designer-system.md +270 -0
- package/.kiro/agents/security-specialist.json +6 -0
- package/.kiro/agents/security-specialist.md +277 -0
- package/.kiro/agents/test-orchestrator.json +6 -0
- package/.kiro/agents/test-orchestrator.md +266 -0
- package/.kiro/agents/ui-ux-designer.json +6 -0
- package/.kiro/agents/ui-ux-designer.md +284 -0
- package/.kiro/devlog/00-START-HERE.md +444 -0
- package/.kiro/devlog/COMPLETE-WORKFLOW.md +553 -0
- package/.kiro/devlog/DEVLOG-INTEGRATION.md +413 -0
- package/.kiro/devlog/DEVLOG-PROCESS-FLOWS.md +484 -0
- package/.kiro/devlog/DEVLOG-QUICK-REF.md +299 -0
- package/.kiro/devlog/DEVLOG.md +22 -0
- package/.kiro/devlog/IMPLEMENTATION-COMPLETE.txt +434 -0
- package/.kiro/devlog/IMPLEMENTATION-SUMMARY.md +358 -0
- package/.kiro/devlog/README.md +363 -0
- package/.kiro/devlog/devlog-update.bat +136 -0
- package/.kiro/devlog/devlog-update.sh +275 -0
- package/.kiro/devlog/feature-completion-hook.bat +78 -0
- package/.kiro/devlog/feature-completion-hook.sh +84 -0
- package/.kiro/documentation/cli.md +31 -0
- package/.kiro/documentation/docs_cli.md +41 -0
- package/.kiro/documentation/docs_cli_authentication.md +43 -0
- package/.kiro/documentation/docs_cli_autocomplete.md +132 -0
- package/.kiro/documentation/docs_cli_billing.md +31 -0
- package/.kiro/documentation/docs_cli_billing_contact-support.md +43 -0
- package/.kiro/documentation/docs_cli_billing_managing-taxes.md +67 -0
- package/.kiro/documentation/docs_cli_billing_related-questions.md +49 -0
- package/.kiro/documentation/docs_cli_billing_subscription-portal.md +31 -0
- package/.kiro/documentation/docs_cli_chat.md +84 -0
- package/.kiro/documentation/docs_cli_chat_configuration.md +40 -0
- package/.kiro/documentation/docs_cli_chat_context.md +258 -0
- package/.kiro/documentation/docs_cli_chat_git-aware-selection.md +41 -0
- package/.kiro/documentation/docs_cli_chat_images.md +53 -0
- package/.kiro/documentation/docs_cli_chat_manage-prompts.md +216 -0
- package/.kiro/documentation/docs_cli_chat_model-selection.md +153 -0
- package/.kiro/documentation/docs_cli_chat_permissions.md +68 -0
- package/.kiro/documentation/docs_cli_chat_planning-agent.md +230 -0
- package/.kiro/documentation/docs_cli_chat_responding.md +123 -0
- package/.kiro/documentation/docs_cli_chat_security.md +87 -0
- package/.kiro/documentation/docs_cli_chat_subagents.md +77 -0
- package/.kiro/documentation/docs_cli_code-intelligence.md +251 -0
- package/.kiro/documentation/docs_cli_custom-agents.md +37 -0
- package/.kiro/documentation/docs_cli_custom-agents_configuration-reference.md +941 -0
- package/.kiro/documentation/docs_cli_custom-agents_creating.md +93 -0
- package/.kiro/documentation/docs_cli_custom-agents_examples.md +360 -0
- package/.kiro/documentation/docs_cli_custom-agents_troubleshooting.md +180 -0
- package/.kiro/documentation/docs_cli_enterprise_billing.md +33 -0
- package/.kiro/documentation/docs_cli_enterprise_concepts.md +34 -0
- package/.kiro/documentation/docs_cli_enterprise_getting-started.md +19 -0
- package/.kiro/documentation/docs_cli_enterprise_iam.md +251 -0
- package/.kiro/documentation/docs_cli_enterprise_monitor-and-track.md +15 -0
- package/.kiro/documentation/docs_cli_enterprise_monitor-and-track_dashboard.md +62 -0
- package/.kiro/documentation/docs_cli_enterprise_monitor-and-track_prompt-logging.md +165 -0
- package/.kiro/documentation/docs_cli_enterprise_monitor-and-track_user-activity.md +123 -0
- package/.kiro/documentation/docs_cli_enterprise_settings.md +15 -0
- package/.kiro/documentation/docs_cli_enterprise_subscribe.md +36 -0
- package/.kiro/documentation/docs_cli_enterprise_subscription-management.md +55 -0
- package/.kiro/documentation/docs_cli_enterprise_supported-regions.md +39 -0
- package/.kiro/documentation/docs_cli_experimental.md +282 -0
- package/.kiro/documentation/docs_cli_experimental_checkpointing.md +439 -0
- package/.kiro/documentation/docs_cli_experimental_delegate.md +422 -0
- package/.kiro/documentation/docs_cli_experimental_knowledge-management.md +449 -0
- package/.kiro/documentation/docs_cli_experimental_tangent-mode.md +357 -0
- package/.kiro/documentation/docs_cli_experimental_thinking.md +331 -0
- package/.kiro/documentation/docs_cli_experimental_todo-lists.md +385 -0
- package/.kiro/documentation/docs_cli_hooks.md +207 -0
- package/.kiro/documentation/docs_cli_installation.md +235 -0
- package/.kiro/documentation/docs_cli_mcp.md +106 -0
- package/.kiro/documentation/docs_cli_mcp_configuration.md +294 -0
- package/.kiro/documentation/docs_cli_mcp_examples.md +273 -0
- package/.kiro/documentation/docs_cli_mcp_governance.md +436 -0
- package/.kiro/documentation/docs_cli_mcp_security.md +77 -0
- package/.kiro/documentation/docs_cli_migrating-from-q.md +129 -0
- package/.kiro/documentation/docs_cli_privacy-and-security.md +83 -0
- package/.kiro/documentation/docs_cli_privacy-and-security_compliance-validation.md +17 -0
- package/.kiro/documentation/docs_cli_privacy-and-security_data-protection.md +104 -0
- package/.kiro/documentation/docs_cli_privacy-and-security_firewalls.md +26 -0
- package/.kiro/documentation/docs_cli_privacy-and-security_infrastructure-security.md +10 -0
- package/.kiro/documentation/docs_cli_privacy-and-security_vpc-endpoints.md +41 -0
- package/.kiro/documentation/docs_cli_reference_built-in-tools.md +624 -0
- package/.kiro/documentation/docs_cli_reference_cli-commands.md +689 -0
- package/.kiro/documentation/docs_cli_reference_settings.md +294 -0
- package/.kiro/documentation/docs_cli_reference_slash-commands.md +559 -0
- package/.kiro/documentation/docs_cli_steering.md +84 -0
- package/.kiro/guides/AGENT_WORKFLOW_GUIDE.md +294 -0
- package/.kiro/guides/DEVLOG.md +882 -0
- package/.kiro/guides/IMPLEMENTATION_EXAMPLES.md +611 -0
- package/.kiro/guides/PIV Loop.md +122 -0
- package/.kiro/guides/PIV Loop.png +0 -0
- package/.kiro/guides/PIVLoop.png +0 -0
- package/.kiro/guides/QUICK_REFERENCE.md +202 -0
- package/.kiro/guides/README.md +149 -0
- package/.kiro/guides/advanced-patterns.md +514 -0
- package/.kiro/guides/agent-coordination.md +434 -0
- package/.kiro/guides/core-workflows.md +409 -0
- package/.kiro/guides/emergency-procedures.md +414 -0
- package/.kiro/guides/project-evaluation.md +534 -0
- package/.kiro/guides/quality-assurance.md +431 -0
- package/.kiro/guides/quick-start.md +235 -0
- package/.kiro/guides/troubleshooting.md +575 -0
- package/.kiro/guides/walkthroughs.md +711 -0
- package/.kiro/prompts/add-to-devlog.md +263 -0
- package/.kiro/prompts/code-review-fix.md +18 -0
- package/.kiro/prompts/code-review-hackathon.md +167 -0
- package/.kiro/prompts/code-review-security.md +454 -0
- package/.kiro/prompts/code-review.md +113 -0
- package/.kiro/prompts/create-prd.md +151 -0
- package/.kiro/prompts/execute-backend.md +257 -0
- package/.kiro/prompts/execute-frontend.md +438 -0
- package/.kiro/prompts/execute-logging.md +491 -0
- package/.kiro/prompts/execute-security.md +482 -0
- package/.kiro/prompts/execute-testing.md +528 -0
- package/.kiro/prompts/execute.md +101 -0
- package/.kiro/prompts/execution-report.md +72 -0
- package/.kiro/prompts/implement-fix.md +228 -0
- package/.kiro/prompts/plan-feature.md +433 -0
- package/.kiro/prompts/prime.md +73 -0
- package/.kiro/prompts/quality-metrics.md +622 -0
- package/.kiro/prompts/quickstart.md +318 -0
- package/.kiro/prompts/rca.md +220 -0
- package/.kiro/prompts/system-review.md +189 -0
- package/README.md +32 -0
- package/bin/cli.js +97 -0
- package/package.json +33 -0
|
@@ -0,0 +1,294 @@
|
|
|
1
|
+
# Kiro-CLI Agent Team Workflow Guide
|
|
2
|
+
|
|
3
|
+
## Overview
|
|
4
|
+
|
|
5
|
+
This guide demonstrates how to leverage our 9-agent team with integrated prompt workflows for systematic, quality-driven development. Each agent now has enhanced capabilities through prompt integration, creating a comprehensive development ecosystem.
|
|
6
|
+
|
|
7
|
+
## Quick Reference: Agent + Prompt Integration
|
|
8
|
+
|
|
9
|
+
| Agent | Primary Prompts | Use Cases |
|
|
10
|
+
|-------|----------------|-----------|
|
|
11
|
+
| **Project Manager** | `@prime`, `@plan-feature`, `@create-prd` | Project setup, feature planning, requirements |
|
|
12
|
+
| **Test Orchestrator** | `@code-review`, `@execution-report`, `@code-review-hackathon` | Quality assurance, project evaluation |
|
|
13
|
+
| **Development Logger** | `@system-review` | Process improvement, workflow analysis |
|
|
14
|
+
| **Security Specialist** | `@rca`, `@implement-fix` | Security incident analysis and resolution |
|
|
15
|
+
| **All Agents** | `@execute` | Systematic task implementation |
|
|
16
|
+
|
|
17
|
+
## Core Development Workflows
|
|
18
|
+
|
|
19
|
+
### 🚀 Workflow 1: New Project Setup
|
|
20
|
+
|
|
21
|
+
**Scenario**: Starting a new fullstack application project
|
|
22
|
+
|
|
23
|
+
**Steps**:
|
|
24
|
+
1. **Initialize Project Context**
|
|
25
|
+
```
|
|
26
|
+
@prime
|
|
27
|
+
```
|
|
28
|
+
- Project Manager loads comprehensive project understanding
|
|
29
|
+
- Analyzes codebase structure, documentation, and requirements
|
|
30
|
+
- Establishes baseline context for all agents
|
|
31
|
+
|
|
32
|
+
2. **Create Project in Archon**
|
|
33
|
+
```
|
|
34
|
+
Project Manager: Create new project "TaskFlow App" with initial task breakdown
|
|
35
|
+
```
|
|
36
|
+
- Sets up project structure in Archon knowledge base
|
|
37
|
+
- Creates initial milestone and task framework
|
|
38
|
+
- Establishes agent coordination protocols
|
|
39
|
+
|
|
40
|
+
3. **Plan First Feature**
|
|
41
|
+
```
|
|
42
|
+
@plan-feature "User Authentication System"
|
|
43
|
+
```
|
|
44
|
+
- Project Manager creates comprehensive implementation plan
|
|
45
|
+
- Breaks down feature into granular tasks (30min-4hr each)
|
|
46
|
+
- Assigns tasks to appropriate specialist agents
|
|
47
|
+
- Establishes dependencies and timeline
|
|
48
|
+
|
|
49
|
+
**Expected Outcome**: Fully planned project with clear task assignments and systematic approach to implementation.
|
|
50
|
+
|
|
51
|
+
---
|
|
52
|
+
|
|
53
|
+
### 🔧 Workflow 2: Feature Development Cycle
|
|
54
|
+
|
|
55
|
+
**Scenario**: Implementing a new feature from planning to deployment
|
|
56
|
+
|
|
57
|
+
**Steps**:
|
|
58
|
+
1. **Feature Planning** (Project Manager)
|
|
59
|
+
```
|
|
60
|
+
@plan-feature "Task Management Dashboard"
|
|
61
|
+
```
|
|
62
|
+
- Comprehensive feature analysis and architecture decisions
|
|
63
|
+
- Task breakdown with clear acceptance criteria
|
|
64
|
+
- Agent assignment based on expertise and availability
|
|
65
|
+
|
|
66
|
+
2. **Systematic Implementation** (Assigned Agents)
|
|
67
|
+
```
|
|
68
|
+
@execute
|
|
69
|
+
```
|
|
70
|
+
- Backend Engineer: API endpoints and business logic
|
|
71
|
+
- Frontend Architect: UI components and state management
|
|
72
|
+
- Database Specialist: Schema updates and data layer
|
|
73
|
+
- Each agent follows systematic execution framework
|
|
74
|
+
|
|
75
|
+
3. **Quality Assurance** (Test Orchestrator)
|
|
76
|
+
```
|
|
77
|
+
@code-review
|
|
78
|
+
```
|
|
79
|
+
- Comprehensive code quality assessment
|
|
80
|
+
- Security, performance, and maintainability review
|
|
81
|
+
- Test coverage and quality gate validation
|
|
82
|
+
|
|
83
|
+
4. **Implementation Reporting** (Test Orchestrator)
|
|
84
|
+
```
|
|
85
|
+
@execution-report
|
|
86
|
+
```
|
|
87
|
+
- Detailed analysis of what was implemented vs planned
|
|
88
|
+
- Quality metrics and validation results
|
|
89
|
+
- Recommendations for process improvement
|
|
90
|
+
|
|
91
|
+
5. **Process Analysis** (Development Logger)
|
|
92
|
+
```
|
|
93
|
+
@system-review [plan-file] [execution-report]
|
|
94
|
+
```
|
|
95
|
+
- Meta-analysis of implementation vs plan adherence
|
|
96
|
+
- Identification of process improvements
|
|
97
|
+
- Updates to workflow and agent coordination
|
|
98
|
+
|
|
99
|
+
**Expected Outcome**: High-quality feature implementation with comprehensive documentation and continuous process improvement.
|
|
100
|
+
|
|
101
|
+
---
|
|
102
|
+
|
|
103
|
+
### 🐛 Workflow 3: Bug Investigation and Resolution
|
|
104
|
+
|
|
105
|
+
**Scenario**: Critical security vulnerability discovered in production
|
|
106
|
+
|
|
107
|
+
**Steps**:
|
|
108
|
+
1. **Root Cause Analysis** (Security Specialist)
|
|
109
|
+
```
|
|
110
|
+
@rca [github-issue-id]
|
|
111
|
+
```
|
|
112
|
+
- Systematic investigation of security vulnerability
|
|
113
|
+
- Analysis of affected components and impact scope
|
|
114
|
+
- Documentation of root cause and proposed fix strategy
|
|
115
|
+
|
|
116
|
+
2. **Fix Implementation** (Security Specialist)
|
|
117
|
+
```
|
|
118
|
+
@implement-fix [github-issue-id]
|
|
119
|
+
```
|
|
120
|
+
- Implementation based on RCA document findings
|
|
121
|
+
- Security-focused testing and validation
|
|
122
|
+
- Documentation of fix and prevention measures
|
|
123
|
+
|
|
124
|
+
3. **Quality Validation** (Test Orchestrator)
|
|
125
|
+
```
|
|
126
|
+
@code-review
|
|
127
|
+
```
|
|
128
|
+
- Security-focused code review of implemented fix
|
|
129
|
+
- Regression testing and security validation
|
|
130
|
+
- Deployment readiness assessment
|
|
131
|
+
|
|
132
|
+
4. **Process Learning** (Development Logger)
|
|
133
|
+
```
|
|
134
|
+
@system-review [rca-document] [fix-implementation-report]
|
|
135
|
+
```
|
|
136
|
+
- Analysis of incident response effectiveness
|
|
137
|
+
- Identification of prevention measures
|
|
138
|
+
- Updates to security processes and monitoring
|
|
139
|
+
|
|
140
|
+
**Expected Outcome**: Systematic security issue resolution with comprehensive documentation and process improvements to prevent recurrence.
|
|
141
|
+
|
|
142
|
+
---
|
|
143
|
+
|
|
144
|
+
### 🏆 Workflow 4: Project Evaluation and Quality Assessment
|
|
145
|
+
|
|
146
|
+
**Scenario**: Comprehensive project evaluation for hackathon submission or major release
|
|
147
|
+
|
|
148
|
+
**Steps**:
|
|
149
|
+
1. **Comprehensive Project Review** (Test Orchestrator)
|
|
150
|
+
```
|
|
151
|
+
@code-review-hackathon
|
|
152
|
+
```
|
|
153
|
+
- Evaluation against multiple quality criteria
|
|
154
|
+
- Assessment of application quality, documentation, innovation
|
|
155
|
+
- Scoring and detailed feedback on all aspects
|
|
156
|
+
|
|
157
|
+
2. **Requirements Documentation** (Project Manager)
|
|
158
|
+
```
|
|
159
|
+
@create-prd "Complete Application Specification"
|
|
160
|
+
```
|
|
161
|
+
- Comprehensive product requirements documentation
|
|
162
|
+
- Feature specifications and acceptance criteria
|
|
163
|
+
- Stakeholder alignment and project scope definition
|
|
164
|
+
|
|
165
|
+
3. **Process Effectiveness Analysis** (Development Logger)
|
|
166
|
+
```
|
|
167
|
+
@system-review [project-plan] [implementation-history]
|
|
168
|
+
```
|
|
169
|
+
- Analysis of overall development process effectiveness
|
|
170
|
+
- Identification of successful patterns and improvement areas
|
|
171
|
+
- Recommendations for future project workflows
|
|
172
|
+
|
|
173
|
+
**Expected Outcome**: Comprehensive project evaluation with detailed feedback, complete documentation, and process insights for future improvements.
|
|
174
|
+
|
|
175
|
+
---
|
|
176
|
+
|
|
177
|
+
## Advanced Use Cases
|
|
178
|
+
|
|
179
|
+
### 🔄 Multi-Agent Collaboration Patterns
|
|
180
|
+
|
|
181
|
+
#### Pattern 1: Sequential Handoff
|
|
182
|
+
```
|
|
183
|
+
Project Manager (@plan-feature) →
|
|
184
|
+
Backend Engineer (@execute) →
|
|
185
|
+
Frontend Architect (@execute) →
|
|
186
|
+
Test Orchestrator (@code-review) →
|
|
187
|
+
Development Logger (@system-review)
|
|
188
|
+
```
|
|
189
|
+
|
|
190
|
+
#### Pattern 2: Parallel Development
|
|
191
|
+
```
|
|
192
|
+
Project Manager (@plan-feature) →
|
|
193
|
+
├── Backend Engineer (@execute)
|
|
194
|
+
├── Frontend Architect (@execute)
|
|
195
|
+
└── Database Specialist (@execute)
|
|
196
|
+
→ Test Orchestrator (@code-review)
|
|
197
|
+
```
|
|
198
|
+
|
|
199
|
+
#### Pattern 3: Iterative Improvement
|
|
200
|
+
```
|
|
201
|
+
Implementation → @code-review → Fix Issues → @execution-report → @system-review → Process Updates
|
|
202
|
+
```
|
|
203
|
+
|
|
204
|
+
### 🎯 Specialized Workflows
|
|
205
|
+
|
|
206
|
+
#### Security-First Development
|
|
207
|
+
1. Security Specialist consultation during planning
|
|
208
|
+
2. Security code review at each implementation stage
|
|
209
|
+
3. Vulnerability assessment before deployment
|
|
210
|
+
4. Incident response procedures with @rca and @implement-fix
|
|
211
|
+
|
|
212
|
+
#### Performance-Optimized Development
|
|
213
|
+
1. Performance requirements in @plan-feature
|
|
214
|
+
2. Performance testing integration in @execute
|
|
215
|
+
3. Performance validation in @code-review
|
|
216
|
+
4. Performance metrics in @execution-report
|
|
217
|
+
|
|
218
|
+
#### Compliance-Driven Development
|
|
219
|
+
1. Compliance requirements in project planning
|
|
220
|
+
2. Compliance validation at each development stage
|
|
221
|
+
3. Audit trail documentation throughout process
|
|
222
|
+
4. Compliance reporting and certification support
|
|
223
|
+
|
|
224
|
+
## Best Practices
|
|
225
|
+
|
|
226
|
+
### 🎯 Effective Prompt Usage
|
|
227
|
+
|
|
228
|
+
**Do:**
|
|
229
|
+
- Always start with `@prime` for new projects or major context changes
|
|
230
|
+
- Use `@plan-feature` before beginning any significant development work
|
|
231
|
+
- Execute `@code-review` before deployment or major releases
|
|
232
|
+
- Generate `@execution-report` after completing major implementations
|
|
233
|
+
- Run `@system-review` periodically to improve processes
|
|
234
|
+
|
|
235
|
+
**Don't:**
|
|
236
|
+
- Skip the planning phase - always use systematic approach
|
|
237
|
+
- Ignore quality gates - maintain high standards throughout
|
|
238
|
+
- Forget to document - use reporting prompts consistently
|
|
239
|
+
- Work in isolation - leverage agent collaboration patterns
|
|
240
|
+
|
|
241
|
+
### 📊 Quality Gates Integration
|
|
242
|
+
|
|
243
|
+
**Mandatory Quality Gates:**
|
|
244
|
+
1. **Planning Gate**: `@plan-feature` must be completed before implementation
|
|
245
|
+
2. **Implementation Gate**: `@execute` framework must be followed by all agents
|
|
246
|
+
3. **Quality Gate**: `@code-review` must pass before deployment
|
|
247
|
+
4. **Documentation Gate**: `@execution-report` must be generated for major features
|
|
248
|
+
5. **Improvement Gate**: `@system-review` must be conducted for process optimization
|
|
249
|
+
|
|
250
|
+
### 🔄 Continuous Improvement Cycle
|
|
251
|
+
|
|
252
|
+
1. **Plan** → Use `@prime` and `@plan-feature` for systematic planning
|
|
253
|
+
2. **Execute** → Follow `@execute` framework for consistent implementation
|
|
254
|
+
3. **Review** → Apply `@code-review` for quality assurance
|
|
255
|
+
4. **Report** → Generate `@execution-report` for documentation
|
|
256
|
+
5. **Improve** → Conduct `@system-review` for process enhancement
|
|
257
|
+
6. **Repeat** → Apply learnings to next development cycle
|
|
258
|
+
|
|
259
|
+
## Troubleshooting Common Issues
|
|
260
|
+
|
|
261
|
+
### Issue: Agent Coordination Problems
|
|
262
|
+
**Solution**: Use Project Manager as central coordinator with clear task assignments and handoff protocols
|
|
263
|
+
|
|
264
|
+
### Issue: Quality Inconsistency
|
|
265
|
+
**Solution**: Implement mandatory quality gates with Test Orchestrator `@code-review` before any deployment
|
|
266
|
+
|
|
267
|
+
### Issue: Process Inefficiency
|
|
268
|
+
**Solution**: Regular `@system-review` analysis to identify and address workflow bottlenecks
|
|
269
|
+
|
|
270
|
+
### Issue: Knowledge Loss
|
|
271
|
+
**Solution**: Consistent use of Development Logger and `@execution-report` for comprehensive documentation
|
|
272
|
+
|
|
273
|
+
## Success Metrics
|
|
274
|
+
|
|
275
|
+
### Development Velocity
|
|
276
|
+
- Time from feature planning to deployment
|
|
277
|
+
- Number of features delivered per sprint/milestone
|
|
278
|
+
- Reduction in rework and bug fixes
|
|
279
|
+
|
|
280
|
+
### Quality Metrics
|
|
281
|
+
- Code review pass rate
|
|
282
|
+
- Test coverage and quality gate compliance
|
|
283
|
+
- Production incident reduction
|
|
284
|
+
- Security vulnerability prevention
|
|
285
|
+
|
|
286
|
+
### Process Effectiveness
|
|
287
|
+
- Agent collaboration efficiency
|
|
288
|
+
- Knowledge retention and reuse
|
|
289
|
+
- Process improvement implementation rate
|
|
290
|
+
- Team satisfaction and workflow adoption
|
|
291
|
+
|
|
292
|
+
---
|
|
293
|
+
|
|
294
|
+
*This workflow guide represents a systematic approach to leveraging our 9-agent team with integrated prompt capabilities for maximum development effectiveness and quality.*
|