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,513 @@
|
|
|
1
|
+
# Project Manager Agent - Hook Configurations
|
|
2
|
+
|
|
3
|
+
# Initial Project Consultation
|
|
4
|
+
consultation:
|
|
5
|
+
- name: "project_consultation"
|
|
6
|
+
description: "Initiate project management consultation for new projects"
|
|
7
|
+
trigger:
|
|
8
|
+
type: "message_pattern"
|
|
9
|
+
pattern: "(?i)(new project|start project|project planning|manage project|project setup)"
|
|
10
|
+
action:
|
|
11
|
+
type: "send_message"
|
|
12
|
+
message: |
|
|
13
|
+
🎯 **Project Manager Consultation Started**
|
|
14
|
+
|
|
15
|
+
I'll help you set up effective project management tailored to your specific needs:
|
|
16
|
+
|
|
17
|
+
**📋 Project Scope Questions:**
|
|
18
|
+
- What type of project are we building?
|
|
19
|
+
• Web application with frontend/backend
|
|
20
|
+
• API service or microservice
|
|
21
|
+
• Mobile application
|
|
22
|
+
• Enterprise system or platform
|
|
23
|
+
• Other (please specify)
|
|
24
|
+
|
|
25
|
+
- What's the primary goal and success criteria?
|
|
26
|
+
- Who are the target users and their key needs?
|
|
27
|
+
- What's the expected timeline and any hard deadlines?
|
|
28
|
+
- What's the team size and expertise level?
|
|
29
|
+
|
|
30
|
+
**⚡ Methodology Preferences:**
|
|
31
|
+
- What development methodology do you prefer?
|
|
32
|
+
• Agile/Scrum with sprints
|
|
33
|
+
• Kanban with continuous flow
|
|
34
|
+
• Waterfall with phases
|
|
35
|
+
• Hybrid approach
|
|
36
|
+
|
|
37
|
+
- How do you like to track progress?
|
|
38
|
+
• Sprint-based with regular reviews
|
|
39
|
+
• Milestone-based with major checkpoints
|
|
40
|
+
• Continuous delivery with daily updates
|
|
41
|
+
• Custom approach
|
|
42
|
+
|
|
43
|
+
**👥 Team Structure Questions:**
|
|
44
|
+
- Which agents should be involved? (Frontend, Backend, Database, DevOps, Testing)
|
|
45
|
+
- How should agents collaborate and hand off work?
|
|
46
|
+
- What's your preferred task granularity? (Large features vs detailed tasks)
|
|
47
|
+
- How often do you want progress updates?
|
|
48
|
+
|
|
49
|
+
**🎯 Quality & Risk Assessment:**
|
|
50
|
+
- What are your quality standards and testing requirements?
|
|
51
|
+
- Risk tolerance for new technologies or approaches?
|
|
52
|
+
- Any compliance, security, or performance requirements?
|
|
53
|
+
- Documentation and knowledge management preferences?
|
|
54
|
+
|
|
55
|
+
Based on your answers, I'll create a customized project management approach with the right task structure, agent coordination, and progress tracking!
|
|
56
|
+
agent: "project-manager"
|
|
57
|
+
|
|
58
|
+
# Project Lifecycle Hooks
|
|
59
|
+
project_management:
|
|
60
|
+
- name: "project_initialization"
|
|
61
|
+
description: "Set up new project structure and initial planning"
|
|
62
|
+
trigger:
|
|
63
|
+
type: "user_command"
|
|
64
|
+
conditions:
|
|
65
|
+
- command: "new-project"
|
|
66
|
+
- parameters: ["project_name", "project_type"]
|
|
67
|
+
action:
|
|
68
|
+
type: "execute_prompt"
|
|
69
|
+
prompt: "prime.md"
|
|
70
|
+
message: "New project requested. Loading project context and creating comprehensive project structure in Archon..."
|
|
71
|
+
agent: "project-manager"
|
|
72
|
+
include_context:
|
|
73
|
+
- project_requirements: true
|
|
74
|
+
- technology_stack: true
|
|
75
|
+
- timeline_constraints: true
|
|
76
|
+
|
|
77
|
+
- name: "quickstart_project_setup"
|
|
78
|
+
description: "Execute comprehensive project quickstart and onboarding"
|
|
79
|
+
trigger:
|
|
80
|
+
type: "user_command"
|
|
81
|
+
conditions:
|
|
82
|
+
- command: "quickstart"
|
|
83
|
+
- command: "quick-start"
|
|
84
|
+
action:
|
|
85
|
+
type: "execute_prompt"
|
|
86
|
+
prompt: "quickstart.md"
|
|
87
|
+
message: "Initiating comprehensive project quickstart with automated setup and team onboarding..."
|
|
88
|
+
agent: "project-manager"
|
|
89
|
+
include_context:
|
|
90
|
+
- project_type: true
|
|
91
|
+
- team_preferences: true
|
|
92
|
+
- technology_stack: true
|
|
93
|
+
- initial_requirements: true
|
|
94
|
+
|
|
95
|
+
- name: "context_loading"
|
|
96
|
+
description: "Load comprehensive project context before major planning activities"
|
|
97
|
+
trigger:
|
|
98
|
+
type: "user_command"
|
|
99
|
+
conditions:
|
|
100
|
+
- command: "load-context"
|
|
101
|
+
- command: "prime"
|
|
102
|
+
action:
|
|
103
|
+
type: "execute_prompt"
|
|
104
|
+
prompt: "prime.md"
|
|
105
|
+
message: "Loading comprehensive project context and codebase understanding..."
|
|
106
|
+
agent: "project-manager"
|
|
107
|
+
include_context:
|
|
108
|
+
- codebase_structure: true
|
|
109
|
+
- existing_documentation: true
|
|
110
|
+
- project_history: true
|
|
111
|
+
|
|
112
|
+
- name: "feature_planning"
|
|
113
|
+
description: "Create comprehensive feature implementation plans"
|
|
114
|
+
trigger:
|
|
115
|
+
type: "user_command"
|
|
116
|
+
conditions:
|
|
117
|
+
- command: "plan-feature"
|
|
118
|
+
- parameters: ["feature_name"]
|
|
119
|
+
action:
|
|
120
|
+
type: "execute_prompt"
|
|
121
|
+
prompt: "plan-feature.md"
|
|
122
|
+
message: "Creating comprehensive feature implementation plan with architecture decisions and task breakdown..."
|
|
123
|
+
agent: "project-manager"
|
|
124
|
+
include_context:
|
|
125
|
+
- existing_architecture: true
|
|
126
|
+
- agent_availability: true
|
|
127
|
+
- project_constraints: true
|
|
128
|
+
|
|
129
|
+
- name: "requirements_documentation"
|
|
130
|
+
description: "Generate Product Requirements Documents for major features"
|
|
131
|
+
trigger:
|
|
132
|
+
type: "user_command"
|
|
133
|
+
conditions:
|
|
134
|
+
- command: "create-prd"
|
|
135
|
+
- parameters: ["feature_name"]
|
|
136
|
+
action:
|
|
137
|
+
type: "execute_prompt"
|
|
138
|
+
prompt: "create-prd.md"
|
|
139
|
+
message: "Generating comprehensive Product Requirements Document..."
|
|
140
|
+
agent: "project-manager"
|
|
141
|
+
include_context:
|
|
142
|
+
- business_requirements: true
|
|
143
|
+
- user_needs: true
|
|
144
|
+
- technical_constraints: true
|
|
145
|
+
|
|
146
|
+
- name: "milestone_review"
|
|
147
|
+
description: "Assess milestone completion and plan next phase"
|
|
148
|
+
trigger:
|
|
149
|
+
type: "milestone_reached"
|
|
150
|
+
conditions:
|
|
151
|
+
- completion_percentage: ">= 90%"
|
|
152
|
+
- milestone_type: ["sprint", "release", "phase"]
|
|
153
|
+
action:
|
|
154
|
+
type: "send_message"
|
|
155
|
+
message: "Milestone approaching completion. Review deliverables, assess quality, identify any remaining tasks, celebrate achievements, and plan next milestone."
|
|
156
|
+
agent: "project-manager"
|
|
157
|
+
include_context:
|
|
158
|
+
- milestone_tasks: true
|
|
159
|
+
- quality_metrics: true
|
|
160
|
+
- team_performance: true
|
|
161
|
+
|
|
162
|
+
# Task Management Hooks
|
|
163
|
+
task_coordination:
|
|
164
|
+
- name: "task_assignment"
|
|
165
|
+
description: "Assign new tasks to appropriate agents"
|
|
166
|
+
trigger:
|
|
167
|
+
type: "task_created"
|
|
168
|
+
conditions:
|
|
169
|
+
- task_status: "todo"
|
|
170
|
+
- assignee: "unassigned"
|
|
171
|
+
action:
|
|
172
|
+
type: "send_message"
|
|
173
|
+
message: "New unassigned task detected. Analyze task requirements, determine best-fit agent based on expertise and availability, assign task with clear context and acceptance criteria."
|
|
174
|
+
agent: "project-manager"
|
|
175
|
+
include_context:
|
|
176
|
+
- task_details: true
|
|
177
|
+
- agent_workloads: true
|
|
178
|
+
- skill_requirements: true
|
|
179
|
+
|
|
180
|
+
- name: "task_blocked"
|
|
181
|
+
description: "Address blocked tasks and resolve impediments"
|
|
182
|
+
trigger:
|
|
183
|
+
type: "task_status_change"
|
|
184
|
+
conditions:
|
|
185
|
+
- to_status: "blocked"
|
|
186
|
+
- block_duration: "> 2 hours"
|
|
187
|
+
action:
|
|
188
|
+
type: "send_message"
|
|
189
|
+
message: "Task blocked for extended period. Investigate blocker, identify resolution options, reassign if needed, update dependencies, and communicate status to stakeholders."
|
|
190
|
+
agent: "project-manager"
|
|
191
|
+
include_context:
|
|
192
|
+
- blocker_details: true
|
|
193
|
+
- dependency_chain: true
|
|
194
|
+
- alternative_approaches: true
|
|
195
|
+
|
|
196
|
+
- name: "task_overdue"
|
|
197
|
+
description: "Manage overdue tasks and adjust planning"
|
|
198
|
+
trigger:
|
|
199
|
+
type: "task_deadline"
|
|
200
|
+
conditions:
|
|
201
|
+
- status: "overdue"
|
|
202
|
+
- priority: ["high", "critical"]
|
|
203
|
+
action:
|
|
204
|
+
type: "send_message"
|
|
205
|
+
message: "High-priority task overdue. Assess impact on project timeline, reallocate resources if needed, update stakeholders, and adjust downstream dependencies."
|
|
206
|
+
agent: "project-manager"
|
|
207
|
+
include_context:
|
|
208
|
+
- task_history: true
|
|
209
|
+
- resource_availability: true
|
|
210
|
+
- impact_analysis: true
|
|
211
|
+
|
|
212
|
+
# Agent Coordination Hooks
|
|
213
|
+
team_management:
|
|
214
|
+
- name: "agent_handoff_coordination"
|
|
215
|
+
description: "Facilitate smooth handoffs between agents"
|
|
216
|
+
trigger:
|
|
217
|
+
type: "agent_change"
|
|
218
|
+
conditions:
|
|
219
|
+
- task_in_progress: true
|
|
220
|
+
- context_transfer_required: true
|
|
221
|
+
action:
|
|
222
|
+
type: "send_message"
|
|
223
|
+
message: "Agent handoff detected. Ensure complete context transfer, verify receiving agent understands requirements, update task assignments, and monitor transition success."
|
|
224
|
+
agent: "project-manager"
|
|
225
|
+
include_context:
|
|
226
|
+
- handoff_context: true
|
|
227
|
+
- task_progress: true
|
|
228
|
+
- agent_capabilities: true
|
|
229
|
+
|
|
230
|
+
- name: "multi_agent_collaboration"
|
|
231
|
+
description: "Coordinate complex multi-agent tasks"
|
|
232
|
+
trigger:
|
|
233
|
+
type: "task_assignment"
|
|
234
|
+
conditions:
|
|
235
|
+
- agent_count: "> 1"
|
|
236
|
+
- task_complexity: ">= 4"
|
|
237
|
+
- coordination_required: true
|
|
238
|
+
action:
|
|
239
|
+
type: "send_message"
|
|
240
|
+
message: "Multi-agent task initiated. Define clear roles and responsibilities, establish communication protocols, set up coordination checkpoints, and monitor collaboration effectiveness."
|
|
241
|
+
agent: "project-manager"
|
|
242
|
+
include_context:
|
|
243
|
+
- agent_roles: true
|
|
244
|
+
- task_breakdown: true
|
|
245
|
+
- communication_plan: true
|
|
246
|
+
|
|
247
|
+
- name: "agent_capacity_management"
|
|
248
|
+
description: "Balance workload across available agents"
|
|
249
|
+
trigger:
|
|
250
|
+
type: "schedule"
|
|
251
|
+
conditions:
|
|
252
|
+
- time: "09:00"
|
|
253
|
+
- days: ["monday", "wednesday", "friday"]
|
|
254
|
+
action:
|
|
255
|
+
type: "send_message"
|
|
256
|
+
message: "Capacity review scheduled. Assess current agent workloads, identify over/under-utilized agents, rebalance task assignments, and optimize team efficiency."
|
|
257
|
+
agent: "project-manager"
|
|
258
|
+
include_context:
|
|
259
|
+
- agent_workloads: true
|
|
260
|
+
- task_priorities: true
|
|
261
|
+
- performance_metrics: true
|
|
262
|
+
|
|
263
|
+
# Quality Assurance Hooks
|
|
264
|
+
quality_management:
|
|
265
|
+
- name: "code_review_coordination"
|
|
266
|
+
description: "Ensure code reviews are completed timely"
|
|
267
|
+
trigger:
|
|
268
|
+
type: "task_status_change"
|
|
269
|
+
conditions:
|
|
270
|
+
- to_status: "review"
|
|
271
|
+
- task_type: ["feature", "bugfix"]
|
|
272
|
+
action:
|
|
273
|
+
type: "send_message"
|
|
274
|
+
message: "Code review required. Assign appropriate reviewer, ensure review criteria are clear, set review deadline, and track completion."
|
|
275
|
+
agent: "project-manager"
|
|
276
|
+
include_context:
|
|
277
|
+
- code_changes: true
|
|
278
|
+
- reviewer_availability: true
|
|
279
|
+
- review_standards: true
|
|
280
|
+
|
|
281
|
+
- name: "testing_coordination"
|
|
282
|
+
description: "Coordinate testing efforts across the team"
|
|
283
|
+
trigger:
|
|
284
|
+
type: "feature_completion"
|
|
285
|
+
conditions:
|
|
286
|
+
- testing_required: true
|
|
287
|
+
- test_coverage: "< 80%"
|
|
288
|
+
action:
|
|
289
|
+
type: "send_message"
|
|
290
|
+
message: "Feature completed but testing insufficient. Coordinate with Test Orchestrator to ensure adequate coverage, schedule integration tests, and verify quality gates."
|
|
291
|
+
agent: "project-manager"
|
|
292
|
+
include_context:
|
|
293
|
+
- feature_scope: true
|
|
294
|
+
- current_coverage: true
|
|
295
|
+
- testing_requirements: true
|
|
296
|
+
|
|
297
|
+
- name: "deployment_readiness"
|
|
298
|
+
description: "Assess and coordinate deployment preparations"
|
|
299
|
+
trigger:
|
|
300
|
+
type: "milestone_completion"
|
|
301
|
+
conditions:
|
|
302
|
+
- milestone_type: "release"
|
|
303
|
+
- deployment_target: ["staging", "production"]
|
|
304
|
+
action:
|
|
305
|
+
type: "send_message"
|
|
306
|
+
message: "Release milestone completed. Coordinate with DevOps Assistant for deployment readiness check, ensure all quality gates passed, and prepare rollback plans."
|
|
307
|
+
agent: "project-manager"
|
|
308
|
+
include_context:
|
|
309
|
+
- release_scope: true
|
|
310
|
+
- quality_metrics: true
|
|
311
|
+
- deployment_requirements: true
|
|
312
|
+
|
|
313
|
+
# Progress Monitoring Hooks
|
|
314
|
+
progress_tracking:
|
|
315
|
+
- name: "daily_standup"
|
|
316
|
+
description: "Conduct daily progress review and planning"
|
|
317
|
+
trigger:
|
|
318
|
+
type: "schedule"
|
|
319
|
+
conditions:
|
|
320
|
+
- time: "09:30"
|
|
321
|
+
- days: ["monday", "tuesday", "wednesday", "thursday", "friday"]
|
|
322
|
+
action:
|
|
323
|
+
type: "send_message"
|
|
324
|
+
message: "Daily standup time. Review yesterday's progress, identify today's priorities, surface any blockers, coordinate agent activities, and update project status."
|
|
325
|
+
agent: "project-manager"
|
|
326
|
+
include_context:
|
|
327
|
+
- daily_progress: true
|
|
328
|
+
- active_tasks: true
|
|
329
|
+
- team_availability: true
|
|
330
|
+
|
|
331
|
+
- name: "weekly_planning"
|
|
332
|
+
description: "Plan weekly objectives and resource allocation"
|
|
333
|
+
trigger:
|
|
334
|
+
type: "schedule"
|
|
335
|
+
conditions:
|
|
336
|
+
- time: "08:00"
|
|
337
|
+
- day: "monday"
|
|
338
|
+
action:
|
|
339
|
+
type: "send_message"
|
|
340
|
+
message: "Weekly planning session. Review previous week's achievements, set this week's objectives, allocate resources, identify risks, and communicate plans to stakeholders."
|
|
341
|
+
agent: "project-manager"
|
|
342
|
+
include_context:
|
|
343
|
+
- weekly_metrics: true
|
|
344
|
+
- upcoming_deadlines: true
|
|
345
|
+
- resource_availability: true
|
|
346
|
+
|
|
347
|
+
- name: "velocity_tracking"
|
|
348
|
+
description: "Monitor team velocity and adjust planning"
|
|
349
|
+
trigger:
|
|
350
|
+
type: "schedule"
|
|
351
|
+
conditions:
|
|
352
|
+
- time: "17:00"
|
|
353
|
+
- day: "friday"
|
|
354
|
+
action:
|
|
355
|
+
type: "send_message"
|
|
356
|
+
message: "Weekly velocity review. Calculate team velocity, compare to historical data, identify trends, adjust future planning, and update stakeholder expectations."
|
|
357
|
+
agent: "project-manager"
|
|
358
|
+
include_context:
|
|
359
|
+
- completed_tasks: true
|
|
360
|
+
- velocity_history: true
|
|
361
|
+
- planning_accuracy: true
|
|
362
|
+
|
|
363
|
+
# Risk Management Hooks
|
|
364
|
+
risk_monitoring:
|
|
365
|
+
- name: "dependency_risk_assessment"
|
|
366
|
+
description: "Monitor and mitigate dependency risks"
|
|
367
|
+
trigger:
|
|
368
|
+
type: "dependency_delay"
|
|
369
|
+
conditions:
|
|
370
|
+
- delay_duration: "> 24 hours"
|
|
371
|
+
- impact_level: ["medium", "high", "critical"]
|
|
372
|
+
action:
|
|
373
|
+
type: "send_message"
|
|
374
|
+
message: "Dependency delay detected with significant impact. Assess cascade effects, identify alternative approaches, communicate with affected stakeholders, and adjust project timeline."
|
|
375
|
+
agent: "project-manager"
|
|
376
|
+
include_context:
|
|
377
|
+
- dependency_chain: true
|
|
378
|
+
- impact_analysis: true
|
|
379
|
+
- mitigation_options: true
|
|
380
|
+
|
|
381
|
+
- name: "scope_creep_detection"
|
|
382
|
+
description: "Identify and manage scope changes"
|
|
383
|
+
trigger:
|
|
384
|
+
type: "requirement_change"
|
|
385
|
+
conditions:
|
|
386
|
+
- change_magnitude: "> 20%"
|
|
387
|
+
- project_phase: ["development", "testing"]
|
|
388
|
+
action:
|
|
389
|
+
type: "send_message"
|
|
390
|
+
message: "Significant scope change detected. Assess impact on timeline and resources, evaluate change necessity, negotiate with stakeholders, and update project plan accordingly."
|
|
391
|
+
agent: "project-manager"
|
|
392
|
+
include_context:
|
|
393
|
+
- change_details: true
|
|
394
|
+
- current_progress: true
|
|
395
|
+
- resource_constraints: true
|
|
396
|
+
|
|
397
|
+
- name: "quality_risk_monitoring"
|
|
398
|
+
description: "Monitor quality metrics and address degradation"
|
|
399
|
+
trigger:
|
|
400
|
+
type: "quality_threshold"
|
|
401
|
+
conditions:
|
|
402
|
+
- metric_type: ["test_coverage", "bug_rate", "performance"]
|
|
403
|
+
- threshold_breach: "below_minimum"
|
|
404
|
+
action:
|
|
405
|
+
type: "send_message"
|
|
406
|
+
message: "Quality metric below acceptable threshold. Investigate root cause, coordinate remediation efforts, adjust quality processes, and prevent future degradation."
|
|
407
|
+
agent: "project-manager"
|
|
408
|
+
include_context:
|
|
409
|
+
- quality_trends: true
|
|
410
|
+
- remediation_options: true
|
|
411
|
+
- process_gaps: true
|
|
412
|
+
|
|
413
|
+
# Stakeholder Communication Hooks
|
|
414
|
+
communication_management:
|
|
415
|
+
- name: "status_reporting"
|
|
416
|
+
description: "Generate and distribute project status reports"
|
|
417
|
+
trigger:
|
|
418
|
+
type: "schedule"
|
|
419
|
+
conditions:
|
|
420
|
+
- time: "16:00"
|
|
421
|
+
- day: "friday"
|
|
422
|
+
action:
|
|
423
|
+
type: "send_message"
|
|
424
|
+
message: "Weekly status report due. Compile project progress, highlight achievements and challenges, update timeline and milestones, and prepare stakeholder communication."
|
|
425
|
+
agent: "project-manager"
|
|
426
|
+
include_context:
|
|
427
|
+
- weekly_progress: true
|
|
428
|
+
- milestone_status: true
|
|
429
|
+
- risk_register: true
|
|
430
|
+
|
|
431
|
+
- name: "escalation_management"
|
|
432
|
+
description: "Handle escalations and critical issues"
|
|
433
|
+
trigger:
|
|
434
|
+
type: "issue_escalation"
|
|
435
|
+
conditions:
|
|
436
|
+
- severity: ["high", "critical"]
|
|
437
|
+
- resolution_time: "> 4 hours"
|
|
438
|
+
action:
|
|
439
|
+
type: "send_message"
|
|
440
|
+
message: "Critical issue escalation. Assess situation, mobilize appropriate resources, communicate with stakeholders, coordinate resolution efforts, and document lessons learned."
|
|
441
|
+
agent: "project-manager"
|
|
442
|
+
include_context:
|
|
443
|
+
- issue_details: true
|
|
444
|
+
- available_resources: true
|
|
445
|
+
- stakeholder_impact: true
|
|
446
|
+
|
|
447
|
+
# Manual Control Hooks
|
|
448
|
+
manual_controls:
|
|
449
|
+
- name: "project_status_request"
|
|
450
|
+
description: "Provide comprehensive project status on demand"
|
|
451
|
+
trigger:
|
|
452
|
+
type: "user_command"
|
|
453
|
+
conditions:
|
|
454
|
+
- command: "project-status"
|
|
455
|
+
action:
|
|
456
|
+
type: "send_message"
|
|
457
|
+
message: "Project status requested. Generate comprehensive status report including progress, milestones, risks, team performance, and recommendations."
|
|
458
|
+
agent: "project-manager"
|
|
459
|
+
|
|
460
|
+
- name: "resource_reallocation"
|
|
461
|
+
description: "Manually adjust resource allocation"
|
|
462
|
+
trigger:
|
|
463
|
+
type: "user_command"
|
|
464
|
+
conditions:
|
|
465
|
+
- command: "reallocate-resources"
|
|
466
|
+
- parameters: ["from_agent", "to_agent", "task_ids"]
|
|
467
|
+
action:
|
|
468
|
+
type: "send_message"
|
|
469
|
+
message: "Resource reallocation requested. Transfer specified tasks, ensure proper context handoff, update assignments in Archon, and monitor transition success."
|
|
470
|
+
agent: "project-manager"
|
|
471
|
+
|
|
472
|
+
- name: "quality_metrics_collection"
|
|
473
|
+
description: "Collect and analyze quality metrics for continuous improvement"
|
|
474
|
+
trigger:
|
|
475
|
+
type: "session_completion"
|
|
476
|
+
conditions:
|
|
477
|
+
- session_duration: ">= 10 minutes"
|
|
478
|
+
action:
|
|
479
|
+
type: "execute_prompt"
|
|
480
|
+
prompt: "quality-metrics.md"
|
|
481
|
+
message: "Collecting comprehensive quality metrics and generating improvement insights..."
|
|
482
|
+
agent: "project-manager"
|
|
483
|
+
include_context:
|
|
484
|
+
- session_metrics: true
|
|
485
|
+
- team_performance: true
|
|
486
|
+
- quality_indicators: true
|
|
487
|
+
|
|
488
|
+
# Configuration
|
|
489
|
+
hook_settings:
|
|
490
|
+
global:
|
|
491
|
+
enabled: true
|
|
492
|
+
log_level: "info"
|
|
493
|
+
archon_integration: true
|
|
494
|
+
|
|
495
|
+
project_management:
|
|
496
|
+
auto_task_assignment: true
|
|
497
|
+
milestone_tracking: true
|
|
498
|
+
risk_monitoring: true
|
|
499
|
+
|
|
500
|
+
team_coordination:
|
|
501
|
+
handoff_monitoring: true
|
|
502
|
+
capacity_balancing: true
|
|
503
|
+
collaboration_tracking: true
|
|
504
|
+
|
|
505
|
+
quality_assurance:
|
|
506
|
+
review_enforcement: true
|
|
507
|
+
testing_coordination: true
|
|
508
|
+
deployment_gates: true
|
|
509
|
+
|
|
510
|
+
reporting:
|
|
511
|
+
daily_standups: true
|
|
512
|
+
weekly_reports: true
|
|
513
|
+
stakeholder_updates: true
|