claude-mpm 4.1.3__tar.gz → 4.1.5__tar.gz

claude_mpm-4.1.5/BUILD_NUMBER

@@ -0,0 +1 @@
+301

{claude_mpm-4.1.3 → claude_mpm-4.1.5}/CLAUDE.md

@@ -292,47 +292,10 @@ See [docs/reference/DEPLOY.md](docs/reference/DEPLOY.md) for the complete deploy
 - Creating GitHub releases
 - Post-deployment verification
 
-## TSK-0053 Refactoring Achievements
-
-The service layer architecture refactoring delivered:
-
-### Technical Achievements
-- **Service-Oriented Architecture**: Complete redesign with five specialized service domains
-- **Interface-Based Contracts**: All major services implement explicit interfaces
-- **Dependency Injection**: Service container with automatic dependency resolution
-- **50-80% Performance Improvement**: Through lazy loading and intelligent caching
-- **Enhanced Security**: Comprehensive input validation and sanitization framework
-- **Backward Compatibility**: Lazy imports maintain existing import paths
-
-### Quality Improvements
-- **Better Testability**: Interface-based architecture enables easy mocking and testing
-- **Improved Maintainability**: Clear separation of concerns and service boundaries
-- **Enhanced Reliability**: Comprehensive testing with 85%+ coverage target
-- **Developer Experience**: Rich documentation and migration guides
-
-### Future-Proofing
-- **Scalability**: Service-oriented design supports future growth
-- **Extensibility**: Plugin architecture through interfaces and hooks
-- **Modularity**: Clear service boundaries enable independent development
-- **Performance**: Intelligent caching and resource optimization foundations
-
-## v4.0.25 Updates
-
-### Version Tracking System Enhancement
-- **BUILD_NUMBER file**: Replaces BUILDVERSION for cleaner naming
-- **Dual tracking**: VERSION (semantic) + BUILD_NUMBER (serial)
-- **Three display formats**: Development, UI/Logging, and PyPI Release
-- **Automatic incrementing**: Git hooks increment build numbers for code changes
-
-### New Features
-- **cleanup-memory command**: New CLI command to manage Claude conversation history
-- **Memory management**: Addresses 2GB+ memory usage from large .claude.json files
-- **Archive system**: Safely archive old conversations while keeping recent ones active
-
 ## Important Notes
 
 - This file (CLAUDE.md) contains ONLY development guidelines for this project
 - Framework features and usage are documented in the framework itself
 - Claude Code automatically reads this file - keep it focused on development tasks
 - Do not include end-user documentation or framework features here
-- The refactored architecture enables faster development and better code quality
+- The refactored architecture enables faster development and better code quality

{claude_mpm-4.1.3 → claude_mpm-4.1.5}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: claude-mpm
-Version: 4.1.3
+Version: 4.1.5
 Summary: Claude Multi-Agent Project Manager - Orchestrate Claude with agent delegation and ticket tracking
 Author-email: Bob Matsuoka <bob@matsuoka.com>
 Maintainer: Claude MPM Team

claude_mpm-4.1.5/VERSION

@@ -0,0 +1 @@
+4.1.5

{claude_mpm-4.1.3 → claude_mpm-4.1.5}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "claude-mpm"
-version = "4.1.3"
+version = "4.1.5"
 description = "Claude Multi-Agent Project Manager - Orchestrate Claude with agent delegation and ticket tracking"
 readme = "README.md"
 requires-python = ">=3.8"
@@ -240,7 +240,7 @@ ignore-imports = false
 
 [tool.commitizen]
 name = "cz_conventional_commits"
-version = "4.1.3"
+version = "4.1.5"
 version_files = [
     "VERSION",
     "src/claude_mpm/VERSION",

claude_mpm-4.1.5/src/claude_mpm/VERSION

@@ -0,0 +1 @@
+4.1.5

{claude_mpm-4.1.3 → claude_mpm-4.1.5}/src/claude_mpm/agents/BASE_AGENT_TEMPLATE.md

@@ -122,25 +122,22 @@ End every response with this structured data:
 
 ## Memory Protection Protocol
 
-### Content Threshold System
-- **Single File Limit**: 20KB or 200 lines triggers mandatory summarization
-- **Critical Files**: Files >100KB ALWAYS summarized, never loaded fully
-- **Cumulative Threshold**: 50KB total or 3 files triggers batch summarization
-- **Implementation Chunking**: Process large files in <100 line segments
-
-### Memory Management Rules
-1. **Check Before Reading**: Always verify file size with LS before Read
-2. **Sequential Processing**: Process ONE file at a time, never parallel
-3. **Pattern Extraction**: Extract patterns, not full implementations
-4. **Targeted Reads**: Use Grep for finding specific content
-5. **Maximum Files**: Never work with more than 3-5 files simultaneously
-
-### Forbidden Memory Practices
-❌ **NEVER** read entire large codebases
-❌ **NEVER** load multiple files in parallel
-❌ **NEVER** retain file contents after extraction
-❌ **NEVER** load files >1MB into memory
-❌ **NEVER** accumulate content across multiple file reads
+### File Processing Limits
+- **20KB/200 lines**: Triggers summarization
+- **100KB+**: Use summarizer, never read fully
+- **1MB+**: Skip entirely
+- **Cumulative**: 50KB or 3 files = batch summarize
+
+### Processing Rules
+1. Check size first: `ls -lh` before reading
+2. Process sequentially: One file at a time
+3. Extract patterns, discard content immediately
+4. Use grep for targeted searches
+5. Maximum 3-5 files per operation
+
+### Forbidden Practices
+❌ Never read files >1MB or process in parallel
+❌ Never retain content after extraction
 
 ## TodoWrite Protocol
 

{claude_mpm-4.1.3 → claude_mpm-4.1.5}/src/claude_mpm/agents/MEMORY.md

@@ -46,52 +46,24 @@ This system provides **Static Memory** support where you (PM) directly manage me
 - Maintain readability and structure
 - Respect 80KB file size limit
 
-### Agent Memory Routing Matrix
-
-**Engineering Agent Memory**:
-- Implementation patterns and anti-patterns
-- Code architecture and design decisions
-- Performance optimizations and bottlenecks
-- Technology stack choices and constraints
-
-**Research Agent Memory**:
-- Analysis findings and investigation results
-- Domain knowledge and business logic
-- Architectural decisions and trade-offs
-- Codebase patterns and conventions
-
-**QA Agent Memory**:
-- Testing strategies and coverage requirements
-- Quality standards and acceptance criteria
-- Bug patterns and regression risks
-- Test infrastructure and tooling
-
-**Security Agent Memory**:
-- Security patterns and vulnerabilities
-- Threat models and attack vectors
-- Compliance requirements and policies
-- Authentication/authorization patterns
-
-**Documentation Agent Memory**:
-- Writing standards and style guides
-- Content organization patterns
-- API documentation conventions
-- User guide templates
-
-**Data Engineer Agent Memory**:
-- Data pipeline patterns and ETL strategies
-- Schema designs and migrations
-- Performance tuning techniques
-- Data quality requirements
-
-**Ops Agent Memory**:
-- Deployment patterns and rollback procedures
-- Infrastructure configurations
-- Monitoring and alerting strategies
-- CI/CD pipeline requirements
-
-**Version Control Agent Memory**:
-- Branching strategies and conventions
-- Commit message standards
-- Code review processes
-- Release management patterns
+### Dynamic Agent Memory Routing
+
+**Memory routing is now dynamically configured**:
+- Each agent's memory categories are defined in their JSON template files
+- Located in: `src/claude_mpm/agents/templates/{agent_name}_agent.json`
+- The `memory_routing_rules` field in each template specifies what types of knowledge that agent should remember
+
+**How Dynamic Routing Works**:
+1. When a memory update is triggered, the PM reads the agent's template
+2. The `memory_routing_rules` array defines categories of information for that agent
+3. Memory is automatically routed to the appropriate agent based on these rules
+4. This allows for flexible, maintainable memory categorization
+
+**Viewing Agent Memory Rules**:
+To see what an agent remembers, check their template file's `memory_routing_rules` field.
+For example:
+- Engineering agents remember: implementation patterns, architecture decisions, performance optimizations
+- Research agents remember: analysis findings, domain knowledge, codebase patterns
+- QA agents remember: testing strategies, quality standards, bug patterns
+- And so on, as defined in each agent's template
+

claude_mpm-4.1.5/src/claude_mpm/agents/templates/OPTIMIZATION_REPORT.md

@@ -0,0 +1,156 @@
+# Agent Template Optimization Report
+## Date: 2025-08-25
+
+## Executive Summary
+
+Successfully optimized agent templates to reduce verbosity while maintaining functionality. Achieved **75% average size reduction** for targeted agents through consolidation of duplicate content, removal of code examples, and leveraging base template inheritance.
+
+## Size Reduction Achievements
+
+### Priority 1 Agents (Completed Previously)
+| Agent | Before | After | Reduction | Status |
+|-------|--------|-------|-----------|---------|
+| Engineer | 22KB | 5.6KB | **74.5%** | ✅ Optimized |
+| QA | 35KB | 8.5KB | **75.7%** | ✅ Optimized |
+| Documentation | 20KB | 5.5KB | **72.5%** | ✅ Optimized |
+| Ops | 25KB | 6.5KB | **74.0%** | ✅ Optimized |
+| Data Engineer | 19KB | 4.9KB | **74.2%** | ✅ Optimized |
+
+### Priority 2 Agents (Completed Now)
+| Agent | Before | After | Reduction | Status |
+|-------|--------|-------|-----------|---------|
+| API QA | 19KB | 5.4KB | **71.6%** | ✅ Optimized |
+| Web QA | 31KB | 5.9KB | **81.0%** | ✅ Optimized |
+| Project Organizer | 17KB | 5.3KB | **68.8%** | ✅ Optimized |
+| Research | 7.6KB | 7.6KB | **0%** | ✅ Already optimal |
+
+### Agents with Separate Instructions (Working Correctly)
+| Agent | JSON Size | MD Size | Status |
+|-------|-----------|---------|---------|
+| Agent Manager | 628B | 9.5KB | ✅ Uses agent-manager.md |
+| Vercel Ops | 7.7KB | 24KB | ✅ Uses vercel_ops_instructions.md |
+
+### Large Agents (Need Future Attention)
+| Agent | Current Size | Notes |
+|-------|--------------|-------|
+| Web UI | 34KB | Complex UI requirements, needs careful optimization |
+| ImageMagick | 17KB | Specialized commands, difficult to reduce |
+| Version Control | 14KB | Git operations, could be optimized |
+| Security | 14KB | Critical instructions, needs careful review |
+| Memory Manager | 12KB | Core system agent, moderate verbosity |
+| Ticketing | 11KB | Could be optimized further |
+| Refactoring Engineer | 11KB | Could leverage engineer base more |
+
+## Key Improvements Made
+
+### 1. Base Template Inheritance
+- All optimized agents now properly inherit from base templates
+- Removed duplicate memory management sections
+- Eliminated redundant todo patterns
+- Consolidated common protocols
+
+### 2. Content Consolidation
+- **Removed verbose code examples** (reduced 60-70% of content)
+- **Consolidated duplicate patterns** into concise lists
+- **Streamlined memory categories** to essential items only
+- **Simplified todo patterns** to representative examples
+
+### 3. Structure Standardization
+- Consistent section ordering across all agents
+- Clear inheritance declarations
+- Focused expertise statements
+- Concise protocol descriptions
+
+### 4. Maintained Functionality
+- All critical instructions preserved
+- Domain expertise intact
+- Tool requirements unchanged
+- Testing criteria maintained
+
+## Total Impact
+
+### Overall Statistics
+- **Total size reduction**: ~140KB across optimized agents
+- **Average reduction**: 75% for priority agents
+- **Smallest optimized agent**: 4.6KB (Code Analyzer)
+- **Largest remaining agent**: 34KB (Web UI)
+
+### Memory Efficiency
+- Reduced token usage for agent loading
+- Faster agent initialization
+- Lower memory footprint during execution
+- Better context window utilization
+
+## Recommendations for Future Work
+
+### High Priority
+1. **Web UI Agent (34KB)**: Needs major refactoring
+   - Split into base UI patterns and specific implementations
+   - Remove duplicate React/Vue/Angular examples
+   - Consolidate component patterns
+
+2. **ImageMagick Agent (17KB)**: Command reference optimization
+   - Create command lookup system instead of inline examples
+   - Group similar operations
+   - Reference external command documentation
+
+3. **Version Control Agent (14KB)**: Git operations consolidation
+   - Combine similar git workflows
+   - Remove duplicate branch strategies
+   - Streamline conflict resolution patterns
+
+### Medium Priority
+1. **Security Agent (14KB)**: Careful optimization needed
+   - Preserve all security checks
+   - Consolidate similar vulnerability patterns
+   - Reference OWASP guidelines externally
+
+2. **Memory Manager (12KB)**: System agent optimization
+   - Core functionality must remain intact
+   - Could externalize some examples
+   - Streamline command descriptions
+
+### Low Priority
+1. **Ticketing Agent (11KB)**: Minor optimization possible
+2. **Refactoring Engineer (11KB)**: Could better leverage engineer base
+
+## Best Practices Established
+
+### For Future Agent Development
+1. **Always inherit from base templates** (BASE_*.md files)
+2. **Avoid inline code examples** - use concise descriptions
+3. **Limit instructions to 5-7KB** for standard agents
+4. **Use external files** for extensive documentation
+5. **Focus on unique capabilities** not common patterns
+
+### Template Structure Guidelines
+```markdown
+# Agent Name
+
+**Inherits from**: BASE_TYPE_AGENT.md
+**Focus**: [Specific expertise in one line]
+
+## Core Expertise
+[2-3 lines maximum]
+
+## [Domain]-Specific Protocol
+[Concise bullet points]
+
+## [Agent]-Specific Todo Patterns
+[5-10 examples maximum]
+
+## Quality Standards
+[Key points only]
+```
+
+## Validation Completed
+
+- ✅ All agents have valid JSON structure
+- ✅ Required fields present in all templates
+- ✅ Instructions reference correct base templates
+- ✅ No critical functionality removed
+- ✅ Agent discovery still works correctly
+
+## Conclusion
+
+Successfully achieved **75% average reduction** in agent template verbosity while maintaining all critical functionality. The optimization improves memory efficiency, reduces token usage, and provides faster agent initialization. Future work should focus on the remaining large agents (Web UI, ImageMagick, Version Control) using the established patterns and best practices.

claude_mpm-4.1.5/src/claude_mpm/agents/templates/api_qa.json

@@ -0,0 +1,171 @@
+{
+  "schema_version": "1.2.0",
+  "agent_id": "api-qa-agent",
+  "agent_version": "1.2.0",
+  "agent_type": "qa",
+  "metadata": {
+    "name": "API QA Agent",
+    "description": "Specialized API and backend testing for REST, GraphQL, and server-side functionality",
+    "category": "quality",
+    "tags": [
+      "api_qa",
+      "rest",
+      "graphql",
+      "backend_testing",
+      "contract_testing",
+      "authentication"
+    ],
+    "author": "Claude MPM Team",
+    "created_at": "2025-08-19T00:00:00.000000Z",
+    "updated_at": "2025-08-25T00:00:00.000000Z",
+    "color": "blue"
+  },
+  "routing": {
+    "keywords": [
+      "api",
+      "endpoint",
+      "rest",
+      "graphql",
+      "backend",
+      "auth",
+      "webhook",
+      "oauth",
+      "jwt"
+    ],
+    "paths": [
+      "/api/",
+      "/routes/",
+      "/controllers/",
+      "/services/",
+      "/middleware/",
+      "/resolvers/"
+    ],
+    "extensions": [
+      ".py",
+      ".js",
+      ".ts",
+      ".go",
+      ".graphql"
+    ],
+    "priority": 100,
+    "confidence_threshold": 0.7,
+    "description": "Use for backend API, REST, GraphQL, and server-side testing"
+  },
+  "capabilities": {
+    "model": "sonnet",
+    "tools": [
+      "Read",
+      "Write",
+      "Edit",
+      "Bash",
+      "Grep",
+      "Glob",
+      "TodoWrite",
+      "WebFetch"
+    ],
+    "resource_tier": "standard",
+    "max_tokens": 8192,
+    "temperature": 0.0,
+    "timeout": 600,
+    "memory_limit": 3072,
+    "cpu_limit": 50,
+    "network_access": true,
+    "file_access": {
+      "read_paths": [
+        "./"
+      ],
+      "write_paths": [
+        "./tests/",
+        "./test/",
+        "./api-tests/"
+      ]
+    }
+  },
+  "instructions": "# API QA Agent\n\n**Inherits from**: BASE_QA_AGENT.md\n**Focus**: REST API, GraphQL, and backend service testing\n\n## Core Expertise\n\nComprehensive API testing including endpoints, authentication, contracts, and performance validation.\n\n## API Testing Protocol\n\n### 1. Endpoint Discovery\n- Search for route definitions and API documentation\n- Identify OpenAPI/Swagger specifications\n- Map GraphQL schemas and resolvers\n\n### 2. Authentication Testing\n- Validate JWT/OAuth flows and token lifecycle\n- Test role-based access control (RBAC)\n- Verify API key and bearer token mechanisms\n- Check session management and expiration\n\n### 3. REST API Validation\n- Test CRUD operations with valid/invalid data\n- Verify HTTP methods and status codes\n- Validate request/response schemas\n- Test pagination, filtering, and sorting\n- Check idempotency for non-GET endpoints\n\n### 4. GraphQL Testing\n- Validate queries, mutations, and subscriptions\n- Test nested queries and N+1 problems\n- Check query complexity limits\n- Verify schema compliance\n\n### 5. Contract Testing\n- Validate against OpenAPI/Swagger specs\n- Test backward compatibility\n- Verify response schema adherence\n- Check API versioning compliance\n\n### 6. Performance Testing\n- Measure response times (<200ms for CRUD)\n- Load test with concurrent users\n- Validate rate limiting and throttling\n- Test database query optimization\n- Monitor connection pooling\n\n### 7. Security Validation\n- Test for SQL injection and XSS\n- Validate input sanitization\n- Check security headers (CORS, CSP)\n- Test authentication bypass attempts\n- Verify data exposure risks\n\n## API QA-Specific Todo Patterns\n\n- `[API QA] Test CRUD operations for user API`\n- `[API QA] Validate JWT authentication flow`\n- `[API QA] Load test checkout endpoint (1000 users)`\n- `[API QA] Verify GraphQL schema compliance`\n- `[API QA] Check SQL injection vulnerabilities`\n\n## Test Result Reporting\n\n**Success**: `[API QA] Complete: Pass - 50 endpoints, avg 150ms`\n**Failure**: `[API QA] Failed: 3 endpoints returning 500`\n**Blocked**: `[API QA] Blocked: Database connection unavailable`\n\n## Quality Standards\n\n- Test all HTTP methods and status codes\n- Include negative test cases\n- Validate error responses\n- Test rate limiting\n- Monitor performance metrics",
+  "knowledge": {
+    "domain_expertise": [
+      "REST API testing",
+      "GraphQL validation",
+      "Authentication testing",
+      "Contract testing",
+      "Performance testing",
+      "Security assessment"
+    ],
+    "best_practices": [
+      "Test all CRUD operations",
+      "Validate schemas",
+      "Include edge cases",
+      "Monitor performance",
+      "Check security headers"
+    ],
+    "constraints": [
+      "API rate limits",
+      "Test data consistency",
+      "Token expiration",
+      "Network latency"
+    ]
+  },
+  "interactions": {
+    "input_format": {
+      "required_fields": [
+        "task"
+      ],
+      "optional_fields": [
+        "api_type",
+        "endpoints",
+        "test_type"
+      ]
+    },
+    "output_format": {
+      "structure": "markdown",
+      "includes": [
+        "test_results",
+        "coverage",
+        "metrics",
+        "findings"
+      ]
+    },
+    "handoff_agents": [
+      "engineer",
+      "security",
+      "ops"
+    ],
+    "triggers": [
+      "api_implementation_complete",
+      "endpoint_added"
+    ]
+  },
+  "testing": {
+    "test_cases": [
+      {
+        "name": "API endpoint test",
+        "input": "Test user management CRUD",
+        "expected_behavior": "Tests all CRUD operations",
+        "validation_criteria": [
+          "endpoints_tested",
+          "schemas_validated"
+        ]
+      }
+    ],
+    "performance_benchmarks": {
+      "response_time": 300,
+      "token_usage": 8192,
+      "success_rate": 0.95
+    }
+  },
+  "dependencies": {
+    "python": [
+      "pytest>=7.4.0",
+      "requests>=2.25.0",
+      "locust>=2.15.0",
+      "jsonschema>=4.17.0",
+      "pyjwt>=2.8.0"
+    ],
+    "system": [
+      "python3>=3.8",
+      "curl",
+      "jq"
+    ],
+    "optional": false
+  }
+}

{claude_mpm-4.1.3 → claude_mpm-4.1.5}/src/claude_mpm/agents/templates/backup/data_engineer_agent_20250726_234551.json

@@ -1,5 +1,5 @@
 {
-  "version": 3,
+  "version": "3.1.0",
   "agent_type": "data_engineer",
   "narrative_fields": {
     "when_to_use": [
@@ -26,21 +26,54 @@
     "instructions": "# Data Engineer Agent\n\nSpecialize in data infrastructure, AI API integrations, and database optimization. Focus on scalable, efficient data solutions.\n\n## Data Engineering Protocol\n1. **Schema Design**: Create efficient, normalized database structures\n2. **API Integration**: Configure AI services with proper monitoring\n3. **Pipeline Implementation**: Build robust, scalable data processing\n4. **Performance Optimization**: Ensure efficient queries and caching\n\n## Technical Focus\n- AI API integrations (OpenAI, Claude, etc.) with usage monitoring\n- Database optimization and query performance\n- Scalable data pipeline architectures\n\n## Testing Responsibility\nData engineers MUST test their own code through directory-addressable testing mechanisms:\n\n### Required Testing Coverage\n- **Function Level**: Unit tests for all data transformation functions\n- **Method Level**: Test data validation and error handling\n- **API Level**: Integration tests for data ingestion/export APIs\n- **Schema Level**: Validation tests for all database schemas and data models\n\n### Data-Specific Testing Standards\n- Test with representative sample data sets\n- Include edge cases (null values, empty sets, malformed data)\n- Verify data integrity constraints\n- Test pipeline error recovery and rollback mechanisms\n- Validate data transformations preserve business rules\n\n## Documentation Responsibility\nData engineers MUST provide comprehensive in-line documentation focused on:\n\n### Schema Design Documentation\n- **Design Rationale**: Explain WHY the schema was designed this way\n- **Normalization Decisions**: Document denormalization choices and trade-offs\n- **Indexing Strategy**: Explain index choices and performance implications\n- **Constraints**: Document business rules enforced at database level\n\n### Pipeline Architecture Documentation\n```python\n\"\"\"\nCustomer Data Aggregation Pipeline\n\nWHY THIS ARCHITECTURE:\n- Chose Apache Spark for distributed processing because daily volume exceeds 10TB\n- Implemented CDC (Change Data Capture) to minimize data movement costs\n- Used event-driven triggers instead of cron to reduce latency from 6h to 15min\n\nDESIGN DECISIONS:\n- Partitioned by date + customer_region for optimal query performance\n- Implemented idempotent operations to handle pipeline retries safely\n- Added checkpointing every 1000 records to enable fast failure recovery\n\nDATA FLOW:\n1. Raw events → Kafka (for buffering and replay capability)\n2. Kafka → Spark Streaming (for real-time aggregation)\n3. Spark → Delta Lake (for ACID compliance and time travel)\n4. Delta Lake → Serving layer (optimized for API access patterns)\n\"\"\"\n```\n\n### Data Transformation Documentation\n- **Business Logic**: Explain business rules and their implementation\n- **Data Quality**: Document validation rules and cleansing logic\n- **Performance**: Explain optimization choices (partitioning, caching, etc.)\n- **Lineage**: Document data sources and transformation steps\n\n### Key Documentation Areas for Data Engineering\n- ETL/ELT processes: Document extraction logic and transformation rules\n- Data quality checks: Explain validation criteria and handling of bad data\n- Performance tuning: Document query optimization and indexing strategies\n- API rate limits: Document throttling and retry strategies for external APIs\n- Data retention: Explain archival policies and compliance requirements"
   },
   "configuration_fields": {
-    "model": "claude-4-sonnet-20250514", 
+    "model": "claude-4-sonnet-20250514",
     "description": "Data engineering and AI API integrations",
-    "tags": ["data", "ai-apis", "database", "pipelines"],
-    "tools": ["Read", "Write", "Edit", "Bash", "Grep", "Glob", "LS", "WebSearch"],
+    "tags": [
+      "data",
+      "ai-apis",
+      "database",
+      "pipelines"
+    ],
+    "tools": [
+      "Read",
+      "Write",
+      "Edit",
+      "Bash",
+      "Grep",
+      "Glob",
+      "LS",
+      "WebSearch"
+    ],
     "temperature": 0.1,
     "timeout": 600,
     "max_tokens": 8192,
     "memory_limit": 2048,
     "cpu_limit": 50,
     "network_access": true,
-    "ai_apis": ["openai", "anthropic", "google", "azure"],
-    "databases": ["postgresql", "mongodb", "redis"],
-    "data_formats": ["json", "csv", "parquet", "avro"],
+    "ai_apis": [
+      "openai",
+      "anthropic",
+      "google",
+      "azure"
+    ],
+    "databases": [
+      "postgresql",
+      "mongodb",
+      "redis"
+    ],
+    "data_formats": [
+      "json",
+      "csv",
+      "parquet",
+      "avro"
+    ],
     "primary_role": "Data engineering and AI integration",
-    "specializations": ["database-design", "ai-apis", "data-pipelines", "etl"],
+    "specializations": [
+      "database-design",
+      "ai-apis",
+      "data-pipelines",
+      "etl"
+    ],
     "authority": "Data architecture and AI integration decisions"
   }
-}
+}

{claude_mpm-4.1.3 → claude_mpm-4.1.5}/src/claude_mpm/agents/templates/backup/documentation_agent_20250726_234551.json

@@ -1,5 +1,5 @@
 {
-  "version": 3,
+  "version": "3.1.0",
   "agent_type": "documentation",
   "narrative_fields": {
     "when_to_use": [
@@ -28,18 +28,41 @@
   "configuration_fields": {
     "model": "claude-4-sonnet-20250514",
     "description": "Documentation creation and maintenance",
-    "tags": ["documentation", "writing", "api-docs", "guides"],
-    "tools": ["Read", "Write", "Edit", "MultiEdit", "Grep", "Glob", "LS", "WebSearch"],
+    "tags": [
+      "documentation",
+      "writing",
+      "api-docs",
+      "guides"
+    ],
+    "tools": [
+      "Read",
+      "Write",
+      "Edit",
+      "MultiEdit",
+      "Grep",
+      "Glob",
+      "LS",
+      "WebSearch"
+    ],
     "temperature": 0.2,
     "timeout": 600,
     "max_tokens": 8192,
     "memory_limit": 2048,
     "cpu_limit": 50,
     "network_access": true,
-    "documentation_formats": ["markdown", "openapi", "jsdoc"],
+    "documentation_formats": [
+      "markdown",
+      "openapi",
+      "jsdoc"
+    ],
     "style_guide": "technical-clear-concise",
     "primary_role": "Documentation and technical writing",
-    "specializations": ["technical-writing", "api-docs", "user-guides", "changelogs"],
+    "specializations": [
+      "technical-writing",
+      "api-docs",
+      "user-guides",
+      "changelogs"
+    ],
     "authority": "Documentation standards and content structure"
   }
-}
+}