claude-autopm 2.7.0 → 2.8.2

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

@@ -1,260 +0,0 @@
----
-allowed-tools: Task, Bash, Read, Write, WebFetch, Glob, Grep
----
-
-# Azure DevOps Daily Standup
-
-Generate daily standup report with yesterday's progress, today's plan, and blockers.
-
-**Usage**: `/azure:standup [--user=<email>] [--team=<name>] [--format=<type>]`
-
-**Examples**:
-- `/azure:standup` - Your personal standup
-- `/azure:standup --team=all` - Full team standup
-- `/azure:standup --user=john@example.com` - Specific user standup
-- `/azure:standup --format=slack` - Format for Slack
-
-## Required Environment Variables
-
-Ensure `.claude/.env` contains:
-
-```bash
-AZURE_DEVOPS_PAT=<your-pat-token>
-AZURE_DEVOPS_ORG=<your-organization>
-AZURE_DEVOPS_PROJECT=<your-project>
-```
-
-## 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. Query Work Items
-
-Use azure-devops-specialist agent to fetch:
-- Tasks completed yesterday
-- Tasks in progress
-- Tasks planned for today
-- Blocked items
-- PR status
-
-### 2. Personal Standup Format
-
-```
-🌅 Daily Standup - January 10, 2025
-👤 John Smith (john@example.com)
-═══════════════════════════════════════════════════════════
-
-📅 YESTERDAY
-────────────────────────────────────────────────────────────
-✅ Completed:
-• Task #102: Implementation (12h) - Password reset logic
-• Task #103: Unit tests (4h) - All tests passing
-• PR #456: Merged - Authentication service refactor
-
-⏳ Worked on but not completed:
-• Task #104: Integration tests (2h/6h) - 33% complete
-
-📊 Yesterday's metrics:
-- Completed: 2 tasks (16h)
-- Commits: 8
-- PRs merged: 1
-- Code coverage: +5%
-
-📅 TODAY
-────────────────────────────────────────────────────────────
-🎯 Planned:
-• Task #104: Complete integration tests (4h remaining)
-• Task #105: Start documentation (3h)
-• Code review for PR #457
-
-📋 Sprint goals:
-- Complete User Story #34 (75% done)
-- Start User Story #35 if time permits
-
-⏰ Capacity: 8h available
-
-🚧 BLOCKERS
-────────────────────────────────────────────────────────────
-⚠️ Task #104: Waiting for test environment fix (DevOps team)
-⚠️ Story #35: Needs design review before starting
-
-💬 NOTES
-────────────────────────────────────────────────────────────
-• Sprint ends in 2 days - on track
-• Will pair with Sarah on integration tests
-• Team retrospective at 3 PM
-
-📈 Sprint Progress: Day 8/10
-Story Points: 21/34 completed (62%)
-Your velocity: 2.6 points/day
-```
-
-### 3. Team Standup Format
-
-```
-🌅 Team Standup - January 10, 2025
-👥 Team: Development (4 members)
-═══════════════════════════════════════════════════════════
-
-📊 TEAM OVERVIEW
-────────────────────────────────────────────────────────────
-Sprint: Sprint 2 (Day 8/10)
-Progress: ████████████░░░░░░░░ 62% (21/34 points)
-Yesterday: 4 tasks completed, 2 blocked
-Today: 6 tasks in progress, 3 starting
-
-👤 John Smith
-────────────────────────────────────────────────────────────
-Yesterday: ✅ Task #102, #103 | 🔄 Task #104 (33%)
-Today: Complete #104, Start #105
-Blockers: Test environment down
-Capacity: 8h
-
-👤 Sarah Johnson
-────────────────────────────────────────────────────────────
-Yesterday: ✅ Task #215 | 🔄 Task #218 (60%)
-Today: Complete #218, Review PR #457
-Blockers: None
-Capacity: 7h
-
-👤 Mike Chen
-────────────────────────────────────────────────────────────
-Yesterday: 🔄 Task #301 (80%), #302 (40%)
-Today: Complete #301, Continue #302
-Blockers: Waiting for API specs
-Capacity: 8h
-
-👤 Lisa Anderson
-────────────────────────────────────────────────────────────
-Yesterday: ✅ Task #401, #402
-Today: Start Story #36 tasks
-Blockers: None
-Capacity: 6h
-
-🚧 TEAM BLOCKERS
-────────────────────────────────────────────────────────────
-1. Test environment down - affecting 2 people
-2. API specs missing - affecting Mike
-3. Design review pending - affecting Story #35
-
-📈 METRICS
-────────────────────────────────────────────────────────────
-Yesterday's velocity: 4.5 points
-Projected completion: 89% by sprint end
-At risk: Story #37 (may slip to next sprint)
-
-🎯 TODAY'S FOCUS
-────────────────────────────────────────────────────────────
-1. Unblock test environment (Critical)
-2. Complete in-progress tasks (6 tasks)
-3. Review and merge 3 PRs
-4. Prepare for sprint review demo
-
-💡 RECOMMENDATIONS
-────────────────────────────────────────────────────────────
-• Pair John & Sarah on integration tests
-• Move Story #37 to next sprint
-• Schedule emergency fix for test environment
-```
-
-### 4. Export Formats
-
-#### Slack Format
-```markdown
-*Daily Standup - Jan 10*
-*John Smith*
-
-*Yesterday:* ✅ 2 tasks done (#102, #103), 1 PR merged
-*Today:* Finishing #104, starting #105 documentation
-*Blockers:* Test environment down (waiting for DevOps)
-*Sprint:* 62% complete, on track
-```
-
-#### Email Format
-```html
-Subject: Daily Standup - Jan 10 - John Smith
-
-<h3>Yesterday</h3>
-<ul>
-  <li>✅ Completed Task #102: Implementation</li>
-  <li>✅ Completed Task #103: Unit tests</li>
-</ul>
-...
-```
-
-#### Markdown Format
-For documentation/wiki:
-```markdown
-## Daily Standup - 2025-01-10
-
-### Yesterday
-- [x] Task #102: Implementation
-- [x] Task #103: Unit tests
-...
-```
-
-### 5. Quick Actions
-
-After standup display:
-
-```
-⚡ Quick Actions:
-[1] Start next task (/azure:next-task)
-[2] Update blocked items
-[3] Send standup to Slack
-[4] Export to file
-[5] View sprint board
-
-Select (1-5): _
-```
-
-### 6. Automated Standup
-
-Schedule daily standup:
-
-```bash
-# Add to cron/scheduler
-0 9 * * * /azure:standup --team=all --format=slack --send
-```
-
-## Smart Features
-
-### Insights
-- Velocity trends
-- Blocker patterns
-- Capacity warnings
-- Risk identification
-
-### Recommendations
-- Task prioritization
-- Pairing suggestions
-- Resource reallocation
-- Sprint adjustments
-
-## Configuration
-
-`.claude/azure/standup-config.yml`:
-```yaml
-standup:
-  default_time: "09:00"
-  include_metrics: true
-  show_blockers: true
-  include_prs: true
-  slack_channel: "#dev-standup"
-  email_list: "team@example.com"
-```

package/autopm/.claude/commands/azure/sync-all.md

@@ -1,99 +0,0 @@
----
-allowed-tools: Task, Bash, Read, Write, Edit, WebFetch, Glob, Grep
----
-
-# Azure DevOps Sync All
-
-Full bidirectional synchronization of all work items.
-
-**Usage**: `/azure:sync-all [--force] [--dry-run]`
-
-**Examples**:
-- `/azure:sync-all` - Normal sync
-- `/azure:sync-all --dry-run` - Preview changes
-- `/azure:sync-all --force` - Overwrite conflicts
-
-## 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
-
-### Full Sync Process
-
-```
-🔄 Full Azure DevOps Synchronization
-═══════════════════════════════════════════════════════════════
-
-Scanning work items...
-- Features: 4 in Azure, 3 local
-- User Stories: 12 in Azure, 10 local
-- Tasks: 45 in Azure, 42 local
-
-Changes to sync:
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-Push to Azure (5 items):
-  ↑ Story #34: Status update
-  ↑ Task #102: Hours logged
-  ↑ Task #103: Completed
-  ↑ Feature #25: Progress update
-  ↑ Bug #215: Fixed
-
-Pull from Azure (8 items):
-  ↓ Story #35: New story
-  ↓ Task #110-115: New tasks
-  ↓ Feature #26: Updated
-
-Conflicts (2 items):
-  ⚠️ Task #102: Different hours
-  ⚠️ Story #34: Different status
-
-Resolution strategy:
-[1] Azure wins all conflicts
-[2] Local wins all conflicts
-[3] Resolve individually
-[4] Cancel sync
-
-Choose: 3
-
-Syncing... ████████████████████ 100%
-
-✅ Sync Complete!
-- Pushed: 5 items
-- Pulled: 8 items
-- Conflicts resolved: 2
-- Errors: 0
-
-Next sync scheduled: 5 minutes
-```
-
-### Sync Report
-
-```
-📊 Sync Report - 2025-01-10 16:00
-
-Items Synced:
-- Features: 4/4 ✓
-- Stories: 12/12 ✓
-- Tasks: 45/45 ✓
-
-Performance:
-- Duration: 3.2s
-- API calls: 15
-- Cache hits: 80%
-
-Health Status: ✅ Excellent
-```

package/autopm/.claude/commands/azure/task-analyze.md

@@ -1,186 +0,0 @@
----
-name: /azure:task-analyze
-type: task-management
-category: azure
----
-
-# /azure:task-analyze
-
-Analyze Task patterns and metrics in Azure DevOps to identify bottlenecks and improvements.
-
-## Usage
-
-```bash
-/azure:task-analyze [options]
-```
-
-## Required Documentation Access
-
-**MANDATORY:** Before analyzing tasks, query Context7 for best practices:
-
-**Documentation Queries:**
-- `mcp://context7/agile/task-analysis` - task analysis best practices
-- `mcp://context7/project-management/task-planning` - task planning best practices
-- `mcp://context7/agile/estimation` - estimation best practices
-- `mcp://context7/azure-devops/tasks` - tasks 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
-
-Performs deep analysis on Tasks to identify patterns, bottlenecks, and areas for improvement.
-
-## Steps
-
-1. **Gather Task data**
-   ```bash
-   # Get all tasks from current sprint
-   sprint=$(az boards iteration project current --query "path" -o tsv)
-
-   # Fetch task metrics
-   az boards query --wiql "SELECT [System.Id], [System.Title], [System.State], \
-     [Microsoft.VSTS.Scheduling.OriginalEstimate], \
-     [Microsoft.VSTS.Scheduling.RemainingWork], \
-     [Microsoft.VSTS.Scheduling.CompletedWork], \
-     [System.CreatedDate], [Microsoft.VSTS.Common.ClosedDate], \
-     [System.AssignedTo] \
-     FROM WorkItems \
-     WHERE [System.WorkItemType] = 'Task' \
-     AND [System.IterationPath] = '$sprint'" \
-     --output json > tasks.json
-   ```
-
-2. **Calculate metrics**
-   ```bash
-   # Cycle time analysis
-   echo "📊 Task Cycle Time Analysis:"
-   jq -r '.[] |
-     select(.fields["Microsoft.VSTS.Common.ClosedDate"] != null) |
-     {
-       id: .id,
-       title: .fields["System.Title"],
-       created: .fields["System.CreatedDate"],
-       closed: .fields["Microsoft.VSTS.Common.ClosedDate"],
-       cycle_days: (((.fields["Microsoft.VSTS.Common.ClosedDate"] | fromdate) -
-                     (.fields["System.CreatedDate"] | fromdate)) / 86400 | floor)
-     }' tasks.json | jq -s 'sort_by(.cycle_days) | reverse'
-
-   # Estimation accuracy
-   echo "📈 Estimation Accuracy:"
-   jq -r '.[] |
-     select(.fields["Microsoft.VSTS.Scheduling.OriginalEstimate"] != null) |
-     {
-       id: .id,
-       title: .fields["System.Title"],
-       original: .fields["Microsoft.VSTS.Scheduling.OriginalEstimate"],
-       completed: .fields["Microsoft.VSTS.Scheduling.CompletedWork"],
-       accuracy: ((.fields["Microsoft.VSTS.Scheduling.CompletedWork"] // 0) /
-                  .fields["Microsoft.VSTS.Scheduling.OriginalEstimate"] * 100 | floor)
-     }' tasks.json
-   ```
-
-3. **Identify patterns**
-   ```bash
-   # Blocked tasks
-   echo "🚫 Frequently Blocked Tasks:"
-   az boards query --wiql "SELECT [System.Id], [System.Title], [System.Tags] \
-     FROM WorkItems \
-     WHERE [System.WorkItemType] = 'Task' \
-     AND [System.Tags] CONTAINS 'blocked'" \
-     --output table
-
-   # Overdue tasks
-   echo "⏰ Overdue Tasks:"
-   az boards query --wiql "SELECT [System.Id], [System.Title], [System.AssignedTo] \
-     FROM WorkItems \
-     WHERE [System.WorkItemType] = 'Task' \
-     AND [System.State] != 'Closed' \
-     AND [Microsoft.VSTS.Scheduling.TargetDate] < @today" \
-     --output table
-   ```
-
-4. **Team performance**
-   ```bash
-   # Tasks per assignee
-   echo "👥 Task Distribution:"
-   jq -r '.[] | .fields["System.AssignedTo"].displayName' tasks.json | \
-     sort | uniq -c | sort -rn
-
-   # Average completion time per person
-   echo "⏱️ Average Completion Time by Assignee:"
-   jq -r '.[] |
-     select(.fields["Microsoft.VSTS.Common.ClosedDate"] != null) |
-     {
-       assignee: .fields["System.AssignedTo"].displayName,
-       cycle_days: (((.fields["Microsoft.VSTS.Common.ClosedDate"] | fromdate) -
-                     (.fields["System.CreatedDate"] | fromdate)) / 86400 | floor)
-     }' tasks.json | \
-     jq -s 'group_by(.assignee) |
-            map({assignee: .[0].assignee,
-                 avg_days: (map(.cycle_days) | add / length | floor)})'
-   ```
-
-5. **Generate recommendations**
-   ```bash
-   echo "💡 Recommendations:"
-
-   # Check for unassigned tasks
-   unassigned=$(jq '[.[] | select(.fields["System.AssignedTo"] == null)] | length' tasks.json)
-   [ "$unassigned" -gt 0 ] && echo "- Assign $unassigned unassigned tasks"
-
-   # Check for tasks without estimates
-   unestimated=$(jq '[.[] | select(.fields["Microsoft.VSTS.Scheduling.OriginalEstimate"] == null)] | length' tasks.json)
-   [ "$unestimated" -gt 0 ] && echo "- Add estimates to $unestimated tasks"
-
-   # Check for long-running tasks
-   long_tasks=$(jq '[.[] |
-     select(.fields["System.State"] == "In Progress") |
-     select(((now - (.fields["System.CreatedDate"] | fromdate)) / 86400) > 5)] | length' tasks.json)
-   [ "$long_tasks" -gt 0 ] && echo "- Review $long_tasks tasks in progress > 5 days"
-   ```
-
-## Options
-
-- `--sprint <name>` - Analyze specific sprint
-- `--team <name>` - Filter by team
-- `--days <n>` - Look back n days (default: 30)
-- `--export` - Export analysis to CSV
-- `--detailed` - Show detailed task breakdown
-
-## Examples
-
-```bash
-# Analyze current sprint
-/azure:task-analyze
-
-# Analyze specific sprint
-/azure:task-analyze --sprint "Sprint 23"
-
-# Export analysis
-/azure:task-analyze --export > analysis.csv
-
-# Detailed analysis for last 14 days
-/azure:task-analyze --days 14 --detailed
-```
-
-## Metrics Provided
-
-- **Cycle Time** - Time from creation to completion
-- **Lead Time** - Time from ready to done
-- **Estimation Accuracy** - Actual vs estimated hours
-- **Throughput** - Tasks completed per day/week
-- **WIP (Work in Progress)** - Current active tasks
-- **Blockers** - Frequency and duration of blocks
-- **Team Velocity** - Story points per sprint
-
-## Related Commands
-
-- `/azure:task-status` - Current task status
-- `/azure:sprint-status` - Sprint overview
-- `/azure:blocked-items` - List blocked items
-- `/pm:issue-analyze` - Analyze local issues (PM system)