claude-autopm 1.10.1 → 1.10.3

package/autopm/.claude/commands/pm/prd-new.md

@@ -4,145 +4,23 @@ allowed-tools: Bash, Read, Write, LS
 
 # PRD New
 
-Launch brainstorming for new product requirement document.
+Launch interactive brainstorming session for new product requirement document.
 
 ## Usage
 ```
 /pm:prd-new <feature_name>
 ```
 
-## Required Rules
-
-**IMPORTANT:** Before executing this command, read and follow:
-- `.claude/rules/datetime.md` - For getting real current date/time
-
-## Preflight Checklist
-
-Before proceeding, complete these validation steps.
-Do not bother the user with preflight checks progress ("I'm not going to ..."). Just do them and move on.
-
-### Input Validation
-1. **Validate feature name format:**
-   - Must contain only lowercase letters, numbers, and hyphens
-   - Must start with a letter
-   - No spaces or special characters allowed
-   - If invalid, tell user: "❌ Feature name must be kebab-case (lowercase letters, numbers, hyphens only). Examples: user-auth, payment-v2, notification-system"
-
-2. **Check for existing PRD:**
-   - Check if `.claude/prds/$ARGUMENTS.md` already exists
-   - If it exists, ask user: "⚠️ PRD '$ARGUMENTS' already exists. Do you want to overwrite it? (yes/no)"
-   - Only proceed with explicit 'yes' confirmation
-   - If user says no, suggest: "Use a different name or run: /pm:prd-parse $ARGUMENTS to create an epic from the existing PRD"
-
-3. **Verify directory structure:**
-   - Check if `.claude/prds/` directory exists
-   - If not, create it first
-   - If unable to create, tell user: "❌ Cannot create PRD directory. Please manually create: .claude/prds/"
-
 ## Instructions
 
-You are a product manager creating a comprehensive Product Requirements Document (PRD) for: **$ARGUMENTS**
-
-Follow this structured approach:
-
-### 1. Discovery & Context
-- Ask clarifying questions about the feature/product "$ARGUMENTS"
-- Understand the problem being solved
-- Identify target users and use cases
-- Gather constraints and requirements
-
-### 2. PRD Structure
-Create a comprehensive PRD with these sections:
-
-#### Executive Summary
-- Brief overview and value proposition
-
-#### Problem Statement
-- What problem are we solving?
-- Why is this important now?
-
-#### User Stories
-- Primary user personas
-- Detailed user journeys
-- Pain points being addressed
-
-#### Requirements
-**Functional Requirements**
-- Core features and capabilities
-- User interactions and flows
-
-**Non-Functional Requirements**
-- Performance expectations
-- Security considerations
-- Scalability needs
-
-#### Success Criteria
-- Measurable outcomes
-- Key metrics and KPIs
-
-#### Constraints & Assumptions
-- Technical limitations
-- Timeline constraints
-- Resource limitations
-
-#### Out of Scope
-- What we're explicitly NOT building
-
-#### Dependencies
-- External dependencies
-- Internal team dependencies
-
-### 3. File Format with Frontmatter
-Save the completed PRD to: `.claude/prds/$ARGUMENTS.md` with this exact structure:
-
-```markdown
----
-name: $ARGUMENTS
-description: [Brief one-line description of the PRD]
-status: backlog
-created: [Current ISO date/time]
----
-
-# PRD: $ARGUMENTS
-
-## Executive Summary
-[Content...]
-
-## Problem Statement
-[Content...]
-
-[Continue with all sections...]
-```
-
-### 4. Frontmatter Guidelines
-- **name**: Use the exact feature name (same as $ARGUMENTS)
-- **description**: Write a concise one-line summary of what this PRD covers
-- **status**: Always start with "backlog" for new PRDs
-- **created**: Get REAL current datetime by running: `date -u +"%Y-%m-%dT%H:%M:%SZ"`
-  - Never use placeholder text
-  - Must be actual system time in ISO 8601 format
-
-### 5. Quality Checks
-
-Before saving the PRD, verify:
-- [ ] All sections are complete (no placeholder text)
-- [ ] User stories include acceptance criteria
-- [ ] Success criteria are measurable
-- [ ] Dependencies are clearly identified
-- [ ] Out of scope items are explicitly listed
-
-### 6. Post-Creation
-
-After successfully creating the PRD:
-1. Confirm: "✅ PRD created: .claude/prds/$ARGUMENTS.md"
-2. Show brief summary of what was captured
-3. Suggest next step: "Ready to create implementation epic? Run: /pm:prd-parse $ARGUMENTS"
-
-## Error Recovery
+Run `node .claude/scripts/pm/prd-new.js $ARGUMENTS` using the Bash tool and show me the complete output.
 
-If any step fails:
-- Clearly explain what went wrong
-- Provide specific steps to fix the issue
-- Never leave partial or corrupted files
+This will launch an interactive brainstorming session that will:
+1. Prompt for product vision
+2. Gather information about target users
+3. Collect key features through interactive prompts
+4. Define success metrics
+5. Capture technical considerations
+6. Generate a comprehensive PRD with proper frontmatter
 
-Conduct a thorough brainstorming session before writing the PRD. Ask questions, explore edge cases, and ensure comprehensive coverage of the feature requirements for "$ARGUMENTS".
+The script handles all validation, creates the necessary directories, and saves the PRD to `.claude/prds/$ARGUMENTS.md`.

package/autopm/.claude/teams.json

@@ -0,0 +1,52 @@
+{
+  "base": {
+    "description": "Core agents available in all teams.",
+    "agents": [
+      "code-analyzer.md",
+      "file-analyzer.md",
+      "test-runner.md",
+      "agent-manager.md"
+    ]
+  },
+  "devops": {
+    "description": "Team for CI/CD, containerization, and infrastructure tasks.",
+    "inherits": ["base"],
+    "agents": [
+      "docker-containerization-expert.md",
+      "kubernetes-orchestrator.md",
+      "github-operations-specialist.md",
+      "azure-devops-specialist.md",
+      "terraform-infrastructure-expert.md"
+    ]
+  },
+  "python_backend": {
+    "description": "Team specializing in Python backend development.",
+    "inherits": ["base"],
+    "agents": [
+      "python-backend-expert.md",
+      "fastapi-backend-engineer.md",
+      "flask-backend-engineer.md",
+      "postgresql-expert.md",
+      "mongodb-expert.md"
+    ]
+  },
+  "frontend": {
+    "description": "Team for JavaScript/TypeScript UI development.",
+    "inherits": ["base"],
+    "agents": [
+      "react-ui-expert.md",
+      "javascript-frontend-engineer.md",
+      "e2e-test-engineer.md",
+      "ux-design-expert.md",
+      "tailwindcss-expert.md"
+    ]
+  },
+  "fullstack": {
+    "description": "Complete team combining frontend and backend capabilities.",
+    "inherits": [
+      "frontend",
+      "python_backend"
+    ],
+    "agents": []
+  }
+}

package/bin/autopm.js

@@ -159,7 +159,7 @@ function main() {
 📖 Quick Start:
    autopm install                    # Install ClaudeAutoPM in current directory
    autopm team load frontend         # Load React/UI development agents
-   claude --bypass-permissions .     # Open Claude Code
+   claude --dangerously-skip-permissions .     # Open Claude Code
 
 🔧 Configuration Setup:
    # View current configuration
@@ -224,7 +224,7 @@ function main() {
       autopm config set github.repo <repository>
       export GITHUB_TOKEN=<your-token>
    3. autopm team load fullstack   # Load appropriate agents
-   4. claude --bypass-permissions . # Open Claude Code
+   4. claude --dangerously-skip-permissions . # Open Claude Code
    5. /pm:validate                 # Verify GitHub integration
 
    6. /pm:prd-new user-auth        # Create Product Requirements Document
@@ -244,7 +244,7 @@ function main() {
       autopm config set azure.project <project>
       export AZURE_DEVOPS_PAT=<your-pat>
    3. autopm team load fullstack   # Load appropriate agents
-   4. claude --bypass-permissions . # Open Claude Code
+   4. claude --dangerously-skip-permissions . # Open Claude Code
    5. /pm:validate                 # Verify Azure DevOps integration
 
    6. /pm:prd-new user-auth        # Create Product Requirements Document

package/bin/commands/config.js

@@ -79,13 +79,28 @@ class ConfigCommand {
 
     console.log('│                                         │');
 
-    // Features - always show them
-    const dockerStatus = config.features?.dockerFirst ? '✅ Enabled' : '❌ Disabled';
-    console.log(`│ Docker First:    ${this.padRight(dockerStatus, 22)} │`);
-
-    const k8sStatus = config.features?.kubernetes ? '✅ Enabled' : '❌ Disabled';
+    // Installation Configuration - check both new and legacy formats
+    const dockerEnabled = config.tools?.docker?.enabled || config.features?.dockerFirst || false;
+    const dockerFirst = config.tools?.docker?.first || false;
+    const dockerStatus = dockerEnabled ? (dockerFirst ? '✅ Enabled (First)' : '✅ Enabled') : '❌ Disabled';
+    console.log(`│ Docker:          ${this.padRight(dockerStatus, 22)} │`);
+
+    const k8sEnabled = config.tools?.kubernetes?.enabled || config.features?.kubernetes || false;
+    const k8sStatus = k8sEnabled ? '✅ Enabled' : '❌ Disabled';
     console.log(`│ Kubernetes:      ${this.padRight(k8sStatus, 22)} │`);
 
+    // Execution strategy - check both formats
+    const executionStrategy = config.execution_strategy || config.execution?.strategy || 'adaptive';
+    console.log(`│ Execution:       ${this.padRight(executionStrategy, 22)} │`);
+
+    // Show parallel limit if hybrid strategy
+    if (executionStrategy === 'hybrid' && config.parallel_limit) {
+      console.log(`│ Parallel Limit:  ${this.padRight(config.parallel_limit.toString(), 22)} │`);
+    }
+
+    console.log('│                                         │');
+
+    // Features - optional/legacy features
     const mcpStatus = config.features?.mcp ? '✅ Enabled' : '❌ Disabled';
     console.log(`│ MCP:             ${this.padRight(mcpStatus, 22)} │`);
 
@@ -96,12 +111,6 @@ class ConfigCommand {
     const cicdPlatform = config.features?.cicd || 'not configured';
     console.log(`│ CI/CD:           ${this.padRight(cicdPlatform, 22)} │`);
 
-    console.log('│                                         │');
-
-    // Execution strategy
-    const executionStrategy = config.execution?.strategy || 'adaptive';
-    console.log(`│ Execution:       ${this.padRight(executionStrategy, 22)} │`);
-
     // Current team
     const currentTeam = config.teams?.current || 'base';
     console.log(`│ Team:            ${this.padRight(currentTeam, 22)} │`);

package/install/install.js

@@ -39,8 +39,10 @@ class Installer {
       '.claude/rules',
       '.claude/scripts',
       '.claude/checklists',
+      '.claude/strategies',
       '.claude/mcp',
       '.claude/.env.example',
+      '.claude/teams.json',
       '.claude-code'
     ];
 
@@ -345,11 +347,34 @@ ${this.colors.BOLD}Examples:${this.colors.NC}
     console.log(`
 ${this.colors.BOLD}Select installation scenario:${this.colors.NC}
 
-1. ${this.colors.CYAN}Minimal${this.colors.NC} - Sequential execution, no Docker/K8s
-2. ${this.colors.CYAN}Docker-only${this.colors.NC} - Adaptive execution with Docker
-3. ${this.colors.GREEN}Full DevOps${this.colors.NC} - Adaptive execution with all features ${this.colors.BOLD}(RECOMMENDED)${this.colors.NC}
-4. ${this.colors.YELLOW}Performance${this.colors.NC} - Hybrid parallel execution for power users
-5. ${this.colors.CYAN}Custom${this.colors.NC} - Configure manually
+${this.colors.CYAN}1. Minimal${this.colors.NC} - Traditional development workflow
+   • Sequential agent execution (one at a time)
+   • Native tooling: npm, pip, local installs
+   • Best for: Simple projects, learning, debugging
+   • No containers or orchestration
+
+${this.colors.CYAN}2. Docker-only${this.colors.NC} - Containerized local development
+   • Adaptive execution (smart sequential/parallel choice)
+   • Docker containers for development environment
+   • Best for: Microservices, consistent environments
+   • Local Docker only, no Kubernetes
+
+${this.colors.GREEN}3. Full DevOps${this.colors.NC} - Complete CI/CD pipeline ${this.colors.BOLD}(RECOMMENDED)${this.colors.NC}
+   • Adaptive execution with Docker-first priority
+   • Kubernetes manifests and cloud deployment ready
+   • GitHub Actions with KIND clusters and Kaniko builds
+   • Best for: Production applications, enterprise projects
+
+${this.colors.YELLOW}4. Performance${this.colors.NC} - Maximum parallel execution
+   • Hybrid strategy: up to 5 parallel agents
+   • Advanced context isolation and security
+   • Full DevOps capabilities with speed optimization
+   • Best for: Large projects, massive refactoring, power users
+
+${this.colors.CYAN}5. Custom${this.colors.NC} - Manual configuration
+   • Configure execution strategy manually
+   • Choose your own agents and workflows
+   • Advanced users only
 `);
 
     if (process.env.AUTOPM_TEST_MODE === '1') {

package/lib/guide/interactive-guide.js

@@ -304,7 +304,7 @@ class InteractiveGuide {
         '🎯 Installation Complete - How to Use ClaudeAutoPM\n\n' +
         'ClaudeAutoPM is now installed! To start using it:\n\n' +
         '1. 📂 Open Claude Code in this directory\n' +
-        '2. 🔓 If needed: claude --bypass-permissions\n' +
+        '2. 🔓 If needed: claude --dangerously-skip-permissions\n' +
         '3. ✅ Test with: /pm:validate\n\n' +
         'Then you can:\n' +
         '• 🔧 Configure your provider (GitHub/Azure DevOps)\n' +
@@ -540,7 +540,7 @@ class InteractiveGuide {
       '4. Sync with your configured provider\n\n' +
       '🚀 Next Steps - Open Claude Code:\n\n' +
       '1. Open Claude Code in this directory\n' +
-      '2. If needed, run: claude --bypass-permissions\n' +
+      '2. If needed, run: claude --dangerously-skip-permissions\n' +
       '3. Then use these PM commands:',
       [
         `/pm:prd-new ${featureName} --template`,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-autopm",
-  "version": "1.10.1",
+  "version": "1.10.3",
   "description": "Autonomous Project Management Framework for Claude Code - Advanced AI-powered development automation",
   "main": "bin/autopm.js",
   "bin": {