Package Exports
- claude-autopm
- claude-autopm/bin/autopm.js
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (claude-autopm) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
ClaudeAutoPM
Automated project management system to ship faster better using spec-driven development and AI agents running in parallel
Stop losing context. Stop blocking on tasks. Stop shipping bugs. ClaudeAutoPM transforms PRDs into epics, epics into issues, and issues into production code โ with full traceability at every step.
๐ Documentation
Full documentation is available at: https://rafeekpro.github.io/ClaudeAutoPM/
- ๐ Complete Guide
- ๐ Command Reference
- ๐ค Agent Registry
- ๐ง Development Guide
- โ๏ธ Configuration
๐ฏ Key Features
Hybrid Command System
ClaudeAutoPM uses a hybrid approach combining deterministic operations with AI-powered intelligence:
| Command Type | Implementation | Use Case | Example |
|---|---|---|---|
| Deterministic | JavaScript/Templates | Scaffolding, templates, automation | autopm docker:create, autopm scaffold:api |
| AI-Powered | Claude Code + Markdown | Analysis, brainstorming, decomposition | /pm:prd-new, /pm:epic-decompose |
| Hybrid | Both modes available | Flexible workflows | pm:prd-new --template or /pm:prd-new |
Core Capabilities
- 96+ Professional CLI Commands - Full yargs-based CLI with comprehensive PM commands
- Hybrid Execution - Choose between templates (deterministic) or AI assistance
- AI Agent Integration - Parallel execution with specialized agents (in Claude Code)
- Dynamic Agent Teams - Switch between specialized agent teams based on context (DevOps, Frontend, Backend, Fullstack)
- Azure DevOps & GitHub - Complete project management integration
- Smart Context Management - Never lose track of your work
- Automated Workflows - From PRD to production deployment
๐ Get Started in 5 Minutes
๐ฏ Quick Start for New Users
npm install -g claude-autopm
# Run the interactive guide
autopm guideThe interactive guide will walk you through:
- โ System requirements verification
- ๐ฆ Installation with preset selection
- โ๏ธ Provider configuration (GitHub/Azure DevOps/Local)
- ๐ค Agent team management and automatic switching
- ๐ Creating your first PRD and project workflow
- ๐ Troubleshooting and diagnostics
- ๐ Complete documentation and resources
Manual Setup
1. Install (30 seconds)
npm install -g claude-autopm2. Setup Your Project (2 minutes)
# Navigate to your project
cd your-project/
# Install ClaudeAutoPM framework
autopm installDuring installation, you'll be asked to:
1. Choose a configuration preset:
| Preset | Description | Best For |
|---|---|---|
| Minimal | Traditional development without containers | Small projects, beginners |
| Docker-only | Container-first with adaptive execution | Medium projects, local development |
| Full DevOps ๐ฏ | Docker + Kubernetes with CI/CD | Production projects (RECOMMENDED) |
| Performance | Maximum parallelization (8 agents) | Large projects, powerful machines |
| Custom | Configure each option manually | Specific requirements |
2. Select your project management provider:
| Provider | Integration | Use Case |
|---|---|---|
| GitHub Issues | Full GitHub API integration | Open source, startups |
| Azure DevOps | Azure Boards & Pipelines | Enterprise, Agile teams |
| Skip for now | Local files only | Evaluation, offline work |
3. Initialize PM System (1 minute)
# In Claude Code, run:
/pm:init
# Create your CLAUDE.md with repository info:
/init include rules from .claude/CLAUDE.md3.5 Provider Configuration (NEW)
# View current configuration
autopm config show
# Switch to Azure DevOps
autopm config set provider azure
autopm config set azure.organization your-org
autopm config set azure.project your-project
export AZURE_DEVOPS_PAT=your-token
# Switch to GitHub
autopm config set provider github
autopm config set github.owner your-username
autopm config set github.repo your-repo
export GITHUB_TOKEN=your-token
# Quick switch between providers
autopm config switch azure
autopm config switch github
# Validate configuration
autopm config validate4. Ship Your First Feature (90 seconds)
Option A: Using Templates (Works Everywhere)
# Create PRD from template
autopm pm:prd-new user-auth --template
# Convert PRD to basic epic structure
autopm pm:prd-parse user-auth --basic
# Generate tasks from template
autopm pm:epic-decompose user-auth --template backend
# Push to GitHub/Azure DevOps
autopm pm:epic-sync user-authOption B: AI-Powered in Claude Code
# Create PRD through AI brainstorming
/pm:prd-new user-auth
# AI-powered PRD analysis and epic creation
/pm:prd-parse user-auth
# Intelligent task decomposition
/pm:epic-decompose user-auth
# Push to GitHub and start building
/pm:epic-sync user-authThat's it! You're now using structured, spec-driven development with AI agents.
๐ฏ Core Workflow: Crawl โ Walk โ Run
Crawl: Basic Commands
/pm:prd-new feature # Create product requirements
/pm:epic-oneshot feature # Plan, decompose, and sync to GitHub
/pm:issue-start 1234 # Start working on a task
/pm:next # Get next priority taskWalk: Team Collaboration
/pm:status # Project dashboard
/pm:standup # Daily standup report
/pm:issue-sync 1234 # Push progress to GitHub
/pm:blocked # Show blocked tasksRun: Advanced Features
- 50+ Specialized AI Agents - Python, React, K8s, AWS, and more
- Parallel Execution - Multiple agents working simultaneously
- Cross-Platform - GitHub, Azure DevOps, GitLab (coming soon)
- MCP Integration - Context management and browser automation
๐ค Dynamic Agent Teams
ClaudeAutoPM now supports dynamic agent teams that can be switched based on your current context:
# List available teams
autopm team list
# Load a specialized team
autopm team load devops # CI/CD and infrastructure agents
autopm team load frontend # React, JavaScript, UX agents
autopm team load python_backend # Python, FastAPI, Flask agents
autopm team load fullstack # Combined frontend + backend
# Check current team
autopm team current๐ Automatic Team Switching
ClaudeAutoPM can automatically switch teams based on your Git branch name!
Setup (one-time):
# Enable automatic team switching
bash scripts/setup-githooks.shBranch Naming Convention:
# Branch pattern: type/team/description
git checkout -b feature/devops/add-ci # Auto-loads 'devops' team
git checkout -b fix/frontend/button-style # Auto-loads 'frontend' team
git checkout -b feat/backend/new-api # Auto-loads 'python_backend' teamAvailable Teams:
- base - Core agents for general tasks
- devops - Docker, Kubernetes, GitHub Operations, Terraform
- frontend - React, JavaScript, E2E testing, UX design
- python_backend - FastAPI, Flask, PostgreSQL, MongoDB
- fullstack - Inherits from both frontend and python_backend
Teams support inheritance, so specialized teams automatically include base agents. The active team configuration is saved in your project and persists across sessions.
๐ Full Documentation
For comprehensive guides, advanced features, and detailed configuration:
๐ Visit the ClaudeAutoPM Wiki
CLI System (96 Commands)
ClaudeAutoPM features a professional CLI powered by yargs with 96 commands:
# View all commands
autopm --help
# Command categories:
# - Azure DevOps (39 commands)
# - Project Management (32 commands)
# - AI & Automation (2 commands)
# - Infrastructure & DevOps (7 commands)
# - Testing & Context (5 commands)
# - UI & Frontend (6 commands)
# - Utilities (5 commands)
# Examples:
autopm pm:init --type web
autopm azure:sprint-status
autopm context:createNew in v1.9.x: Complete PM Command Suite
The latest release includes 17 new PM commands providing comprehensive project management capabilities:
PRD & Epic Management
# Create new Product Requirements Document
autopm pm:prd-new user-authentication --description "OAuth 2.0 integration"
# Parse PRD into executable epic with tasks
autopm pm:prd-parse user-authentication --overwrite
# Close completed epic
autopm pm:epic-close user-auth "All authentication features complete"Issue Lifecycle
# Start working on an issue
autopm pm:issue-start ISSUE-123
# Show issue details and progress
autopm pm:issue-show ISSUE-123
# Edit issue details
autopm pm:issue-edit ISSUE-123 --title "Updated: Fix authentication bug"
# Close completed issue
autopm pm:issue-close ISSUE-123 "Fixed OAuth redirect issue"Pull Request Workflow
# Create PR with auto-generated description
autopm pm:pr-create "feat: implement OAuth authentication"
# List all open PRs
autopm pm:pr-list --status open
# Create draft PR for work in progress
autopm pm:pr-create "wip: user dashboard" --draftContext Management
# Create development context for feature
autopm pm:context-create user-authentication
# Update context with current progress
autopm pm:context-update user-authentication
# Prime context for AI assistance
autopm pm:context-prime user-authenticationProject Maintenance
# Optimize project structure and reduce context size
autopm pm:optimize --apply
# Clean archived work and free up space
autopm pm:clean --archive-old
# Sync work state across team
autopm pm:sync --push-remote
# Create versioned release
autopm pm:release minor --tag "v1.2.0"Popular Topics
- Configuration Options
- Agent Registry (50+ agents)
- Command Reference
- Docker & Kubernetes
- Azure DevOps Integration
๐ก What Makes This Different?
| Traditional Development | ClaudeAutoPM System |
|---|---|
| Context lost between sessions | Persistent context across all work |
| Serial task execution | Parallel agents on independent tasks |
| "Vibe coding" from memory | Spec-driven with full traceability |
| Progress hidden in branches | Transparent audit trail in GitHub |
| Manual task coordination | Intelligent prioritization with /pm:next |
๐ Key Principles
- No Vibe Coding - Every line traces back to a specification
- GitHub as Database - Issues are the single source of truth
- Parallel by Default - Multiple agents, maximum velocity
- Context Preservation - Never lose project state again
๐ ๏ธ System Requirements
- Node.js >= 16.0.0
- npm >= 8.0.0
- Git (system installation)
- Claude Code or compatible AI assistant
๐งช Testing
Running Tests
# Run all unit tests (default)
npm test
# Run Azure DevOps integration tests (requires Azure environment)
npm run test:azure:integrationTest Separation
Tests are separated into unit and integration categories:
- Unit tests - Run without external dependencies (default)
- Integration tests - Require Azure DevOps environment variables:
AZURE_DEVOPS_PAT- Personal Access TokenAZURE_DEVOPS_ORG- Organization nameAZURE_DEVOPS_PROJECT- Project name
To run integration tests, set AZURE_DEVOPS_INTEGRATION_TESTS=true along with the required environment variables.
๐ Configuration Preset Details
Feature Comparison
| Feature | Minimal | Docker-only | Full DevOps | Performance |
|---|---|---|---|---|
| Docker Support | โ | โ | โ | โ |
| Kubernetes | โ | โ | โ | โ |
| Git Safety Hooks | โ | โ | โ | โ |
| CI/CD Simulation (TODO) | โ | โ | โ | โ |
| Max Parallel Agents | 1 | 3 | 5 | 8 |
| Execution Strategy | Sequential | Adaptive | Adaptive | Hybrid |
| Context Optimization (TODO) | โ | โ | โ | โ |
| Integration Tests | โ | โ | โ | โ |
| Learning Mode (TODO) | โ | โ | โ | โ |
Execution Strategies
- Sequential: Safe, one agent at a time, predictable
- Adaptive: Intelligent parallelization based on task complexity (learning mode planned)
- Hybrid: Maximum parallelization, fastest but requires monitoring
When to Choose Each Preset
Minimal
- New to ClaudeAutoPM
- Small personal projects
- No Docker environment available
- Learning the system
Docker-only
- Medium-sized projects
- Local development focus
- Docker available but not Kubernetes
- Team of 2-10 developers
Full DevOps (Recommended)
- Production projects
- CI/CD pipelines required
- Enterprise environments
- Teams with DevOps practices
- Best balance of features and safety
Performance
- Large codebases (>100k LOC)
- Powerful development machines (16+ cores)
- Experienced teams
- When build speed is critical
What Gets Installed
All presets install the same core files:
.claude/agents/- AI agent definitions.claude/commands/- PM command library.claude/rules/- Development rules.claude/scripts/- Helper scripts.claude/checklists/- Development checklists.claude/mcp/- Model Context Protocol configs
Optional components (based on preset):
- Git hooks โ
.git/hooks/(Docker-only, Full DevOps, Performance) - Docker configurations โ
.claude/docker/(all except Minimal) - Kubernetes manifests โ
.claude/k8s/(Full DevOps, Performance) - CI/CD templates โ
.github/workflows/or.azure-pipelines/
Git Hooks Installation
Git hooks install in two phases:
Automatic enablement (based on preset):
- Minimal: No hooks
- Docker-only, Full DevOps, Performance: Hooks enabled
User confirmation (if enabled):
Would you like to install git hooks for automated commit/push validation? (y/n)- Yes โ Installs
pre-commitandpre-pushhooks - No โ Skips, can install later with
.claude/scripts/setup-hooks.sh
- Yes โ Installs
Provider Integration Details
GitHub Issues
- Creates issues and PRs via GitHub API
- Syncs epics as GitHub milestones
- Requires:
GITHUB_TOKENwith repo scope - Commands: All
pm:*plusgithub:*commands
Azure DevOps โจ NEW: Full 3-Level Hierarchy Support
- Epic โ User Story โ Task hierarchy (full Azure DevOps model)
- Integrates with Azure Boards work items
- Automatic parent-child linking of work items
- Syncs with Azure Pipelines
- Requires:
AZURE_DEVOPS_PATwith Work Items scope - Commands: All
pm:*plusazure:*commands
Azure DevOps Workflow Example:
# Configure for Azure DevOps
autopm config set provider azure
autopm config set azure.organization mycompany
autopm config set azure.project myproject
# Create and decompose PRD (creates Epic โ User Stories โ Tasks)
autopm pm:prd-new payment-gateway
autopm pm:epic-decompose payment-gateway # Creates 3-level hierarchy
# Sync to Azure DevOps - creates linked work items
autopm pm:epic-sync payment-gateway
# โ
Created Epic #1234 "Payment Gateway Integration"
# โ
Created User Story #1235 "As a user, I want to pay with credit card"
# โ
Created Task #1236 "Implement Stripe API integration"
# โ
Created Task #1237 "Add payment form validation"
# โ
Created User Story #1238 "As a user, I want to see payment history"
# โ
Created Task #1239 "Create payment history endpoint"
# โ
Created Task #1240 "Build payment history UI"
# Work items are automatically linked with parent-child relationships
# View in Azure Boards to see the full hierarchy visualizationSkip for now
- All data stored locally in
.claude/ - No external synchronization
- Can migrate to provider later
- Perfect for evaluation or offline work
๐ Support This Project
If ClaudeAutoPM helps your team ship better:
- โญ Star this repository
- ๐ฆ Try on npm
- ๐ฆ Follow @rafeekpro on X
Built by developers who ship, for developers who ship.
Inspired by CCPM - Building upon the foundation of AI-powered project management.