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

claude_mpm/cli/ticket_cli.py

@@ -1,35 +0,0 @@
-from pathlib import Path
-
-# \!/usr/bin/env python3
-"""
-Ticket CLI module for claude-mpm.
-
-This module provides the entry point for the 'ticket' alias command.
-It delegates to the scripts/ticket.py module for implementation.
-"""
-
-import sys
-
-
-def main():
-    """Main entry point for ticket CLI alias."""
-    # Import and run the main ticket CLI
-    try:
-        # Try to import from scripts
-        scripts_dir = Path(__file__).parent.parent.parent.parent / "scripts"
-        sys.path.insert(0, str(scripts_dir))
-
-        from ticket import main as ticket_main
-
-        return ticket_main()
-    except ImportError:
-        print("Error: Ticket functionality not available")
-        print("Install ai-trackdown-pytools: pip install ai-trackdown-pytools")
-        return 1
-    except Exception as e:
-        print(f"Error running ticket command: {e}")
-        return 1
-
-
-if __name__ == "__main__":
-    sys.exit(main())

claude_mpm/commands/mpm-agents-auto-configure.md

@@ -1,278 +0,0 @@
----
-namespace: mpm/agents
-command: auto-configure
-aliases: [mpm-agents-auto-configure]
-migration_target: /mpm/agents:auto-configure
-category: agents
-deprecated_aliases: [mpm-auto-configure]
-description: Automatically detect project toolchain and configure appropriate agents
----
-# Automatically configure agents based on project detection
-
-Automatically detect your project's toolchain and configure the most appropriate agents.
-
-## Usage
-
-```
-/mpm-auto-configure [options]
-```
-
-## Description
-
-This command provides intelligent auto-configuration that:
-1. Scans your project to detect programming languages, frameworks, and tools
-2. Recommends the most appropriate agents for your stack
-3. Optionally deploys the recommended agents with confirmation
-
-This is the fastest way to get started with Claude MPM in any project!
-
-## Options
-
-- `--preview` - Show what would be configured without making any changes
-- `--yes` - Automatically apply recommendations without prompting
-- `--force` - Force reconfiguration even if agents are already deployed
-
-## Implementation
-
-When you run `/mpm-auto-configure`, the PM will:
-
-1. **Detect Your Stack**:
-   - Scan for package.json, requirements.txt, Cargo.toml, go.mod, etc.
-   - Identify frameworks (FastAPI, Next.js, React, Express, etc.)
-   - Detect testing tools (pytest, Jest, Playwright, etc.)
-   - Find build tools and deployment configurations
-
-2. **Recommend Agents**:
-   - **Essential agents**: Required for your primary stack
-   - **Recommended agents**: Complementary agents for full functionality
-   - **Optional agents**: Specialized agents for detected tools
-
-3. **Deploy Agents** (with confirmation):
-   - Show what will be deployed
-   - Request confirmation (unless --yes is used)
-   - Deploy agents to your project
-   - Verify deployment success
-
-## Examples
-
-### Preview Mode (Recommended First Step)
-```
-/mpm-auto-configure --preview
-```
-Shows what would be configured without making changes. Great for understanding recommendations before applying.
-
-### Interactive Configuration
-```
-/mpm-auto-configure
-```
-Detect, recommend, and prompt for confirmation before deploying.
-
-### Automatic Configuration
-```
-/mpm-auto-configure --yes
-```
-Automatically apply all recommendations without prompting. Best for quick setup.
-
-### Force Reconfiguration
-```
-/mpm-auto-configure --force
-```
-Reconfigure agents even if some are already deployed. Useful for stack changes.
-
-## Expected Output
-
-```
-🤖 Auto-Configuration for Claude MPM
-=====================================
-
-Step 1: Detecting Project Stack
---------------------------------
-✓ Detected Python 3.11
-✓ Detected FastAPI 0.104.0
-✓ Detected pytest 7.4.0
-✓ Detected Docker configuration
-✓ Detected Vercel deployment
-
-Step 2: Agent Recommendations
-------------------------------
-Essential Agents (3):
-  ✓ fastapi-engineer - FastAPI framework detected
-  ✓ python-engineer - Python project support
-  ✓ api-qa - API testing and validation
-
-Recommended Agents (2):
-  ○ docker-ops - Docker configuration found
-  ○ vercel-ops - Vercel deployment detected
-
-Optional Agents (1):
-  ○ playwright-qa - Browser testing capability
-
-Step 3: Deploy Agents
----------------------
-Deploy 5 agents? (y/n): y
-
-Deploying agents...
-✓ fastapi-engineer deployed
-✓ python-engineer deployed
-✓ api-qa deployed
-✓ docker-ops deployed
-✓ vercel-ops deployed
-
-🎉 Auto-configuration complete!
-5 agents deployed successfully.
-
-Next steps:
-- Run /mpm-agents to see your deployed agents
-- Start working with specialized agents for your stack
-- Use /mpm-help for more information
-```
-
-## What Gets Detected
-
-### Languages
-- Python (CPython, PyPy)
-- JavaScript/TypeScript (Node.js, Deno, Bun)
-- Rust
-- Go
-- Java
-
-### Python Frameworks
-- FastAPI
-- Flask
-- Django
-- Starlette
-- Pyramid
-
-### JavaScript/TypeScript Frameworks
-- Next.js
-- React
-- Vue
-- Svelte
-- Angular
-- Express
-- Nest.js
-- Fastify
-
-### Testing Tools
-- pytest (Python)
-- unittest (Python)
-- Jest (JavaScript)
-- Vitest (JavaScript)
-- Playwright (Browser)
-- Cypress (Browser)
-
-### Build Tools
-- Vite
-- Webpack
-- Rollup
-- esbuild
-- Turbopack
-
-### Deployment Platforms
-- Vercel
-- Railway
-- Docker
-- PM2
-- Kubernetes
-
-## Agent Mapping Examples
-
-### Python + FastAPI
-**Essential:**
-- fastapi-engineer
-- python-engineer
-- api-qa
-
-**Recommended:**
-- docker-ops (if Docker detected)
-- vercel-ops (if Vercel detected)
-
-### Next.js + React
-**Essential:**
-- nextjs-engineer
-- react-engineer
-- web-qa
-
-**Recommended:**
-- playwright-qa (if Playwright detected)
-- vercel-ops (if Vercel detected)
-
-### Full-Stack (FastAPI + React)
-**Essential:**
-- fastapi-engineer
-- python-engineer
-- react-engineer
-- api-qa
-- web-qa
-
-**Recommended:**
-- playwright-qa
-- docker-ops
-- local-ops-agent
-
-## Default Configuration Fallback
-
-When auto-configuration cannot detect your project's toolchain (e.g., a new or uncommon language/framework), it automatically falls back to a sensible set of default general-purpose agents instead of leaving your project unconfigured.
-
-### When Defaults are Applied
-
-Default agents are deployed when:
-- Primary language is detected as "Unknown"
-- No specific framework or toolchain can be identified
-- No agent recommendations can be generated from detected technologies
-
-### Default Agents
-
-The following general-purpose agents are recommended with moderate confidence (0.7):
-
-- **engineer**: General-purpose engineer for code implementation
-- **research**: Code exploration and analysis
-- **qa**: Testing and quality assurance
-- **ops**: Infrastructure and deployment operations
-- **documentation**: Documentation and technical writing
-
-All default recommendations will be marked with `is_default: True` in the metadata.
-
-### Disabling Default Fallback
-
-To disable the default configuration fallback, edit `.claude-mpm/config/agent_capabilities.yaml`:
-
-```yaml
-default_configuration:
-  enabled: false  # Disable default fallback
-```
-
-When disabled, auto-configuration will recommend zero agents if the toolchain cannot be detected.
-
-### Customizing Defaults
-
-You can customize which agents are deployed by default by editing the `default_configuration.agents` section in `.claude-mpm/config/agent_capabilities.yaml`:
-
-```yaml
-default_configuration:
-  enabled: true
-  min_confidence: 0.7  # Confidence score for default recommendations
-  agents:
-    - agent_id: engineer
-      reasoning: "General-purpose engineer for code implementation"
-      priority: 1
-    - agent_id: research
-      reasoning: "Code exploration and analysis"
-      priority: 2
-    # Add or remove agents as needed
-```
-
-## Tips
-
-1. **Start with preview**: Always run with `--preview` first to see recommendations
-2. **Review carefully**: Check that detected stack matches your project
-3. **Customize later**: You can always deploy/remove agents manually after auto-config
-4. **Re-run after changes**: Run again with `--force` if you add new frameworks
-5. **Complementary commands**: Use `/mpm-agents-detect` and `/mpm-agents-recommend` for more details
-
-## Related Commands
-
-- `/mpm-agents-detect` - Just show detected toolchain
-- `/mpm-agents-recommend` - Show recommendations without deploying
-- `/mpm-agents` - Manage agents manually
-- `/mpm-help agents` - Learn about manual agent management

claude_mpm/commands/mpm-agents-detect.md

@@ -1,177 +0,0 @@
----
-namespace: mpm/agents
-command: detect
-aliases: [mpm-agents-detect]
-migration_target: /mpm/agents:detect
-category: agents
-deprecated_aliases: []
-description: Scan project to detect programming languages, frameworks, tools, and configurations
----
-# Detect project toolchain and frameworks
-
-Scan your project to detect programming languages, frameworks, tools, and configurations.
-
-## Usage
-
-```
-/mpm-agents-detect
-```
-
-## Description
-
-This command scans your project directory to automatically detect:
-- Programming languages and their versions
-- Web frameworks and libraries
-- Testing tools and frameworks
-- Build tools and bundlers
-- Package managers
-- Deployment configurations
-
-This is useful for understanding what Claude MPM can detect in your project before running auto-configuration.
-
-## Implementation
-
-When you run `/mpm-agents-detect`, the PM will execute:
-```bash
-claude-mpm agents detect
-```
-
-This performs a comprehensive scan of your project looking for:
-- Package manifests (package.json, requirements.txt, Cargo.toml, go.mod, pom.xml)
-- Framework-specific files (next.config.js, fastapi imports, etc.)
-- Test configurations (pytest.ini, jest.config.js, playwright.config.ts)
-- Build configurations (vite.config.js, webpack.config.js, tsconfig.json)
-- Deployment files (Dockerfile, vercel.json, railway.json)
-
-## Expected Output
-
-```
-🔍 Project Toolchain Detection
-================================
-
-Languages:
-  ✓ Python 3.11.5
-  ✓ Node.js 20.10.0
-  ✓ TypeScript 5.3.2
-
-Frameworks:
-  ✓ FastAPI 0.104.0
-  ✓ React 18.2.0
-  ✓ Next.js 14.0.4
-
-Testing:
-  ✓ pytest 7.4.3
-  ✓ Jest 29.7.0
-  ✓ Playwright 1.40.0
-
-Build Tools:
-  ✓ Vite 5.0.0
-  ✓ TypeScript Compiler
-
-Package Managers:
-  ✓ poetry (Python)
-  ✓ npm (Node.js)
-
-Deployment:
-  ✓ Docker (Dockerfile found)
-  ✓ Vercel (vercel.json found)
-  ✓ PM2 (ecosystem.config.js found)
-
-Configuration Files Detected:
-  - pyproject.toml
-  - package.json
-  - tsconfig.json
-  - next.config.js
-  - pytest.ini
-  - jest.config.js
-  - playwright.config.ts
-  - Dockerfile
-  - vercel.json
-
-Summary:
-  Full-stack project with Python backend (FastAPI) and
-  React/Next.js frontend, comprehensive testing setup,
-  and multiple deployment targets.
-```
-
-## What Gets Detected
-
-### Language Detection
-- **Python**: Looks for .py files, requirements.txt, pyproject.toml, setup.py
-- **JavaScript/TypeScript**: Looks for .js/.ts files, package.json, tsconfig.json
-- **Rust**: Looks for Cargo.toml, .rs files
-- **Go**: Looks for go.mod, .go files
-- **Java**: Looks for pom.xml, build.gradle, .java files
-
-### Framework Detection
-**Python:**
-- FastAPI (imports, decorator patterns)
-- Flask (imports, app patterns)
-- Django (settings.py, manage.py)
-
-**JavaScript/TypeScript:**
-- Next.js (next.config.js, pages/ or app/ directory)
-- React (package.json dependencies, JSX usage)
-- Vue (vue.config.js, .vue files)
-- Express (imports, app patterns)
-- Nest.js (nest-cli.json, decorators)
-
-### Testing Detection
-- pytest (pytest.ini, conftest.py)
-- unittest (test_*.py patterns)
-- Jest (jest.config.js)
-- Vitest (vitest.config.js)
-- Playwright (playwright.config.ts)
-- Cypress (cypress.json)
-
-### Build Tool Detection
-- Vite (vite.config.js/ts)
-- Webpack (webpack.config.js)
-- Rollup (rollup.config.js)
-- esbuild (esbuild configuration)
-- Turbopack (next.config.js with turbopack)
-
-### Deployment Detection
-- Docker (Dockerfile, docker-compose.yml)
-- Vercel (vercel.json, .vercel directory)
-- Railway (railway.json, railway.toml)
-- PM2 (ecosystem.config.js)
-- Kubernetes (k8s/, kubernetes/ directories)
-
-## Use Cases
-
-1. **Before Auto-Configuration**: Run this to see what will be detected
-2. **Troubleshooting**: Verify that your project setup is being recognized correctly
-3. **Documentation**: Generate a summary of your project's tech stack
-4. **Planning**: Understand what agents might be recommended
-
-## Tips
-
-1. **Run from project root**: Detection works best from your project's root directory
-2. **Check detection accuracy**: Verify detected versions match your actual setup
-3. **Missing detections**: If something isn't detected, you can still deploy agents manually
-4. **Configuration files**: Detection relies on standard configuration files being present
-
-## Common Issues
-
-**Nothing detected?**
-- Make sure you're in the project root directory
-- Check that you have standard configuration files (package.json, requirements.txt, etc.)
-- Some projects may need manual agent deployment
-
-**Wrong versions detected?**
-- Detection shows what's configured in manifest files
-- Actual runtime versions may differ
-- This doesn't affect agent functionality
-
-**Framework not detected?**
-- Some frameworks are harder to detect automatically
-- You can still use auto-configure and manually select agents
-- Or deploy specific agents manually with `/mpm-agents deploy <name>`
-
-## Related Commands
-
-- `/mpm-agents-recommend` - See agent recommendations based on detection
-- `/mpm-auto-configure` - Automatically configure agents based on detection
-- `/mpm-agents` - Manually manage agents
-- `/mpm-help auto-configure` - Learn about auto-configuration

claude_mpm/commands/mpm-agents-list.md

@@ -1,131 +0,0 @@
----
-namespace: mpm/agents
-command: list
-aliases: [mpm-agents-list]
-migration_target: /mpm/agents:list
-category: agents
-deprecated_aliases: [mpm-agents]
-description: List all available Claude MPM agents with versions and deployment status
----
-# Show available agents and their versions
-
-Show all available Claude MPM agents with their versions and deployment status.
-
-## Usage
-
-```
-/mpm-agents
-```
-
-## Description
-
-This command lists all available Claude MPM agents, including both built-in agents and any custom agents you've created. It shows their current deployment status, version information, and capabilities.
-
-## What This Command Does
-
-When you run `/mpm-agents`, I will:
-
-1. **List Available Agents**: Run `claude-mpm agents list` to show all agents
-2. **Display Agent Information**:
-   - Agent names and IDs
-   - Brief descriptions
-   - Model preferences (opus, sonnet, haiku)
-   - Tool availability
-   - Version information
-   - Deployment status
-
-## Output Example
-
-The command displays agents in a formatted table showing:
-- Agent name and description
-- Version and model preference
-- Tools available to the agent
-- Current deployment status
-
-## Implementation
-
-To show available agents, I'll execute:
-```bash
-claude-mpm agents list --deployed
-```
-
-This will display all deployed agents that are currently available for use.
-
-Alternatively, you can use these variations:
-- `claude-mpm agents list --system` - Show system agents
-- `claude-mpm agents list --by-tier` - Group agents by precedence tier
-- `claude-mpm agents list --all` - Show all agents including undeployed
-
-## Auto-Configuration Subcommands (NEW!)
-
-### Quick Agent Setup
-
-Claude MPM now includes intelligent auto-configuration that detects your project and recommends the right agents:
-
-#### `agents detect`
-Scan your project to detect toolchain and frameworks:
-```bash
-claude-mpm agents detect
-```
-
-Shows detected:
-- Programming languages (Python, Node.js, Rust, Go, etc.)
-- Frameworks (FastAPI, Next.js, React, Express, etc.)
-- Testing tools (pytest, Jest, Playwright, etc.)
-- Build tools and package managers
-- Deployment configurations
-
-#### `agents recommend`
-Get agent recommendations based on detected toolchain:
-```bash
-claude-mpm agents recommend
-```
-
-Shows:
-- Essential agents for your stack
-- Recommended complementary agents
-- Optional specialized agents
-- Rationale for each recommendation
-
-#### `auto-configure`
-Automatically detect, recommend, and deploy agents:
-```bash
-claude-mpm auto-configure --preview  # See what would be configured
-claude-mpm auto-configure            # Interactive configuration
-claude-mpm auto-configure --yes      # Auto-apply without prompts
-```
-
-**Example workflow:**
-1. Run `claude-mpm agents detect` to see what's detected
-2. Run `claude-mpm agents recommend` to see suggestions
-3. Run `claude-mpm auto-configure` to apply configuration
-4. Or skip straight to `claude-mpm auto-configure --yes`
-
-### Supported Stacks
-
-**Python:**
-- FastAPI, Flask, Django → fastapi-engineer, python-engineer
-- pytest, unittest → api-qa, python-qa
-
-**JavaScript/TypeScript:**
-- Next.js → nextjs-engineer, react-engineer
-- React, Vue, Svelte → react-engineer, web-qa
-- Express, Nest.js → node-engineer, api-qa
-- Jest, Vitest, Playwright → playwright-qa, web-qa
-
-**Full-Stack Projects:**
-Automatically recommends both frontend and backend agents based on your complete stack.
-
-**Deployment:**
-- Vercel → vercel-ops
-- Railway → railway-ops
-- Docker → docker-ops
-- PM2 → local-ops-agent
-
-## Related Commands
-
-For more information on auto-configuration:
-- `/mpm-help auto-configure` - Detailed auto-configuration help
-- `/mpm-agents-detect` - Run detection via slash command
-- `/mpm-agents-recommend` - Show recommendations via slash command
-- `/mpm-auto-configure` - Run auto-configuration via slash command