amazingteam 3.0.0

package/.ai-team/memory/qa/validation_notes.md

@@ -0,0 +1,110 @@
+# QA Memory - Validation Notes
+
+This file records validation observations and lessons learned by the QA agent.
+
+---
+
+## Validation Process
+
+### For Features
+
+1. **Requirements Review**
+   - Verify acceptance criteria are testable
+   - Identify edge cases
+   - Note dependencies
+
+2. **Test Design**
+   - Design test cases for each criterion
+   - Include happy path and error paths
+   - Consider boundary conditions
+
+3. **Execution**
+   - Run all relevant tests
+   - Verify behavior matches expectations
+   - Document any deviations
+
+4. **Reporting**
+   - Summarize results
+   - Report issues found
+   - Recommend sign-off or revision
+
+### For Bug Fixes
+
+1. **Reproduction Verification**
+   - Verify the reported issue exists
+   - Confirm fix addresses root cause
+   - Check for similar issues
+
+2. **Regression Testing**
+   - Run related tests
+   - Check adjacent functionality
+   - Verify no new issues
+
+3. **Documentation**
+   - Update test coverage
+   - Add regression tests
+   - Document lessons learned
+
+---
+
+## Validation Results Log
+
+### [Date] - [Issue/Feature]
+
+**Type**: [Feature/Bug Fix/Refactor]
+
+**Items Tested**: [List of items]
+
+**Results**: [Summary of results]
+
+**Issues Found**: [List any issues]
+
+**Recommendation**: [Approve/Request Changes]
+
+---
+
+## Common Validation Issues
+
+### False Positives
+
+| Issue | Cause | Mitigation |
+|-------|-------|------------|
+| Flaky test | Timing/state | Add retry/stabilize |
+| Environment config | Different settings | Use consistent config |
+
+### False Negatives
+
+| Issue | Cause | Mitigation |
+|-------|-------|------------|
+| Missing test case | Incomplete coverage | Add test |
+| Wrong assertion | Misunderstood requirement | Clarify requirement |
+
+---
+
+## Validation Checklist
+
+### Pre-Validation
+
+- [ ] Requirements understood
+- [ ] Test cases designed
+- [ ] Environment prepared
+
+### During Validation
+
+- [ ] Tests executed
+- [ ] Results recorded
+- [ ] Edge cases explored
+
+### Post-Validation
+
+- [ ] Results summarized
+- [ ] Issues documented
+- [ ] Recommendation provided
+
+---
+
+## Notes
+
+- Record validation patterns that work well
+- Document common issues and solutions
+- Track validation efficiency metrics

package/.ai-team/memory/reviewer/quality_rules.md

@@ -0,0 +1,105 @@
+# Reviewer Memory - Quality Rules
+
+This file defines code quality rules and standards enforced by the Reviewer agent.
+
+---
+
+## Code Quality Standards
+
+### Naming Conventions
+
+| Element | Convention | Example |
+|---------|------------|---------|
+| Variables | camelCase | `userName` |
+| Constants | SCREAMING_SNAKE_CASE | `MAX_RETRY_COUNT` |
+| Functions | camelCase | `getUserById` |
+| Classes | PascalCase | `UserService` |
+| Interfaces | PascalCase | `IUserRepository` |
+| Types | PascalCase | `UserRole` |
+| Files | kebab-case | `user-service.ts` |
+
+### Code Structure
+
+| Rule | Rationale |
+|------|-----------|
+| Max function length: 30 lines | Readability |
+| Max nesting: 3 levels | Complexity management |
+| One responsibility per function | Maintainability |
+| No magic numbers | Clarity |
+
+### TypeScript Rules
+
+| Rule | Standard |
+|------|----------|
+| Explicit return types | Required for public functions |
+| No `any` type | Use specific types |
+| Strict null checks | Enabled |
+| No unused variables | Error |
+
+---
+
+## Quality Metrics
+
+### Maintainability Index
+
+| Score | Rating | Action |
+|-------|--------|--------|
+| 0-9 | Low | Refactor required |
+| 10-19 | Medium | Consider refactoring |
+| 20+ | High | Good |
+
+### Complexity Thresholds
+
+| Metric | Warning | Error |
+|--------|---------|-------|
+| Cyclomatic Complexity | 10 | 20 |
+| Cognitive Complexity | 15 | 25 |
+| Lines of Code (per function) | 20 | 30 |
+
+---
+
+## Forbidden Patterns
+
+| Pattern | Why Forbidden | Alternative |
+|---------|---------------|-------------|
+| `any` type | Loses type safety | Use specific type or `unknown` |
+| `console.log` in production | Performance, security | Use logger |
+| Deep nesting | Hard to read | Early returns, extract methods |
+| Magic numbers | Unclear meaning | Named constants |
+| Uncaught promises | Silent failures | Try/catch or .catch() |
+
+---
+
+## Code Smells
+
+### Detect and Address
+
+| Smell | Detection | Fix |
+|-------|-----------|-----|
+| Long method | > 30 lines | Extract methods |
+| Large class | > 200 lines | Split responsibilities |
+| Duplicate code | Similar blocks | Extract common code |
+| Dead code | Unused | Remove |
+| Feature envy | Using other's data | Move method |
+
+---
+
+## Security Rules
+
+### Must Check
+
+| Area | Rule |
+|------|------|
+| Input | Validate and sanitize |
+| Output | Encode for context |
+| Auth | Verify on every request |
+| Secrets | Never in code |
+| Logs | No sensitive data |
+
+---
+
+## Notes
+
+- Update when new patterns emerge
+- Document exceptions to rules
+- Track effectiveness of rules

package/.ai-team/memory/reviewer/recurring_risks.md

@@ -0,0 +1,109 @@
+# Reviewer Memory - Recurring Risks
+
+This file tracks recurring code risks and patterns that frequently cause issues.
+
+---
+
+## Risk Categories
+
+### High Risk Patterns
+
+| Risk | Frequency | Impact | Mitigation |
+|------|-----------|--------|------------|
+| Missing null checks | High | Runtime error | Use optional chaining |
+| Unhandled promises | Medium | Silent failure | Async/await with try/catch |
+| Hardcoded values | Medium | Maintenance | Use configuration |
+| Missing tests | High | Regression | Require tests for changes |
+
+### Medium Risk Patterns
+
+| Risk | Frequency | Impact | Mitigation |
+|------|-----------|--------|------------|
+| Complex conditionals | Medium | Bugs | Simplify or document |
+| Large functions | Medium | Maintainability | Extract methods |
+| Deep nesting | Low | Readability | Early returns |
+| Missing error handling | Medium | Poor UX | Handle all cases |
+
+---
+
+## Risk Detection Patterns
+
+### Security Risks
+
+```typescript
+// Risk: SQL Injection
+const query = `SELECT * FROM users WHERE id = ${userId}`;
+// Fix: Use parameterized queries
+
+// Risk: XSS
+element.innerHTML = userInput;
+// Fix: Use textContent or sanitize
+
+// Risk: Hardcoded secrets
+const apiKey = "sk-xxxxx";
+// Fix: Use environment variables
+```
+
+### Performance Risks
+
+```typescript
+// Risk: N+1 queries
+for (const user of users) {
+  const posts = await getPosts(user.id);
+}
+// Fix: Batch query
+
+// Risk: Memory leak
+const listener = () => {};
+element.addEventListener('click', listener);
+// Fix: Remove listener when done
+```
+
+### Correctness Risks
+
+```typescript
+// Risk: Race condition
+let value = 0;
+async function increment() {
+  value++;
+}
+// Fix: Use atomic operations or locks
+
+// Risk: Stale closure
+for (var i = 0; i < 3; i++) {
+  setTimeout(() => console.log(i), 100);
+}
+// Fix: Use let or capture value
+```
+
+---
+
+## Risk Log
+
+### [Date] - [Risk Description]
+
+**Pattern**: [Code pattern that indicates risk]
+
+**Impact**: [What could go wrong]
+
+**Frequency**: [How often seen]
+
+**Mitigation**: [How to prevent/fix]
+
+---
+
+## Risk Assessment Matrix
+
+| Likelihood \ Impact | Low | Medium | High |
+|---------------------|-----|--------|------|
+| High | Monitor | Address | Critical |
+| Medium | Accept | Monitor | Address |
+| Low | Accept | Accept | Monitor |
+
+---
+
+## Notes
+
+- Update when new recurring risks are identified
+- Track effectiveness of mitigations
+- Share patterns with Developer agent for prevention

package/.ai-team/memory/reviewer/review_notes.md

@@ -0,0 +1,124 @@
+# Reviewer Memory - Review Notes
+
+This file stores code review observations and patterns identified by the Reviewer agent.
+
+---
+
+## Review Process
+
+### Step 1: Understand Context
+
+1. Read PR description
+2. Review related issue
+3. Understand the change purpose
+4. Note acceptance criteria
+
+### Step 2: Examine Changes
+
+1. Review each file systematically
+2. Check coding standards
+3. Identify potential issues
+4. Note positive aspects
+
+### Step 3: Provide Feedback
+
+1. Write clear, constructive comments
+2. Explain reasoning
+3. Provide code examples when helpful
+4. Prioritize by severity
+
+### Step 4: Summarize
+
+1. Overall assessment
+2. Required changes
+3. Optional suggestions
+4. Merge recommendation
+
+---
+
+## Review Categories
+
+### 🔴 Critical (Must Fix)
+
+- Security vulnerabilities
+- Data loss risks
+- Breaking bugs
+- Performance critical issues
+
+### 🟡 Important (Should Fix)
+
+- Potential bugs
+- Maintainability concerns
+- Missing error handling
+- Incomplete tests
+
+### 🟢 Suggestions (Nice to Have)
+
+- Code style improvements
+- Documentation enhancements
+- Minor optimizations
+
+### 💬 Questions
+
+- Clarification needed
+- Design discussion points
+- Alternative approaches
+
+---
+
+## Review Checklist
+
+### Code Quality
+
+- [ ] Code is readable
+- [ ] Naming is clear
+- [ ] Functions are focused
+- [ ] No duplication
+- [ ] Error handling is appropriate
+
+### Security
+
+- [ ] No sensitive data exposed
+- [ ] Input validation present
+- [ ] Authentication/authorization correct
+- [ ] No injection vulnerabilities
+
+### Performance
+
+- [ ] No obvious bottlenecks
+- [ ] Resources properly managed
+- [ ] Caching used appropriately
+
+### Testing
+
+- [ ] Tests cover new code
+- [ ] Edge cases tested
+- [ ] Tests are meaningful
+
+### Documentation
+
+- [ ] Public APIs documented
+- [ ] Complex logic explained
+- [ ] README updated if needed
+
+---
+
+## Review Log
+
+### [Date] - PR #[number]
+
+**Summary**: [Brief description]
+
+**Strengths**: [What was done well]
+
+**Concerns**: [Issues found]
+
+**Verdict**: [Approve/Request Changes]
+
+---
+
+## Notes
+
+- Track patterns in code issues
+- Note areas that frequently need attention
+- Record effective review techniques

package/.ai-team/memory/triage/classification_heuristics.md

@@ -0,0 +1,82 @@
+# Triage Memory - Classification Heuristics
+
+This file stores issue classification patterns and heuristics.
+
+---
+
+## Classification Quick Reference
+
+### Issue Type Indicators
+
+| Type | Indicators |
+|------|------------|
+| bug | Error messages, crashes, unexpected behavior |
+| feature | New capability request, "would like to" |
+| enhancement | Improvement to existing, "better", "faster" |
+| docs | Missing/outdated documentation |
+| tech | Technical debt, infrastructure |
+| question | "How do I", clarification needed |
+
+### Priority Indicators
+
+| Priority | Indicators |
+|----------|------------|
+| critical | Production down, security issue, data loss |
+| high | Major feature broken, many users affected |
+| medium | Standard issue, workaround exists |
+| low | Minor issue, niche case |
+
+---
+
+## Debugging Heuristics
+
+### Error Pattern → Likely Cause
+
+| Error Pattern | Likely Cause | Investigation |
+|---------------|--------------|---------------|
+| Null reference | Missing null check | Check data flow |
+| Timeout | Network/slow operation | Check async code |
+| Permission denied | Access control | Check auth/config |
+| Type error | Type mismatch | Check types/interfaces |
+| Not found | Missing resource | Check paths/IDs |
+
+### Recent Change Check
+
+1. Check commits in last 24-48 hours
+2. Look for changes in affected modules
+3. Check dependency updates
+4. Review config changes
+
+---
+
+## Classification Log
+
+### [Date] - Issue #[number]
+
+**Symptoms**: [What was reported]
+
+**Classification**: [Type/Priority]
+
+**Rationale**: [Why classified this way]
+
+**Outcome**: [Resolution or handoff]
+
+---
+
+## Common Issue Patterns
+
+### Pattern: [Pattern Name]
+
+**Symptoms**: [Typical symptoms]
+
+**Root Cause**: [Typical cause]
+
+**Quick Fix**: [Typical fix]
+
+---
+
+## Notes
+
+- Update with new patterns as discovered
+- Document false positives
+- Track classification accuracy

package/.ai-team/memory/triage/debug_notes.md

@@ -0,0 +1,87 @@
+# Triage Memory - Debug Notes
+
+This file stores debugging observations and investigation patterns.
+
+---
+
+## Investigation Checklist
+
+### Initial Assessment
+
+- [ ] Error message captured
+- [ ] Stack trace available
+- [ ] Reproduction steps documented
+- [ ] Environment noted
+- [ ] Recent changes reviewed
+
+### Deep Investigation
+
+- [ ] Affected files identified
+- [ ] Root cause hypothesis formed
+- [ ] Similar issues searched
+- [ ] Related code reviewed
+- [ ] Tests checked
+
+---
+
+## Debug Log
+
+### [Date] - Issue #[number]
+
+**Error**: [Error message]
+
+**Context**: [When/where it occurs]
+
+**Investigation**: [Steps taken]
+
+**Findings**: [What was found]
+
+**Root Cause**: [Final determination]
+
+**Resolution**: [How fixed]
+
+---
+
+## Recurring Issues
+
+### Issue Pattern: [Pattern Name]
+
+**Frequency**: [How often it occurs]
+
+**Symptoms**: [Typical presentation]
+
+**Root Cause**: [Underlying cause]
+
+**Fix**: [Standard fix]
+
+**Prevention**: [How to prevent]
+
+---
+
+## Environment-Specific Issues
+
+### Development
+
+| Issue | Cause | Resolution |
+|-------|-------|------------|
+| | | |
+
+### Staging
+
+| Issue | Cause | Resolution |
+|-------|-------|------------|
+| | | |
+
+### Production
+
+| Issue | Cause | Resolution |
+|-------|-------|------------|
+| | | |
+
+---
+
+## Notes
+
+- Document all investigations, even unsuccessful ones
+- Track patterns that lead to quick resolutions
+- Note environment-specific behaviors