claude-autopm 2.8.2 → 2.8.4

package/packages/plugin-pm/commands/azure/feature-show.md

@@ -0,0 +1,205 @@
+---
+name: /azure:feature-show
+type: epic-management
+category: azure
+---
+
+# /azure:feature-show
+
+Display detailed information about a Feature in Azure DevOps.
+
+## Usage
+
+```bash
+/azure:feature-show <feature-id>
+```
+
+## Required Documentation Access
+
+**MANDATORY:** Before Azure DevOps integration and agile workflows, query Context7 for best practices:
+
+**Documentation Queries:**
+- `mcp://context7/azure-devops/boards` - boards best practices
+- `mcp://context7/agile/user-stories` - user stories best practices
+- `mcp://context7/project-management/work-items` - work items best practices
+- `mcp://context7/agile/sprint-planning` - sprint planning 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
+
+
+## Description
+
+Shows comprehensive details about a Feature including User Stories, progress, and metrics.
+
+## Steps
+
+1. **Fetch Feature details**
+   ```bash
+   # Get feature information
+   az boards work-item show --id <feature-id> --output json > feature.json
+
+   # Extract key fields
+   feature_title=$(jq -r '.fields["System.Title"]' feature.json)
+   feature_state=$(jq -r '.fields["System.State"]' feature.json)
+   feature_desc=$(jq -r '.fields["System.Description"]' feature.json)
+   business_value=$(jq -r '.fields["Microsoft.VSTS.Common.BusinessValue"]' feature.json)
+   target_date=$(jq -r '.fields["Microsoft.VSTS.Scheduling.TargetDate"]' feature.json)
+   ```
+
+2. **Display Feature information**
+   ```bash
+   echo "════════════════════════════════════════════════════════════════"
+   echo "📦 FEATURE #<feature-id>: $feature_title"
+   echo "════════════════════════════════════════════════════════════════"
+   echo ""
+   echo "📊 Status: $feature_state"
+   echo "💰 Business Value: $business_value"
+   echo "📅 Target Date: $target_date"
+   echo ""
+   echo "📝 Description:"
+   echo "$feature_desc"
+   echo ""
+   ```
+
+3. **Show child User Stories**
+   ```bash
+   echo "📚 User Stories:"
+   echo "────────────────────────────────────────────────────────────────"
+
+   # Query child user stories
+   az boards query --wiql "SELECT [System.Id], [System.Title], [System.State], \
+     [Microsoft.VSTS.Scheduling.StoryPoints] \
+     FROM WorkItemLinks \
+     WHERE Source.[System.Id] = <feature-id> \
+     AND [System.Links.LinkType] = 'Child' \
+     AND Target.[System.WorkItemType] = 'User Story'" \
+     --output json > stories.json
+
+   # Display stories with progress
+   jq -r '.[] |
+     "  📖 [\(.id)] \(.fields["System.Title"])\n" +
+     "     State: \(.fields["System.State"]) | Points: \(.fields["Microsoft.VSTS.Scheduling.StoryPoints"] // "unestimated")"
+   ' stories.json
+   ```
+
+4. **Calculate progress metrics**
+   ```bash
+   echo ""
+   echo "📈 Progress Metrics:"
+   echo "────────────────────────────────────────────────────────────────"
+
+   # Count stories by state
+   total_stories=$(jq 'length' stories.json)
+   completed_stories=$(jq '[.[] | select(.fields["System.State"] == "Closed")] | length' stories.json)
+   active_stories=$(jq '[.[] | select(.fields["System.State"] == "Active")] | length' stories.json)
+
+   # Calculate story points
+   total_points=$(jq '[.[] | .fields["Microsoft.VSTS.Scheduling.StoryPoints"] // 0] | add' stories.json)
+   completed_points=$(jq '[.[] |
+     select(.fields["System.State"] == "Closed") |
+     .fields["Microsoft.VSTS.Scheduling.StoryPoints"] // 0] | add' stories.json)
+
+   # Display metrics
+   echo "  📊 Stories: $completed_stories/$total_stories completed"
+   echo "  🎯 Story Points: $completed_points/$total_points completed"
+
+   # Calculate percentage
+   if [ "$total_points" -gt 0 ]; then
+     percentage=$((completed_points * 100 / total_points))
+     echo "  📉 Progress: $percentage%"
+
+     # Progress bar
+     echo -n "  ["
+     for i in {1..20}; do
+       if [ $((i * 5)) -le $percentage ]; then
+         echo -n "█"
+       else
+         echo -n "░"
+       fi
+     done
+     echo "] $percentage%"
+   fi
+   ```
+
+5. **Show related information**
+   ```bash
+   echo ""
+   echo "🔗 Related Information:"
+   echo "────────────────────────────────────────────────────────────────"
+
+   # Parent epic/initiative
+   parent=$(jq -r '.relations[] |
+     select(.rel == "System.LinkTypes.Hierarchy-Reverse") |
+     .url' feature.json)
+   if [ -n "$parent" ]; then
+     parent_id=$(echo "$parent" | grep -oE '[0-9]+$')
+     parent_info=$(az boards work-item show --id "$parent_id" --query '{Title:fields["System.Title"], Type:fields["System.WorkItemType"]}' -o json)
+     echo "  🎯 Parent: $(echo "$parent_info" | jq -r '"\(.Type) #'$parent_id': \(.Title)"')"
+   fi
+
+   # Related PRs
+   echo "  🔀 Pull Requests:"
+   az boards work-item relation show --id <feature-id> --query "[?attributes.name=='Pull Request'].url" -o tsv | while read pr_url; do
+     echo "    - $pr_url"
+   done
+
+   # Tags
+   tags=$(jq -r '.fields["System.Tags"]' feature.json)
+   [ -n "$tags" ] && echo "  🏷️ Tags: $tags"
+
+   # Assigned to
+   assignee=$(jq -r '.fields["System.AssignedTo"].displayName' feature.json)
+   [ -n "$assignee" ] && echo "  👤 Assigned to: $assignee"
+   ```
+
+6. **Show timeline**
+   ```bash
+   echo ""
+   echo "📅 Timeline:"
+   echo "────────────────────────────────────────────────────────────────"
+
+   created=$(jq -r '.fields["System.CreatedDate"]' feature.json)
+   activated=$(jq -r '.fields["Microsoft.VSTS.Common.ActivatedDate"]' feature.json)
+   resolved=$(jq -r '.fields["Microsoft.VSTS.Common.ResolvedDate"]' feature.json)
+   closed=$(jq -r '.fields["Microsoft.VSTS.Common.ClosedDate"]' feature.json)
+
+   echo "  📝 Created: $created"
+   [ "$activated" != "null" ] && echo "  ▶️ Activated: $activated"
+   [ "$resolved" != "null" ] && echo "  ✅ Resolved: $resolved"
+   [ "$closed" != "null" ] && echo "  🏁 Closed: $closed"
+   ```
+
+## Options
+
+- `--json` - Output in JSON format
+- `--minimal` - Show only essential information
+- `--no-children` - Don't show child work items
+- `--export` - Export to markdown file
+
+## Examples
+
+```bash
+# Show feature details
+/azure:feature-show 12345
+
+# Minimal view
+/azure:feature-show 12345 --minimal
+
+# Export to file
+/azure:feature-show 12345 --export > feature-12345.md
+
+# JSON output for processing
+/azure:feature-show 12345 --json | jq '.stories'
+```
+
+## Related Commands
+
+- `/azure:feature-list` - List all Features
+- `/azure:feature-edit` - Edit Feature details
+- `/azure:feature-status` - Feature dashboard
+- `/azure:us-list` - List User Stories
+- `/pm:epic-show` - Show local epic (PM system)

package/packages/plugin-pm/commands/azure/feature-start.md

@@ -0,0 +1,130 @@
+---
+allowed-tools: Task, Bash, Read, Write, Edit, WebFetch, Glob, Grep
+---
+
+# Azure DevOps Feature Start
+
+Start working on a Feature - update status, create branch, decompose into stories.
+
+**Usage**: `/azure:feature-start <feature-id> [--branch-name=<name>]`
+
+**Examples**:
+- `/azure:feature-start 25`
+- `/azure:feature-start 25 --branch-name=feature/auth-system`
+
+## Required Documentation Access
+
+**MANDATORY:** Before Azure DevOps integration and agile workflows, query Context7 for best practices:
+
+**Documentation Queries:**
+- `mcp://context7/azure-devops/boards` - boards best practices
+- `mcp://context7/agile/user-stories` - user stories best practices
+- `mcp://context7/project-management/work-items` - work items best practices
+- `mcp://context7/agile/sprint-planning` - sprint planning 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
+
+
+## Instructions
+
+### 1. Feature Activation
+
+```
+🚀 Starting Feature #25: Authentication System
+
+Preflight Checklist:
+✓ Feature approved by Product Owner
+✓ Technical design reviewed
+✓ Team capacity available
+✓ Dependencies identified
+
+Creating feature branch...
+✓ Branch: feature/authentication-system
+✓ Protected branch rules applied
+✓ CI/CD pipeline configured
+
+Status updated to: In Progress
+Assigned to: Development Team
+
+Next Actions:
+[1] Decompose into User Stories
+[2] Assign team members
+[3] Schedule kickoff meeting
+[4] Create technical design doc
+
+Select (1-4): _
+```
+
+### 2. Update Feature Status
+
+```json
+{
+  "op": "replace",
+  "path": "/fields/System.State",
+  "value": "In Progress"
+},
+{
+  "op": "add",
+  "path": "/fields/System.History",
+  "value": "Feature development started"
+}
+```
+
+### 3. Setup Workspace
+
+```bash
+# Create feature branch
+git checkout -b feature/authentication-system
+
+# Create feature directory
+mkdir -p .claude/azure/features/authentication-system
+
+# Initialize feature tracking
+cat > .claude/azure/features/authentication-system/README.md << EOF
+# Feature: Authentication System
+
+Started: $(date)
+Target: End of Q1
+Team: John, Sarah, Mike
+
+## User Stories
+- [ ] User Registration
+- [ ] Login/Logout
+- [ ] Password Reset
+- [ ] MFA Setup
+
+## Milestones
+- [ ] Week 1: Core auth
+- [ ] Week 2: MFA
+- [ ] Week 3: Testing
+- [ ] Week 4: Deploy
+EOF
+```
+
+### 4. Success Output
+
+```
+✅ Feature #25 started successfully!
+
+📦 Authentication System
+Status: In Progress
+Branch: feature/authentication-system
+Team: 3 developers assigned
+
+📋 Generated 6 User Stories:
+- #41: User Registration (5 pts)
+- #42: Login/Logout (8 pts)
+- #43: Password Reset (5 pts)
+- #44: MFA Setup (13 pts)
+- #45: Session Management (8 pts)
+- #46: Admin Controls (8 pts)
+
+Total: 47 story points
+Estimated: 4 sprints
+
+Ready to start first story: /azure:us-start 41
+```

package/packages/plugin-pm/commands/azure/fix-integration-example.md

@@ -0,0 +1,93 @@
+---
+allowed-tools: Task
+---
+
+# Azure DevOps Integration Fix - Example Command
+
+This demonstrates the CORRECT way to integrate Azure DevOps commands with the azure-devops-specialist agent.
+
+**Usage**: `/azure:example <work-item-id>`
+
+## The Problem
+
+The original commands had extensive documentation about using the azure-devops-specialist agent but never actually invoked it. They tried to handle Azure DevOps operations directly, which fails.
+
+## The Solution
+
+**ALWAYS use the Task tool to invoke the azure-devops-specialist agent:**
+
+```bash
+# CORRECT approach
+Task(subagent_type="azure-devops-specialist", 
+     description="Handle Azure DevOps operation",
+     prompt="Your detailed instructions for the agent...")
+```
+
+## Example Implementation
+
+When user runs `/azure:example 123`, this command should execute:
+
+```bash
+# Invoke the specialized agent
+Task(subagent_type="azure-devops-specialist", 
+     description="Process work item 123",
+     prompt="Process Azure DevOps work item ID: **123**
+     
+Complete workflow:
+1. Authenticate with Azure DevOps using PAT token
+2. Fetch work item details and status
+3. Perform requested operations (status updates, comments, etc.)
+4. Update local documentation
+5. Provide success confirmation with Azure DevOps URL
+     
+Environment variables:
+- AZURE_DEVOPS_PAT: Personal access token
+- AZURE_DEVOPS_ORG: Organization name  
+- AZURE_DEVOPS_PROJECT: Project name
+     
+Return structured output with:
+- Work item details
+- Operations performed
+- Azure DevOps links
+- Next suggested actions")
+```
+## Required Documentation Access
+
+**MANDATORY:** Before Azure DevOps integration and agile workflows, query Context7 for best practices:
+
+**Documentation Queries:**
+- `mcp://context7/azure-devops/boards` - boards best practices
+- `mcp://context7/agile/user-stories` - user stories best practices
+- `mcp://context7/project-management/work-items` - work items best practices
+- `mcp://context7/agile/sprint-planning` - sprint planning 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
+
+
+
+## Key Changes Made
+
+1. **us-new.md**: Added Task tool invocation at the top
+2. **task-start.md**: Added Task tool invocation pattern
+3. **All commands**: Should follow this pattern
+
+## What the Agent Should Handle
+
+The azure-devops-specialist agent should:
+- Make all Azure DevOps API calls
+- Handle authentication and error handling
+- Process work item operations
+- Generate local documentation
+- Provide structured output
+
+## What the Commands Should Do
+
+The command files should:
+- Validate inputs
+- Call the agent with Task tool
+- Provide agent instructions
+- Define output format expectations

package/packages/plugin-pm/commands/azure/help.md

@@ -0,0 +1,150 @@
+---
+allowed-tools: Bash, Read, Write
+---
+
+# Azure DevOps Help
+
+Display help information for Azure DevOps commands.
+
+**Usage**: `/azure:help [command]`
+
+**Examples**:
+- `/azure:help` - Show all commands
+- `/azure:help us-new` - Help for specific command
+
+## Required Documentation Access
+
+**MANDATORY:** Before Azure DevOps integration and agile workflows, query Context7 for best practices:
+
+**Documentation Queries:**
+- `mcp://context7/azure-devops/boards` - boards best practices
+- `mcp://context7/agile/user-stories` - user stories best practices
+- `mcp://context7/project-management/work-items` - work items best practices
+- `mcp://context7/agile/sprint-planning` - sprint planning 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
+
+
+## Instructions
+
+### Display Help
+
+```
+📚 Azure DevOps Commands Help
+═══════════════════════════════════════════════════════════════
+
+QUICK START
+─────────────────────────────────────────────────────────────
+/azure:init                Initialize Azure DevOps integration
+/azure:standup            Daily standup report
+/azure:sprint-status      Current sprint dashboard
+/azure:next-task          Get next recommended task
+
+USER STORIES (Work with User Stories)
+─────────────────────────────────────────────────────────────
+/azure:us-new            Create new User Story
+/azure:us-list           List User Stories
+/azure:us-show <id>      Show User Story details
+/azure:us-edit <id>      Edit User Story
+/azure:us-parse <id>     Parse Story into Tasks
+/azure:us-status [id]    Story status overview
+/azure:import-us         Import from PRD/Epic
+
+TASKS (Work with Tasks)
+─────────────────────────────────────────────────────────────
+/azure:task-new          Create new Task
+/azure:task-list         List Tasks
+/azure:task-show <id>    Show Task details
+/azure:task-edit <id>    Edit Task
+/azure:task-start <id>   Start working on Task
+/azure:task-close <id>   Complete Task
+/azure:task-status       Task status overview
+
+FEATURES (Work with Features/Epics)
+─────────────────────────────────────────────────────────────
+/azure:feature-new       Create new Feature
+/azure:feature-list      List Features
+/azure:feature-start     Start Feature work
+/azure:feature-decompose Break down Feature
+
+WORKFLOW (Sprint & Team Management)
+─────────────────────────────────────────────────────────────
+/azure:sprint-status     Sprint dashboard
+/azure:standup          Daily standup
+/azure:active-work      Show active items
+/azure:blocked-items    Show blocked items
+/azure:next-task        Task recommendations
+
+UTILITIES
+─────────────────────────────────────────────────────────────
+/azure:search <query>    Search work items
+/azure:init             Initialize integration
+/azure:help [cmd]       Show help
+
+📖 Examples:
+─────────────────────────────────────────────────────────────
+# Start your day
+/azure:standup
+/azure:next-task --auto-start
+
+# Create and work on a story
+/azure:us-new "User login"
+/azure:us-parse 34
+/azure:task-start 101
+
+# Check progress
+/azure:sprint-status
+/azure:us-status 34
+
+💡 Tips:
+─────────────────────────────────────────────────────────────
+• Use TAB for command completion
+• Add --help to any command for details
+• Commands support shortcuts (e.g., 'us' for 'user-story')
+• Most lists support filters (--status, --assigned-to, etc.)
+
+📚 Documentation: .claude/commands/azure/README.md
+🔧 Configuration: .claude/azure/config.yml
+```
+
+### Command-Specific Help
+
+When specific command requested:
+
+```
+📖 Help: /azure:us-new
+
+Create a new User Story in Azure DevOps
+
+USAGE:
+  /azure:us-new <story-name>
+
+ARGUMENTS:
+  story-name    Name for the User Story (kebab-case)
+
+OPTIONS:
+  --points      Story points (1,2,3,5,8,13,21)
+  --sprint      Target sprint
+  --assigned-to Assignee email
+  --priority    Priority (1-4)
+
+EXAMPLES:
+  /azure:us-new user-authentication
+  /azure:us-new login-flow --points=8 --sprint="Sprint 2"
+  /azure:us-new api-integration --assigned-to=john@example.com
+
+WORKFLOW:
+  1. Creates User Story with interactive prompts
+  2. Sets acceptance criteria
+  3. Optionally parses into tasks
+  4. Links to current sprint if specified
+
+RELATED:
+  /azure:us-parse    - Break story into tasks
+  /azure:us-edit     - Edit existing story
+  /azure:us-status   - Check story progress
+```