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,711 @@
|
|
|
1
|
+
# Development Walkthroughs
|
|
2
|
+
|
|
3
|
+
## Complete Step-by-Step Guides for Real-World Projects
|
|
4
|
+
|
|
5
|
+
This guide provides detailed, step-by-step instructions for building three different types of applications using the Kiro-CLI Agent Team System. Each walkthrough demonstrates the systematic approach and agent coordination patterns for different project types.
|
|
6
|
+
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
## 🌟 Walkthrough 1: Greenfield Fullstack Application
|
|
10
|
+
|
|
11
|
+
**Project**: Task Management SaaS Platform
|
|
12
|
+
**Tech Stack**: React + TypeScript + Node.js + PostgreSQL
|
|
13
|
+
**Timeline**: 2-3 weeks
|
|
14
|
+
**Complexity**: High
|
|
15
|
+
|
|
16
|
+
### Phase 1: Project Initialization and Planning
|
|
17
|
+
|
|
18
|
+
#### Step 1: Start Project Planning
|
|
19
|
+
```bash
|
|
20
|
+
# Type this in your terminal or chat:
|
|
21
|
+
@prime
|
|
22
|
+
```
|
|
23
|
+
|
|
24
|
+
**What happens**: Project Manager loads comprehensive project context and begins systematic planning.
|
|
25
|
+
|
|
26
|
+
**You'll be asked questions like**:
|
|
27
|
+
- What type of application are you building?
|
|
28
|
+
- Who are your target users?
|
|
29
|
+
- What are the core features needed?
|
|
30
|
+
- What's your timeline and team size?
|
|
31
|
+
|
|
32
|
+
**Your responses** (example):
|
|
33
|
+
```
|
|
34
|
+
Application Type: Task Management SaaS Platform
|
|
35
|
+
Target Users: Small to medium businesses (10-100 employees)
|
|
36
|
+
Core Features:
|
|
37
|
+
- User authentication and team management
|
|
38
|
+
- Task creation, assignment, and tracking
|
|
39
|
+
- Project organization and dashboards
|
|
40
|
+
- Real-time collaboration and notifications
|
|
41
|
+
- Reporting and analytics
|
|
42
|
+
Timeline: 3 weeks for MVP
|
|
43
|
+
Team: Solo developer with AI agent assistance
|
|
44
|
+
```
|
|
45
|
+
|
|
46
|
+
#### Step 2: Create Comprehensive Feature Plan
|
|
47
|
+
```bash
|
|
48
|
+
@plan-feature "Task Management SaaS MVP"
|
|
49
|
+
```
|
|
50
|
+
|
|
51
|
+
**What happens**: Project Manager creates detailed implementation plan with task breakdown.
|
|
52
|
+
|
|
53
|
+
**Expected output**: Comprehensive project plan with:
|
|
54
|
+
- Feature breakdown and user stories
|
|
55
|
+
- Technical architecture recommendations
|
|
56
|
+
- Development phases and milestones
|
|
57
|
+
- Agent assignment and coordination plan
|
|
58
|
+
|
|
59
|
+
#### Step 3: Generate Product Requirements Document
|
|
60
|
+
```bash
|
|
61
|
+
@create-prd "Task Management SaaS Platform"
|
|
62
|
+
```
|
|
63
|
+
|
|
64
|
+
**What happens**: Project Manager creates formal PRD with business requirements, technical specifications, and success criteria.
|
|
65
|
+
|
|
66
|
+
### Phase 2: Database Design and Setup
|
|
67
|
+
|
|
68
|
+
#### Step 4: Design Database Schema
|
|
69
|
+
```bash
|
|
70
|
+
# Switch to Database Specialist
|
|
71
|
+
Database Specialist, I need to design a database schema for a task management SaaS platform with users, teams, projects, tasks, and real-time collaboration features.
|
|
72
|
+
```
|
|
73
|
+
|
|
74
|
+
**What happens**: Database Specialist asks clarifying questions about:
|
|
75
|
+
- Data relationships and constraints
|
|
76
|
+
- Performance requirements
|
|
77
|
+
- Scalability needs
|
|
78
|
+
- Compliance requirements
|
|
79
|
+
|
|
80
|
+
#### Step 5: Execute Database Implementation
|
|
81
|
+
```bash
|
|
82
|
+
@execute
|
|
83
|
+
```
|
|
84
|
+
|
|
85
|
+
**What happens**: Database Specialist systematically:
|
|
86
|
+
- Designs normalized schema with proper relationships
|
|
87
|
+
- Creates migration scripts with rollback procedures
|
|
88
|
+
- Sets up indexes for optimal query performance
|
|
89
|
+
- Implements data validation and constraints
|
|
90
|
+
- Creates test data fixtures
|
|
91
|
+
|
|
92
|
+
**Expected deliverables**:
|
|
93
|
+
- Complete PostgreSQL schema
|
|
94
|
+
- Migration scripts in `database/migrations/`
|
|
95
|
+
- Schema documentation
|
|
96
|
+
- Performance optimization plan
|
|
97
|
+
|
|
98
|
+
### Phase 3: Backend API Development
|
|
99
|
+
|
|
100
|
+
#### Step 6: Design Backend Architecture
|
|
101
|
+
```bash
|
|
102
|
+
# Switch to Backend Engineer
|
|
103
|
+
Backend Engineer, I need to build a REST API for the task management platform with JWT authentication, real-time features, and integration with the PostgreSQL database designed by the Database Specialist.
|
|
104
|
+
```
|
|
105
|
+
|
|
106
|
+
**What happens**: Backend Engineer analyzes requirements and asks about:
|
|
107
|
+
- API design patterns and endpoints needed
|
|
108
|
+
- Authentication and authorization requirements
|
|
109
|
+
- Real-time features and WebSocket needs
|
|
110
|
+
- Performance and scalability requirements
|
|
111
|
+
|
|
112
|
+
#### Step 7: Execute Backend Implementation
|
|
113
|
+
```bash
|
|
114
|
+
@execute
|
|
115
|
+
```
|
|
116
|
+
|
|
117
|
+
**What happens**: Backend Engineer systematically implements:
|
|
118
|
+
- Express.js server with TypeScript
|
|
119
|
+
- JWT-based authentication system
|
|
120
|
+
- RESTful API endpoints for all entities
|
|
121
|
+
- WebSocket integration for real-time updates
|
|
122
|
+
- Input validation with Zod
|
|
123
|
+
- Comprehensive error handling
|
|
124
|
+
- API documentation with Swagger
|
|
125
|
+
|
|
126
|
+
**Expected deliverables**:
|
|
127
|
+
- Complete Node.js/Express API in `backend/`
|
|
128
|
+
- Authentication middleware and JWT handling
|
|
129
|
+
- All CRUD endpoints for users, teams, projects, tasks
|
|
130
|
+
- Real-time WebSocket implementation
|
|
131
|
+
- API documentation and testing endpoints
|
|
132
|
+
|
|
133
|
+
### Phase 4: Frontend Application Development
|
|
134
|
+
|
|
135
|
+
#### Step 8: Design Frontend Architecture
|
|
136
|
+
```bash
|
|
137
|
+
# Switch to Frontend Architect
|
|
138
|
+
Frontend Architect, I need to build a modern React application for the task management SaaS platform. It should have a professional dashboard interface, real-time updates, and excellent user experience.
|
|
139
|
+
```
|
|
140
|
+
|
|
141
|
+
**What happens**: Frontend Architect asks about:
|
|
142
|
+
- Design preferences and branding requirements
|
|
143
|
+
- User experience priorities and workflows
|
|
144
|
+
- Device support and responsive design needs
|
|
145
|
+
- Performance and accessibility requirements
|
|
146
|
+
|
|
147
|
+
#### Step 9: Execute Frontend Implementation
|
|
148
|
+
```bash
|
|
149
|
+
@execute
|
|
150
|
+
```
|
|
151
|
+
|
|
152
|
+
**What happens**: Frontend Architect systematically builds:
|
|
153
|
+
- React application with TypeScript
|
|
154
|
+
- Modern component architecture with atomic design
|
|
155
|
+
- Redux Toolkit for state management
|
|
156
|
+
- RTK Query for API integration
|
|
157
|
+
- Real-time WebSocket integration
|
|
158
|
+
- Responsive design with Tailwind CSS
|
|
159
|
+
- Comprehensive routing and navigation
|
|
160
|
+
|
|
161
|
+
**Expected deliverables**:
|
|
162
|
+
- Complete React application in `frontend/`
|
|
163
|
+
- Professional dashboard and task management UI
|
|
164
|
+
- Real-time collaboration features
|
|
165
|
+
- Mobile-responsive design
|
|
166
|
+
- User authentication flows
|
|
167
|
+
|
|
168
|
+
### Phase 5: Quality Assurance and Testing
|
|
169
|
+
|
|
170
|
+
#### Step 10: Implement Comprehensive Testing
|
|
171
|
+
```bash
|
|
172
|
+
# Switch to Test Orchestrator
|
|
173
|
+
Test Orchestrator, I need to implement comprehensive testing for the fullstack task management application, including unit tests, integration tests, and end-to-end testing.
|
|
174
|
+
```
|
|
175
|
+
|
|
176
|
+
#### Step 11: Execute Testing Implementation
|
|
177
|
+
```bash
|
|
178
|
+
@execute
|
|
179
|
+
```
|
|
180
|
+
|
|
181
|
+
**What happens**: Test Orchestrator systematically creates:
|
|
182
|
+
- Unit tests for all business logic
|
|
183
|
+
- API integration tests
|
|
184
|
+
- Frontend component tests
|
|
185
|
+
- End-to-end user workflow tests
|
|
186
|
+
- Performance and accessibility testing
|
|
187
|
+
- Quality gates and CI/CD integration
|
|
188
|
+
|
|
189
|
+
### Phase 6: Security Implementation
|
|
190
|
+
|
|
191
|
+
#### Step 12: Security Assessment and Implementation
|
|
192
|
+
```bash
|
|
193
|
+
# Switch to Security Specialist
|
|
194
|
+
Security Specialist, I need to conduct a comprehensive security review and implement security measures for the task management SaaS platform.
|
|
195
|
+
```
|
|
196
|
+
|
|
197
|
+
#### Step 13: Execute Security Implementation
|
|
198
|
+
```bash
|
|
199
|
+
@execute
|
|
200
|
+
```
|
|
201
|
+
|
|
202
|
+
**What happens**: Security Specialist systematically:
|
|
203
|
+
- Conducts security audit of all components
|
|
204
|
+
- Implements additional security measures
|
|
205
|
+
- Sets up vulnerability scanning
|
|
206
|
+
- Creates security documentation
|
|
207
|
+
- Establishes security monitoring
|
|
208
|
+
|
|
209
|
+
### Phase 7: Deployment and DevOps
|
|
210
|
+
|
|
211
|
+
#### Step 14: Setup Production Infrastructure
|
|
212
|
+
```bash
|
|
213
|
+
# Switch to DevOps Engineer
|
|
214
|
+
DevOps Engineer, I need to set up production deployment for the task management SaaS platform with Docker containers, CI/CD pipeline, and monitoring.
|
|
215
|
+
```
|
|
216
|
+
|
|
217
|
+
#### Step 15: Execute Infrastructure Implementation
|
|
218
|
+
```bash
|
|
219
|
+
@execute
|
|
220
|
+
```
|
|
221
|
+
|
|
222
|
+
**What happens**: DevOps Engineer systematically:
|
|
223
|
+
- Creates Docker containers for all services
|
|
224
|
+
- Sets up CI/CD pipeline with GitHub Actions
|
|
225
|
+
- Configures production environment
|
|
226
|
+
- Implements monitoring and logging
|
|
227
|
+
- Creates deployment documentation
|
|
228
|
+
|
|
229
|
+
### Phase 8: Final Quality Review
|
|
230
|
+
|
|
231
|
+
#### Step 16: Comprehensive Code Review
|
|
232
|
+
```bash
|
|
233
|
+
# Switch to Test Orchestrator
|
|
234
|
+
@code-review "Complete fullstack application review"
|
|
235
|
+
```
|
|
236
|
+
|
|
237
|
+
#### Step 17: Generate Implementation Report
|
|
238
|
+
```bash
|
|
239
|
+
@execution-report
|
|
240
|
+
```
|
|
241
|
+
|
|
242
|
+
**Final deliverables**:
|
|
243
|
+
- Complete fullstack SaaS application
|
|
244
|
+
- Production-ready deployment
|
|
245
|
+
- Comprehensive documentation
|
|
246
|
+
- Quality metrics and performance benchmarks
|
|
247
|
+
|
|
248
|
+
---
|
|
249
|
+
|
|
250
|
+
## 🖥️ Walkthrough 2: Cross-Platform TUI Application
|
|
251
|
+
|
|
252
|
+
**Project**: Developer Productivity CLI Tool
|
|
253
|
+
**Tech Stack**: Rust + Ratatui + SQLite
|
|
254
|
+
**Timeline**: 1-2 weeks
|
|
255
|
+
**Complexity**: Medium
|
|
256
|
+
|
|
257
|
+
### Phase 1: Project Setup and Architecture
|
|
258
|
+
|
|
259
|
+
#### Step 1: Initialize TUI Project Planning
|
|
260
|
+
```bash
|
|
261
|
+
@prime
|
|
262
|
+
```
|
|
263
|
+
|
|
264
|
+
**Your responses** (example):
|
|
265
|
+
```
|
|
266
|
+
Application Type: Cross-platform Terminal User Interface (TUI) application
|
|
267
|
+
Purpose: Developer productivity tool for managing tasks, notes, and time tracking
|
|
268
|
+
Target Users: Software developers and technical professionals
|
|
269
|
+
Core Features:
|
|
270
|
+
- Interactive terminal interface with keyboard navigation
|
|
271
|
+
- Task management with categories and priorities
|
|
272
|
+
- Note-taking with markdown support
|
|
273
|
+
- Time tracking and productivity analytics
|
|
274
|
+
- Local SQLite database for data persistence
|
|
275
|
+
- Cross-platform support (Windows, macOS, Linux)
|
|
276
|
+
Tech Stack: Rust + Ratatui + SQLite
|
|
277
|
+
Timeline: 2 weeks for full-featured application
|
|
278
|
+
```
|
|
279
|
+
|
|
280
|
+
#### Step 2: Create TUI-Specific Feature Plan
|
|
281
|
+
```bash
|
|
282
|
+
@plan-feature "Developer Productivity TUI Tool"
|
|
283
|
+
```
|
|
284
|
+
|
|
285
|
+
**What happens**: Project Manager creates plan optimized for TUI development patterns:
|
|
286
|
+
- Terminal interface design and navigation flows
|
|
287
|
+
- Keyboard shortcuts and accessibility
|
|
288
|
+
- Data persistence and local storage
|
|
289
|
+
- Cross-platform compatibility requirements
|
|
290
|
+
|
|
291
|
+
### Phase 2: Database Design for Local Storage
|
|
292
|
+
|
|
293
|
+
#### Step 3: Design Local Database Schema
|
|
294
|
+
```bash
|
|
295
|
+
# Switch to Database Specialist
|
|
296
|
+
Database Specialist: I need to design a lightweight SQLite database schema for a TUI productivity application with tasks, notes, time tracking, and user preferences.
|
|
297
|
+
```
|
|
298
|
+
|
|
299
|
+
**What happens**: Database Specialist designs schema optimized for:
|
|
300
|
+
- Local SQLite performance
|
|
301
|
+
- Simple data relationships
|
|
302
|
+
- Fast queries for TUI responsiveness
|
|
303
|
+
- Data export/import capabilities
|
|
304
|
+
|
|
305
|
+
#### Step 4: Execute Database Implementation
|
|
306
|
+
```bash
|
|
307
|
+
@execute
|
|
308
|
+
```
|
|
309
|
+
|
|
310
|
+
**Expected deliverables**:
|
|
311
|
+
- SQLite schema with migration system
|
|
312
|
+
- Rust database connection and query modules
|
|
313
|
+
- Data models and serialization
|
|
314
|
+
- Backup and restore functionality
|
|
315
|
+
|
|
316
|
+
### Phase 3: Backend Logic and Data Layer
|
|
317
|
+
|
|
318
|
+
#### Step 5: Implement Core Business Logic
|
|
319
|
+
```bash
|
|
320
|
+
# Switch to Backend Engineer
|
|
321
|
+
Backend Engineer: I need to implement the core business logic for a Rust TUI application with task management, note-taking, and time tracking features using SQLite for local data storage.
|
|
322
|
+
```
|
|
323
|
+
|
|
324
|
+
#### Step 6: Execute Backend Implementation
|
|
325
|
+
```bash
|
|
326
|
+
@execute
|
|
327
|
+
```
|
|
328
|
+
|
|
329
|
+
**What happens**: Backend Engineer implements:
|
|
330
|
+
- Rust application structure with proper modules
|
|
331
|
+
- SQLite integration with connection pooling
|
|
332
|
+
- Business logic for tasks, notes, and time tracking
|
|
333
|
+
- Data validation and error handling
|
|
334
|
+
- Configuration management
|
|
335
|
+
- Cross-platform file system handling
|
|
336
|
+
|
|
337
|
+
**Expected deliverables**:
|
|
338
|
+
- Core Rust modules in `src/`
|
|
339
|
+
- Database abstraction layer
|
|
340
|
+
- Business logic implementation
|
|
341
|
+
- Configuration and settings management
|
|
342
|
+
|
|
343
|
+
### Phase 4: TUI Interface Development
|
|
344
|
+
|
|
345
|
+
#### Step 7: Design Terminal User Interface
|
|
346
|
+
```bash
|
|
347
|
+
# Switch to Frontend Architect
|
|
348
|
+
Frontend Architect: I need to design and implement a terminal user interface using Ratatui for a developer productivity tool. The interface should be intuitive, keyboard-driven, and visually appealing in the terminal.
|
|
349
|
+
```
|
|
350
|
+
|
|
351
|
+
**What happens**: Frontend Architect focuses on:
|
|
352
|
+
- Terminal interface design patterns
|
|
353
|
+
- Keyboard navigation and shortcuts
|
|
354
|
+
- Visual hierarchy in text-based interface
|
|
355
|
+
- Responsive terminal layouts
|
|
356
|
+
|
|
357
|
+
#### Step 8: Execute TUI Implementation
|
|
358
|
+
```bash
|
|
359
|
+
@execute
|
|
360
|
+
```
|
|
361
|
+
|
|
362
|
+
**What happens**: Frontend Architect builds:
|
|
363
|
+
- Ratatui-based terminal interface
|
|
364
|
+
- Multiple screens/views (tasks, notes, time tracking)
|
|
365
|
+
- Keyboard event handling and navigation
|
|
366
|
+
- Terminal-optimized visual design
|
|
367
|
+
- Status bars and help systems
|
|
368
|
+
- Modal dialogs and forms
|
|
369
|
+
|
|
370
|
+
**Expected deliverables**:
|
|
371
|
+
- Complete TUI interface in `src/ui/`
|
|
372
|
+
- Keyboard navigation system
|
|
373
|
+
- Multiple application screens
|
|
374
|
+
- Terminal-optimized user experience
|
|
375
|
+
|
|
376
|
+
### Phase 5: Cross-Platform Compatibility
|
|
377
|
+
|
|
378
|
+
#### Step 9: Ensure Cross-Platform Support
|
|
379
|
+
```bash
|
|
380
|
+
# Switch to DevOps Engineer
|
|
381
|
+
DevOps Engineer: I need to ensure this Rust TUI application works correctly across Windows, macOS, and Linux, with proper build processes and distribution methods.
|
|
382
|
+
```
|
|
383
|
+
|
|
384
|
+
#### Step 10: Execute Cross-Platform Implementation
|
|
385
|
+
```bash
|
|
386
|
+
@execute
|
|
387
|
+
```
|
|
388
|
+
|
|
389
|
+
**What happens**: DevOps Engineer implements:
|
|
390
|
+
- Cross-platform build configuration
|
|
391
|
+
- Platform-specific optimizations
|
|
392
|
+
- Distribution and packaging
|
|
393
|
+
- Installation scripts
|
|
394
|
+
- CI/CD for multiple platforms
|
|
395
|
+
|
|
396
|
+
### Phase 6: Testing and Quality Assurance
|
|
397
|
+
|
|
398
|
+
#### Step 11: Implement TUI-Specific Testing
|
|
399
|
+
```bash
|
|
400
|
+
# Switch to Test Orchestrator
|
|
401
|
+
Test Orchestrator: I need to implement comprehensive testing for a Rust TUI application, including unit tests, integration tests, and terminal interface testing.
|
|
402
|
+
```
|
|
403
|
+
|
|
404
|
+
#### Step 12: Execute Testing Implementation
|
|
405
|
+
```bash
|
|
406
|
+
@execute
|
|
407
|
+
```
|
|
408
|
+
|
|
409
|
+
**What happens**: Test Orchestrator creates:
|
|
410
|
+
- Unit tests for business logic
|
|
411
|
+
- Integration tests for database operations
|
|
412
|
+
- TUI interaction testing
|
|
413
|
+
- Cross-platform compatibility tests
|
|
414
|
+
- Performance benchmarks
|
|
415
|
+
|
|
416
|
+
### Phase 7: Final Polish and Documentation
|
|
417
|
+
|
|
418
|
+
#### Step 13: Create User Documentation
|
|
419
|
+
```bash
|
|
420
|
+
# Switch to UI/UX Designer
|
|
421
|
+
UI/UX Designer: I need to create comprehensive user documentation and help systems for the TUI productivity application, focusing on keyboard shortcuts and terminal usage patterns.
|
|
422
|
+
```
|
|
423
|
+
|
|
424
|
+
#### Step 14: Final Quality Review
|
|
425
|
+
```bash
|
|
426
|
+
@code-review "Cross-platform TUI application review"
|
|
427
|
+
```
|
|
428
|
+
|
|
429
|
+
**Final deliverables**:
|
|
430
|
+
- Cross-platform TUI application
|
|
431
|
+
- Installation packages for all platforms
|
|
432
|
+
- Comprehensive user documentation
|
|
433
|
+
- Performance benchmarks
|
|
434
|
+
|
|
435
|
+
---
|
|
436
|
+
|
|
437
|
+
## 🤖 Walkthrough 3: Agentic AI Application
|
|
438
|
+
|
|
439
|
+
**Project**: AI-Powered Code Review Assistant
|
|
440
|
+
**Tech Stack**: Python + FastAPI + LangChain + Vector Database
|
|
441
|
+
**Timeline**: 2-3 weeks
|
|
442
|
+
**Complexity**: High
|
|
443
|
+
|
|
444
|
+
### Phase 1: AI Application Architecture Planning
|
|
445
|
+
|
|
446
|
+
#### Step 1: Initialize AI Project Planning
|
|
447
|
+
```bash
|
|
448
|
+
@prime
|
|
449
|
+
```
|
|
450
|
+
|
|
451
|
+
**Your responses** (example):
|
|
452
|
+
```
|
|
453
|
+
Application Type: Agentic AI Application - Code Review Assistant
|
|
454
|
+
Purpose: AI-powered system that automatically reviews code, suggests improvements, and learns from feedback
|
|
455
|
+
Target Users: Development teams and individual developers
|
|
456
|
+
Core Features:
|
|
457
|
+
- Automated code analysis and review
|
|
458
|
+
- AI-powered suggestions and improvements
|
|
459
|
+
- Learning from user feedback and corrections
|
|
460
|
+
- Integration with Git repositories and CI/CD
|
|
461
|
+
- Multi-language code support
|
|
462
|
+
- Contextual understanding of codebases
|
|
463
|
+
- Collaborative review workflows
|
|
464
|
+
Tech Stack: Python + FastAPI + LangChain + ChromaDB + OpenAI API
|
|
465
|
+
AI Components: LLM integration, vector embeddings, retrieval-augmented generation
|
|
466
|
+
Timeline: 3 weeks for MVP with learning capabilities
|
|
467
|
+
```
|
|
468
|
+
|
|
469
|
+
#### Step 2: Create AI-Specific Architecture Plan
|
|
470
|
+
```bash
|
|
471
|
+
@plan-feature "AI Code Review Assistant with Learning Capabilities"
|
|
472
|
+
```
|
|
473
|
+
|
|
474
|
+
**What happens**: Project Manager creates plan optimized for AI development:
|
|
475
|
+
- AI model integration and prompt engineering
|
|
476
|
+
- Vector database for code embeddings
|
|
477
|
+
- Learning and feedback loops
|
|
478
|
+
- API design for AI services
|
|
479
|
+
- Scalability for AI workloads
|
|
480
|
+
|
|
481
|
+
### Phase 2: AI Infrastructure and Vector Database
|
|
482
|
+
|
|
483
|
+
#### Step 3: Design AI Data Architecture
|
|
484
|
+
```bash
|
|
485
|
+
# Switch to Database Specialist
|
|
486
|
+
Database Specialist: I need to design a data architecture for an AI code review system that includes vector embeddings for code similarity, user feedback storage, and learning data management.
|
|
487
|
+
```
|
|
488
|
+
|
|
489
|
+
**What happens**: Database Specialist designs:
|
|
490
|
+
- Vector database schema for code embeddings
|
|
491
|
+
- Relational database for metadata and feedback
|
|
492
|
+
- Data pipeline for AI training data
|
|
493
|
+
- Performance optimization for vector queries
|
|
494
|
+
|
|
495
|
+
#### Step 4: Execute AI Database Implementation
|
|
496
|
+
```bash
|
|
497
|
+
@execute
|
|
498
|
+
```
|
|
499
|
+
|
|
500
|
+
**Expected deliverables**:
|
|
501
|
+
- ChromaDB vector database setup
|
|
502
|
+
- PostgreSQL for structured data
|
|
503
|
+
- Data ingestion pipelines
|
|
504
|
+
- Embedding generation workflows
|
|
505
|
+
|
|
506
|
+
### Phase 3: AI Backend and LLM Integration
|
|
507
|
+
|
|
508
|
+
#### Step 5: Implement AI Backend Services
|
|
509
|
+
```bash
|
|
510
|
+
# Switch to Backend Engineer
|
|
511
|
+
Backend Engineer: I need to build a FastAPI backend that integrates with LLMs, manages vector embeddings, and provides AI-powered code review capabilities with learning from user feedback.
|
|
512
|
+
```
|
|
513
|
+
|
|
514
|
+
**What happens**: Backend Engineer asks about:
|
|
515
|
+
- LLM integration patterns and API usage
|
|
516
|
+
- Code analysis and embedding strategies
|
|
517
|
+
- Feedback collection and learning mechanisms
|
|
518
|
+
- Performance and rate limiting requirements
|
|
519
|
+
|
|
520
|
+
#### Step 6: Execute AI Backend Implementation
|
|
521
|
+
```bash
|
|
522
|
+
@execute
|
|
523
|
+
```
|
|
524
|
+
|
|
525
|
+
**What happens**: Backend Engineer implements:
|
|
526
|
+
- FastAPI application with async support
|
|
527
|
+
- LangChain integration for LLM workflows
|
|
528
|
+
- Code parsing and analysis modules
|
|
529
|
+
- Vector embedding generation and search
|
|
530
|
+
- Feedback collection and learning systems
|
|
531
|
+
- AI prompt engineering and optimization
|
|
532
|
+
|
|
533
|
+
**Expected deliverables**:
|
|
534
|
+
- Complete AI backend in `backend/`
|
|
535
|
+
- LLM integration with prompt templates
|
|
536
|
+
- Code analysis and review engines
|
|
537
|
+
- Vector search and similarity matching
|
|
538
|
+
- Learning and adaptation mechanisms
|
|
539
|
+
|
|
540
|
+
### Phase 4: AI Agent Implementation
|
|
541
|
+
|
|
542
|
+
#### Step 7: Design AI Agent Architecture
|
|
543
|
+
```bash
|
|
544
|
+
# Switch to Frontend Architect
|
|
545
|
+
Frontend Architect: I need to create an intelligent frontend that interfaces with the AI backend, presents code reviews in an intuitive way, and collects user feedback for continuous learning.
|
|
546
|
+
```
|
|
547
|
+
|
|
548
|
+
**What happens**: Frontend Architect focuses on:
|
|
549
|
+
- AI-human interaction patterns
|
|
550
|
+
- Code review presentation and visualization
|
|
551
|
+
- Feedback collection interfaces
|
|
552
|
+
- Real-time AI processing indicators
|
|
553
|
+
|
|
554
|
+
#### Step 8: Execute AI Frontend Implementation
|
|
555
|
+
```bash
|
|
556
|
+
@execute
|
|
557
|
+
```
|
|
558
|
+
|
|
559
|
+
**What happens**: Frontend Architect builds:
|
|
560
|
+
- React application with AI-optimized UX
|
|
561
|
+
- Code diff visualization with AI annotations
|
|
562
|
+
- Interactive feedback collection
|
|
563
|
+
- Real-time AI processing indicators
|
|
564
|
+
- Learning progress visualization
|
|
565
|
+
- Integration with development tools
|
|
566
|
+
|
|
567
|
+
**Expected deliverables**:
|
|
568
|
+
- AI-powered frontend interface
|
|
569
|
+
- Code review visualization
|
|
570
|
+
- Feedback collection system
|
|
571
|
+
- Developer tool integrations
|
|
572
|
+
|
|
573
|
+
### Phase 5: AI Model Training and Optimization
|
|
574
|
+
|
|
575
|
+
#### Step 9: Implement Learning and Adaptation
|
|
576
|
+
```bash
|
|
577
|
+
# Switch to Backend Engineer (AI focus)
|
|
578
|
+
Backend Engineer: I need to implement the learning mechanisms that allow the AI system to improve from user feedback and adapt to different coding styles and preferences.
|
|
579
|
+
```
|
|
580
|
+
|
|
581
|
+
#### Step 10: Execute AI Learning Implementation
|
|
582
|
+
```bash
|
|
583
|
+
@execute
|
|
584
|
+
```
|
|
585
|
+
|
|
586
|
+
**What happens**: Backend Engineer implements:
|
|
587
|
+
- Feedback processing and analysis
|
|
588
|
+
- Model fine-tuning workflows
|
|
589
|
+
- Prompt optimization based on feedback
|
|
590
|
+
- Performance monitoring for AI components
|
|
591
|
+
- A/B testing for AI improvements
|
|
592
|
+
|
|
593
|
+
### Phase 6: AI Security and Ethics
|
|
594
|
+
|
|
595
|
+
#### Step 11: Implement AI Security Measures
|
|
596
|
+
```bash
|
|
597
|
+
# Switch to Security Specialist
|
|
598
|
+
Security Specialist: I need to implement security measures specific to AI applications, including prompt injection prevention, data privacy for code analysis, and secure API usage.
|
|
599
|
+
```
|
|
600
|
+
|
|
601
|
+
#### Step 12: Execute AI Security Implementation
|
|
602
|
+
```bash
|
|
603
|
+
@execute
|
|
604
|
+
```
|
|
605
|
+
|
|
606
|
+
**What happens**: Security Specialist implements:
|
|
607
|
+
- Prompt injection prevention
|
|
608
|
+
- Code privacy and data protection
|
|
609
|
+
- API rate limiting and abuse prevention
|
|
610
|
+
- AI model security measures
|
|
611
|
+
- Audit logging for AI decisions
|
|
612
|
+
|
|
613
|
+
### Phase 7: AI Testing and Validation
|
|
614
|
+
|
|
615
|
+
#### Step 13: Implement AI-Specific Testing
|
|
616
|
+
```bash
|
|
617
|
+
# Switch to Test Orchestrator
|
|
618
|
+
Test Orchestrator: I need to implement comprehensive testing for an AI application, including AI model validation, prompt testing, and learning system verification.
|
|
619
|
+
```
|
|
620
|
+
|
|
621
|
+
#### Step 14: Execute AI Testing Implementation
|
|
622
|
+
```bash
|
|
623
|
+
@execute
|
|
624
|
+
```
|
|
625
|
+
|
|
626
|
+
**What happens**: Test Orchestrator creates:
|
|
627
|
+
- AI model accuracy testing
|
|
628
|
+
- Prompt engineering validation
|
|
629
|
+
- Learning system verification
|
|
630
|
+
- Performance benchmarks for AI operations
|
|
631
|
+
- User acceptance testing for AI features
|
|
632
|
+
|
|
633
|
+
### Phase 8: AI Deployment and Monitoring
|
|
634
|
+
|
|
635
|
+
#### Step 15: Setup AI Production Infrastructure
|
|
636
|
+
```bash
|
|
637
|
+
# Switch to DevOps Engineer
|
|
638
|
+
DevOps Engineer: I need to set up production infrastructure for an AI application with GPU support, model serving, vector database hosting, and AI-specific monitoring.
|
|
639
|
+
```
|
|
640
|
+
|
|
641
|
+
#### Step 16: Execute AI Infrastructure Implementation
|
|
642
|
+
```bash
|
|
643
|
+
@execute
|
|
644
|
+
```
|
|
645
|
+
|
|
646
|
+
**What happens**: DevOps Engineer implements:
|
|
647
|
+
- GPU-enabled container deployment
|
|
648
|
+
- Vector database hosting and scaling
|
|
649
|
+
- AI model serving infrastructure
|
|
650
|
+
- Performance monitoring for AI workloads
|
|
651
|
+
- Cost optimization for AI API usage
|
|
652
|
+
|
|
653
|
+
### Phase 9: AI Quality and Ethics Review
|
|
654
|
+
|
|
655
|
+
#### Step 17: Comprehensive AI System Review
|
|
656
|
+
```bash
|
|
657
|
+
@code-review "AI application with ethical considerations"
|
|
658
|
+
```
|
|
659
|
+
|
|
660
|
+
#### Step 18: Generate AI Implementation Report
|
|
661
|
+
```bash
|
|
662
|
+
@execution-report
|
|
663
|
+
```
|
|
664
|
+
|
|
665
|
+
**Final deliverables**:
|
|
666
|
+
- Complete AI-powered code review system
|
|
667
|
+
- Learning and adaptation capabilities
|
|
668
|
+
- Production AI infrastructure
|
|
669
|
+
- Comprehensive AI testing and validation
|
|
670
|
+
- Ethics and security documentation
|
|
671
|
+
|
|
672
|
+
---
|
|
673
|
+
|
|
674
|
+
## 🎯 Key Success Patterns
|
|
675
|
+
|
|
676
|
+
### Universal Workflow Pattern
|
|
677
|
+
1. **@prime** - Always start with comprehensive project context loading
|
|
678
|
+
2. **@plan-feature** - Create detailed implementation plans
|
|
679
|
+
3. **@execute** - Use systematic implementation for each agent
|
|
680
|
+
4. **@code-review** - Ensure quality at major milestones
|
|
681
|
+
5. **@execution-report** - Document and analyze results
|
|
682
|
+
|
|
683
|
+
### Agent Coordination Pattern
|
|
684
|
+
1. **Project Manager** - Overall coordination and planning
|
|
685
|
+
2. **Database Specialist** - Data architecture and persistence
|
|
686
|
+
3. **Backend Engineer** - Core business logic and APIs
|
|
687
|
+
4. **Frontend Architect** - User interface and experience
|
|
688
|
+
5. **Test Orchestrator** - Quality assurance and testing
|
|
689
|
+
6. **Security Specialist** - Security and compliance
|
|
690
|
+
7. **DevOps Engineer** - Infrastructure and deployment
|
|
691
|
+
8. **UI/UX Designer** - User experience optimization
|
|
692
|
+
9. **Development Logger** - Process improvement and learning
|
|
693
|
+
|
|
694
|
+
### Quality Gates
|
|
695
|
+
1. **Planning Gate** - Comprehensive requirements and architecture
|
|
696
|
+
2. **Implementation Gate** - Systematic development with @execute
|
|
697
|
+
3. **Quality Gate** - Code review and testing validation
|
|
698
|
+
4. **Security Gate** - Security assessment and compliance
|
|
699
|
+
5. **Deployment Gate** - Production readiness and monitoring
|
|
700
|
+
|
|
701
|
+
## 📚 Next Steps
|
|
702
|
+
|
|
703
|
+
After completing any walkthrough:
|
|
704
|
+
|
|
705
|
+
1. **Review the implementation** with `@code-review`
|
|
706
|
+
2. **Generate comprehensive report** with `@execution-report`
|
|
707
|
+
3. **Analyze process effectiveness** with Development Logger
|
|
708
|
+
4. **Plan next iteration** based on learnings and feedback
|
|
709
|
+
5. **Update documentation** and share insights with team
|
|
710
|
+
|
|
711
|
+
Each walkthrough demonstrates the power of systematic development with the Kiro-CLI Agent Team System, ensuring consistent quality and comprehensive coverage regardless of project type or complexity.
|