claude-autopm 1.10.2 → 1.10.4

package/autopm/.claude/commands/pm/issue-show.md

@@ -13,79 +13,12 @@ Display issue and sub-issues with detailed information.
 
 ## Instructions
 
-You are displaying comprehensive information about a GitHub issue and related sub-issues for: **Issue #$ARGUMENTS**
-
-### 1. Fetch Issue Data
-- Use `gh issue view #$ARGUMENTS` to get GitHub issue details
-- Look for local task file: first check `.claude/epics/*/$ARGUMENTS.md` (new naming)
-- If not found, search for file with `github:.*issues/$ARGUMENTS` in frontmatter (old naming)
-- Check for related issues and sub-tasks
-
-### 2. Issue Overview
-Display issue header:
-```
-🎫 Issue #$ARGUMENTS: {Issue Title}
-   Status: {open/closed}
-   Labels: {labels}
-   Assignee: {assignee}
-   Created: {creation_date}
-   Updated: {last_update}
-   
-📝 Description:
-{issue_description}
-```
-
-### 3. Local File Mapping
-If local task file exists:
-```
-📁 Local Files:
-   Task file: .claude/epics/{epic_name}/{task_file}
-   Updates: .claude/epics/{epic_name}/updates/$ARGUMENTS/
-   Last local update: {timestamp}
-```
-
-### 4. Sub-Issues and Dependencies
-Show related issues:
-```
-🔗 Related Issues:
-   Parent Epic: #{epic_issue_number}
-   Dependencies: #{dep1}, #{dep2}
-   Blocking: #{blocked1}, #{blocked2}
-   Sub-tasks: #{sub1}, #{sub2}
-```
-
-### 5. Recent Activity
-Display recent comments and updates:
-```
-💬 Recent Activity:
-   {timestamp} - {author}: {comment_preview}
-   {timestamp} - {author}: {comment_preview}
-   
-   View full thread: gh issue view #$ARGUMENTS --comments
-```
-
-### 6. Progress Tracking
-If task file exists, show progress:
-```
-✅ Acceptance Criteria:
-   ✅ Criterion 1 (completed)
-   🔄 Criterion 2 (in progress)
-   ⏸️ Criterion 3 (blocked)
-   □ Criterion 4 (not started)
-```
-
-### 7. Quick Actions
-```
-🚀 Quick Actions:
-   Start work: /pm:issue-start $ARGUMENTS
-   Sync updates: /pm:issue-sync $ARGUMENTS
-   Add comment: gh issue comment #$ARGUMENTS --body "your comment"
-   View in browser: gh issue view #$ARGUMENTS --web
-```
-
-### 8. Error Handling
-- Handle invalid issue numbers gracefully
-- Check for network/authentication issues
-- Provide helpful error messages and alternatives
-
-Provide comprehensive issue information to help developers understand context and current status for Issue #$ARGUMENTS.
+Run `node .claude/scripts/pm/issue-show.js $ARGUMENTS` using the Bash tool and show me the complete output.
+
+This will display comprehensive information about the GitHub issue including:
+1. Issue details and status
+2. Local file mappings and task files
+3. Sub-issues and dependencies
+4. Recent activity and comments
+5. Progress tracking with acceptance criteria
+6. Quick action suggestions

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/commands/pm/prd-parse.md

@@ -11,165 +11,15 @@ Convert PRD to technical implementation epic.
 /pm:prd-parse <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.
-
-### Validation Steps
-1. **Verify <feature_name> was provided as a parameter:**
-   - If not, tell user: "❌ <feature_name> was not provided as parameter. Please run: /pm:prd-parse <feature_name>"
-   - Stop execution if <feature_name> was not provided
-
-2. **Verify PRD exists:**
-   - Check if `.claude/prds/$ARGUMENTS.md` exists
-   - If not found, tell user: "❌ PRD not found: $ARGUMENTS. First create it with: /pm:prd-new $ARGUMENTS"
-   - Stop execution if PRD doesn't exist
-
-3. **Validate PRD frontmatter:**
-   - Verify PRD has valid frontmatter with: name, description, status, created
-   - If frontmatter is invalid or missing, tell user: "❌ Invalid PRD frontmatter. Please check: .claude/prds/$ARGUMENTS.md"
-   - Show what's missing or invalid
-
-4. **Check for existing epic:**
-   - Check if `.claude/epics/$ARGUMENTS/epic.md` already exists
-   - If it exists, ask user: "⚠️ Epic '$ARGUMENTS' already exists. Overwrite? (yes/no)"
-   - Only proceed with explicit 'yes' confirmation
-   - If user says no, suggest: "View existing epic with: /pm:epic-show $ARGUMENTS"
-
-5. **Verify directory permissions:**
-   - Ensure `.claude/epics/` directory exists or can be created
-   - If cannot create, tell user: "❌ Cannot create epic directory. Please check permissions."
-
 ## Instructions
 
-You are a technical lead converting a Product Requirements Document into a detailed implementation epic for: **$ARGUMENTS**
-
-### 1. Read the PRD
-- Load the PRD from `.claude/prds/$ARGUMENTS.md`
-- Analyze all requirements and constraints
-- Understand the user stories and success criteria
-- Extract the PRD description from frontmatter
-
-### 2. Technical Analysis
-- Identify architectural decisions needed
-- Determine technology stack and approaches
-- Map functional requirements to technical components
-- Identify integration points and dependencies
-
-### 3. File Format with Frontmatter
-Create the epic file at: `.claude/epics/$ARGUMENTS/epic.md` with this exact structure:
-
-```markdown
----
-name: $ARGUMENTS
-status: backlog
-created: [Current ISO date/time]
-progress: 0%
-prd: .claude/prds/$ARGUMENTS.md
-github: [Will be updated when synced to GitHub]
----
-
-# Epic: $ARGUMENTS
-
-## Overview
-Brief technical summary of the implementation approach
-
-## Architecture Decisions
-- Key technical decisions and rationale
-- Technology choices
-- Design patterns to use
-
-## Technical Approach
-### Frontend Components
-- UI components needed
-- State management approach
-- User interaction patterns
-
-### Backend Services
-- API endpoints required
-- Data models and schema
-- Business logic components
-
-### Infrastructure
-- Deployment considerations
-- Scaling requirements
-- Monitoring and observability
-
-## Implementation Strategy
-- Development phases
-- Risk mitigation
-- Testing approach
-
-## Task Breakdown Preview
-High-level task categories that will be created:
-- [ ] Category 1: Description
-- [ ] Category 2: Description
-- [ ] etc.
-
-## Dependencies
-- External service dependencies
-- Internal team dependencies
-- Prerequisite work
-
-## Success Criteria (Technical)
-- Performance benchmarks
-- Quality gates
-- Acceptance criteria
-
-## Estimated Effort
-- Overall timeline estimate
-- Resource requirements
-- Critical path items
-```
-
-### 4. Frontmatter Guidelines
-- **name**: Use the exact feature name (same as $ARGUMENTS)
-- **status**: Always start with "backlog" for new epics
-- **created**: Get REAL current datetime by running: `date -u +"%Y-%m-%dT%H:%M:%SZ"`
-- **progress**: Always start with "0%" for new epics
-- **prd**: Reference the source PRD file path
-- **github**: Leave placeholder text - will be updated during sync
-
-### 5. Output Location
-Create the directory structure if it doesn't exist:
-- `.claude/epics/$ARGUMENTS/` (directory)
-- `.claude/epics/$ARGUMENTS/epic.md` (epic file)
-
-### 6. Quality Validation
-
-Before saving the epic, verify:
-- [ ] All PRD requirements are addressed in the technical approach
-- [ ] Task breakdown categories cover all implementation areas
-- [ ] Dependencies are technically accurate
-- [ ] Effort estimates are realistic
-- [ ] Architecture decisions are justified
-
-### 7. Post-Creation
-
-After successfully creating the epic:
-1. Confirm: "✅ Epic created: .claude/epics/$ARGUMENTS/epic.md"
-2. Show summary of:
-   - Number of task categories identified
-   - Key architecture decisions
-   - Estimated effort
-3. Suggest next step: "Ready to break down into tasks? Run: /pm:epic-decompose $ARGUMENTS"
-
-## Error Recovery
-
-If any step fails:
-- Clearly explain what went wrong
-- If PRD is incomplete, list specific missing sections
-- If technical approach is unclear, identify what needs clarification
-- Never create an epic with incomplete information
+Run `node .claude/scripts/pm/prd-parse.js $ARGUMENTS` using the Bash tool and show me the complete output.
 
-Focus on creating a technically sound implementation plan that addresses all PRD requirements while being practical and achievable for "$ARGUMENTS".
+This will convert the Product Requirements Document into a detailed technical implementation epic including:
+1. Technical analysis and architecture decisions
+2. Implementation strategy and phases
+3. Task breakdown preview (limited to 10 or fewer tasks)
+4. Dependencies and success criteria
+5. Effort estimates and timeline
 
-## IMPORTANT:
-- Aim for as few tasks as possible and limit the total number of tasks to 10 or less.
-- When creating the epic, identify ways to simplify and improve it. Look for ways to leverage existing functionality instead of creating more code when possible.
+The script handles all validation, reads the PRD file, and creates the epic structure at `.claude/epics/$ARGUMENTS/epic.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/install/install.js

@@ -42,6 +42,7 @@ class Installer {
       '.claude/strategies',
       '.claude/mcp',
       '.claude/.env.example',
+      '.claude/teams.json',
       '.claude-code'
     ];
 

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.2",
+  "version": "1.10.4",
   "description": "Autonomous Project Management Framework for Claude Code - Advanced AI-powered development automation",
   "main": "bin/autopm.js",
   "bin": {