@versatil/claude-opera
Version:
π Claude Opera by VERSATIL v6.4.0 - Production-ready OPERA orchestration with 17 agents (7 core + 10 language-specific sub-agents), automatic roadmap generation, 11-MCP ecosystem, RAG memory achieving 98%+ context retention, proactive daemon with file-ba
1,060 lines (852 loc) β’ 29.4 kB
Markdown
# Cursor IDE Integration Guide
**VERSATIL SDLC Framework v6.4.0** - Complete Cursor Workflow Integration
This guide provides everything you need to use VERSATIL with Cursor IDE, including auto-activation setup, automatic roadmap generation, workflow templates, and troubleshooting.
**NEW in v6.4.0**:
- π **Automatic Roadmap Generation** - Get a personalized 4-week development plan during installation
- π€ **17 OPERA Agents** - 7 core agents + 10 language-specific sub-agents
- π― **Smart Agent Matching** - Automatically recommends agents based on your tech stack
## π― Quick Start (5 Minutes)
### Prerequisites
- Cursor IDE installed ([download](https://cursor.sh))
- VERSATIL SDLC Framework installed globally (`npm install -g @versatil/sdlc-framework`)
- Node.js >= 18.0.0
### Initial Setup
```bash
# Navigate to your project
cd /path/to/your/project
# Initialize Cursor integration (auto-generates roadmap)
versatil cursor:init
# This creates:
# - .cursorrules (Cursor-specific agent configuration)
# - .cursor/settings.json (Auto-activation rules)
# - .versatil-project.json (Project-specific config)
# - docs/VERSATIL_ROADMAP.md (π Your personalized 4-week development plan)
# π Review Your Personalized Roadmap
cat docs/VERSATIL_ROADMAP.md
# β Includes: 4-week plan, agent recommendations, quality gates, best practices
```
### Verify Auto-Activation
```bash
# Test agent activation
versatil test-activation
# Expected output:
# β
Cursor IDE detected
# β
.cursorrules found
# β
Agent triggers configured
# β
Proactive orchestrator ready
# β
Roadmap generated: docs/VERSATIL_ROADMAP.md
#
# π Project Analysis:
# - Type: fullstack
# - Technologies: React, Node.js, TypeScript
# - Recommended Agents: 7 (James-React, Marcus-Node, Maria-QA, etc.)
#
# π€ Edit a test file to verify:
# - Create src/LoginForm.test.tsx β Maria-QA should activate
# - Create src/Button.tsx β James-Frontend + James-React should activate
# - Create src/api/users.ts β Marcus-Backend + Marcus-Node should activate
```
## π Automatic Roadmap Generation (NEW in v6.4.0)
When you run `versatil cursor:init`, the framework automatically analyzes your project and generates a personalized development roadmap.
### What Gets Auto-Generated
**1. Project Analysis**
```bash
π Analyzing project at: /Users/you/my-react-app
Detected:
- Type: frontend
- Technologies: React, TypeScript, Next.js
- Framework: Next.js
- Complexity: moderate
- Tests: Present (Jest, Playwright)
- CI/CD: Configured (GitHub Actions)
```
**2. Agent Recommendations** (from 17 available agents)
```
π€ Recommended OPERA Agents:
Critical Agents (Primary Development):
β James-Frontend - UI/UX development, accessibility
β James-React - React hooks, performance, component patterns
β James-NextJS - Next.js SSR/SSG, App Router, Edge functions
β Maria-QA - Testing automation, coverage analysis
β Marcus-Backend - API routes, serverless functions
β Marcus-Node - Node.js optimization, middleware
Recommended Agents (Enhanced Workflow):
π Sarah-PM - Project coordination, documentation
π Alex-BA - Requirements, user stories
```
**3. Personalized 4-Week Roadmap** (`docs/VERSATIL_ROADMAP.md`)
```markdown
# πΊοΈ my-react-app - VERSATIL Development Roadmap
## Week 1: Foundation & Architecture
**Primary Agents**: Alex-BA, Sarah-PM, James-NextJS
Tasks:
- [ ] Review and refine requirements with Alex-BA
- [ ] Set up Next.js 14 with App Router
- [ ] Configure TypeScript strict mode
- [ ] Set up linting and formatting (ESLint, Prettier)
- [ ] Initialize database (Prisma + PostgreSQL)
- [ ] Configure CI/CD pipeline
Quality Gates:
- β
All developers can run project locally
- β
Linting rules enforced
- β
CI pipeline passes
## Week 2: Core Feature Development
**Primary Agents**: James-React, Marcus-Node, Maria-QA
Tasks:
- [ ] Implement core UI components with accessibility
- [ ] Set up API routes with validation
- [ ] Implement authentication (NextAuth.js)
- [ ] Add database migrations
- [ ] Write unit tests (80%+ coverage)
Quality Gates:
- β
Unit tests passing
- β
Code review by Maria-QA passed
- β
No critical security vulnerabilities
- β
Accessibility (WCAG 2.1 AA)
## Week 3: Integration & Quality Assurance
**Primary Agents**: Maria-QA, James-NextJS, Marcus-Node
Tasks:
- [ ] E2E testing with Playwright
- [ ] Performance optimization (Lighthouse >= 90)
- [ ] Security audit (OWASP compliance)
- [ ] Visual regression testing
- [ ] Load testing (< 200ms API response)
Quality Gates:
- β
All E2E tests passing
- β
Lighthouse score >= 90
- β
Security scan passed
## Week 4: Polish & Production Readiness
**Primary Agents**: Sarah-PM, Maria-QA, James-NextJS
Tasks:
- [ ] User acceptance testing (UAT)
- [ ] Complete API documentation
- [ ] Set up monitoring (Sentry, Vercel Analytics)
- [ ] Configure CDN and caching
- [ ] Production deployment to Vercel
- [ ] Post-deployment verification
Quality Gates:
- β
All production checklist completed
- β
Documentation complete
- β
Monitoring operational
```
### Roadmap Templates by Project Type
The framework includes pre-built templates for common stacks:
| Your Stack | Template | Recommended Agents |
|------------|----------|-------------------|
| **React + Node.js** | [react-node-fullstack.md](../../templates/roadmaps/react-node-fullstack.md) | James-React, Marcus-Node, Maria-QA |
| **Vue + Python** | [vue-python-backend.md](../../templates/roadmaps/vue-python-backend.md) | James-Vue, Marcus-Python, Maria-QA |
| **Next.js Monorepo** | [nextjs-monorepo.md](../../templates/roadmaps/nextjs-monorepo.md) | James-NextJS, Marcus-Node, Maria-QA |
| **Python ML/AI** | [python-ml.md](../../templates/roadmaps/python-ml.md) | Dr.AI-ML, Marcus-Python, Maria-QA |
| **Rails Backend** | Auto-generated | Marcus-Rails, Maria-QA, Sarah-PM |
| **Go Microservices** | Auto-generated | Marcus-Go, Oliver-DevOps, Maria-QA |
### How Agent Matching Works
The roadmap generator analyzes your project and automatically recommends the right agents:
```typescript
// Detected: package.json with "react": "^18.0.0"
β Recommends: James-Frontend + James-React
// Detected: package.json with "next": "^14.0.0"
β Recommends: James-Frontend + James-React + James-NextJS
// Detected: package.json with "express": "^4.0.0"
β Recommends: Marcus-Backend + Marcus-Node
// Detected: requirements.txt with "django"
β Recommends: Marcus-Backend + Marcus-Python
// Detected: go.mod
β Recommends: Marcus-Backend + Marcus-Go
// Detected: Gemfile with "rails"
β Recommends: Marcus-Backend + Marcus-Rails
// Detected: requirements.txt with "tensorflow"
β Recommends: Dr.AI-ML + Marcus-Python
```
### Benefits of Auto-Generated Roadmaps
β
**Zero Planning Overhead**: No need to manually create development plans
β
**Tech Stack Alignment**: Roadmap tailored to your specific technologies
β
**Agent Discovery**: Automatically find the right agents for your project
β
**Best Practices**: Industry-standard practices embedded in each template
β
**Quality Gates**: Pre-defined success criteria for each phase
β
**Time Savings**: 83% faster setup (30 min β 5 min)
## π€ How Auto-Activation Works
### File Pattern Matching
VERSATIL agents activate automatically based on file patterns and code context:
```yaml
Scenario 1: Test File Editing
File: src/LoginForm.test.tsx
Trigger: *.test.*, describe(, it(, expect(
Auto-Activates: Maria-QA
Actions:
- Test coverage analysis
- Missing test detection
- Assertion validation
- Inline suggestions appear as you type
Scenario 2: React Component
File: src/components/Button.tsx
Trigger: *.tsx, useState, useEffect, component
Auto-Activates: James-Frontend
Actions:
- Accessibility check (WCAG 2.1 AA)
- Component structure validation
- Responsive design verification
- Performance optimization suggestions
Scenario 3: API Endpoint
File: src/api/users.ts
Trigger: *.api.*, router., async function
Auto-Activates: Marcus-Backend
Actions:
- Security pattern validation (OWASP)
- Response time check (< 200ms target)
- Stress test generation
- Database query optimization
Scenario 4: Multi-Agent Collaboration
User Request: "Add user authentication feature"
Auto-Activates: Alex-BA β Marcus-Backend β James-Frontend β Maria-QA
Workflow:
1. Alex-BA: Extracts requirements, creates user stories
2. Marcus: Implements /api/auth/login, JWT, OWASP security
3. James: Creates LoginForm.tsx, accessibility validation
4. Maria: Generates test suite, runs coverage analysis
```
### Real-Time Feedback (Statusline)
As you code, Cursor's statusline shows agent activity:
```
π€ Maria-QA analyzing... β ββββββββββ 80% coverage β β οΈ 2 missing tests
π€ James validating UI... β β
Accessible β β οΈ Missing aria-label
π€ Marcus security scan... β β
OWASP compliant β β±οΈ 180ms response
```
## π .cursorrules Template
The `.cursorrules` file configures Cursor-specific behavior for VERSATIL agents.
### Basic Template
```yaml
# VERSATIL SDLC Framework - Cursor Configuration
# Generated by: versatil cursor:init
# Project Context
project_name: "My Project"
project_type: "fullstack" # Options: fullstack, frontend, backend, mobile, ai-ml
tech_stack:
frontend: ["React", "TypeScript", "Tailwind CSS"]
backend: ["Node.js", "Express", "PostgreSQL"]
testing: ["Jest", "React Testing Library", "Playwright"]
# Agent Preferences
agents:
maria-qa:
enabled: true
auto_run_on_save: true
coverage_threshold: 80
test_frameworks: ["jest", "playwright"]
james-frontend:
enabled: true
accessibility_standard: "WCAG 2.1 AA"
responsive_breakpoints: [320, 768, 1024, 1920]
css_framework: "tailwind"
marcus-backend:
enabled: true
security_standard: "OWASP Top 10 2023"
performance_target_ms: 200
auto_stress_test: true
sarah-pm:
enabled: true
sprint_duration_days: 14
daily_standup_time: "09:00"
alex-ba:
enabled: true
requirement_format: "user_stories"
acceptance_criteria_format: "gherkin"
dr-ai-ml:
enabled: false # Only for AI/ML projects
# Quality Gates
quality_gates:
pre_commit:
enabled: true
require_tests: true
min_coverage: 80
lint_check: true
pre_deploy:
enabled: true
require_e2e_tests: true
security_scan: true
performance_check: true
# Proactive Features
proactive:
inline_suggestions: true
statusline_updates: true
background_monitoring: true
auto_documentation: true
# Custom Rules (Optional)
custom_rules:
- "Always use TypeScript strict mode"
- "Follow conventional commits format"
- "Prefer functional components over class components"
- "All API endpoints must have OpenAPI documentation"
```
### Advanced Template (Enterprise)
```yaml
# Enterprise Configuration with Team Workflows
# Team Configuration
team:
size: 8
roles:
- frontend_developers: 3
- backend_developers: 2
- qa_engineers: 2
- product_manager: 1
workflow: "gitflow" # Options: gitflow, trunk-based, feature-branch
code_review:
required_reviewers: 2
auto_assign_maria: true
block_on_quality_gate_failure: true
# Advanced Agent Configuration
agents:
maria-qa:
proactive_actions:
test_coverage_analysis:
enabled: true
threshold: 85
report_format: "html"
missing_test_detection:
enabled: true
scan_on_file_save: true
suggest_test_cases: true
assertion_validation:
enabled: true
check_edge_cases: true
validate_error_scenarios: true
visual_regression:
enabled: true
browser: "chrome"
viewports: [375, 768, 1920]
james-frontend:
proactive_actions:
accessibility_check_wcag:
enabled: true
level: "AA"
auto_fix_simple_issues: true
component_structure_validation:
enabled: true
enforce_patterns: ["composition", "container-presentational"]
responsive_design_verification:
enabled: true
breakpoints: [320, 768, 1024, 1920]
test_orientation: true
performance_optimization_suggestions:
enabled: true
target_lighthouse_score: 90
check_bundle_size: true
suggest_code_splitting: true
# MCP Integration
mcp:
enabled: true
server: "claude-desktop"
auto_sync: true
memory_persistence: true
# RAG Memory System
rag:
enabled: true
vector_storage: "supabase"
learning_mode: "continuous"
pattern_recognition: true
project_patterns:
- "Component naming conventions"
- "API response structures"
- "Test assertion patterns"
- "Error handling approaches"
# Monitoring & Analytics
monitoring:
track_agent_performance: true
collect_usage_analytics: false # Privacy-first
error_reporting: true
dashboards:
realtime_sdlc_tracker: true
quality_metrics: true
velocity_tracking: true
```
## π§ Cursor Settings Integration
### .cursor/settings.json
This file is auto-generated by `versatil cursor:init` but can be customized:
```json
{
"versatil.proactive_agents": {
"enabled": true,
"auto_activation": true,
"background_monitoring": true,
"inline_suggestions": true,
"statusline_updates": true,
"slash_commands_fallback": true,
"activation_triggers": {
"maria-qa": {
"file_patterns": [
"*.test.*",
"**/__tests__/**",
"**/test/**",
"*.spec.*"
],
"code_patterns": [
"describe(",
"it(",
"test(",
"expect(",
"jest.",
"vitest."
],
"keywords": ["test", "spec", "coverage", "quality"],
"auto_run_on_save": true,
"background_analysis": true,
"proactive_actions": [
"test_coverage_analysis",
"missing_test_detection",
"assertion_validation",
"quality_gate_enforcement"
]
},
"james-frontend": {
"file_patterns": [
"*.tsx",
"*.jsx",
"*.vue",
"*.svelte",
"*.css",
"*.scss"
],
"code_patterns": [
"useState",
"useEffect",
"component",
"props",
"className"
],
"keywords": ["component", "react", "vue", "ui", "frontend"],
"auto_run_on_save": true,
"background_analysis": true,
"proactive_actions": [
"accessibility_check_wcag",
"component_structure_validation",
"responsive_design_verification",
"performance_optimization_suggestions"
]
},
"marcus-backend": {
"file_patterns": [
"*.api.*",
"**/routes/**",
"**/controllers/**",
"**/server/**"
],
"code_patterns": [
"router.",
"app.",
"express.",
"fastify.",
"async function"
],
"keywords": ["api", "server", "database", "auth", "security"],
"auto_run_on_save": true,
"background_analysis": true,
"proactive_actions": [
"security_pattern_validation_owasp",
"response_time_check_200ms",
"stress_test_generation",
"database_query_optimization"
]
}
}
}
}
```
## π¨ Troubleshooting Auto-Activation
### Problem 1: Agents Not Activating
**Symptoms**: Edit a test file, but Maria-QA doesn't activate
**Diagnosis**:
```bash
# Run activation test
versatil test-activation
# Check if monitoring is running
versatil agents --status
# Enable debug mode
VERSATIL_DEBUG=true versatil agents --watch
```
**Common Causes & Fixes**:
1. **Missing .cursorrules file**
```bash
# Regenerate
versatil cursor:init --force
```
2. **Proactive agents disabled**
```bash
# Check status
versatil config show | grep proactive
# Enable
versatil config set proactive_agents.enabled=true
```
3. **File patterns not matching**
```bash
# Test specific file
versatil test-activation --file src/LoginForm.test.tsx
# Should output matching agents and why they matched
```
4. **Cursor IDE extension issue**
- Restart Cursor IDE
- Check Cursor settings: Settings β Extensions β VERSATIL
- Ensure extension is enabled
### Problem 2: Statusline Not Updating
**Symptoms**: Agents activate but no statusline feedback
**Fix**:
```json
// .cursor/settings.json
{
"versatil.proactive_agents": {
"statusline_updates": true, // β Ensure this is true
"inline_suggestions": true
}
}
```
**Restart Cursor IDE after changing settings**
### Problem 3: Too Many Agent Activations
**Symptoms**: Multiple agents activating for simple edits
**Fix - Adjust sensitivity**:
```yaml
# .cursorrules
agents:
maria-qa:
auto_run_on_save: false # Only activate on demand
background_analysis: true # Still run in background
```
### Problem 4: Slow Performance
**Symptoms**: Cursor lags when editing files
**Fix - Reduce background monitoring**:
```json
// .cursor/settings.json
{
"versatil.proactive_agents": {
"background_monitoring": false, // Disable for large projects
"auto_activation": true // Keep on-save activation
}
}
```
## π¬ Workflow Examples
### Workflow 1: Feature Development (Full OPERA Cycle)
```bash
# Step 1: User types feature request in Cursor
# "Add user authentication with email/password"
# Auto-Activation Sequence:
# π€ Alex-BA activates (detects feature request)
# - Analyzes: "user authentication" keyword
# - Creates user stories:
# * "As a user, I want to login with email/password"
# * "As a user, I want secure session management"
# - Defines acceptance criteria (Gherkin format)
# π€ Marcus-Backend activates (handoff from Alex)
# - Implements: src/api/auth/login.ts
# - Adds: JWT token generation, bcrypt password hashing
# - Security: OWASP validation (SQL injection, XSS prevention)
# - Auto-generates: Stress tests (1000 concurrent logins)
# π€ James-Frontend activates (parallel with Marcus)
# - Creates: src/components/LoginForm.tsx
# - Accessibility: aria-labels, keyboard navigation, focus management
# - Responsive: Mobile-first design, tested at 4 breakpoints
# - Integrates: API calls to Marcus's /api/auth/login
# π€ Maria-QA activates (watches both)
# - Validates: Test coverage 85% (both frontend + backend)
# - Runs: Visual regression tests (3 browsers x 4 viewports)
# - Checks: Security compliance (OWASP Top 10)
# - Quality Gate: BLOCKS merge if coverage < 80%
# π€ Sarah-PM activates (coordinates)
# - Updates: Sprint board (moves card to "In Review")
# - Tracks: Progress in statusline
# - Generates: Completion report with metrics
# Statusline shows:
# π€ 5 agents collaborating β ββββββββββ 85% complete β ETA: 2 min
```
### Workflow 2: Bug Fix (Targeted Agent Use)
```bash
# User opens: src/components/UserProfile.tsx
# User comments: "// BUG: Avatar image not loading"
# Auto-Activation:
# π€ James-Frontend activates (*.tsx file)
# - Detects: "BUG" keyword
# - Analyzes: Image loading code
# - Suggests: Add error boundary, lazy loading, placeholder
# User fixes code, saves file
# π€ Maria-QA activates (on save)
# - Checks: Test coverage for error scenarios
# - Suggests: Add test for broken image URL
# - Runs: Visual regression (avatar states)
# Statusline shows:
# β
Bug fix validated β 90% coverage β 0 visual regressions
```
### Workflow 3: Code Review (Quality Enforcement)
```bash
# User creates pull request in GitHub
# Auto-Activation (via GitHub Actions + VERSATIL):
# π€ Maria-QA (PR validation mode)
# - Runs: Full test suite
# - Checks: Coverage delta (new code must have 80%+ coverage)
# - Validates: No regressions in existing tests
# - Reports: Inline PR comments with test suggestions
# π€ Marcus-Backend (if API changes detected)
# - Security: OWASP scan on changed endpoints
# - Performance: Stress test (ensures < 200ms response)
# - Breaking Changes: API contract validation
# π€ James-Frontend (if UI changes detected)
# - Accessibility: WCAG 2.1 AA audit
# - Visual Regression: Screenshot comparison
# - Bundle Size: Checks for size increase
# Quality Gate Decision:
# β
PASS: PR can be merged (all gates green)
# β FAIL: PR blocked (coverage 75%, needs 80%)
#
# Maria comments on PR:
# "β οΈ Quality gate failed:
# - Test coverage: 75% (required: 80%)
# - Missing tests for: UserProfile error handling
# - Suggested test cases:
# * should show placeholder when avatar fails to load
# * should retry avatar load on error"
```
## π― Best Practices
### 1. File Organization for Optimal Auto-Activation
```
src/
βββ components/ # James-Frontend auto-activates
β βββ Button.tsx
β βββ LoginForm.tsx
β βββ __tests__/ # Maria-QA auto-activates
β βββ Button.test.tsx
β βββ LoginForm.test.tsx
β
βββ api/ # Marcus-Backend auto-activates
β βββ auth/
β β βββ login.ts
β βββ users/
β βββ profile.ts
β
βββ features/ # Alex-BA watches for *.feature files
β βββ authentication.feature
β
βββ ml-models/ # Dr.AI-ML auto-activates
βββ recommendation.py
```
### 2. Naming Conventions
```typescript
// β
GOOD - Triggers correct agent activation
// File: src/components/LoginForm.test.tsx
describe('LoginForm', () => { // Maria-QA detects 'describe('
it('should validate email format', () => {
expect(validateEmail('test@example.com')).toBe(true);
});
});
// File: src/api/auth/login.ts
router.post('/api/auth/login', async (req, res) => { // Marcus detects 'router.'
// Implementation
});
// β BAD - May not trigger auto-activation
// File: src/components/forms.tsx (generic name)
function SomeComponent() { // No clear pattern
// Less likely to match activation triggers
}
```
### 3. Agent Collaboration Patterns
```yaml
# Pattern 1: Sequential Handoff
Alex-BA (requirements) β Marcus-Backend (implementation) β Maria-QA (testing)
# Pattern 2: Parallel Execution
Marcus-Backend (API) || James-Frontend (UI) β Maria-QA (integration tests)
# Pattern 3: Continuous Monitoring
Sarah-PM (watches all) + Maria-QA (enforces quality gates)
# Pattern 4: Emergency Response
User: "URGENT: Production API timeout"
β Marcus-Backend (immediate analysis)
β Maria-QA (stress test generation)
β Sarah-PM (stakeholder communication)
```
### 4. Quality Gate Integration
```yaml
# Pre-Commit Gate (Local)
Trigger: git commit
Agents: Maria-QA + Marcus-Backend
Checks:
- Lint check (ESLint, Prettier)
- Unit tests (must pass)
- Coverage threshold (80%+)
- Security scan (basic SAST)
Block: true (prevent commit if fails)
# Pre-Push Gate (CI)
Trigger: git push
Agents: All relevant agents
Checks:
- Full test suite
- Integration tests
- Visual regression
- Performance benchmarks
Block: true (prevent push if fails)
# Pre-Deploy Gate (CD)
Trigger: Deployment to staging/production
Agents: Full OPERA team
Checks:
- E2E tests (Playwright + Chrome MCP)
- Security audit (OWASP ZAP, Snyk)
- Performance validation (Lighthouse)
- Accessibility audit (axe, pa11y)
- API contract validation
Block: true (prevent deployment if fails)
```
## π Integration with Other Tools
### GitHub Actions Integration
```yaml
# .github/workflows/versatil-quality-gate.yml
name: VERSATIL Quality Gate
on: [pull_request]
jobs:
quality-check:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- name: Install VERSATIL
run: npm install -g @versatil/sdlc-framework
- name: Run Quality Gate
run: |
versatil quality-gate pre-deploy
- name: Maria-QA Review
run: versatil agents maria --review-pr ${{ github.event.pull_request.number }}
- name: Comment Results
uses: actions/github-script@v6
with:
script: |
const report = require('./versatil-report.json');
github.rest.issues.createComment({
issue_number: context.issue.number,
owner: context.repo.owner,
repo: context.repo.repo,
body: report.markdown
});
```
### VS Code / Cursor Extensions
```json
// .vscode/settings.json (also works in Cursor)
{
"versatil.autoActivation": true,
"versatil.statusBar": true,
"versatil.inlineSuggestions": true,
"editor.codeActionsOnSave": {
"source.fixAll.versatil": true
},
"versatil.agents": {
"maria-qa": {
"showCoverageGutters": true,
"highlightUncoveredCode": true
},
"james-frontend": {
"showAccessibilityHints": true
}
}
}
```
## π Monitoring Agent Performance
### Real-Time Agent Dashboard
```bash
# Start live agent monitoring
versatil agents --watch
# Output:
# π€ VERSATIL Agent Dashboard
# βββββββββββββββββββ¬βββββββββββ¬ββββββββββββ¬βββββββββββββββ
# β Agent β Status β Active β Last Action β
# βββββββββββββββββββΌβββββββββββΌββββββββββββΌβββββββββββββββ€
# β Maria-QA β Running β Yes β 2s ago β
# β James-Frontend β Idle β No β 5m ago β
# β Marcus-Backend β Running β Yes β 10s ago β
# β Sarah-PM β Idle β No β 1h ago β
# β Alex-BA β Idle β No β 3h ago β
# β Dr.AI-ML β Disabled β No β Never β
# βββββββββββββββββββ΄βββββββββββ΄ββββββββββββ΄βββββββββββββββ
#
# Current Tasks:
# π€ Maria-QA: Analyzing test coverage for LoginForm.test.tsx
# π€ Marcus-Backend: Running stress test on /api/auth/login (1000 req)
#
# Press Ctrl+C to exit
```
### Agent Performance Metrics
```bash
# View agent statistics
versatil agents --stats
# Output:
# π Agent Performance (Last 7 Days)
#
# Maria-QA:
# - Activations: 247
# - Avg Response Time: 1.8s
# - Tests Generated: 89
# - Bugs Detected: 12
# - Coverage Improvement: +15%
#
# James-Frontend:
# - Activations: 183
# - Accessibility Fixes: 34
# - Performance Improvements: 21
# - Components Optimized: 67
#
# Marcus-Backend:
# - Activations: 156
# - Security Issues Found: 8
# - APIs Optimized: 23
# - Stress Tests Generated: 45
```
## π Next Steps
1. **Run Initial Setup** (auto-generates roadmap)
```bash
versatil cursor:init
```
2. **Review Your Personalized Roadmap** π
```bash
cat docs/VERSATIL_ROADMAP.md
```
3. **Test Auto-Activation**
```bash
versatil test-activation
```
4. **Start Coding** - Agents will activate automatically based on roadmap recommendations!
5. **Monitor Performance**
```bash
versatil agents --watch
```
6. **Read Advanced Docs**
- [Installation Guide](../getting-started/installation.md) - Updated for v6.4.0
- [Roadmap Templates](../../templates/roadmaps/) - Example roadmaps by project type
- [Agent Reference](../../.claude/AGENTS.md) - All 17 agents documented
- [5-Rule System](../../.claude/rules/README.md) - Automation rules
- [Quality Gates Guide](QUALITY_GATES.md) - Quality enforcement
## π‘ Tips from First Production User (VERSSAI Team)
> "After working with VERSATIL on our 85-90% complete enterprise platform, here are our recommendations:"
1. **Start Small** - Enable Maria-QA first, then add other agents gradually
2. **Customize .cursorrules** - Tailor agent behavior to your project's needs
3. **Use Quality Gates** - Pre-commit gates caught 23 bugs before they reached PR
4. **Monitor Agent Activity** - `versatil agents --watch` helps understand what's happening
5. **Trust the Auto-Activation** - Agents are smart about when to activate
6. **Review Agent Suggestions** - Not all suggestions need to be followed immediately
7. **Leverage RAG Memory** - The more you use VERSATIL, the smarter it gets
**Framework Version**: 6.4.0
**Last Updated**: 2025-10-12
**Maintained By**: VERSATIL Development Team
**Community**: [GitHub Discussions](https://github.com/versatil-sdlc-framework/discussions)
**What's New in v6.4.0**:
- π Automatic roadmap generation during installation
- π€ 17 OPERA agents (7 core + 10 language-specific sub-agents)
- π― Smart agent matching based on detected technologies
- β‘ 83% faster setup (30 min β 5 min)
## π Related Documentation
- [Getting Started Guide](GET_STARTED.md)
- [Agent Reference](.claude/AGENTS.md)
- [5-Rule System](.claude/rules/README.md)
- [MCP Integration](mcp-integration.md)
- [Quality Gates](QUALITY_GATES.md)
- [Migration Guide](MIGRATION_EXISTING_PROJECT.md)