claude-autopm 2.7.0 → 2.8.2

package/autopm/.claude/commands/ai/langgraph-workflow.md

@@ -1,65 +0,0 @@
----
-name: langgraph-workflow
-type: ai-workflow
-category: ai
----
-
-# LangGraph Workflow Command
-
-Create complex AI workflows using LangGraph with state management and multi-agent collaboration.
-
-## Command
-```
-/ai:langgraph-workflow
-```
-
-## Purpose
-Use the langgraph-workflow-expert agent to create sophisticated AI workflows with graph-based orchestration, state management, and conditional routing.
-
-## Parameters
-- `workflow_type`: Type of workflow (conversational, data-processing, multi-agent, human-in-loop)
-- `agents`: Number and types of agents in the workflow
-- `state_management`: State persistence (memory, database, checkpoints)
-- `routing`: Conditional routing logic (simple, complex, ml-based)
-
-## Agent Usage
-```
-Use the langgraph-workflow-expert agent to create a comprehensive LangGraph workflow system.
-```
-
-## Expected Outcome
-- Complete LangGraph workflow implementation
-- State schema and management
-- Multi-agent coordination patterns
-- Conditional routing and decision trees
-- Human-in-the-loop integration
-- Error handling and recovery mechanisms
-- Monitoring and debugging tools
-
-## Example Usage
-```
-## Required Documentation Access
-
-**MANDATORY:** Before AI integration and LLM workflows, query Context7 for best practices:
-
-**Documentation Queries:**
-- `mcp://context7/ai/llm-integration` - llm integration best practices
-- `mcp://context7/ai/workflow-orchestration` - workflow orchestration best practices
-- `mcp://context7/openai/api` - api best practices
-- `mcp://context7/langchain/agents` - agents best practices
-
-**Why This is Required:**
-- Ensures adherence to current industry standards and best practices
-- Prevents outdated or incorrect implementation patterns
-- Provides access to latest framework/tool documentation
-- Reduces errors from stale knowledge or assumptions
-
-
-Task: Create multi-agent research workflow with coordinator, researcher, analyzer, and writer agents
-Agent: langgraph-workflow-expert
-Parameters: workflow_type=multi-agent, agents=4, state_management=checkpoints, routing=complex
-```
-
-## Related Agents
-- openai-python-expert: For OpenAI model integration
-- gemini-api-expert: For Google AI model integration

package/autopm/.claude/commands/ai/openai-chat.md

@@ -1,65 +0,0 @@
----
-name: openai-chat-integration
-type: ai-integration
-category: ai
----
-
-# OpenAI Chat Integration Command
-
-Create a complete chat application using OpenAI Python SDK with advanced features.
-
-## Command
-```
-/ai:openai-chat
-```
-
-## Purpose
-Use the openai-python-expert agent to create a production-ready chat application with OpenAI integration, including function calling, embeddings, and safety features.
-
-## Parameters
-- `model`: OpenAI model to use (gpt-4, gpt-3.5-turbo, gpt-4-vision-preview)
-- `features`: Required features (streaming, function-calling, embeddings, vision)
-- `safety`: Safety configuration (content-filtering, rate-limiting, moderation)
-- `storage`: Conversation storage (memory, database, file)
-
-## Agent Usage
-```
-Use the openai-python-expert agent to create a comprehensive chat application with OpenAI integration.
-```
-
-## Expected Outcome
-- Complete chat application with OpenAI SDK integration
-- Streaming response handling
-- Function calling implementation
-- Rate limiting and error handling
-- Conversation persistence
-- Content moderation and safety controls
-- Production-ready configuration
-
-## Example Usage
-```
-## Required Documentation Access
-
-**MANDATORY:** Before AI integration and LLM workflows, query Context7 for best practices:
-
-**Documentation Queries:**
-- `mcp://context7/ai/llm-integration` - llm integration best practices
-- `mcp://context7/ai/workflow-orchestration` - workflow orchestration best practices
-- `mcp://context7/openai/api` - api best practices
-- `mcp://context7/langchain/agents` - agents best practices
-
-**Why This is Required:**
-- Ensures adherence to current industry standards and best practices
-- Prevents outdated or incorrect implementation patterns
-- Provides access to latest framework/tool documentation
-- Reduces errors from stale knowledge or assumptions
-
-
-Task: Create chat application with GPT-4, streaming responses, function calling for web search, and conversation history
-Agent: openai-python-expert
-Parameters: model=gpt-4, features=streaming,function-calling,embeddings, safety=content-filtering,rate-limiting, storage=database
-```
-
-## Related Agents
-- gemini-api-expert: For Google AI alternative
-- langgraph-workflow-expert: For complex conversation workflows

package/autopm/.claude/commands/azure/COMMANDS.md

@@ -1,107 +0,0 @@
-# Azure DevOps Command Equivalents
-
-## Complete PM → Azure Command Mapping
-
-```bash
-# PRD → User Story
-/pm:prd-new         →  /azure:us-new
-/pm:prd-list        →  /azure:us-list  
-/pm:prd-edit        →  /azure:us-edit
-/pm:prd-parse       →  /azure:us-parse
-/pm:prd-status      →  /azure:us-status
-
-# Issue → Task
-/pm:issue-start     →  /azure:task-start
-/pm:issue-close     →  /azure:task-close
-/pm:issue-edit      →  /azure:task-edit
-/pm:issue-show      →  /azure:task-show
-/pm:issue-status    →  /azure:task-status
-/pm:issue-sync      →  /azure:task-sync
-/pm:issue-reopen    →  /azure:task-reopen
-/pm:issue-analyze   →  /azure:task-analyze
-
-# Epic → Feature
-/pm:epic-decompose  →  /azure:feature-decompose
-/pm:epic-start      →  /azure:feature-start
-/pm:epic-close      →  /azure:feature-close
-/pm:epic-edit       →  /azure:feature-edit
-/pm:epic-list       →  /azure:feature-list
-/pm:epic-show       →  /azure:feature-show
-/pm:epic-status     →  /azure:feature-status
-/pm:epic-sync       →  /azure:feature-sync
-/pm:epic-merge      →  /azure:feature-merge
-/pm:epic-refresh    →  /azure:feature-refresh
-/pm:epic-oneshot    →  /azure:feature-oneshot
-
-# Workflow → Sprint/Board
-/pm:status          →  /azure:sprint-status
-/pm:standup         →  /azure:standup
-/pm:next            →  /azure:next-task
-/pm:in-progress     →  /azure:active-work
-/pm:blocked         →  /azure:blocked-items
-/pm:search          →  /azure:search
-/pm:validate        →  /azure:validate
-/pm:clean           →  /azure:clean
-
-# System → Config
-/pm:init            →  /azure:init
-/pm:import          →  /azure:import
-/pm:sync            →  /azure:sync-all
-/pm:help            →  /azure:help
-/pm:test-reference-update → /azure:test-sync
-```
-
-## Already Implemented ✅
-
-```bash
-/azure:us-new          # ✅ Created
-/azure:us-list         # ✅ Created
-/azure:us-parse        # ✅ Created
-/azure:us-status       # ✅ Created
-/azure:import-us       # ✅ Created (maps to /pm:import)
-/azure:task-start      # ✅ Created
-/azure:task-list       # ✅ Created
-/azure:task-close      # ✅ Created
-/azure:feature-decompose # ✅ Created
-```
-
-## Need to Create 🔧
-
-```bash
-# High Priority
-/azure:us-edit
-/azure:us-show
-/azure:task-edit
-/azure:task-show
-/azure:task-status
-/azure:sprint-status
-/azure:standup
-/azure:next-task
-
-# Medium Priority  
-/azure:feature-new
-/azure:feature-list
-/azure:feature-start
-/azure:feature-close
-/azure:feature-status
-/azure:active-work
-/azure:blocked-items
-
-# Low Priority
-/azure:task-sync
-/azure:task-reopen
-/azure:task-analyze
-/azure:feature-edit
-/azure:feature-show
-/azure:feature-sync
-/azure:feature-merge
-/azure:feature-refresh
-/azure:feature-oneshot
-/azure:search
-/azure:validate
-/azure:clean
-/azure:init
-/azure:sync-all
-/azure:help
-/azure:test-sync
-```

package/autopm/.claude/commands/azure/COMMAND_MAPPING.md

@@ -1,252 +0,0 @@
-# PM and Azure DevOps Command Mapping
-
-## 🤝 Complementary Systems
-
-**IMPORTANT**: The PM and Azure systems are designed to **coexist and complement** each other, not replace one another.
-
-- **PM System** (`/pm:*`): Local, file-based, works offline, universal git platform support
-- **Azure System** (`/azure:*`): Enterprise integration, team collaboration, metrics tracking
-
-See [PM-AZURE-COEXISTENCE.md](../../docs/PM-AZURE-COEXISTENCE.md) for detailed strategy.
-
-## Command Translation Table
-
-Below is a mapping showing equivalent commands between systems. Use the system that best fits your current context.
-
-### PRD Commands → User Story Commands
-
-| PM Command | Azure DevOps Command | Status | Description |
-|------------|---------------------|---------|-------------|
-| `/pm:prd-new` | `/azure:us-new` | ✅ Created | Create new User Story |
-| `/pm:prd-list` | `/azure:us-list` | ✅ Created | List User Stories |
-| `/pm:prd-edit` | `/azure:us-edit` | ✅ Created | Edit User Story |
-| `/pm:prd-parse` | `/azure:us-parse` | ✅ Created | Parse User Story into Tasks |
-| `/pm:prd-status` | `/azure:us-status` | ✅ Created | User Story status dashboard |
-
-### Issue Commands → Task Commands
-
-| PM Command | Azure DevOps Command | Status | Description |
-|------------|---------------------|---------|-------------|
-| `/pm:issue-start` | `/azure:task-start` | ✅ Created | Start working on Task |
-| `/pm:issue-close` | `/azure:task-close` | ✅ Created | Complete Task |
-| `/pm:issue-edit` | `/azure:task-edit` | ✅ Created | Edit Task details |
-| `/pm:issue-show` | `/azure:task-show` | ✅ Created | Show Task details |
-| `/pm:issue-status` | `/azure:task-status` | ✅ Created | Task status |
-| `/pm:issue-sync` | `/azure:task-sync` | ✅ Created | Sync Tasks |
-| `/pm:issue-reopen` | `/azure:task-reopen` | ✅ Created | Reopen closed Task |
-| `/pm:issue-analyze` | `/azure:task-analyze` | 🔧 TODO | Analyze Task patterns |
-
-### Epic Commands → Feature Commands
-
-| PM Command | Azure DevOps Command | Status | Description |
-|------------|---------------------|---------|-------------|
-| `/pm:epic-decompose` | `/azure:feature-decompose` | ✅ Created | Break down Feature into User Stories |
-| `/pm:epic-start` | `/azure:feature-start` | ✅ Created | Start Feature development |
-| `/pm:epic-close` | `/azure:feature-close` | 🔧 TODO | Complete Feature |
-| `/pm:epic-edit` | `/azure:feature-edit` | 🔧 TODO | Edit Feature details |
-| `/pm:epic-list` | `/azure:feature-list` | ✅ Created | List Features |
-| `/pm:epic-show` | `/azure:feature-show` | 🔧 TODO | Show Feature details |
-| `/pm:epic-status` | `/azure:feature-status` | 🔧 TODO | Feature progress dashboard |
-| `/pm:epic-sync` | `/azure:feature-sync` | 🔧 TODO | Sync Features |
-| `/pm:epic-merge` | `/azure:feature-merge` | 🔧 TODO | Merge Feature branches |
-| `/pm:epic-refresh` | `/azure:feature-refresh` | 🔧 TODO | Refresh Feature from source |
-| `/pm:epic-oneshot` | `/azure:feature-oneshot` | 🔧 TODO | Quick Feature creation |
-
-### Workflow Commands → Sprint/Board Commands
-
-| PM Command | Azure DevOps Command | Status | Description |
-|------------|---------------------|---------|-------------|
-| `/pm:status` | `/azure:sprint-status` | ✅ Created | Sprint overview dashboard |
-| `/pm:standup` | `/azure:standup` | ✅ Created | Daily standup report |
-| `/pm:next` | `/azure:next-task` | ✅ Created | Get next recommended task |
-| `/pm:in-progress` | `/azure:active-work` | ✅ Created | Show all active work items |
-| `/pm:blocked` | `/azure:blocked-items` | ✅ Created | List blocked work items |
-| `/pm:search` | `/azure:search` | 🔧 TODO | Search work items |
-| `/pm:validate` | `/azure:validate` | 🔧 TODO | Validate work item structure |
-| `/pm:clean` | `/azure:clean` | 🔧 TODO | Clean up completed items |
-
-### System Commands → Azure DevOps Config
-
-| PM Command | Azure DevOps Command | Status | Description |
-|------------|---------------------|---------|-------------|
-| `/pm:init` | `/azure:init` | 🔧 TODO | Initialize Azure DevOps project |
-| `/pm:import` | `/azure:import-us` | ✅ Created | Import from external source |
-| `/pm:sync` | `/azure:sync-all` | 🔧 TODO | Full bi-directional sync |
-| `/pm:help` | `/azure:help` | 🔧 TODO | Azure DevOps command help |
-| `/pm:test-reference-update` | `/azure:test-sync` | 🔧 TODO | Sync test references |
-
-## Implementation Priority
-
-### 🎯 High Priority (Core Workflow)
-1. `/azure:us-edit` - Edit User Stories
-2. `/azure:task-edit` - Edit Tasks
-3. `/azure:task-show` - View Task details
-4. `/azure:sprint-status` - Sprint dashboard
-5. `/azure:standup` - Daily standup
-
-### 📊 Medium Priority (Management)
-1. `/azure:feature-list` - List all Features
-2. `/azure:feature-status` - Feature dashboard
-3. `/azure:feature-start` - Start Feature work
-4. `/azure:feature-close` - Complete Feature
-5. `/azure:active-work` - Active items view
-6. `/azure:blocked-items` - Blocked items
-
-### 🔧 Low Priority (Advanced)
-1. `/azure:feature-merge` - Merge Feature branches
-2. `/azure:task-analyze` - Task analytics
-4. `/azure:search` - Advanced search
-5. `/azure:validate` - Validation tools
-6. `/azure:clean` - Cleanup utilities
-
-## Command Files to Create
-
-### Next Batch (High Priority)
-
-```bash
-# User Story Management
-.claude/commands/azure/us-edit.md
-.claude/commands/azure/us-show.md
-.claude/commands/azure/us-sync.md
-.claude/commands/azure/us-close.md
-
-# Task Management
-.claude/commands/azure/task-edit.md
-.claude/commands/azure/task-show.md
-.claude/commands/azure/task-status.md
-.claude/commands/azure/task-sync.md
-.claude/commands/azure/task-reopen.md
-.claude/commands/azure/task-analyze.md
-.claude/commands/azure/task-new.md
-
-# Feature Management
-.claude/commands/azure/feature-new.md
-.claude/commands/azure/feature-list.md
-.claude/commands/azure/feature-show.md
-.claude/commands/azure/feature-edit.md
-.claude/commands/azure/feature-status.md
-.claude/commands/azure/feature-start.md
-.claude/commands/azure/feature-close.md
-.claude/commands/azure/feature-sync.md
-.claude/commands/azure/feature-merge.md
-
-# Sprint/Workflow
-.claude/commands/azure/sprint-status.md
-.claude/commands/azure/sprint-plan.md
-.claude/commands/azure/standup.md
-.claude/commands/azure/next-task.md
-.claude/commands/azure/active-work.md
-.claude/commands/azure/blocked-items.md
-
-# System
-.claude/commands/azure/init.md
-.claude/commands/azure/sync-all.md
-.claude/commands/azure/search.md
-.claude/commands/azure/validate.md
-.claude/commands/azure/clean.md
-.claude/commands/azure/help.md
-```
-
-## Azure DevOps Work Item Hierarchy
-
-```
-Feature/Epic
-    └── User Story
-            └── Task
-                  └── Sub-task (optional)
-```
-
-## Field Mapping
-
-### User Story Fields
-- **Title** → System.Title
-- **Description** → System.Description  
-- **Acceptance Criteria** → Microsoft.VSTS.Common.AcceptanceCriteria
-- **Story Points** → Microsoft.VSTS.Scheduling.StoryPoints
-- **Priority** → Microsoft.VSTS.Common.Priority
-- **Sprint** → System.IterationPath
-- **Area** → System.AreaPath
-
-### Task Fields
-- **Title** → System.Title
-- **Description** → System.Description
-- **Remaining Work** → Microsoft.VSTS.Scheduling.RemainingWork
-- **Original Estimate** → Microsoft.VSTS.Scheduling.OriginalEstimate
-- **Completed Work** → Microsoft.VSTS.Scheduling.CompletedWork
-- **Activity** → Microsoft.VSTS.Common.Activity
-
-### Feature Fields
-- **Title** → System.Title
-- **Description** → System.Description
-- **Business Value** → Microsoft.VSTS.Common.BusinessValue
-- **Time Criticality** → Microsoft.VSTS.Common.TimeCriticality
-- **Effort** → Microsoft.VSTS.Scheduling.Effort
-- **Target Date** → Microsoft.VSTS.Scheduling.TargetDate
-
-## State Mappings
-
-### User Story States
-- `backlog` → New
-- `ready` → Ready
-- `active` → Active
-- `resolved` → Resolved
-- `closed` → Closed
-- `removed` → Removed
-
-### Task States
-- `new` → To Do
-- `active` → In Progress
-- `resolved` → Done
-- `closed` → Closed
-- `removed` → Removed
-
-### Feature States
-- `new` → New
-- `in_progress` → In Progress
-- `testing` → Testing
-- `done` → Done
-- `closed` → Closed
-
-## Quick Reference
-
-### Most Used Commands
-
-```bash
-# Daily workflow
-/azure:standup                    # Morning standup
-/azure:task-start <id>            # Start task
-/azure:task-close <id>            # Complete task
-/azure:next-task                  # Get next task
-
-# Planning
-/azure:us-new <name>              # Create User Story
-/azure:us-parse <id>              # Break into tasks
-/azure:sprint-plan                # Plan sprint
-
-# Status
-/azure:sprint-status              # Sprint dashboard
-/azure:us-status <id>             # Story progress
-/azure:blocked-items              # Show blockers
-```
-
-## Integration Points
-
-### Git Integration
-- Branch naming: `task-{id}-{title}`
-- PR templates included
-- Auto-merge capabilities
-
-### CI/CD Integration
-- Pipeline status tracking
-- Build associations
-- Deployment tracking
-
-### Time Tracking
-- Automatic time logging
-- Capacity planning
-- Velocity calculations
-
-### Notifications
-- Status change alerts
-- Assignment notifications
-- Blocker escalations

package/autopm/.claude/commands/azure/INTEGRATION_FIX.md

@@ -1,103 +0,0 @@
-# Azure DevOps Agent-Command Integration Fix
-
-## Problem Identified
-
-The Azure DevOps commands were **fundamentally broken** because they never actually invoked the `azure-devops-specialist` agent. Instead, they:
-
-1. ✅ Documented how to use the agent (good documentation)
-2. ❌ Never actually called the agent (broken execution)  
-3. ❌ Tried to handle Azure DevOps operations directly (ineffective)
-
-## Root Cause
-
-**Architectural mismatch**: Commands contained instructions *about* the agent but no mechanism to *invoke* the agent.
-
-## Solution Implemented
-
-### 1. Updated Command Structure
-
-**Before** (broken):
-```markdown
-## Instructions
-You are a Product Owner creating a User Story...
-Use the azure-devops-specialist agent to:
-1. Create work item
-2. Set metadata
-```
-
-**After** (fixed):
-```markdown
-## Instructions
-**CRITICAL**: This command MUST use the azure-devops-specialist agent.
-
-### Command Execution Pattern
-Task(subagent_type="azure-devops-specialist", 
-     description="Create Azure DevOps User Story",
-     prompt="Detailed instructions...")
-```
-
-### 2. Files Updated
-
-#### Commands Fixed:
-- ✅ `us-new.md` - User Story creation
-- ✅ `task-start.md` - Task activation  
-- ➡️ **Need to update remaining 38+ commands with same pattern**
-
-#### Agent Enhanced:
-- ✅ `azure-devops-specialist.md` - Added command workflow integration patterns
-
-### 3. Integration Pattern
-
-```bash
-# CORRECT usage in commands
-Task(subagent_type="azure-devops-specialist", 
-     description="Brief operation description",
-     prompt="Complete workflow instructions including:
-     1. Environment validation
-     2. Azure DevOps API operations  
-     3. Local documentation updates
-     4. Status reporting")
-```
-
-## What Commands Should Do
-
-1. **Input validation** (task IDs, environment variables)
-2. **Call azure-devops-specialist agent** via Task tool
-3. **Provide complete instructions** to the agent
-4. **Define expected output format**
-
-## What Agent Should Do
-
-1. **Environment setup** (PAT tokens, authentication)
-2. **Azure DevOps API calls** (work items, status updates)
-3. **Local file management** (`.claude/azure/` tracking)
-4. **Structured reporting** (URLs, next steps)
-
-## Testing the Fix
-
-To verify the integration works:
-
-```bash
-# Test the fixed commands
-/azure:us-new test-story
-/azure:task-start 123
-
-# Should now properly invoke azure-devops-specialist agent
-# Instead of failing with direct Azure DevOps operations
-```
-
-## Remaining Work
-
-1. **Update all 38+ Azure commands** with Task tool invocation pattern
-2. **Test end-to-end workflows** with real Azure DevOps instance  
-3. **Validate error handling** when API calls fail
-4. **Document success patterns** for other command integrations
-
-## Key Learnings
-
-- Commands must **invoke agents**, not just document them
-- Use `Task(subagent_type="...", prompt="...")` for all agent calls
-- Agent documentation should include **command integration patterns**
-- **Test integration**, don't assume documentation equals implementation
-
-This fix transforms the Azure DevOps system from **documented but broken** to **properly integrated and functional**.