proagents 1.0.0

package/proagents/team/code-ownership.md

@@ -0,0 +1,306 @@
+# Code Ownership Guide
+
+Define and manage code ownership for effective collaboration.
+
+---
+
+## Overview
+
+Code ownership helps:
+- Ensure quality through accountability
+- Route PRs to right reviewers
+- Maintain consistent standards per area
+- Enable faster decision making
+
+---
+
+## CODEOWNERS File
+
+### Setup
+
+Create `.github/CODEOWNERS` file:
+
+```
+# CODEOWNERS file
+
+# Default owners (required reviewers for all PRs)
+*                       @tech-lead
+
+# Frontend
+/src/components/        @frontend-team
+/src/pages/             @frontend-team
+/src/styles/            @frontend-team @design-team
+
+# Backend API
+/api/                   @backend-team
+/src/services/          @backend-team
+
+# Database
+/migrations/            @backend-team @dba-team
+/prisma/                @backend-team @dba-team
+
+# Infrastructure
+/.github/               @devops-team
+/terraform/             @devops-team
+/docker/                @devops-team
+Dockerfile              @devops-team
+
+# Authentication/Security
+/src/auth/              @security-team @backend-team
+/src/middleware/auth*   @security-team
+
+# Documentation
+*.md                    @docs-team
+/docs/                  @docs-team
+
+# Configuration
+package.json            @tech-lead
+tsconfig.json           @tech-lead
+.env.example            @devops-team
+
+# Tests
+/tests/                 @qa-team
+/__tests__/             @qa-team
+*.test.ts               @qa-team
+*.spec.ts               @qa-team
+
+# Critical paths (multiple approvers)
+/src/payments/          @backend-team @security-team @tech-lead
+```
+
+### Rules
+
+- Later rules override earlier ones
+- Use `@username` or `@org/team`
+- Each owner must approve
+- Empty pattern matches all files
+
+---
+
+## Ownership Responsibilities
+
+### Code Owner Duties
+
+| Responsibility | Description |
+|---------------|-------------|
+| Review PRs | Review all PRs to owned area within SLA |
+| Maintain Quality | Ensure code meets standards |
+| Documentation | Keep docs for owned area current |
+| On-call | Be available for issues in owned area |
+| Mentoring | Help others understand the code |
+
+### Review SLAs
+
+| PR Size | Review Time |
+|---------|-------------|
+| Small (< 100 lines) | 4 hours |
+| Medium (100-500 lines) | 1 business day |
+| Large (> 500 lines) | 2 business days |
+| Critical (security/breaking) | 2 hours |
+
+---
+
+## Ownership Matrix
+
+### By Feature Area
+
+| Area | Primary Owner | Secondary | Escalation |
+|------|---------------|-----------|------------|
+| Authentication | @auth-lead | @backend-team | @security-team |
+| User Management | @user-lead | @backend-team | @tech-lead |
+| Payments | @payment-lead | @backend-team | @finance-team |
+| Dashboard | @frontend-lead | @frontend-team | @tech-lead |
+| API Gateway | @api-lead | @backend-team | @tech-lead |
+| Mobile App | @mobile-lead | @mobile-team | @tech-lead |
+
+### By Service
+
+| Service | Team | Owner | Backup |
+|---------|------|-------|--------|
+| web-frontend | Frontend | @alice | @bob |
+| api-gateway | Backend | @carol | @dave |
+| user-service | Backend | @eve | @frank |
+| payment-service | Backend | @grace | @henry |
+| mobile-app | Mobile | @iris | @jack |
+
+---
+
+## Assigning Ownership
+
+### New Code
+
+When creating new modules:
+
+1. Identify appropriate team/owner
+2. Add to CODEOWNERS file
+3. Document ownership in README
+4. Set up monitoring alerts
+
+```markdown
+<!-- Module README.md -->
+# User Service
+
+## Ownership
+
+| Role | Contact |
+|------|---------|
+| Owner | @user-team |
+| Primary Contact | @alice |
+| Escalation | @tech-lead |
+
+## On-call Rotation
+- Week 1: @alice
+- Week 2: @bob
+- Week 3: @carol
+```
+
+### Transferring Ownership
+
+```markdown
+## Ownership Transfer Checklist
+
+**From:** @current-owner
+**To:** @new-owner
+**Area:** /src/feature/
+
+- [ ] Knowledge transfer sessions completed
+- [ ] Documentation reviewed and updated
+- [ ] Access permissions updated
+- [ ] CODEOWNERS file updated
+- [ ] On-call rotation updated
+- [ ] Alerts/monitoring updated
+- [ ] Team notified
+```
+
+---
+
+## PR Review Process
+
+### Automatic Assignment
+
+GitHub automatically assigns reviewers based on CODEOWNERS:
+
+```yaml
+# .github/workflows/assign-reviewers.yml
+name: Auto Assign Reviewers
+
+on:
+  pull_request:
+    types: [opened, ready_for_review]
+
+jobs:
+  assign:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+
+      - name: Assign reviewers
+        uses: kentaro-m/auto-assign-action@v1.2.4
+        with:
+          configuration-path: '.github/auto-assign.yml'
+```
+
+### Review Requirements
+
+```yaml
+# Branch protection rules
+main:
+  required_reviews: 2
+  require_code_owner_reviews: true
+  dismiss_stale_reviews: true
+  require_review_from_maintainers: true
+```
+
+---
+
+## Conflict Resolution
+
+### When Owners Disagree
+
+1. **Discussion** - Owners discuss in PR comments
+2. **Sync Meeting** - Schedule quick call if needed
+3. **Escalation** - Tech lead makes final decision
+4. **Documentation** - Document decision rationale
+
+### Ownership Disputes
+
+| Scenario | Resolution |
+|----------|------------|
+| Unclear ownership | Tech lead decides |
+| Overlapping areas | Define boundaries, update CODEOWNERS |
+| Abandoned ownership | Reassign with knowledge transfer |
+| New team structure | Update all ownership docs |
+
+---
+
+## Metrics
+
+### Ownership Health
+
+```markdown
+## Code Ownership Report
+
+### Coverage
+- Total files: 1,234
+- Files with owners: 1,200 (97%)
+- Orphaned files: 34 (3%)
+
+### Review Performance (Last 30 Days)
+| Team | Avg Review Time | Reviews Completed |
+|------|-----------------|-------------------|
+| Frontend | 6 hours | 45 |
+| Backend | 8 hours | 62 |
+| Mobile | 12 hours | 23 |
+
+### Areas Needing Attention
+- /src/legacy/ - No owner assigned
+- /src/utils/ - Owner on leave, need backup
+```
+
+---
+
+## Best Practices
+
+1. **Clear Boundaries** - Define ownership precisely
+2. **Backup Owners** - Always have secondary owner
+3. **Regular Review** - Review ownership quarterly
+4. **Documentation** - Keep ownership docs current
+5. **Knowledge Sharing** - Avoid single point of failure
+6. **Responsive** - Meet review SLAs
+7. **Collaborative** - Work with other owners on overlap
+
+---
+
+## Configuration
+
+```yaml
+# proagents.config.yaml
+ownership:
+  enabled: true
+  file: ".github/CODEOWNERS"
+
+  review_sla:
+    small: "4h"
+    medium: "1d"
+    large: "2d"
+    critical: "2h"
+
+  alerts:
+    stale_review: true
+    orphaned_code: true
+    ownership_gaps: true
+
+  reporting:
+    frequency: "weekly"
+    notify: ["tech-lead@company.com"]
+```
+
+---
+
+## Slash Commands
+
+| Command | Description |
+|---------|-------------|
+| `/owner [path]` | Show owner for path |
+| `/ownership-report` | Generate ownership report |
+| `/assign-owner` | Assign ownership |

package/proagents/team/communication-templates.md

@@ -0,0 +1,441 @@
+# Communication Templates
+
+Standard templates for team communication during development.
+
+---
+
+## Feature Development Notifications
+
+### Feature Start Notification
+
+```markdown
+## 🚀 Feature Started
+
+**Feature:** [Feature Name]
+**Branch:** `feature/[branch-name]`
+**Assigned:** @developer
+**Started:** [Date]
+
+### Summary
+[Brief description of the feature]
+
+### Scope
+- [Key deliverable 1]
+- [Key deliverable 2]
+- [Key deliverable 3]
+
+### Areas Affected
+- Files: [list or "TBD after analysis"]
+- Modules: [list affected modules]
+- APIs: [list affected APIs]
+
+### Dependencies
+- Depends on: [other features/PRs]
+- Blocks: [features waiting on this]
+
+### Timeline
+- Analysis: [date]
+- Implementation: [date range]
+- Review: [date]
+- Target completion: [date]
+
+### Notes
+[Any additional context or considerations]
+
+---
+cc: @team-lead @relevant-stakeholders
+```
+
+### Feature Progress Update
+
+```markdown
+## 📊 Feature Progress Update
+
+**Feature:** [Feature Name]
+**Branch:** `feature/[branch-name]`
+**Date:** [Date]
+
+### Current Status
+- **Phase:** [Implementation / Testing / Review]
+- **Progress:** [X]%
+- **On Track:** ✅ Yes / ⚠️ At Risk / ❌ Delayed
+
+### Completed
+- [x] [Completed item 1]
+- [x] [Completed item 2]
+
+### In Progress
+- [ ] [Current work item]
+
+### Remaining
+- [ ] [Remaining item 1]
+- [ ] [Remaining item 2]
+
+### Blockers
+- [Blocker description, if any]
+- Waiting on: @person
+
+### Changes from Plan
+- [Any scope changes or pivots]
+
+### Next Steps
+1. [Next step 1]
+2. [Next step 2]
+
+---
+cc: @team-lead
+```
+
+### Feature Complete Notification
+
+```markdown
+## ✅ Feature Complete
+
+**Feature:** [Feature Name]
+**Branch:** `feature/[branch-name]`
+**PR:** #[PR number]
+**Completed:** [Date]
+
+### Summary
+[Brief summary of what was delivered]
+
+### What Was Built
+- [Deliverable 1]
+- [Deliverable 2]
+- [Deliverable 3]
+
+### Files Changed
+- Created: [X] files
+- Modified: [X] files
+- Deleted: [X] files
+
+### Test Coverage
+- Unit tests: [X] added
+- Integration tests: [X] added
+- Coverage: [X]%
+
+### Documentation
+- [Link to docs if applicable]
+
+### Ready for Review
+- [ ] Code review: @reviewer
+- [ ] Design review: @designer (if applicable)
+- [ ] QA review: @qa (if applicable)
+
+### Deployment Notes
+- [Any deployment considerations]
+- [Environment variables needed]
+
+---
+cc: @team-lead @reviewers
+```
+
+---
+
+## Code Review Communication
+
+### Review Request
+
+```markdown
+## 👀 Review Request
+
+**PR:** #[PR number]
+**Feature:** [Feature Name]
+**Author:** @developer
+
+### Review Type
+- [ ] Full review (new feature)
+- [ ] Quick review (bug fix)
+- [ ] Architecture review
+- [ ] Security review
+
+### Changes Summary
+[Brief description of changes]
+
+### Key Areas to Review
+1. [Specific area 1] - [why it needs attention]
+2. [Specific area 2] - [why it needs attention]
+
+### Testing Done
+- [x] Unit tests pass
+- [x] Manual testing completed
+- [x] [Other testing]
+
+### Review Deadline
+[Date] - [Reason if urgent]
+
+### Context
+[Any additional context reviewers need]
+
+---
+Requested reviewers: @reviewer1 @reviewer2
+```
+
+### Review Complete
+
+```markdown
+## ✅ Review Complete
+
+**PR:** #[PR number]
+**Reviewer:** @reviewer
+
+### Decision
+- ✅ Approved
+- 🔄 Approved with suggestions
+- ⚠️ Request changes
+
+### Summary
+[Brief summary of review findings]
+
+### Comments
+- **Blocking:** [X] items
+- **Suggestions:** [X] items
+- **Praise:** [X] items
+
+### Key Feedback
+1. [Most important feedback point]
+2. [Second important point]
+
+### Next Steps
+- [ ] [Required action if changes requested]
+
+---
+cc: @developer
+```
+
+---
+
+## Bug Reports
+
+### Bug Report Template
+
+```markdown
+## 🐛 Bug Report
+
+**Title:** [Brief description]
+**Severity:** 🔴 Critical / 🟠 High / 🟡 Medium / 🟢 Low
+**Found in:** [Environment/Version]
+**Reported by:** @reporter
+**Date:** [Date]
+
+### Description
+[Detailed description of the bug]
+
+### Steps to Reproduce
+1. [Step 1]
+2. [Step 2]
+3. [Step 3]
+
+### Expected Behavior
+[What should happen]
+
+### Actual Behavior
+[What actually happens]
+
+### Screenshots/Videos
+[Attach if applicable]
+
+### Environment
+- Browser/Device: [details]
+- OS: [details]
+- Version: [app version]
+
+### Logs
+```
+[Relevant error logs]
+```
+
+### Impact
+- Users affected: [estimate]
+- Workaround available: Yes/No
+
+### Related
+- Related issues: #[issue numbers]
+- Related PRs: #[PR numbers]
+
+---
+Assigned: @developer
+Priority: [Priority level]
+```
+
+### Bug Fix Notification
+
+```markdown
+## 🔧 Bug Fixed
+
+**Bug:** #[Issue number] - [Title]
+**PR:** #[PR number]
+**Fixed by:** @developer
+**Fixed in:** [Version/Branch]
+
+### Root Cause
+[Explanation of why the bug occurred]
+
+### Solution
+[Brief explanation of the fix]
+
+### Files Changed
+- [File 1]: [What changed]
+- [File 2]: [What changed]
+
+### Testing
+- [x] Bug no longer reproducible
+- [x] Related functionality tested
+- [x] Regression tests added
+
+### Deployment
+- [ ] Deployed to staging
+- [ ] Ready for production
+
+### Verification Steps
+1. [How to verify the fix]
+2. [Step 2]
+
+---
+cc: @reporter @qa
+```
+
+---
+
+## Deployment Communication
+
+### Deployment Notification
+
+```markdown
+## 🚢 Deployment Notification
+
+**Environment:** [Staging / Production]
+**Version:** [Version number]
+**Date/Time:** [Date and time]
+**Deployed by:** @deployer
+
+### Changes Included
+- [Feature 1] (#PR)
+- [Feature 2] (#PR)
+- [Bug fix 1] (#PR)
+
+### Deployment Checklist
+- [x] All tests passing
+- [x] Code review approved
+- [x] Staging tested
+- [x] Rollback plan ready
+
+### Breaking Changes
+- [List any breaking changes]
+- Migration required: Yes/No
+
+### Action Required
+- [ ] [Any manual steps needed]
+- [ ] [Configuration changes]
+
+### Monitoring
+- Dashboard: [link]
+- Alerts: [configured]
+
+### Rollback Plan
+[How to rollback if issues found]
+
+---
+cc: @team @on-call
+```
+
+### Incident Notification
+
+```markdown
+## 🚨 Incident Alert
+
+**Severity:** 🔴 Critical / 🟠 High / 🟡 Medium
+**Status:** Investigating / Identified / Monitoring / Resolved
+**Started:** [Time]
+**Duration:** [Ongoing / X minutes]
+
+### Impact
+- Affected: [What's affected]
+- Users impacted: [Estimate]
+- Error rate: [X]%
+
+### Summary
+[Brief description of the incident]
+
+### Timeline
+- [Time]: [Event]
+- [Time]: [Event]
+- [Time]: [Event]
+
+### Current Actions
+- [Action being taken]
+- [Action being taken]
+
+### Incident Commander
+@person
+
+### Updates
+Next update in: [X] minutes
+
+---
+cc: @on-call @leadership
+```
+
+---
+
+## Handoff Communication
+
+### Work Handoff
+
+```markdown
+## 🔄 Work Handoff
+
+**From:** @current-developer
+**To:** @next-developer
+**Feature/Task:** [Name]
+**Date:** [Date]
+
+### Current Status
+- Branch: `[branch-name]`
+- Phase: [Phase]
+- Progress: [X]%
+
+### What's Done
+- [x] [Completed item 1]
+- [x] [Completed item 2]
+
+### What's Remaining
+- [ ] [Remaining item 1]
+- [ ] [Remaining item 2]
+
+### Key Context
+- [Important decision made and why]
+- [Known issue to be aware of]
+- [Design consideration]
+
+### Files to Focus On
+- `[file1.ts]` - [what's there]
+- `[file2.ts]` - [what's there]
+
+### Blockers/Dependencies
+- [Any blockers]
+- Waiting on: [items/people]
+
+### Resources
+- Design: [link]
+- Requirements: [link]
+- Related PRs: #[numbers]
+
+### Questions?
+[Best way to reach for questions]
+
+---
+cc: @team-lead
+```
+
+---
+
+## Slash Commands
+
+| Command | Description |
+|---------|-------------|
+| `/notify-start` | Send feature start notification |
+| `/notify-update` | Send progress update |
+| `/notify-complete` | Send completion notification |
+| `/notify-deploy` | Send deployment notification |
+| `/handoff` | Generate handoff document |