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,122 @@
|
|
|
1
|
+
# PIV Loop
|
|
2
|
+
|
|
3
|
+
The following is a guideline for the development process -> Plan ➡️Implement ➡️Verify / Validate (PIV Loop)
|
|
4
|
+
|
|
5
|
+
## Planning
|
|
6
|
+
|
|
7
|
+
### Phase 1
|
|
8
|
+
|
|
9
|
+
During phase 1 of Planning, the user "vibe codes" and either generates a markdown summary OR the user will use the context / session as the summary of what it is the user is trying to create.
|
|
10
|
+
|
|
11
|
+
This is where the user is trying to undersatand:
|
|
12
|
+
|
|
13
|
+
- Tech stack decisions
|
|
14
|
+
|
|
15
|
+
- Architectural patterns
|
|
16
|
+
|
|
17
|
+
- Constraints and conventions
|
|
18
|
+
|
|
19
|
+
- Creating stable resources
|
|
20
|
+
|
|
21
|
+
When the user has a clear idea of what the overall plan is, a Product Requirements Document (PRD) is created. The @create-prd prompt can be used to generate this from the context or from a markdown:
|
|
22
|
+
|
|
23
|
+
```bash
|
|
24
|
+
@create-prd # create the PRD from the context
|
|
25
|
+
|
|
26
|
+
# OR
|
|
27
|
+
|
|
28
|
+
@create-prd ./[vibe-plan-documnet.md] # create the PRD from a markdown
|
|
29
|
+
User: "Use @PRD.md to execute @quickstart"
|
|
30
|
+
```
|
|
31
|
+
|
|
32
|
+
### Phase 2
|
|
33
|
+
|
|
34
|
+
This is where the PIV loop iteration begins. The user now begins planning out the features of the application:
|
|
35
|
+
|
|
36
|
+
- Codebase analysis
|
|
37
|
+
|
|
38
|
+
- Documentation analysis
|
|
39
|
+
|
|
40
|
+
- Integration points
|
|
41
|
+
|
|
42
|
+
- Task specific rules
|
|
43
|
+
|
|
44
|
+
```bash
|
|
45
|
+
# Very SIMPLE example of how to proceed. Feel free to add more details
|
|
46
|
+
|
|
47
|
+
User: "What feature do you recommend I work on?"
|
|
48
|
+
|
|
49
|
+
Agent: "I recommend you work on feature [XYZ]"
|
|
50
|
+
|
|
51
|
+
@create-plan [XYZ]
|
|
52
|
+
```
|
|
53
|
+
|
|
54
|
+
The user could also ask for the top 5 features to implement and recommend which one(s) to start with an why. Use your judgement.
|
|
55
|
+
|
|
56
|
+
## Implementation
|
|
57
|
+
|
|
58
|
+
Once the feature planning document(s) are created, the next step in the process is to execute, or implement, the plan. The user makes sure to review the plan before proceeding - it is IMPORTANT that the user understands the plan. This is the user's opportunity to converse with the agent to clarify and make any changes.
|
|
59
|
+
|
|
60
|
+
Some things the user looks out for:
|
|
61
|
+
|
|
62
|
+
- Ensuring tools are being used correctly
|
|
63
|
+
|
|
64
|
+
- The correct files are being read and written to
|
|
65
|
+
|
|
66
|
+
- Tasks are being managed properly (is Archon being used?)
|
|
67
|
+
|
|
68
|
+
- "Thinking" tokens are being produced showing the coding agent understands the plan of attack.
|
|
69
|
+
|
|
70
|
+
```bash
|
|
71
|
+
User: "I reviewed the plan and noticed you did not
|
|
72
|
+
include [ABC] as part of the tech stack - please update
|
|
73
|
+
my system documents to include this (tech.md and feature plan)"
|
|
74
|
+
Agent: "You are absolutely right! I will update the tech.md file
|
|
75
|
+
and test plan to reflect the use of [ABC]"
|
|
76
|
+
```
|
|
77
|
+
|
|
78
|
+
Once the user is satisfied that the plan is robust, they can execute the implementation:
|
|
79
|
+
|
|
80
|
+
```bash
|
|
81
|
+
# Begin feature implementation
|
|
82
|
+
|
|
83
|
+
@execute [plan relative path].md # copy the relative path of the file
|
|
84
|
+
```
|
|
85
|
+
|
|
86
|
+
## Validation
|
|
87
|
+
|
|
88
|
+
Once the feature has been implemented, it is the time to validate the code. The user performs a code review to ensure that it is functioning as expected:
|
|
89
|
+
|
|
90
|
+
```bash
|
|
91
|
+
# Review the code
|
|
92
|
+
@code-review
|
|
93
|
+
```
|
|
94
|
+
|
|
95
|
+
The coding assistant will have run the applicable unit and integration tests. The user may need to conduct manual verification tests as well.
|
|
96
|
+
|
|
97
|
+
This is also an opportunity to verify what went well and what didn't. A system review takes place to identify areas where the "system" can be improved - the agent can identify what parts of the system need to be updated, and how.
|
|
98
|
+
|
|
99
|
+
```bash
|
|
100
|
+
# Create an execution report to identify issues
|
|
101
|
+
@execution-report
|
|
102
|
+
@system-review [file generated from execution report]
|
|
103
|
+
```
|
|
104
|
+
|
|
105
|
+
## Next Feature...
|
|
106
|
+
|
|
107
|
+
Now it is time for the user to move onto the next feature. To know what that is:
|
|
108
|
+
|
|
109
|
+
```bash
|
|
110
|
+
# ask for the next feature
|
|
111
|
+
User: "What feature do you recommend on next. Give me 5 tops features
|
|
112
|
+
and recommend which one you think I should do and why"
|
|
113
|
+
Agent: "Ok, here are the top 5 features you should work on..."
|
|
114
|
+
Agent: "I recommend you proceed with [XYZ] because..."
|
|
115
|
+
User: "Ok great, @create-plan [XYZ]"
|
|
116
|
+
```
|
|
117
|
+
|
|
118
|
+
The user keeps looping through the process until the MVP is completed.
|
|
119
|
+
|
|
120
|
+

|
|
121
|
+
|
|
122
|
+
|
|
Binary file
|
|
Binary file
|
|
@@ -0,0 +1,202 @@
|
|
|
1
|
+
# Kiro-CLI Agent Team Quick Reference
|
|
2
|
+
|
|
3
|
+
## Essential Commands
|
|
4
|
+
|
|
5
|
+
### 🚀 Core Development Flow
|
|
6
|
+
```bash
|
|
7
|
+
@prime # Load project context (Project Manager)
|
|
8
|
+
@plan-feature [name] # Create implementation plan (Project Manager)
|
|
9
|
+
@execute # Systematic task execution (All Agents)
|
|
10
|
+
@code-review # Quality assurance review (Test Orchestrator)
|
|
11
|
+
@execution-report # Implementation documentation (Test Orchestrator)
|
|
12
|
+
```
|
|
13
|
+
|
|
14
|
+
### 🔧 Specialized Workflows
|
|
15
|
+
```bash
|
|
16
|
+
@create-prd [feature] # Product requirements doc (Project Manager)
|
|
17
|
+
@rca [issue-id] # Root cause analysis (Security Specialist)
|
|
18
|
+
@implement-fix [issue-id] # Fix implementation (Security Specialist)
|
|
19
|
+
@system-review [plan] [report] # Process improvement (Development Logger)
|
|
20
|
+
@code-review-hackathon # Project evaluation (Test Orchestrator)
|
|
21
|
+
```
|
|
22
|
+
|
|
23
|
+
## Agent Responsibilities
|
|
24
|
+
|
|
25
|
+
| Agent | Primary Role | Key Prompts | Best For |
|
|
26
|
+
|-------|-------------|-------------|----------|
|
|
27
|
+
| **Project Manager** | Coordination & Planning | `@prime`, `@plan-feature`, `@create-prd` | Project setup, feature planning, team coordination |
|
|
28
|
+
| **Backend Engineer** | Server-side Development | `@execute` | APIs, business logic, database integration |
|
|
29
|
+
| **Frontend Architect** | Client-side Development | `@execute` | UI components, state management, user experience |
|
|
30
|
+
| **Database Specialist** | Data Layer Management | `@execute` | Schema design, migrations, query optimization |
|
|
31
|
+
| **DevOps Engineer** | Infrastructure & Deployment | `@execute` | CI/CD, containerization, cloud deployment |
|
|
32
|
+
| **Security Specialist** | Application Security | `@rca`, `@implement-fix` | Vulnerability assessment, security fixes |
|
|
33
|
+
| **Test Orchestrator** | Quality Assurance | `@code-review`, `@execution-report`, `@code-review-hackathon` | Testing strategy, quality gates, project evaluation |
|
|
34
|
+
| **UI/UX Designer** | User Experience Design | `@execute` | Interface design, usability, accessibility |
|
|
35
|
+
| **Development Logger** | Process Documentation | `@system-review` | Workflow analysis, process improvement |
|
|
36
|
+
|
|
37
|
+
## Common Workflow Patterns
|
|
38
|
+
|
|
39
|
+
### 🎯 New Feature Development
|
|
40
|
+
```
|
|
41
|
+
1. @prime (load context)
|
|
42
|
+
2. @plan-feature [name] (create plan)
|
|
43
|
+
3. @execute (implement by assigned agents)
|
|
44
|
+
4. @code-review (quality check)
|
|
45
|
+
5. @execution-report (document results)
|
|
46
|
+
```
|
|
47
|
+
|
|
48
|
+
### 🐛 Bug Fix Process
|
|
49
|
+
```
|
|
50
|
+
1. @rca [issue-id] (analyze problem)
|
|
51
|
+
2. @implement-fix [issue-id] (fix implementation)
|
|
52
|
+
3. @code-review (validate fix)
|
|
53
|
+
4. @system-review (improve process)
|
|
54
|
+
```
|
|
55
|
+
|
|
56
|
+
### 🏆 Project Evaluation
|
|
57
|
+
```
|
|
58
|
+
1. @code-review-hackathon (comprehensive evaluation)
|
|
59
|
+
2. @create-prd [project] (complete documentation)
|
|
60
|
+
3. @system-review (process analysis)
|
|
61
|
+
```
|
|
62
|
+
|
|
63
|
+
## Quality Gates Checklist
|
|
64
|
+
|
|
65
|
+
### ✅ Before Implementation
|
|
66
|
+
- [ ] Project context loaded with `@prime`
|
|
67
|
+
- [ ] Feature planned with `@plan-feature`
|
|
68
|
+
- [ ] Tasks assigned to appropriate agents
|
|
69
|
+
- [ ] Dependencies identified and resolved
|
|
70
|
+
|
|
71
|
+
### ✅ During Implementation
|
|
72
|
+
- [ ] All agents following `@execute` framework
|
|
73
|
+
- [ ] Regular progress updates and coordination
|
|
74
|
+
- [ ] Issues documented and addressed promptly
|
|
75
|
+
- [ ] Quality standards maintained throughout
|
|
76
|
+
|
|
77
|
+
### ✅ Before Deployment
|
|
78
|
+
- [ ] Code review completed with `@code-review`
|
|
79
|
+
- [ ] All tests passing and coverage adequate
|
|
80
|
+
- [ ] Security validation completed
|
|
81
|
+
- [ ] Performance benchmarks met
|
|
82
|
+
- [ ] Documentation updated and complete
|
|
83
|
+
|
|
84
|
+
### ✅ After Deployment
|
|
85
|
+
- [ ] Implementation report generated with `@execution-report`
|
|
86
|
+
- [ ] Process review conducted with `@system-review`
|
|
87
|
+
- [ ] Lessons learned documented and shared
|
|
88
|
+
- [ ] Process improvements identified and planned
|
|
89
|
+
|
|
90
|
+
## Emergency Procedures
|
|
91
|
+
|
|
92
|
+
### 🚨 Critical Security Issue
|
|
93
|
+
```bash
|
|
94
|
+
1. @rca [issue-id] # Immediate analysis
|
|
95
|
+
2. @implement-fix [issue-id] # Emergency fix
|
|
96
|
+
3. @code-review # Rapid validation
|
|
97
|
+
4. Deploy with monitoring
|
|
98
|
+
```
|
|
99
|
+
|
|
100
|
+
### ⚡ Production Incident
|
|
101
|
+
```bash
|
|
102
|
+
1. Assess impact and contain issue
|
|
103
|
+
2. @rca [incident-id] for systematic analysis
|
|
104
|
+
3. @implement-fix [incident-id] for resolution
|
|
105
|
+
4. @system-review for prevention measures
|
|
106
|
+
```
|
|
107
|
+
|
|
108
|
+
### 🔄 Process Breakdown
|
|
109
|
+
```bash
|
|
110
|
+
1. Identify specific workflow issues
|
|
111
|
+
2. @system-review [current-process] [issues]
|
|
112
|
+
3. Update agent configurations and workflows
|
|
113
|
+
4. Test improved process with small feature
|
|
114
|
+
```
|
|
115
|
+
|
|
116
|
+
## Best Practices
|
|
117
|
+
|
|
118
|
+
### 🎯 Do's
|
|
119
|
+
- ✅ Always start with `@prime` for context
|
|
120
|
+
- ✅ Use `@plan-feature` before major development
|
|
121
|
+
- ✅ Follow `@execute` framework consistently
|
|
122
|
+
- ✅ Run `@code-review` before deployment
|
|
123
|
+
- ✅ Generate `@execution-report` for documentation
|
|
124
|
+
- ✅ Conduct `@system-review` for improvement
|
|
125
|
+
|
|
126
|
+
### ❌ Don'ts
|
|
127
|
+
- ❌ Skip planning phase - leads to scope creep
|
|
128
|
+
- ❌ Ignore quality gates - creates technical debt
|
|
129
|
+
- ❌ Work without coordination - causes conflicts
|
|
130
|
+
- ❌ Skip documentation - loses valuable insights
|
|
131
|
+
- ❌ Avoid process review - misses improvement opportunities
|
|
132
|
+
|
|
133
|
+
## Troubleshooting
|
|
134
|
+
|
|
135
|
+
### Issue: Agent Coordination Problems
|
|
136
|
+
**Solution**: Use Project Manager as central coordinator
|
|
137
|
+
```bash
|
|
138
|
+
@prime # Establish shared context
|
|
139
|
+
@plan-feature [name] # Clear task assignments
|
|
140
|
+
```
|
|
141
|
+
|
|
142
|
+
### Issue: Quality Issues
|
|
143
|
+
**Solution**: Implement systematic quality gates
|
|
144
|
+
```bash
|
|
145
|
+
@code-review # Before any deployment
|
|
146
|
+
@execution-report # Document quality metrics
|
|
147
|
+
```
|
|
148
|
+
|
|
149
|
+
### Issue: Process Inefficiency
|
|
150
|
+
**Solution**: Regular process analysis and improvement
|
|
151
|
+
```bash
|
|
152
|
+
@system-review [plan] [report] # Identify bottlenecks
|
|
153
|
+
Update agent configurations based on findings
|
|
154
|
+
```
|
|
155
|
+
|
|
156
|
+
### Issue: Knowledge Loss
|
|
157
|
+
**Solution**: Comprehensive documentation workflow
|
|
158
|
+
```bash
|
|
159
|
+
@execution-report # After major implementations
|
|
160
|
+
@system-review # For process insights
|
|
161
|
+
Regular DEVLOG updates
|
|
162
|
+
```
|
|
163
|
+
|
|
164
|
+
## Success Metrics
|
|
165
|
+
|
|
166
|
+
### 📊 Development Velocity
|
|
167
|
+
- Time from feature request to deployment
|
|
168
|
+
- Number of features delivered per sprint
|
|
169
|
+
- Reduction in rework and bug fixes
|
|
170
|
+
|
|
171
|
+
### 🎯 Quality Metrics
|
|
172
|
+
- Code review pass rate
|
|
173
|
+
- Test coverage percentage
|
|
174
|
+
- Production incident frequency
|
|
175
|
+
- Security vulnerability count
|
|
176
|
+
|
|
177
|
+
### 🔄 Process Effectiveness
|
|
178
|
+
- Agent coordination efficiency
|
|
179
|
+
- Knowledge retention and reuse
|
|
180
|
+
- Process improvement implementation rate
|
|
181
|
+
- Team satisfaction with workflows
|
|
182
|
+
|
|
183
|
+
## Getting Help
|
|
184
|
+
|
|
185
|
+
### 📚 Documentation
|
|
186
|
+
- `AGENT_WORKFLOW_GUIDE.md` - Comprehensive workflow documentation
|
|
187
|
+
- `IMPLEMENTATION_EXAMPLES.md` - Real-world usage examples
|
|
188
|
+
- Individual agent specifications in `agents/` directory
|
|
189
|
+
|
|
190
|
+
### 🔧 Configuration
|
|
191
|
+
- Agent hooks in `agents/hooks/` directory
|
|
192
|
+
- System prompts in `agents/prompts/` directory
|
|
193
|
+
- Project steering documents in `.kiro/steering/`
|
|
194
|
+
|
|
195
|
+
### 🎯 Support
|
|
196
|
+
- Use agent consultation triggers for guidance
|
|
197
|
+
- Review implementation examples for patterns
|
|
198
|
+
- Analyze system reviews for process improvements
|
|
199
|
+
|
|
200
|
+
---
|
|
201
|
+
|
|
202
|
+
*Keep this reference handy for quick access to essential commands and workflows!*
|
|
@@ -0,0 +1,149 @@
|
|
|
1
|
+
# Kiro-CLI Agent Team Documentation
|
|
2
|
+
|
|
3
|
+
## 🎯 **Your Complete Guide to Systematic Development**
|
|
4
|
+
|
|
5
|
+
Welcome to the comprehensive documentation for our 9-agent development team with integrated prompt workflows. This guide system will help you leverage the full power of systematic, quality-driven development.
|
|
6
|
+
|
|
7
|
+
## 🚀 **Quick Navigation**
|
|
8
|
+
|
|
9
|
+
### **Getting Started (5 minutes)**
|
|
10
|
+
- 📖 **[Quick Start Guide](quick-start.md)** - Essential setup and first workflows
|
|
11
|
+
- 🎯 **[Core Workflows](core-workflows.md)** - The 4 fundamental development patterns
|
|
12
|
+
|
|
13
|
+
### **Daily Operations (Choose Your Focus)**
|
|
14
|
+
- 👥 **[Agent Coordination](agent-coordination.md)** - Multi-agent collaboration patterns
|
|
15
|
+
- ✅ **[Quality Assurance](quality-assurance.md)** - Testing, review, and validation processes
|
|
16
|
+
- 🆘 **[Emergency Procedures](emergency-procedures.md)** - Incident response and critical fixes
|
|
17
|
+
|
|
18
|
+
### **Advanced Usage**
|
|
19
|
+
- 🏆 **[Project Evaluation](project-evaluation.md)** - Assessment and optimization workflows
|
|
20
|
+
- 🔧 **[Advanced Patterns](advanced-patterns.md)** - Complex workflows and customization
|
|
21
|
+
- 🛠️ **[Troubleshooting](troubleshooting.md)** - Common issues and solutions
|
|
22
|
+
|
|
23
|
+
## 🎭 **Meet Your Agent Team**
|
|
24
|
+
|
|
25
|
+
| Agent | Expertise | Primary Prompts | Best For |
|
|
26
|
+
|-------|-----------|----------------|----------|
|
|
27
|
+
| **Project Manager** | Coordination & Planning | `@prime`, `@plan-feature`, `@create-prd` | Project setup, feature planning |
|
|
28
|
+
| **Backend Engineer** | Server Development | `@execute` | APIs, business logic, databases |
|
|
29
|
+
| **Frontend Architect** | Client Development | `@execute` | UI, state management, UX |
|
|
30
|
+
| **Database Specialist** | Data Management | `@execute` | Schema, migrations, optimization |
|
|
31
|
+
| **DevOps Engineer** | Infrastructure | `@execute` | Deployment, CI/CD, monitoring |
|
|
32
|
+
| **Security Specialist** | Application Security | `@rca`, `@implement-fix` | Vulnerability assessment, fixes |
|
|
33
|
+
| **Test Orchestrator** | Quality Assurance | `@code-review`, `@execution-report` | Testing, validation, evaluation |
|
|
34
|
+
| **UI/UX Designer** | User Experience | `@execute` | Design, usability, accessibility |
|
|
35
|
+
| **Development Logger** | Process Improvement | `@system-review` | Workflow analysis, optimization |
|
|
36
|
+
|
|
37
|
+
## 🎯 **Essential Commands Quick Reference**
|
|
38
|
+
|
|
39
|
+
### **Core Development Flow**
|
|
40
|
+
```bash
|
|
41
|
+
@prime # Load project context
|
|
42
|
+
@plan-feature [name] # Create implementation plan
|
|
43
|
+
@execute # Systematic implementation
|
|
44
|
+
@code-review # Quality validation
|
|
45
|
+
@execution-report # Document results
|
|
46
|
+
```
|
|
47
|
+
|
|
48
|
+
### **Specialized Workflows**
|
|
49
|
+
```bash
|
|
50
|
+
@create-prd [feature] # Requirements documentation
|
|
51
|
+
@rca [issue-id] # Root cause analysis
|
|
52
|
+
@implement-fix [issue-id] # Systematic fixes
|
|
53
|
+
@system-review # Process improvement
|
|
54
|
+
@code-review-hackathon # Project evaluation
|
|
55
|
+
```
|
|
56
|
+
|
|
57
|
+
## 🏗️ **System Architecture**
|
|
58
|
+
|
|
59
|
+
### **Quality Gate System**
|
|
60
|
+
Our integrated system includes 5 mandatory quality gates:
|
|
61
|
+
|
|
62
|
+
1. **Planning Gate**: `@prime` + `@plan-feature` before implementation
|
|
63
|
+
2. **Implementation Gate**: `@execute` framework for all agents
|
|
64
|
+
3. **Quality Gate**: `@code-review` before deployment
|
|
65
|
+
4. **Documentation Gate**: `@execution-report` for major features
|
|
66
|
+
5. **Improvement Gate**: `@system-review` for process optimization
|
|
67
|
+
|
|
68
|
+
### **Workflow Patterns**
|
|
69
|
+
- **Sequential**: Project Manager → Specialist Agent → Test Orchestrator
|
|
70
|
+
- **Parallel**: Multiple agents working simultaneously with coordination
|
|
71
|
+
- **Iterative**: Implementation → Review → Fix → Improve cycles
|
|
72
|
+
- **Emergency**: Rapid response with maintained quality standards
|
|
73
|
+
|
|
74
|
+
## 📊 **Success Metrics**
|
|
75
|
+
|
|
76
|
+
### **Development Velocity**
|
|
77
|
+
- Time from feature request to deployment
|
|
78
|
+
- Agent coordination efficiency
|
|
79
|
+
- Reduction in rework and conflicts
|
|
80
|
+
|
|
81
|
+
### **Quality Metrics**
|
|
82
|
+
- Code review pass rates
|
|
83
|
+
- Test coverage and compliance
|
|
84
|
+
- Security vulnerability prevention
|
|
85
|
+
- Production incident reduction
|
|
86
|
+
|
|
87
|
+
### **Process Effectiveness**
|
|
88
|
+
- Knowledge retention and reuse
|
|
89
|
+
- Process improvement implementation
|
|
90
|
+
- Team workflow adoption
|
|
91
|
+
- Continuous learning integration
|
|
92
|
+
|
|
93
|
+
## 🎓 **Learning Path**
|
|
94
|
+
|
|
95
|
+
### **Beginner (Week 1)**
|
|
96
|
+
1. Read [Quick Start Guide](quick-start.md)
|
|
97
|
+
2. Practice [Core Workflows](core-workflows.md)
|
|
98
|
+
3. Try [Agent Coordination](agent-coordination.md) patterns
|
|
99
|
+
|
|
100
|
+
### **Intermediate (Week 2-3)**
|
|
101
|
+
1. Master [Quality Assurance](quality-assurance.md) processes
|
|
102
|
+
2. Learn [Emergency Procedures](emergency-procedures.md)
|
|
103
|
+
3. Explore [Project Evaluation](project-evaluation.md) methods
|
|
104
|
+
|
|
105
|
+
### **Advanced (Week 4+)**
|
|
106
|
+
1. Implement [Advanced Patterns](advanced-patterns.md)
|
|
107
|
+
2. Customize workflows for your team
|
|
108
|
+
3. Contribute improvements back to the system
|
|
109
|
+
|
|
110
|
+
## 🆘 **Need Help?**
|
|
111
|
+
|
|
112
|
+
### **Quick Solutions**
|
|
113
|
+
- 🔍 **Can't find something?** Check [Troubleshooting](troubleshooting.md)
|
|
114
|
+
- 🚨 **Emergency?** Go to [Emergency Procedures](emergency-procedures.md)
|
|
115
|
+
- 🤔 **Not sure which workflow?** Start with [Core Workflows](core-workflows.md)
|
|
116
|
+
|
|
117
|
+
### **Support Resources**
|
|
118
|
+
- **Agent Specifications**: Detailed docs in `agents/` directory
|
|
119
|
+
- **Hook Configurations**: Automation setup in `agents/hooks/`
|
|
120
|
+
- **System Prompts**: Implementation details in `agents/prompts/`
|
|
121
|
+
- **Development Log**: Process insights in `DEVLOG.md`
|
|
122
|
+
|
|
123
|
+
## 🎯 **What Makes This System Special**
|
|
124
|
+
|
|
125
|
+
### **Systematic Quality**
|
|
126
|
+
Every aspect of development has built-in quality assurance through integrated prompts and agent coordination.
|
|
127
|
+
|
|
128
|
+
### **Predictable Outcomes**
|
|
129
|
+
Standardized workflows create consistent, reliable results across all project types and team sizes.
|
|
130
|
+
|
|
131
|
+
### **Continuous Learning**
|
|
132
|
+
Process improvement is built into every development cycle through systematic analysis and optimization.
|
|
133
|
+
|
|
134
|
+
### **Scalable Excellence**
|
|
135
|
+
The system handles everything from individual features to complete applications with the same level of quality and coordination.
|
|
136
|
+
|
|
137
|
+
---
|
|
138
|
+
|
|
139
|
+
## 🚀 **Ready to Get Started?**
|
|
140
|
+
|
|
141
|
+
1. **New to the system?** → [Quick Start Guide](quick-start.md)
|
|
142
|
+
2. **Ready to build?** → [Core Workflows](core-workflows.md)
|
|
143
|
+
3. **Need specific help?** → Choose the relevant focused guide above
|
|
144
|
+
|
|
145
|
+
**Transform your development process with systematic, quality-driven workflows!**
|
|
146
|
+
|
|
147
|
+
---
|
|
148
|
+
|
|
149
|
+
*Last updated: 2026-01-04 | System version: 1.0 | Agent team: 9 specialists + 12 integrated prompts*
|