-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathJAEGIS-METHOD-v1.0\jaegis-agent\checklists.txt
More file actions
222 lines (189 loc) · 7.99 KB
/
JAEGIS-METHOD-v1.0\jaegis-agent\checklists.txt
File metadata and controls
222 lines (189 loc) · 7.99 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
==================== START: pm-checklist ====================
# Product Manager Validation Checklist
## Requirements Validation
- [ ] All functional requirements are clearly defined and measurable
- [ ] Non-functional requirements include performance, security, and scalability
- [ ] Requirements are validated for technical feasibility
- [ ] User needs are backed by research or evidence
- [ ] Success metrics are specific and measurable
## Market Research Integration
- [ ] Competitive analysis completed and integrated
- [ ] Target user personas validated through research
- [ ] Market positioning is clear and differentiated
- [ ] User journey is mapped and validated
- [ ] Value proposition is research-backed
## Technical Feasibility
- [ ] Technology stack is validated for current versions
- [ ] Dependencies are checked for security and compatibility
- [ ] Performance requirements are realistic and achievable
- [ ] Scalability needs are addressed in requirements
- [ ] Security requirements meet current standards
## Documentation Quality
- [ ] PRD follows standardized template format
- [ ] All sections are complete and comprehensive
- [ ] Handoff materials are prepared for technical teams
- [ ] Validation reports are included
- [ ] Research citations are provided where applicable
## Collaboration & Handoff
- [ ] Shared context is updated with PRD insights
- [ ] Handoff materials prepared for System Architect
- [ ] Handoff materials prepared for Design Architect (if UI components)
- [ ] Validation gates are documented
- [ ] Next steps are clearly defined
==================== END: pm-checklist ====================
==================== START: architect-checklist ====================
# System Architect Validation Checklist
## Architecture Design
- [ ] System architecture addresses all PRD requirements
- [ ] Architecture patterns are current and well-established
- [ ] Component relationships are clearly defined
- [ ] Data flow is documented and validated
- [ ] Integration points are specified and secure
## Technology Validation
- [ ] All frameworks are current stable versions
- [ ] Dependencies pass security vulnerability checks
- [ ] Technology stack is compatible and well-supported
- [ ] Migration paths are available for future updates
- [ ] Community support is active and reliable
## Security Integration
- [ ] Security patterns are integrated from design phase
- [ ] Authentication and authorization strategies are defined
- [ ] Data protection measures are specified
- [ ] Network security is addressed
- [ ] Compliance requirements are integrated
## Performance & Scalability
- [ ] Performance requirements are addressed in architecture
- [ ] Scalability patterns are integrated
- [ ] Caching strategies are defined where appropriate
- [ ] Database design supports performance requirements
- [ ] Monitoring and observability are planned
## Documentation & Standards
- [ ] Architecture documentation is comprehensive
- [ ] Diagrams are clear and follow standards
- [ ] Implementation guidance is provided
- [ ] Code organization standards are defined
- [ ] Testing strategies are specified
## Validation & Research
- [ ] All technologies researched for current best practices
- [ ] Dependency validation completed with web research
- [ ] Security assessment completed
- [ ] Performance validation completed
- [ ] Alternative solutions evaluated
## Collaboration & Handoff
- [ ] Shared context updated with architectural decisions
- [ ] Handoff materials prepared for DevOps team
- [ ] Handoff materials prepared for Development team
- [ ] Validation reports included in handoff
- [ ] Implementation roadmap is clear
==================== END: architect-checklist ====================
==================== START: dependency-safety ====================
# Dependency Safety Validation Checklist
## Package Version Validation
- [ ] All packages are current stable versions (not outdated)
- [ ] Package versions are compatible with each other
- [ ] No deprecated packages are used
- [ ] Migration paths exist for all dependencies
- [ ] Package maintainers are active and reliable
## Security Assessment
- [ ] No known security vulnerabilities in dependencies
- [ ] Security patches are available and current
- [ ] Dependency licenses are compatible with project
- [ ] Supply chain security is validated
- [ ] Vulnerability monitoring is in place
## Compatibility Validation
- [ ] Framework versions are compatible
- [ ] Node.js/runtime versions are supported
- [ ] Operating system compatibility verified
- [ ] Browser compatibility confirmed (for frontend)
- [ ] Mobile platform compatibility (if applicable)
## System Requirements
- [ ] All system tools are available and accessible
- [ ] PATH requirements are documented and verified
- [ ] Installation procedures are validated
- [ ] Alternative installation methods researched
- [ ] System dependencies are documented
## Research Validation
- [ ] Current best practices researched and integrated
- [ ] Community recommendations validated
- [ ] Performance benchmarks reviewed
- [ ] Alternative solutions evaluated
- [ ] Future roadmap considerations included
## Documentation
- [ ] All dependencies documented with versions
- [ ] Installation instructions provided
- [ ] Troubleshooting guidance included
- [ ] Update procedures documented
- [ ] Rollback procedures defined
==================== END: dependency-safety ====================
==================== START: validation-checklist ====================
# Comprehensive Validation Checklist
## Pre-Generation Validation
- [ ] Requirements are clear and validated
- [ ] Technology research completed
- [ ] Current best practices identified
- [ ] Security standards researched
- [ ] Performance benchmarks established
## Real-Time Validation
- [ ] Dependencies validated during generation
- [ ] Security checks performed continuously
- [ ] Compatibility verified in real-time
- [ ] Best practices applied consistently
- [ ] Quality gates enforced
## Post-Generation Validation
- [ ] All outputs meet quality standards
- [ ] Dependencies are current and secure
- [ ] Documentation is comprehensive
- [ ] Handoff materials are complete
- [ ] Validation reports generated
## Cross-Agent Validation
- [ ] Shared context is maintained
- [ ] Agent outputs are consistent
- [ ] Handoffs are complete and validated
- [ ] Collaborative intelligence is maintained
- [ ] Quality standards are enforced
## Research Integration
- [ ] Web research findings integrated
- [ ] Current standards applied
- [ ] Alternative solutions considered
- [ ] Best practices implemented
- [ ] Future considerations included
## Final Quality Assurance
- [ ] All validation gates passed
- [ ] Documentation is complete
- [ ] Implementation guidance provided
- [ ] Monitoring and maintenance planned
- [ ] Success criteria defined
==================== END: validation-checklist ====================
==================== START: coordination-checklist ====================
# Agent Coordination Validation Checklist
## Shared Context Management
- [ ] Project context initialized and maintained
- [ ] Agent status tracked and updated
- [ ] Decision history preserved
- [ ] Knowledge base updated continuously
- [ ] Context consistency verified across agents
## Handoff Validation
- [ ] Pre-handoff validation completed
- [ ] Context transfer successful
- [ ] Next agent properly initialized
- [ ] Handoff materials comprehensive
- [ ] Post-handoff validation confirmed
## Collaborative Intelligence
- [ ] Agents maintain shared awareness
- [ ] Cross-agent validation performed
- [ ] Consistent standards applied
- [ ] Quality gates enforced
- [ ] Team coordination maintained
## Validation Integration
- [ ] Dependency validation active
- [ ] Security assessment ongoing
- [ ] Research integration continuous
- [ ] Quality assurance maintained
- [ ] Best practices enforced
## Quality Assurance
- [ ] All outputs validated for quality
- [ ] Standards compliance verified
- [ ] Documentation completeness confirmed
- [ ] Implementation readiness validated
- [ ] Success criteria met
==================== END: coordination-checklist ====================