claude-autopm 1.18.0 → 1.20.1

package/README.md

@@ -269,6 +269,165 @@ autopm pm:epic-sync user-auth
 
 **That's it!** You're now using structured, spec-driven development with AI agents.
 
+## 📋 Complete PM Workflow Guide
+
+### Understanding the Process: PRD → Epic → Tasks
+
+ClaudeAutoPM follows a structured workflow from requirements to implementation:
+
+```
+PRD (Product Requirements)
+  ↓
+Epic Split (Optional - for complex projects)
+  ↓
+Task Decomposition
+  ↓
+GitHub/Azure Sync
+  ↓
+Development & Tracking
+```
+
+### Quick Decision Guide
+
+**When to use ONE epic (`/pm:epic-decompose`):**
+- ✅ Simple feature (1-2 weeks)
+- ✅ Single component (frontend OR backend)
+- ✅ One developer
+- ✅ Examples: "Add user profile page", "Create REST API endpoint"
+
+**When to use MULTIPLE epics (`/pm:epic-split`):**
+- ✅ Complex project (2+ months)
+- ✅ Multiple components (frontend + backend + infrastructure)
+- ✅ Multiple teams working in parallel
+- ✅ Examples: "E-commerce platform", "Social media dashboard"
+
+### Workflow Examples
+
+<details>
+<summary><b>Simple Feature Workflow</b> - Single epic, quick delivery</summary>
+
+```bash
+# 1. Create PRD
+/pm:prd-new user-profile
+
+# 2. Parse and analyze
+/pm:prd-parse user-profile
+
+# 3. Decompose into tasks (ONE epic)
+/pm:epic-decompose user-profile
+# Creates: .claude/epics/user-profile/
+#   ├── epic.md
+#   ├── 001.md  # Create profile component
+#   ├── 002.md  # Add avatar upload
+#   ├── 003.md  # Implement edit form
+#   └── 004.md  # Add validation
+
+# 4. Sync with GitHub/Azure
+/pm:epic-sync user-profile
+
+# 5. Start working
+/pm:next                    # Get next task
+/pm:issue-start #123        # Begin work
+# ... development ...
+/pm:issue-close #123        # Complete task
+```
+</details>
+
+<details>
+<summary><b>Complex Project Workflow</b> - Multiple epics, phased delivery</summary>
+
+```bash
+# 1. Create PRD
+/pm:prd-new ecommerce-platform
+
+# 2. Parse and analyze
+/pm:prd-parse ecommerce-platform
+
+# 3. Split into multiple epics (AUTOMATIC)
+/pm:epic-split ecommerce-platform
+# Automatically creates 6 epics:
+#   Epic 1: Infrastructure (Docker, DB, Redis) - P0, 1w
+#   Epic 2: Auth Backend (JWT, users, RBAC) - P0, 2w
+#   Epic 3: Product API (catalog, orders) - P0, 3w
+#   Epic 4: Frontend Foundation (React setup) - P0, 1w
+#   Epic 5: E-commerce UI (pages, cart) - P1, 3w
+#   Epic 6: Testing & Deployment (CI/CD) - P1, 1w
+
+# 4. Decompose EACH epic into tasks
+/pm:epic-decompose ecommerce-platform/01-infrastructure    # 12 tasks
+/pm:epic-decompose ecommerce-platform/02-auth-backend      # 15 tasks
+/pm:epic-decompose ecommerce-platform/03-product-api       # 20 tasks
+/pm:epic-decompose ecommerce-platform/04-frontend          # 10 tasks
+/pm:epic-decompose ecommerce-platform/05-ui                # 25 tasks
+/pm:epic-decompose ecommerce-platform/06-testing           #  8 tasks
+# TOTAL: ~90 tasks across 6 epics
+
+# 5. Sync ALL epics at once
+/pm:epic-sync ecommerce-platform
+
+# 6. Parallel team work
+/pm:next  # Team 1: Infrastructure (P0)
+/pm:next  # Team 2: Auth Backend (P0, parallel)
+/pm:next  # Team 3: Frontend Foundation (P0, parallel)
+```
+</details>
+
+<details>
+<summary><b>Multiple PRDs Workflow</b> - Independent features</summary>
+
+```bash
+# Create multiple independent features
+/pm:prd-new login-page
+/pm:prd-new payment-system
+/pm:prd-new notifications
+
+# Process each independently
+/pm:prd-parse login-page
+/pm:epic-decompose login-page      # 5 tasks
+/pm:epic-sync login-page
+
+/pm:prd-parse payment-system
+/pm:epic-decompose payment-system  # 8 tasks
+/pm:epic-sync payment-system
+
+/pm:prd-parse notifications
+/pm:epic-decompose notifications   # 4 tasks
+/pm:epic-sync notifications
+
+# /pm:next automatically picks highest priority across ALL epics
+```
+</details>
+
+### Key Commands Reference
+
+| Command | Purpose | When to Use |
+|---------|---------|-------------|
+| `/pm:prd-new <name>` | Create PRD | Always start here |
+| `/pm:prd-parse <name>` | Analyze PRD | After writing requirements |
+| `/pm:epic-split <name>` | Create multiple epics | Complex, multi-component projects |
+| `/pm:epic-decompose <name>` | Break into tasks | Always (once per epic) |
+| `/pm:epic-sync <name>` | Sync with GitHub/Azure | After decomposition |
+| `/pm:context` | Show current state | Check progress anytime |
+| `/pm:next` | Get next task | Ready to work |
+| `/pm:issue-start #N` | Start task | Before coding |
+| `/pm:issue-close #N` | Complete task | After finishing |
+
+### FAQ
+
+**Q: Can I create multiple PRDs at once?**
+A: Yes! Each PRD is independent. Create as many as you need.
+
+**Q: How do I decide between epic-split and epic-decompose?**
+A: Use epic-split for multi-component projects (frontend + backend + infra). Use epic-decompose for single-component features.
+
+**Q: Do I need to decompose ALL epics after split?**
+A: Yes, before syncing. But you can decompose them one at a time as needed.
+
+**Q: How do I check my progress?**
+A: Use `/pm:context` to see current project, epics, and task progress.
+
+📖 **Full Workflow Guide:** See [PM-WORKFLOW-GUIDE.md](PM-WORKFLOW-GUIDE.md) for detailed examples and decision flows.
+
 ## 🎯 Core Workflow: Crawl → Walk → Run
 
 ### Crawl: Basic Commands

package/autopm/.claude/agents/README.md

@@ -57,7 +57,7 @@ Language-specific development:
 Framework specialists:
 
 - `react-frontend-engineer` - React/Next.js expert
-- `playwright-test-engineer` - E2E testing expert
+- `frontend-testing-engineer` - E2E testing expert
 - *Planned: angular, vue, django, spring, express*
 
 ### Cloud (4 agents, 5+ planned)

package/autopm/.claude/agents/core/mcp-manager.md

@@ -28,7 +28,7 @@ Each MCP server is defined in a Markdown file with:
 - **monitoring**: Observability and metrics
 
 ### Configuration Management
-- Servers defined in `autopm/.claude/mcp/*.md`
+- Servers defined in `.claude/mcp/*.md`
 - Active servers tracked in `.claude/config.json`
 - Runtime config generated to `.claude/mcp-servers.json`
 - Environment variables in `.claude/.env`

package/autopm/.claude/agents/decision-matrices/python-backend-selection.md

@@ -1,8 +1,8 @@
-# Python Backend Agent Decision Matrix
+# Python Backend Framework Selection Guide
 
 ## Quick Selection Guide
 
-Choose between `fastapi-backend-engineer` and `flask-backend-engineer` based on your project requirements:
+The `python-backend-engineer` agent supports both **FastAPI** and **Flask** frameworks. Use this guide to choose the right framework for your project:
 
 | Requirement | FastAPI | Flask |
 |-------------|---------|-------|
@@ -27,9 +27,9 @@ Choose between `fastapi-backend-engineer` and `flask-backend-engineer` based on
 - ⚙️ **Moderate/Possible**: Doable with some effort
 - ⚠️ **Limited**: Has constraints or limitations
 
-## Detailed Agent Comparison
+## Detailed Framework Comparison
 
-### fastapi-backend-engineer
+### FastAPI (use python-backend-engineer with framework=fastapi)
 
 **Best For:**
 - **Modern APIs**: REST/GraphQL APIs with auto-documentation
@@ -55,7 +55,7 @@ Choose between `fastapi-backend-engineer` and `flask-backend-engineer` based on
 - IoT data ingestion APIs
 - Modern single-page app backends
 
-### flask-backend-engineer
+### Flask (use python-backend-engineer with framework=flask)
 
 **Best For:**
 - **Traditional Web Applications**: Server-rendered applications
@@ -86,7 +86,7 @@ Choose between `fastapi-backend-engineer` and `flask-backend-engineer` based on
 ### 1. What type of application are you building?
 
 #### API-Only Applications
-→ **fastapi-backend-engineer**
+→ **FastAPI** (python-backend-engineer with framework=fastapi)
 **Reasoning:**
 - Auto-generated API documentation
 - Built-in request/response validation
@@ -94,7 +94,7 @@ Choose between `fastapi-backend-engineer` and `flask-backend-engineer` based on
 - Native async support for database operations
 
 #### Web Applications with Templates
-→ **flask-backend-engineer**
+→ **Flask** (python-backend-engineer with framework=flask)
 **Reasoning:**
 - Mature template engine (Jinja2)
 - Server-side rendering capabilities
@@ -103,13 +103,13 @@ Choose between `fastapi-backend-engineer` and `flask-backend-engineer` based on
 
 #### Hybrid (API + Web)
 → **Consider both or choose based on primary focus:**
-- API-heavy → fastapi-backend-engineer
-- Web-heavy → flask-backend-engineer
+- API-heavy → FastAPI (python-backend-engineer with framework=fastapi)
+- Web-heavy → Flask (python-backend-engineer with framework=flask)
 
 ### 2. What are your performance requirements?
 
 #### High Performance Required
-→ **fastapi-backend-engineer**
+→ **FastAPI** (python-backend-engineer with framework=fastapi)
 **Use When:**
 - 1000+ requests per second expected
 - Low latency requirements (< 100ms)
@@ -117,7 +117,7 @@ Choose between `fastapi-backend-engineer` and `flask-backend-engineer` based on
 - Concurrent user handling important
 
 #### Standard Performance Acceptable
-→ **flask-backend-engineer**
+→ **Flask** (python-backend-engineer with framework=flask)
 **Use When:**
 - < 1000 requests per second
 - Response time requirements moderate
@@ -127,7 +127,7 @@ Choose between `fastapi-backend-engineer` and `flask-backend-engineer` based on
 ### 3. What is your team's experience level?
 
 #### Python Beginners to Intermediate
-→ **flask-backend-engineer**
+→ **Flask** (python-backend-engineer with framework=flask)
 **Reasoning:**
 - Simpler concepts and patterns
 - Extensive tutorials and examples
@@ -135,7 +135,7 @@ Choose between `fastapi-backend-engineer` and `flask-backend-engineer` based on
 - Gradual learning curve
 
 #### Python Advanced or Performance-Focused Teams
-→ **fastapi-backend-engineer**
+→ **FastAPI** (python-backend-engineer with framework=fastapi)
 **Reasoning:**
 - Leverages advanced Python features
 - Type hints and modern patterns
@@ -145,7 +145,7 @@ Choose between `fastapi-backend-engineer` and `flask-backend-engineer` based on
 ### 4. What are your integration requirements?
 
 #### Modern Stack (React, Vue, Mobile Apps)
-→ **fastapi-backend-engineer**
+→ **FastAPI** (python-backend-engineer with framework=fastapi)
 **Features:**
 - Auto-generated API clients
 - OpenAPI specification
@@ -153,7 +153,7 @@ Choose between `fastapi-backend-engineer` and `flask-backend-engineer` based on
 - CORS handling built-in
 
 #### Traditional Stack (Server-rendered, jQuery)
-→ **flask-backend-engineer**
+→ **Flask** (python-backend-engineer with framework=flask)
 **Features:**
 - Template inheritance
 - Form handling with WTForms
@@ -165,7 +165,7 @@ Choose between `fastapi-backend-engineer` and `flask-backend-engineer` based on
 ### API Development
 
 #### RESTful API for Mobile App
-**Choice**: fastapi-backend-engineer
+**Choice**: FastAPI (python-backend-engineer with framework=fastapi)
 **Reasoning:**
 - Auto-generated API documentation
 - Request/response validation
@@ -173,7 +173,7 @@ Choose between `fastapi-backend-engineer` and `flask-backend-engineer` based on
 - Easy async database operations
 
 #### Enterprise API with Complex Business Logic
-**Choice**: fastapi-backend-engineer
+**Choice**: FastAPI (python-backend-engineer with framework=fastapi)
 **Reasoning:**
 - Type safety for complex data structures
 - Dependency injection for business services
@@ -183,7 +183,7 @@ Choose between `fastapi-backend-engineer` and `flask-backend-engineer` based on
 ### Web Applications
 
 #### Content Management System
-**Choice**: flask-backend-engineer
+**Choice**: Flask (python-backend-engineer with framework=flask)
 **Reasoning:**
 - Server-side rendering capabilities
 - Admin interface patterns
@@ -191,7 +191,7 @@ Choose between `fastapi-backend-engineer` and `flask-backend-engineer` based on
 - Traditional web architecture
 
 #### E-commerce Platform
-**Choice**: flask-backend-engineer
+**Choice**: Flask (python-backend-engineer with framework=flask)
 **Reasoning:**
 - Complex form handling (checkout, admin)
 - Server-side rendering for SEO
@@ -201,7 +201,7 @@ Choose between `fastapi-backend-engineer` and `flask-backend-engineer` based on
 ### Hybrid Applications
 
 #### SaaS Platform (Web + API)
-**Primary Choice**: fastapi-backend-engineer
+**Primary Choice**: FastAPI (python-backend-engineer with framework=fastapi)
 **Reasoning:**
 - API-first for modern frontend
 - WebSocket for real-time features
@@ -215,7 +215,7 @@ Choose between `fastapi-backend-engineer` and `flask-backend-engineer` based on
 ### Specific Scenarios
 
 #### Microservices Architecture
-**Choice**: fastapi-backend-engineer
+**Choice**: FastAPI (python-backend-engineer with framework=fastapi)
 **Features:**
 - Smaller, focused services
 - Async communication between services
@@ -223,7 +223,7 @@ Choose between `fastapi-backend-engineer` and `flask-backend-engineer` based on
 - High performance per service
 
 #### Machine Learning API
-**Choice**: fastapi-backend-engineer
+**Choice**: FastAPI (python-backend-engineer with framework=fastapi)
 **Features:**
 - Async model inference
 - Request validation for ML inputs
@@ -231,7 +231,7 @@ Choose between `fastapi-backend-engineer` and `flask-backend-engineer` based on
 - WebSocket for real-time predictions
 
 #### Legacy System Integration
-**Choice**: flask-backend-engineer
+**Choice**: Flask (python-backend-engineer with framework=flask)
 **Features:**
 - Established integration patterns
 - Flexible architecture for custom needs
@@ -240,8 +240,8 @@ Choose between `fastapi-backend-engineer` and `flask-backend-engineer` based on
 
 #### Startup MVP
 **Choice**: Depends on team and product
-- **Technical team building API**: fastapi-backend-engineer
-- **Mixed team building web app**: flask-backend-engineer
+- **Technical team building API**: FastAPI (python-backend-engineer with framework=fastapi)
+- **Mixed team building web app**: Flask (python-backend-engineer with framework=flask)
 
 ## Performance Comparison
 

package/autopm/.claude/agents/decision-matrices/ui-framework-selection.md

@@ -31,26 +31,26 @@ Use this matrix to choose the right UI framework agent based on your project req
 ### Project Type
 
 #### Enterprise Applications
-**Primary Choice: antd-react-expert**
+**Primary Choice: react-ui-expert**
 - Pre-built complex components (ProTable, ProForm)
 - Enterprise-grade data management
 - Professional design language
 - Built-in admin patterns
 
-**Alternative: mui-react-expert**
+**Alternative: react-frontend-engineer**
 - Material Design consistency
 - DataGrid for complex tables
 - Strong TypeScript support
 - Large ecosystem
 
 #### Startup/MVP
-**Primary Choice: bootstrap-ui-expert**
+**Primary Choice: react-ui-expert**
 - Fastest development time
 - Extensive pre-built templates
 - Strong community resources
 - Easy developer onboarding
 
-**Alternative: chakra-ui-expert**
+**Alternative: react-frontend-engineer**
 - Modern developer experience
 - Excellent component composition
 - Built-in accessibility
@@ -63,7 +63,7 @@ Use this matrix to choose the right UI framework agent based on your project req
 - Utility-first approach
 - Optimal performance
 
-**Alternative: chakra-ui-expert**
+**Alternative: react-frontend-engineer**
 - Styled-system approach
 - Design tokens
 - Easy customization
@@ -72,43 +72,43 @@ Use this matrix to choose the right UI framework agent based on your project req
 ### Team Expertise
 
 #### Junior Developers
-1. **bootstrap-ui-expert** - Familiar patterns, extensive docs
-2. **chakra-ui-expert** - Intuitive API, good defaults
-3. **mui-react-expert** - Material Design guidelines
+1. **react-ui-expert** - Familiar patterns, extensive docs
+2. **react-frontend-engineer** - Intuitive API, good defaults
+3. **react-frontend-engineer** - Material Design guidelines
 
 #### Senior/Design Teams
 1. **tailwindcss-expert** - Full control, custom systems
-2. **chakra-ui-expert** - Balanced flexibility/productivity
-3. **mui-react-expert** - Advanced patterns, customization
+2. **react-frontend-engineer** - Balanced flexibility/productivity
+3. **react-frontend-engineer** - Advanced patterns, customization
 
 ### Technical Requirements
 
 #### Performance Critical
 1. **tailwindcss-expert** - Purged CSS, optimal bundles
-2. **chakra-ui-expert** - Tree-shakeable, efficient
-3. **bootstrap-ui-expert** - Minimal JS overhead
+2. **react-frontend-engineer** - Tree-shakeable, efficient
+3. **react-ui-expert** - Minimal JS overhead
 
 #### Accessibility Required
-1. **chakra-ui-expert** - Accessibility-first design
-2. **mui-react-expert** - ARIA compliance built-in
-3. **antd-react-expert** - Enterprise accessibility
+1. **react-frontend-engineer** - Accessibility-first design
+2. **react-frontend-engineer** - ARIA compliance built-in
+3. **react-ui-expert** - Enterprise accessibility
 
 #### Mobile-First
 1. **tailwindcss-expert** - Mobile-first utilities
-2. **bootstrap-ui-expert** - Mobile-first grid
-3. **chakra-ui-expert** - Responsive design patterns
+2. **react-ui-expert** - Mobile-first grid
+3. **react-frontend-engineer** - Responsive design patterns
 
 ### Industry/Domain
 
 #### Financial Services
-**Primary: antd-react-expert**
+**Primary: react-ui-expert**
 - Data-heavy interfaces
 - Professional appearance
 - Complex forms/tables
 - Enterprise features
 
 #### Healthcare
-**Primary: mui-react-expert**
+**Primary: react-frontend-engineer**
 - Accessibility compliance
 - Professional UI standards
 - Form-heavy applications
@@ -122,7 +122,7 @@ Use this matrix to choose the right UI framework agent based on your project req
 - Marketing integration
 
 #### SaaS Products
-**Primary: chakra-ui-expert**
+**Primary: react-frontend-engineer**
 - Modern user expectations
 - Dashboard interfaces
 - Component flexibility
@@ -138,13 +138,13 @@ Use this matrix to choose the right UI framework agent based on your project req
 
 #### From Material-UI v4 → v5
 - **Reason**: Keep existing investment
-- **Agent**: mui-react-expert
+- **Agent**: react-frontend-engineer
 - **Effort**: Moderate (migration guide available)
 - **Benefits**: Better performance, new features
 
 #### From Custom CSS → Component Library
 - **Reason**: Faster development, consistency
-- **Agent**: chakra-ui-expert (modern) or bootstrap-ui-expert (familiar)
+- **Agent**: react-frontend-engineer (modern) or react-ui-expert (familiar)
 - **Effort**: Moderate to High
 - **Benefits**: Accessibility, maintainability
 
@@ -153,41 +153,41 @@ Use this matrix to choose the right UI framework agent based on your project req
 Ask these questions to determine the best agent:
 
 1. **What is the primary use case?**
-   - Admin dashboard → antd-react-expert
-   - Marketing site → bootstrap-ui-expert or tailwindcss-expert
-   - SaaS product → chakra-ui-expert or mui-react-expert
+   - Admin dashboard → react-ui-expert
+   - Marketing site → react-ui-expert or tailwindcss-expert
+   - SaaS product → react-frontend-engineer or react-frontend-engineer
 
 2. **What is the team's experience level?**
-   - Junior team → bootstrap-ui-expert or chakra-ui-expert
-   - Senior team → tailwindcss-expert or mui-react-expert
+   - Junior team → react-ui-expert or react-frontend-engineer
+   - Senior team → tailwindcss-expert or react-frontend-engineer
 
 3. **How important is design flexibility?**
    - Critical → tailwindcss-expert
-   - Important → chakra-ui-expert
-   - Standard → mui-react-expert or antd-react-expert
-   - Basic → bootstrap-ui-expert
+   - Important → react-frontend-engineer
+   - Standard → react-frontend-engineer or react-ui-expert
+   - Basic → react-ui-expert
 
 4. **What are the performance requirements?**
-   - Critical → tailwindcss-expert or chakra-ui-expert
-   - Important → mui-react-expert (with optimization)
-   - Standard → antd-react-expert or bootstrap-ui-expert
+   - Critical → tailwindcss-expert or react-frontend-engineer
+   - Important → react-frontend-engineer (with optimization)
+   - Standard → react-ui-expert or react-frontend-engineer
 
 5. **Is accessibility a requirement?**
-   - Critical → chakra-ui-expert or mui-react-expert
-   - Important → antd-react-expert
-   - Standard → bootstrap-ui-expert or tailwindcss-expert (with extra work)
+   - Critical → react-frontend-engineer or react-ui-expert
+   - Important → react-ui-expert
+   - Standard → react-ui-expert or tailwindcss-expert (with extra work)
 
 6. **What type of data interfaces are needed?**
-   - Complex tables → antd-react-expert or mui-react-expert
+   - Complex tables → react-ui-expert or react-frontend-engineer
    - Forms → All frameworks suitable
-   - Charts/visualization → mui-react-expert or tailwindcss-expert
-   - Simple content → bootstrap-ui-expert or chakra-ui-expert
+   - Charts/visualization → react-frontend-engineer or tailwindcss-expert
+   - Simple content → react-ui-expert or react-frontend-engineer
 
 ## Agent Selection Examples
 
 ### Example 1: B2B SaaS Dashboard
 **Requirements**: Professional look, complex data tables, user management, responsive
-**Choice**: antd-react-expert
+**Choice**: react-ui-expert
 **Reasoning**: ProTable for data, enterprise components, professional design
 
 ### Example 2: Consumer Mobile App
@@ -197,15 +197,15 @@ Ask these questions to determine the best agent:
 
 ### Example 3: Startup MVP
 **Requirements**: Fast development, standard UI patterns, small team, limited budget
-**Choice**: bootstrap-ui-expert
+**Choice**: react-ui-expert
 **Reasoning**: Fastest development, familiar patterns, extensive resources
 
 ### Example 4: Design System Creation
 **Requirements**: Component library, design tokens, accessibility, maintainability
-**Choice**: chakra-ui-expert
+**Choice**: react-frontend-engineer
 **Reasoning**: Built for design systems, accessibility-first, component composition
 
 ### Example 5: Material Design Application
 **Requirements**: Google Material Design, complex components, data visualization
-**Choice**: mui-react-expert
+**Choice**: react-frontend-engineer
 **Reasoning**: Official Material Design implementation, advanced components

package/autopm/.claude/agents/devops/github-operations-specialist.md

@@ -300,7 +300,7 @@ Before delivering GitHub configurations:
 
 - **react-frontend-engineer**: Frontend deployment workflows
 - **python-backend-engineer**: Backend CI/CD pipelines
-- **playwright-test-engineer**: E2E testing in workflows
+- **frontend-testing-engineer**: E2E testing in workflows
 - **kubernetes-orchestrator**: Deployment to K8s clusters
 - **azure-devops-specialist**: Cross-platform integration
 

package/autopm/.claude/agents/frameworks/README.md

@@ -9,22 +9,22 @@ Specialized agents for specific frameworks and libraries. These agents understan
 - **Styling**: Tailwind CSS, CSS-in-JS, responsive design
 - **Features**: SSR/SSG, performance optimization, accessibility
 
-### 🎭 playwright-test-engineer
+### 🎭 frontend-testing-engineer
 - **Expertise**: Playwright, E2E testing, visual regression
 - **Features**: Cross-browser testing, parallel execution
 - **Integration**: MCP browser control, CI/CD pipelines
 
-### 🎭 playwright-mcp-frontend-tester
+### 🎭 frontend-testing-engineer
 - **Expertise**: Advanced Playwright with MCP browser control
 - **Features**: Visual testing, accessibility audits, UX validation
 - **Specialties**: Real browser control, performance monitoring, WCAG compliance
 
-### 🚀 fastapi-backend-engineer
+### 🚀 python-backend-engineer
 - **Expertise**: FastAPI, Pydantic, async Python, OpenAPI
 - **Features**: High-performance APIs, WebSockets, background tasks
 - **Integration**: SQLAlchemy, Redis, Celery, authentication
 
-### 🍶 flask-backend-engineer
+### 🍶 python-backend-engineer
 - **Expertise**: Flask, Blueprints, Flask extensions ecosystem
 - **Features**: Web apps, REST APIs, Jinja2 templates
 - **Integration**: Flask-SQLAlchemy, Flask-Login, Flask-RESTful
@@ -43,7 +43,7 @@ Specialized agents for specific frameworks and libraries. These agents understan
 - **Expertise**: Next.js 14+, App Router, Server Components
 - **Features**: ISR, API routes, middleware
 
-### 🔥 fastapi-backend-engineer
+### 🔥 python-backend-engineer
 - **Expertise**: FastAPI, Pydantic, async Python
 - **Features**: OpenAPI, WebSocket, background tasks
 

package/autopm/.claude/agents/frameworks/e2e-test-engineer.md

@@ -192,7 +192,7 @@ test('visual regression', async ({ page }) => {
 - mcp__playwright__fill
 
 ## Integration Points
-- Tests applications from: react-ui-expert, python-backend-expert
+- Tests applications from: react-frontend-engineer, python-backend-engineer
 - Validates deployments by: kubernetes-orchestrator
 - Reports to: github-operations-specialist
 - Uses infrastructure from: docker-containerization-expert

package/autopm/.claude/agents/frameworks/nats-messaging-expert.md

@@ -130,7 +130,7 @@ Use these queries:
 
 ## Integration Points
 
-- Works with: kubernetes-orchestrator, docker-expert, nodejs-backend-engineer, python-backend-engineer, github-operations-specialist
+- Works with: kubernetes-orchestrator, docker-containerization-expert, nodejs-backend-engineer, python-backend-engineer, github-operations-specialist
 - Provides to: Microservices, event systems, real-time apps, distributed systems
 - Client libraries: Go, Python, Node.js, Java, C#, Rust
 

package/autopm/.claude/agents/frameworks/react-frontend-engineer.md

@@ -191,7 +191,7 @@ Before delivering code:
 **Integration with Other Agents:**
 
 - **python-backend-engineer**: API contract definition and type generation
-- **playwright-test-engineer**: E2E test scenarios and component interaction testing
+- **frontend-testing-engineer**: E2E test scenarios and component interaction testing
 - **azure-devops-specialist**: CI/CD pipeline for build and deployment
 - **github-operations-specialist**: PR workflows and code review automation
 

package/autopm/.claude/agents/frameworks/react-ui-expert.md

@@ -137,9 +137,9 @@ accessibility_level:
 - Agent
 
 ## Integration Points
-- Works with: react-frontend-engineer, playwright-test-engineer
-- Provides UI for: python-backend-expert, nodejs-backend-engineer
-- Tested by: e2e-test-engineer
+- Works with: react-frontend-engineer, frontend-testing-engineer
+- Provides UI for: python-backend-engineer, nodejs-backend-engineer
+- Tested by: frontend-testing-engineer
 
 ## Example Invocation