claude-mpm 5.1.9__py3-none-any.whl → 5.4.22__py3-none-any.whl

claude_mpm/commands/mpm-agents-recommend.md

@@ -1,223 +0,0 @@
----
-namespace: mpm/agents
-command: recommend
-aliases: [mpm-agents-recommend]
-migration_target: /mpm/agents:recommend
-category: agents
-deprecated_aliases: []
-description: Get intelligent agent recommendations based on detected project toolchain
----
-# Show recommended agents for detected project stack
-
-Get intelligent agent recommendations based on your project's detected toolchain.
-
-## Usage
-
-```
-/mpm-agents-recommend
-```
-
-## Description
-
-This command analyzes your detected project stack and recommends the most appropriate agents, organized by priority:
-- **Essential agents**: Core agents required for your primary stack
-- **Recommended agents**: Complementary agents for full functionality
-- **Optional agents**: Specialized agents for detected tools
-
-Each recommendation includes an explanation of why that agent is suggested.
-
-## Implementation
-
-When you run `/mpm-agents-recommend`, the PM will execute:
-```bash
-claude-mpm agents recommend
-```
-
-This runs the detection phase and then applies recommendation rules to suggest the best agents for your specific technology stack.
-
-## Expected Output
-
-```
-🤖 Agent Recommendations
-=========================
-
-Based on detected stack:
-  Python 3.11, FastAPI 0.104.0, pytest, Docker, Vercel
-
-Essential Agents (Must Have):
-  ✓ fastapi-engineer
-    Reason: FastAPI framework detected - specialized agent for FastAPI development
-    Capabilities: FastAPI routes, Pydantic models, async endpoints, dependency injection
-
-  ✓ python-engineer
-    Reason: Python project - general Python development support
-    Capabilities: Python code, testing, debugging, package management
-
-  ✓ api-qa
-    Reason: API testing for FastAPI backend
-    Capabilities: API endpoint testing, validation, load testing, contract testing
-
-Recommended Agents (Strongly Suggested):
-  ○ docker-ops
-    Reason: Docker configuration detected
-    Capabilities: Docker builds, container management, docker-compose orchestration
-
-  ○ vercel-ops
-    Reason: Vercel deployment configuration found
-    Capabilities: Vercel deployments, serverless functions, domain management
-
-  ○ playwright-qa
-    Reason: Comprehensive E2E testing capability
-    Capabilities: Browser automation, visual testing, API testing
-
-Optional Agents (Nice to Have):
-  ○ local-ops-agent
-    Reason: Local development and PM2 process management
-    Capabilities: Local server management, port handling, PM2 operations
-
-  ○ security-agent
-    Reason: Security scanning and best practices
-    Capabilities: Dependency scanning, code security, auth patterns
-
-Summary:
-  Recommended: 3 essential + 2 recommended = 5 agents
-  Optional: 2 additional agents for enhanced capabilities
-
-  Total recommended deployment: 5 agents
-  Maximum useful deployment: 7 agents
-
-Next Steps:
-  1. Review recommendations above
-  2. Run '/mpm-auto-configure --preview' to see deployment plan
-  3. Run '/mpm-auto-configure' to deploy recommended agents
-  4. Or deploy individually: '/mpm-agents deploy <agent-name>'
-```
-
-## Recommendation Logic
-
-### Python Projects
-
-**If FastAPI detected:**
-- Essential: fastapi-engineer, python-engineer, api-qa
-- Recommended: docker-ops (if Docker), vercel-ops (if Vercel)
-
-**If Flask detected:**
-- Essential: flask-engineer, python-engineer, api-qa
-- Recommended: docker-ops (if Docker)
-
-**If Django detected:**
-- Essential: django-engineer, python-engineer, api-qa
-- Recommended: docker-ops (if Docker)
-
-**If pytest detected:**
-- Add to recommended: api-qa, playwright-qa
-
-### JavaScript/TypeScript Projects
-
-**If Next.js detected:**
-- Essential: nextjs-engineer, react-engineer, web-qa
-- Recommended: playwright-qa, vercel-ops (if Vercel)
-
-**If React detected (without Next.js):**
-- Essential: react-engineer, web-qa
-- Recommended: playwright-qa
-
-**If Vue detected:**
-- Essential: vue-engineer, web-qa
-- Recommended: playwright-qa
-
-**If Express detected:**
-- Essential: node-engineer, api-qa
-- Recommended: docker-ops (if Docker)
-
-**If Nest.js detected:**
-- Essential: nestjs-engineer, node-engineer, api-qa
-- Recommended: docker-ops (if Docker)
-
-### Full-Stack Projects
-
-**Python backend + React frontend:**
-- Essential: fastapi-engineer (or flask-engineer), python-engineer, react-engineer, api-qa, web-qa
-- Recommended: playwright-qa, docker-ops, local-ops-agent
-
-**Node.js backend + React frontend:**
-- Essential: node-engineer, react-engineer, api-qa, web-qa
-- Recommended: playwright-qa, docker-ops
-
-### Testing-Focused Projects
-
-**If Playwright detected:**
-- Add to recommended: playwright-qa
-
-**If Jest/Vitest detected:**
-- Ensure web-qa or api-qa in recommended
-
-### Deployment-Focused Projects
-
-**If Vercel detected:**
-- Add to recommended: vercel-ops
-
-**If Railway detected:**
-- Add to recommended: railway-ops
-
-**If Docker detected:**
-- Add to recommended: docker-ops
-
-**If PM2 detected:**
-- Add to recommended: local-ops-agent
-
-## Agent Descriptions
-
-### Backend Specialists
-- **fastapi-engineer**: FastAPI expert - routes, Pydantic, async, websockets
-- **flask-engineer**: Flask expert - blueprints, extensions, templates
-- **django-engineer**: Django expert - models, views, ORM, admin
-- **node-engineer**: Node.js expert - Express, async, streams
-- **nestjs-engineer**: NestJS expert - modules, decorators, DI
-
-### Frontend Specialists
-- **nextjs-engineer**: Next.js expert - app router, server components, SSR
-- **react-engineer**: React expert - hooks, state, components
-- **vue-engineer**: Vue expert - composition API, components
-
-### QA Specialists
-- **api-qa**: API testing expert - REST, GraphQL, validation
-- **web-qa**: Web testing expert - fetch, integration, E2E
-- **playwright-qa**: Browser automation expert - UI testing, visual regression
-
-### Ops Specialists
-- **docker-ops**: Docker expert - builds, compose, containers
-- **vercel-ops**: Vercel deployment expert - serverless, edge
-- **railway-ops**: Railway deployment expert
-- **local-ops-agent**: Local development expert - PM2, ports, processes
-
-## Use Cases
-
-1. **Planning**: Understand what agents you should deploy before starting work
-2. **Validation**: Verify that auto-configuration will suggest the right agents
-3. **Learning**: Discover what capabilities are available for your stack
-4. **Optimization**: Find additional agents that could enhance your workflow
-
-## Tips
-
-1. **Start here**: Run this before `/mpm-auto-configure` to preview recommendations
-2. **Essential vs Optional**: Focus on essential agents first, add others as needed
-3. **Stack-specific**: Recommendations are tailored to YOUR detected stack
-4. **Flexible**: You can always deploy additional agents later or skip some
-5. **Explanations**: Pay attention to the "Reason" for each recommendation
-
-## Customizing Recommendations
-
-After seeing recommendations, you can:
-1. **Accept all**: Run `/mpm-auto-configure` to deploy all recommended agents
-2. **Pick and choose**: Deploy specific agents with `/mpm-agents deploy <name>`
-3. **Skip optional**: Deploy only essential and recommended agents
-4. **Add more**: Deploy additional agents not in recommendations
-
-## Related Commands
-
-- `/mpm-agents-detect` - See what was detected in your project
-- `/mpm-auto-configure` - Automatically deploy recommended agents
-- `/mpm-agents deploy <name>` - Deploy specific agents manually
-- `/mpm-agents` - View all available and deployed agents
-- `/mpm-help agents` - Learn more about agent management

claude_mpm/commands/mpm-config-view.md

@@ -1,150 +0,0 @@
----
-namespace: mpm/config
-command: view
-aliases: [mpm-config-view]
-migration_target: /mpm/config:view
-category: config
-deprecated_aliases: [mpm-config]
-description: View and validate Claude MPM configuration settings
----
-# View and validate claude-mpm configuration
-
-Manage Claude MPM configuration settings through validation, viewing, and status checks.
-
-## Usage
-
-```
-/mpm-config [subcommand] [options]
-```
-
-## Description
-
-This slash command provides access to Claude MPM's configuration management capabilities through the actual CLI commands.
-
-## Available Subcommands
-
-### Validate Configuration
-Validate configuration files for correctness and completeness.
-
-```
-/mpm-config validate [--config-file PATH] [--strict] [--fix]
-```
-
-**Options:**
-- `--config-file PATH`: Validate specific config file (default: all)
-- `--strict`: Use strict validation rules
-- `--fix`: Attempt to fix validation errors automatically
-
-**Example:**
-```
-/mpm-config validate --strict
-/mpm-config validate --config-file .claude/config.yaml --fix
-```
-
-### View Configuration
-Display current configuration settings.
-
-```
-/mpm-config view [--section SECTION] [--format FORMAT] [--show-defaults]
-```
-
-**Options:**
-- `--section SECTION`: Specific configuration section to view
-- `--format FORMAT`: Output format (yaml, json, table)
-- `--show-defaults`: Include default values in output
-
-**Examples:**
-```
-/mpm-config view
-/mpm-config view --section agents --format json
-/mpm-config view --show-defaults
-```
-
-### Configuration Status
-Show configuration health and status.
-
-```
-/mpm-config status [--verbose]
-```
-
-**Options:**
-- `--verbose`: Show detailed status information
-
-**Example:**
-```
-/mpm-config status --verbose
-```
-
-## Implementation
-
-This command executes:
-```bash
-claude-mpm config [subcommand] [options]
-```
-
-The slash command passes through to the actual CLI configuration management system.
-
-## Configuration Categories
-
-Configuration is organized into sections:
-
-- **agents**: Agent deployment and management settings
-- **memory**: Memory system configuration
-- **websocket**: WebSocket server settings (port, host)
-- **hooks**: Hook service configuration
-- **logging**: Logging levels and output
-- **tickets**: Ticket tracking settings
-- **monitor**: Dashboard and monitoring settings
-
-## Expected Output
-
-### Validation Output
-```
-Validating configuration files...
-
-✓ .claude/config.yaml: Valid
-✓ .claude/agents/config.yaml: Valid
-✓ Configuration schema: Valid
-
-Configuration is valid and ready to use.
-```
-
-### View Output
-```yaml
-agents:
-  deploy_mode: project
-  auto_reload: true
-
-websocket:
-  host: localhost
-  port: 8765
-
-logging:
-  level: INFO
-  format: detailed
-```
-
-### Status Output
-```
-Configuration Status
-====================
-
-Files Found: 2
-  ✓ .claude/config.yaml
-  ✓ .claude/agents/config.yaml
-
-Validation: Passed
-Schema Version: 4.5
-Last Modified: 2025-01-15 14:30:22
-
-Active Settings:
-  - WebSocket Port: 8765
-  - Agent Deploy Mode: project
-  - Logging Level: INFO
-```
-
-## Related Commands
-
-- `/mpm-status`: Show overall system status
-- `/mpm-doctor`: Diagnose configuration issues
-- `/mpm-init`: Initialize project configuration

claude_mpm/commands/mpm-ticket-organize.md

@@ -1,304 +0,0 @@
----
-namespace: mpm/ticket
-command: organize
-aliases: [mpm-ticket-organize]
-migration_target: /mpm/ticket:organize
-category: tickets
-deprecated_aliases: [mpm-organize]
-description: Organize project files into proper directories with intelligent pattern detection
----
-# /mpm-organize
-
-Organize your project files into proper directories using intelligent pattern detection and framework-aware structure management.
-
-## Usage
-
-```
-/mpm-organize                       # Interactive mode with preview
-/mpm-organize --dry-run             # Preview changes without applying
-/mpm-organize --force               # Proceed even with uncommitted changes
-/mpm-organize --no-backup           # Skip backup creation (not recommended)
-```
-
-## Description
-
-This slash command delegates to the **Project Organizer agent** to perform thorough project housekeeping. The agent analyzes your project structure, detects existing patterns and framework conventions, then organizes files into proper directories following best practices.
-
-**Smart Organization**: The agent follows the official [Project Organization Standard](../../../docs/reference/PROJECT_ORGANIZATION.md), which defines comprehensive organization rules for Claude MPM projects. It also checks CLAUDE.md for project-specific guidelines and respects framework-specific conventions.
-
-**Standard Documentation**: After organizing, this command ensures the organization standard is documented and accessible at `docs/reference/PROJECT_ORGANIZATION.md` with proper linking from CLAUDE.md.
-
-## Features
-
-- **📁 Intelligent Pattern Detection**: Analyzes existing directory structure and naming conventions
-- **🎯 Framework-Aware**: Respects Next.js, React, Django, Rails, and other framework patterns
-- **🔍 CLAUDE.md Integration**: Follows project-specific guidelines when available
-- **✅ Safe Operations**: Uses `git mv` for tracked files to preserve history
-- **💾 Automatic Backups**: Creates backups before major reorganizations
-- **🔄 Import Path Updates**: Updates import statements after file moves
-- **📊 Organization Report**: Detailed summary of changes and recommendations
-
-## Options
-
-### Safety Options
-- `--dry-run`: Preview all changes without making them (recommended first run)
-- `--no-backup`: Skip backup creation before reorganization (not recommended)
-- `--force`: Proceed even with uncommitted changes (use with caution)
-
-### Organization Options
-- `--docs-only`: Only organize documentation files
-- `--tests-only`: Only organize test files
-- `--scripts-only`: Only organize script files
-- `--skip-imports`: Don't update import paths after moves
-
-### Output Options
-- `--verbose`: Show detailed analysis and reasoning
-- `--quiet`: Minimal output, errors only
-- `--report [path]`: Save organization report to file
-
-## What This Command Does
-
-### 1. Organization Standard Verification
-- Ensures `docs/reference/PROJECT_ORGANIZATION.md` exists and is current
-- Creates or updates the standard if needed
-- Links the standard from CLAUDE.md for easy reference
-
-### 2. CLAUDE.md Analysis
-- Checks for existing organization guidelines
-- Extracts project-specific rules and conventions
-- Identifies priority areas for organization
-
-### 3. Project Structure Detection
-- Scans directory hierarchy and patterns
-- Identifies naming conventions (camelCase, kebab-case, snake_case)
-- Maps current file type locations
-- Detects framework-specific conventions (Next.js, Django, Rails, etc.)
-- Determines organization type (feature/type/domain-based)
-
-### 4. File Organization Strategy
-
-The agent organizes files into standard directories per [PROJECT_ORGANIZATION.md](../../../docs/reference/PROJECT_ORGANIZATION.md):
-
-```
-docs/           # All documentation files (*.md, guides, architecture)
-tests/          # All test files and test utilities
-tmp/            # Temporary and ephemeral files
-scripts/        # Ad-hoc scripts and utilities
-src/            # Source code following framework conventions
-.claude/        # Claude MPM configuration and agents
-```
-
-### 5. Framework-Specific Handling
-
-**Next.js Projects**:
-- Respects `pages/`, `app/`, `public/`, API routes
-- Organizes components by feature or domain
-- Maintains Next.js conventions
-
-**Django Projects**:
-- Maintains app structure
-- Organizes migrations, templates, static files
-- Preserves Django conventions
-
-**React Projects**:
-- Organizes components, hooks, utils
-- Maintains component hierarchy
-- Groups related files
-
-**Other Frameworks**:
-- Detects and respects framework conventions
-- Applies appropriate organizational patterns
-
-### 6. Safe File Movement
-
-For each file to be moved:
-1. Analyzes file purpose and dependencies
-2. Determines optimal location based on patterns
-3. Uses `git mv` for version-controlled files
-4. Updates import paths in affected files
-5. Validates build still works
-
-### 7. Backup Creation
-
-Before major reorganization:
-```bash
-backup_YYYYMMDD_HHMMSS.tar.gz  # Complete project backup
-```
-
-### 8. Import Path Updates
-
-Automatically updates:
-- Python imports (`from old.path import X` → `from new.path import X`)
-- JavaScript/TypeScript imports (`import X from './old/path'` → `import X from './new/path'`)
-- Relative path references
-- Configuration file paths
-
-### 9. Organization Report
-
-Generates detailed report including:
-- Files moved and their new locations
-- Pattern analysis and detected conventions
-- Import paths updated
-- Recommendations for further improvements
-- Violations of best practices (if any)
-
-## Examples
-
-### Preview Organization (Recommended First Run)
-```bash
-/mpm-organize --dry-run
-```
-Shows what would be changed without making any modifications.
-
-### Full Organization with Backup
-```bash
-/mpm-organize
-```
-Interactive mode with automatic backup before changes.
-
-### Force Organization (With Uncommitted Changes)
-```bash
-/mpm-organize --force --verbose
-```
-Organizes project even with uncommitted changes, shows detailed output.
-
-### Organize Documentation Only
-```bash
-/mpm-organize --docs-only --dry-run
-```
-Preview how documentation files would be organized.
-
-### Quick Organization Without Backup
-```bash
-/mpm-organize --no-backup
-```
-Skip backup creation for small changes (use with caution).
-
-### Save Organization Report
-```bash
-/mpm-organize --report /tmp/organize-report.md
-```
-Save detailed report to file for review.
-
-## Implementation
-
-This slash command delegates to the **Project Organizer agent** (`project-organizer`), which performs intelligent file organization based on detected patterns and framework conventions.
-
-The agent receives the command options as context and then:
-1. Analyzes CLAUDE.md for organization guidelines
-2. Detects project framework and patterns
-3. Identifies misplaced files
-4. Creates safe reorganization plan
-5. Executes file moves with git integration
-6. Updates import paths across codebase
-7. Validates build integrity
-8. Generates organization report
-
-When you invoke `/mpm-organize [options]`, Claude MPM:
-- Passes the options to the Project Organizer agent as task context
-- The agent executes the organization workflow
-- Results are returned to you through the agent's structured output
-
-## Expected Output
-
-### Dry Run Mode
-```
-🔍 Analyzing project structure...
-✓ Detected framework: Next.js
-✓ Organization pattern: Feature-based
-✓ Found CLAUDE.md guidelines
-
-📁 Proposed Changes:
-
-  docs/
-    ← README_OLD.md (from root)
-    ← architecture-notes.txt (from root)
-
-  tests/
-    ← test_helper.py (from src/)
-    ← api.test.js (from src/api/)
-
-  tmp/
-    ← debug_output.log (from root)
-    ← scratch.py (from root)
-
-  scripts/
-    ← migrate.sh (from root)
-    ← deploy_helper.py (from root)
-
-📊 Summary:
-  - 8 files to move
-  - 12 import paths to update
-  - 0 conflicts detected
-
-Run without --dry-run to apply changes.
-```
-
-### Actual Organization
-```
-🔍 Analyzing project structure...
-✓ Detected framework: Next.js
-✓ Organization pattern: Feature-based
-✓ Created backup: backup_20250102_143022.tar.gz
-
-📁 Organizing files...
-  ✓ Moved README_OLD.md → docs/
-  ✓ Moved architecture-notes.txt → docs/
-  ✓ Updated 5 import statements
-
-✅ Organization complete!
-
-📊 Report saved to: /tmp/organization-report.md
-```
-
-## Safety Guarantees
-
-- **Backup Created**: Full project backup before changes (unless --no-backup)
-- **Git Integration**: Uses `git mv` to preserve file history
-- **Dry Run Available**: Preview all changes before applying
-- **Import Updates**: Automatically fixes broken imports
-- **Build Validation**: Verifies build still works after changes
-- **Rollback Support**: Backup enables full rollback if needed
-
-## When to Use This Command
-
-Use `/mpm-organize` when:
-- Starting a new project and establishing structure
-- Project has accumulated misplaced files
-- After major feature additions
-- Before major refactoring
-- When onboarding new team members
-- To enforce organization standards
-
-## Best Practices
-
-1. **Always Start with Dry Run**: Use `--dry-run` first to preview changes
-2. **Commit First**: Commit your work before organizing (or use --force)
-3. **Review CLAUDE.md**: Ensure guidelines are current before organizing
-4. **Test After**: Run tests after organization to verify nothing broke
-5. **Update Documentation**: Document any new organizational patterns
-
-## Notes
-
-- This slash command delegates to the **Project Organizer agent** (`project-organizer`)
-- The agent performs intelligent file placement based on learned patterns
-- Respects framework-specific conventions automatically
-- Integrates with git to preserve file history
-- Updates import paths to prevent build breakage
-- Creates comprehensive reports for audit trails
-- Can be run repeatedly safely (idempotent)
-- Follows guidelines in CLAUDE.md when available
-- Falls back to framework conventions and best practices
-
-## Related Documentation
-
-- **[Project Organization Standard](../../../docs/reference/PROJECT_ORGANIZATION.md)**: Comprehensive organization rules and guidelines
-- **[Project Structure](../../../docs/developer/STRUCTURE.md)**: Authoritative file organization reference
-- **[CLAUDE.md](../../../CLAUDE.md)**: Development guidelines with organization quick reference
-
-## Related Commands
-
-- `/mpm-init`: Initialize or update project documentation and structure
-- `/mpm-doctor`: Diagnose project health and issues
-- `/mpm-status`: Check current project state
-- `/mpm-config`: Configure organization rules and preferences