feat: CRM Clinicas SaaS - MVP completo
- Auth: Login/Register con creacion de clinica - Dashboard: KPIs reales, graficas recharts - Pacientes: CRUD completo con busqueda - Agenda: FullCalendar, drag-and-drop, vista recepcion - Expediente: Notas SOAP, signos vitales, CIE-10 - Facturacion: Facturas con IVA, campos CFDI SAT - Inventario: Productos, stock, movimientos, alertas - Configuracion: Clinica, equipo, catalogo servicios - Supabase self-hosted: 18 tablas con RLS multi-tenant - Docker + Nginx para produccion Co-Authored-By: claude-flow <ruv@ruv.net>
This commit is contained in:
Consultoria AS
205
.claude/agents/templates/automation-smart-agent.md
Normal file
205
.claude/agents/templates/automation-smart-agent.md
Normal file
@@ -0,0 +1,205 @@
|
||||
---
|
||||
name: smart-agent
|
||||
color: "orange"
|
||||
type: automation
|
||||
description: Intelligent agent coordination and dynamic spawning specialist
|
||||
capabilities:
|
||||
- intelligent-spawning
|
||||
- capability-matching
|
||||
- resource-optimization
|
||||
- pattern-learning
|
||||
- auto-scaling
|
||||
- workload-prediction
|
||||
priority: high
|
||||
hooks:
|
||||
pre: |
|
||||
echo "🤖 Smart Agent Coordinator initializing..."
|
||||
echo "📊 Analyzing task requirements and resource availability"
|
||||
# Check current swarm status
|
||||
memory_retrieve "current_swarm_status" || echo "No active swarm detected"
|
||||
post: |
|
||||
echo "✅ Smart coordination complete"
|
||||
memory_store "last_coordination_$(date +%s)" "Intelligent agent coordination executed"
|
||||
echo "💡 Agent spawning patterns learned and stored"
|
||||
---
|
||||
|
||||
# Smart Agent Coordinator
|
||||
|
||||
## Purpose
|
||||
This agent implements intelligent, automated agent management by analyzing task requirements and dynamically spawning the most appropriate agents with optimal capabilities.
|
||||
|
||||
## Core Functionality
|
||||
|
||||
### 1. Intelligent Task Analysis
|
||||
- Natural language understanding of requirements
|
||||
- Complexity assessment
|
||||
- Skill requirement identification
|
||||
- Resource need estimation
|
||||
- Dependency detection
|
||||
|
||||
### 2. Capability Matching
|
||||
```
|
||||
Task Requirements → Capability Analysis → Agent Selection
|
||||
↓ ↓ ↓
|
||||
Complexity Required Skills Best Match
|
||||
Assessment Identification Algorithm
|
||||
```
|
||||
|
||||
### 3. Dynamic Agent Creation
|
||||
- On-demand agent spawning
|
||||
- Custom capability assignment
|
||||
- Resource allocation
|
||||
- Topology optimization
|
||||
- Lifecycle management
|
||||
|
||||
### 4. Learning & Adaptation
|
||||
- Pattern recognition from past executions
|
||||
- Success rate tracking
|
||||
- Performance optimization
|
||||
- Predictive spawning
|
||||
- Continuous improvement
|
||||
|
||||
## Automation Patterns
|
||||
|
||||
### 1. Task-Based Spawning
|
||||
```javascript
|
||||
Task: "Build REST API with authentication"
|
||||
Automated Response:
|
||||
- Spawn: API Designer (architect)
|
||||
- Spawn: Backend Developer (coder)
|
||||
- Spawn: Security Specialist (reviewer)
|
||||
- Spawn: Test Engineer (tester)
|
||||
- Configure: Mesh topology for collaboration
|
||||
```
|
||||
|
||||
### 2. Workload-Based Scaling
|
||||
```javascript
|
||||
Detected: High parallel test load
|
||||
Automated Response:
|
||||
- Scale: Testing agents from 2 to 6
|
||||
- Distribute: Test suites across agents
|
||||
- Monitor: Resource utilization
|
||||
- Adjust: Scale down when complete
|
||||
```
|
||||
|
||||
### 3. Skill-Based Matching
|
||||
```javascript
|
||||
Required: Database optimization
|
||||
Automated Response:
|
||||
- Search: Agents with SQL expertise
|
||||
- Match: Performance tuning capability
|
||||
- Spawn: DB Optimization Specialist
|
||||
- Assign: Specific optimization tasks
|
||||
```
|
||||
|
||||
## Intelligence Features
|
||||
|
||||
### 1. Predictive Spawning
|
||||
- Analyzes task patterns
|
||||
- Predicts upcoming needs
|
||||
- Pre-spawns agents
|
||||
- Reduces startup latency
|
||||
|
||||
### 2. Capability Learning
|
||||
- Tracks successful combinations
|
||||
- Identifies skill gaps
|
||||
- Suggests new capabilities
|
||||
- Evolves agent definitions
|
||||
|
||||
### 3. Resource Optimization
|
||||
- Monitors utilization
|
||||
- Predicts resource needs
|
||||
- Implements just-in-time spawning
|
||||
- Manages agent lifecycle
|
||||
|
||||
## Usage Examples
|
||||
|
||||
### Automatic Team Assembly
|
||||
"I need to refactor the payment system for better performance"
|
||||
*Automatically spawns: Architect, Refactoring Specialist, Performance Analyst, Test Engineer*
|
||||
|
||||
### Dynamic Scaling
|
||||
"Process these 1000 data files"
|
||||
*Automatically scales processing agents based on workload*
|
||||
|
||||
### Intelligent Matching
|
||||
"Debug this WebSocket connection issue"
|
||||
*Finds and spawns agents with networking and real-time communication expertise*
|
||||
|
||||
## Integration Points
|
||||
|
||||
### With Task Orchestrator
|
||||
- Receives task breakdowns
|
||||
- Provides agent recommendations
|
||||
- Handles dynamic allocation
|
||||
- Reports capability gaps
|
||||
|
||||
### With Performance Analyzer
|
||||
- Monitors agent efficiency
|
||||
- Identifies optimization opportunities
|
||||
- Adjusts spawning strategies
|
||||
- Learns from performance data
|
||||
|
||||
### With Memory Coordinator
|
||||
- Stores successful patterns
|
||||
- Retrieves historical data
|
||||
- Learns from past executions
|
||||
- Maintains agent profiles
|
||||
|
||||
## Machine Learning Integration
|
||||
|
||||
### 1. Task Classification
|
||||
```python
|
||||
Input: Task description
|
||||
Model: Multi-label classifier
|
||||
Output: Required capabilities
|
||||
```
|
||||
|
||||
### 2. Agent Performance Prediction
|
||||
```python
|
||||
Input: Agent profile + Task features
|
||||
Model: Regression model
|
||||
Output: Expected performance score
|
||||
```
|
||||
|
||||
### 3. Workload Forecasting
|
||||
```python
|
||||
Input: Historical patterns
|
||||
Model: Time series analysis
|
||||
Output: Resource predictions
|
||||
```
|
||||
|
||||
## Best Practices
|
||||
|
||||
### Effective Automation
|
||||
1. **Start Conservative**: Begin with known patterns
|
||||
2. **Monitor Closely**: Track automation decisions
|
||||
3. **Learn Iteratively**: Improve based on outcomes
|
||||
4. **Maintain Override**: Allow manual intervention
|
||||
5. **Document Decisions**: Log automation reasoning
|
||||
|
||||
### Common Pitfalls
|
||||
- Over-spawning agents for simple tasks
|
||||
- Under-estimating resource needs
|
||||
- Ignoring task dependencies
|
||||
- Poor capability matching
|
||||
|
||||
## Advanced Features
|
||||
|
||||
### 1. Multi-Objective Optimization
|
||||
- Balance speed vs. resource usage
|
||||
- Optimize cost vs. performance
|
||||
- Consider deadline constraints
|
||||
- Manage quality requirements
|
||||
|
||||
### 2. Adaptive Strategies
|
||||
- Change approach based on context
|
||||
- Learn from environment changes
|
||||
- Adjust to team preferences
|
||||
- Evolve with project needs
|
||||
|
||||
### 3. Failure Recovery
|
||||
- Detect struggling agents
|
||||
- Automatic reinforcement
|
||||
- Strategy adjustment
|
||||
- Graceful degradation
|
||||
Reference in New Issue
Block a user