claude-autopm 3.0.0 → 3.0.2

package/README.md

@@ -268,9 +268,14 @@ autopm install
 autopm config set provider github
 autopm config set github.owner YOUR_USERNAME
 autopm config set github.repo YOUR_REPO
-export GITHUB_TOKEN=your_github_token
 
-# 5. Open Claude Code
+# Add your token to .claude/.env (recommended) or export directly
+echo "GITHUB_TOKEN=your_github_token" >> .claude/.env
+
+# 5. Verify configuration
+autopm config validate
+
+# 6. Open Claude Code
 claude --dangerously-skip-permissions .
 ```
 

package/bin/autopm.js

@@ -278,12 +278,22 @@ function main() {
    autopm config set provider github
    autopm config set github.owner <username>
    autopm config set github.repo <repository>
+
+   # Add token to .claude/.env (recommended)
+   echo "GITHUB_TOKEN=ghp_your_token_here" >> .claude/.env
+
+   # Or export as environment variable
    export GITHUB_TOKEN=ghp_your_token_here
 
    # Configure Azure DevOps provider
    autopm config set provider azure
    autopm config set azure.organization <org>
    autopm config set azure.project <project>
+
+   # Add token to .claude/.env (recommended)
+   echo "AZURE_DEVOPS_PAT=your_azure_pat" >> .claude/.env
+
+   # Or export as environment variable
    export AZURE_DEVOPS_PAT=your_azure_pat
 
    # Quick switch between providers
@@ -312,6 +322,13 @@ function main() {
    autopm mcp status                # Show all MCP servers status
 
 🔑 Token Setup:
+   # RECOMMENDED: Store tokens in .claude/.env file
+   echo "GITHUB_TOKEN=ghp_your_token" >> .claude/.env
+   echo "AZURE_DEVOPS_PAT=your_pat" >> .claude/.env
+
+   # The .env file is automatically loaded during validation
+   autopm config validate
+
    # GitHub PAT (Settings → Developer settings → Personal access tokens)
    Scopes: repo, workflow, admin:repo_hook
 

package/bin/commands/config.js

@@ -7,11 +7,28 @@
 
 const fs = require('fs-extra');
 const path = require('path');
+const dotenv = require('dotenv');
 
 class ConfigCommand {
   constructor() {
     this.configPath = path.join(process.cwd(), '.claude', 'config.json');
     this.envPath = path.join(process.cwd(), '.claude', '.env');
+
+    // Load .env file if it exists
+    this.loadEnv();
+  }
+
+  /**
+   * Load environment variables from .claude/.env
+   */
+  loadEnv() {
+    try {
+      if (fs.existsSync(this.envPath)) {
+        dotenv.config({ path: this.envPath });
+      }
+    } catch (error) {
+      // Silently ignore - env file is optional
+    }
   }
 
   /**

package/package.json

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

package/packages/plugin-cloud/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@claudeautopm/plugin-cloud",
-  "version": "2.0.0",
+  "version": "3.0.0",
   "description": "Complete cloud infrastructure plugin with agents for AWS, Azure, GCP, Kubernetes, Terraform, and infrastructure automation for ClaudeAutoPM",
   "main": "plugin.json",
   "type": "module",

package/packages/plugin-core/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@claudeautopm/plugin-core",
-  "version": "2.0.0",
+  "version": "3.0.0",
   "description": "Core framework functionality for ClaudeAutoPM - universal agents, rules, hooks, and utilities",
   "main": "index.js",
   "type": "module",

package/packages/plugin-data/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@claudeautopm/plugin-data",
-  "version": "2.0.0",
+  "version": "3.0.0",
   "description": "Complete data engineering plugin with Airflow, Kedro, LangGraph, Kafka, dbt, pandas experts, data quality rules, and example scripts for ClaudeAutoPM",
   "main": "plugin.json",
   "type": "module",

package/packages/plugin-databases/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@claudeautopm/plugin-databases",
-  "version": "2.0.0",
+  "version": "3.0.0",
   "description": "Complete database plugin with PostgreSQL, MongoDB, Redis, BigQuery, and Cosmos DB experts, database rules, and optimization scripts for ClaudeAutoPM",
   "main": "plugin.json",
   "type": "module",

package/packages/plugin-devops/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@claudeautopm/plugin-devops",
-  "version": "2.0.0",
+  "version": "3.0.0",
   "description": "Complete DevOps plugin with agents, commands, rules, and scripts for CI/CD, Docker, GitHub, observability, and infrastructure automation for ClaudeAutoPM",
   "main": "plugin.json",
   "type": "module",

package/packages/plugin-ml/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@claudeautopm/plugin-ml",
-  "version": "2.1.0",
+  "version": "3.0.0",
   "description": "Comprehensive Machine Learning plugin with 10 specialist agents: TensorFlow/Keras, PyTorch, RL, Scikit-learn, Neural Architecture, Gradient Boosting, Computer Vision, NLP Transformers, Time Series, and AutoML. Context7-verified patterns.",
   "main": "plugin.json",
   "scripts": {

package/packages/plugin-pm/commands/pm:epic-oneshot.md

@@ -45,75 +45,120 @@ See `.claude/rules/tdd.enforcement.md` for complete requirements.
 
 ### 1. Validate Prerequisites
 
-Check that epic exists and hasn't been processed:
 ```bash
-# Epic must exist
-test -f .claude/epics/$ARGUMENTS/epic.md || echo "❌ Epic not found. Run: /pm:prd-parse $ARGUMENTS"
-
-# Check for existing tasks
-if ls .claude/epics/$ARGUMENTS/[0-9]*.md 2>/dev/null | grep -q .; then
-  echo "⚠️ Tasks already exist. This will create duplicates."
-  echo "Delete existing tasks or use /pm:epic-sync instead."
+# Check if PRD exists
+if [ ! -f ".claude/prds/$ARGUMENTS.md" ]; then
+  echo "❌ PRD not found: $ARGUMENTS.md"
+  echo "💡 Create it first with: /pm:prd-new $ARGUMENTS"
   exit 1
 fi
 
-# Check if already synced
-if grep -q "github:" .claude/epics/$ARGUMENTS/epic.md; then
-  echo "⚠️ Epic already synced to GitHub."
-  echo "Use /pm:epic-sync to update."
+echo "✅ PRD found"
+
+# Check if epic already exists
+if [ -f ".claude/epics/$ARGUMENTS/epic.md" ]; then
+  echo "⚠️ Epic already exists: $ARGUMENTS"
+  echo "💡 View it with: /pm:epic-show $ARGUMENTS"
+  echo "💡 Or use a different name"
   exit 1
 fi
+
+echo "✅ Ready to create epic"
 ```
 
-### 2. Execute Decompose
+### 2. Execute Epic Oneshot Script
 
-Simply run the decompose command:
+Run the all-in-one script that handles:
+- PRD parsing
+- Task decomposition
+- GitHub/Azure sync
+
+```bash
+node .claude/scripts/pm/epic-oneshot.cjs $ARGUMENTS
 ```
-Running: /pm:epic-decompose $ARGUMENTS
+
+### 3. Verify Success
+
+```bash
+# Check epic was created
+if [ -f ".claude/epics/$ARGUMENTS/epic.md" ]; then
+  echo ""
+  echo "✅ Epic Oneshot Complete!"
+  echo ""
+  echo "📋 Next steps:"
+  echo "  • View epic: /pm:epic-show $ARGUMENTS"
+  echo "  • Start work: /pm:epic-start $ARGUMENTS"
+  echo "  • Get next task: /pm:next"
+  echo ""
+else
+  echo "❌ Epic creation failed. Check output above for errors."
+  exit 1
+fi
 ```
 
-This will:
-- Read the epic
-- Create task files (using parallel agents if appropriate)
-- Update epic with task summary
+## What It Does
 
-### 3. Execute Sync
+This command executes a complete workflow in one operation:
 
-Immediately follow with sync:
-```
-Running: /pm:epic-sync $ARGUMENTS
-```
+**Step 1: Parse PRD**
+- Reads `.claude/prds/$ARGUMENTS.md`
+- Extracts features, requirements, technical details
+- Creates epic structure
+
+**Step 2: Decompose Tasks**
+- Analyzes epic content
+- Generates implementation tasks
+- Adds tasks to epic.md
 
-This will:
-- Create epic issue on GitHub
-- Create sub-issues (using parallel agents if appropriate)
-- Rename task files to issue IDs
-- Create epic branch
+**Step 3: Sync to Provider**
+- Creates epic issue on GitHub/Azure
+- Creates sub-issues for each task
+- Links everything together
 
-### 4. Output
+## Output Structure
+
+After successful execution:
 
 ```
-🚀 Epic Oneshot Complete: $ARGUMENTS
-
-Step 1: Decomposition ✓
-  - Tasks created: {count}
-  
-Step 2: GitHub Sync ✓
-  - Epic: #{number}
-  - Sub-issues created: {count}
-  - Branch: epic/$ARGUMENTS
-
-Ready for development!
-  Start work: /pm:epic-start $ARGUMENTS
-  Or single task: /pm:issue-start {task_number}
+.claude/
+  epics/
+    <feature-name>/
+      epic.md              # Main epic with embedded tasks
+      metadata.json        # Epic metadata
+      tasks/               # Individual task files (if created)
+```
+
+## Example Usage
+
+```bash
+# Complete workflow in one command
+/pm:epic-oneshot gym-trading-env
+
+# What happens:
+# 1. Parses .claude/prds/gym-trading-env.md
+# 2. Creates .claude/epics/gym-trading-env/epic.md
+# 3. Generates implementation tasks
+# 4. Syncs to GitHub/Azure DevOps
+# 5. Ready to start work!
 ```
 
 ## Important Notes
 
-This is simply a convenience wrapper that runs:
-1. `/pm:epic-decompose` 
-2. `/pm:epic-sync`
+**Advantages of Oneshot:**
+- ✅ Fastest way from PRD to implementation
+- ✅ No manual intervention needed
+- ✅ Automatic task generation
+- ✅ Immediate GitHub sync
 
-Both commands handle their own error checking, parallel execution, and validation. This command just orchestrates them in sequence.
+**When NOT to use:**
+- ❌ Complex PRDs needing manual review between steps
+- ❌ Custom task decomposition required
+- ❌ Learning the PM workflow (use step-by-step instead)
 
-Use this when you're confident the epic is ready and want to go from epic to GitHub issues in one step.
+**Alternative: Step-by-Step**
+```bash
+# If you prefer manual control:
+/pm:prd-parse <feature>       # Step 1: Create epic
+/pm:epic-decompose <feature>  # Step 2: Add tasks (if available)
+/pm:epic-sync <feature>       # Step 3: Sync to provider
+```