claude-autopm 2.8.2 → 2.8.3

package/packages/plugin-pm/commands/azure/active-work.md

@@ -0,0 +1,198 @@
+---
+allowed-tools: Task, Bash, Read, Write, WebFetch, Glob, Grep
+---
+
+# Azure DevOps Active Work
+
+Show all currently active work items across the team or for specific user.
+
+**Usage**: `/azure:active-work [--user=<email>] [--type=<type>]`
+
+**Examples**:
+- `/azure:active-work` - All active work
+- `/azure:active-work --user=me` - Your active work
+- `/azure:active-work --type=task` - Active tasks only
+- `/azure:active-work --team=dev` - Dev team active work
+
+## 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 Active Items
+
+Use azure-devops-specialist agent to fetch:
+- State = "Active" or "In Progress"
+- Group by type (Feature, User Story, Task)
+- Include progress metrics
+
+### 2. Display Format
+
+```
+🔄 Active Work Items - Real-time Status
+═══════════════════════════════════════════════════════════════
+Last updated: 10:45 AM | Sprint: Day 8/10
+
+📦 FEATURES (1 active)
+────────────────────────────────────────────────────────────────
+#25 Authentication System
+Progress: ████████████████░░░░ 82% | 4/5 stories complete
+Owner: Product Team | Due: End of Sprint 2
+└── Remaining: OAuth integration (90%), Search integration (10%)
+
+📋 USER STORIES (4 active)
+────────────────────────────────────────────────────────────────
+#34 Password Reset ████████████░░░░░░░░ 75%
+    Owner: John | 3/5 tasks done | 15h/27h complete
+    ⚡ In Progress: Task #104 (Integration tests)
+
+#35 User Profile ██████░░░░░░░░░░░░░░ 40%
+    Owner: Sarah | 2/6 tasks done | 8h/20h complete
+    ⚠️ At Risk: Behind schedule by 1 day
+
+#36 OAuth Login ████████████████░░░░ 90%
+    Owner: Mike | 5/6 tasks done | 18h/20h complete
+    ✅ On Track: Completing today
+
+#37 Search Feature ██░░░░░░░░░░░░░░░░░░ 10%
+    Owner: Lisa | 1/8 tasks done | 2h/32h complete
+    🔴 Blocked: Waiting for search API
+
+⚙️ TASKS (12 active)
+────────────────────────────────────────────────────────────────
+Currently In Progress:
+┌──────┬────────────────────┬──────────┬─────────┬────────────┐
+│ ID   │ Task               │ Assigned │ Hours   │ Started    │
+├──────┼────────────────────┼──────────┼─────────┼────────────┤
+│ #104 │ Integration tests  │ John     │ 2h/6h   │ 2 hrs ago  │
+│ #218 │ UI components      │ Sarah    │ 5h/8h   │ Yesterday  │
+│ #301 │ API endpoints      │ Mike     │ 7h/10h  │ 3 days ago │
+│ #402 │ Database schema    │ Lisa     │ 1h/4h   │ Today      │
+└──────┴────────────────────┴──────────┴─────────┴────────────┘
+
+🔥 HOT ITEMS (Need Attention)
+────────────────────────────────────────────────────────────────
+⏰ Due Today:
+  • Task #301: API endpoints (Mike) - 3h remaining
+  • Story #36: OAuth Login - Final testing needed
+
+⚠️ Overdue:
+  • Task #215: Bug fix (unassigned) - 1 day overdue
+
+🔄 Long Running (>3 days):
+  • Task #301: API endpoints - Consider breaking down
+  • Story #35: User Profile - May need help
+
+📊 TEAM UTILIZATION
+────────────────────────────────────────────────────────────────
+John:   ████████░░ 80% (2 active items, 32h/40h)
+Sarah:  █████████░ 88% (3 active items, 28h/32h)
+Mike:   ███████░░░ 75% (2 active items, 30h/40h)
+Lisa:   ██████░░░░ 67% (1 active item, 16h/24h)
+
+Team Average: 78% utilized
+Available Capacity: 30h across team
+
+💡 RECOMMENDATIONS
+────────────────────────────────────────────────────────────────
+1. Help Mike complete Task #301 (due today)
+2. Assign Task #215 (overdue bug)
+3. Check on Story #35 progress with Sarah
+4. Unblock Story #37 or defer to next sprint
+
+⚡ Quick Actions:
+[1] Update progress on my items
+[2] Take on Task #215
+[3] View blocked items details
+[4] Export active work list
+[5] Refresh status
+
+Select (1-5): _
+```
+
+### 3. Personal Active Work View
+
+```
+👤 Your Active Work
+═══════════════════════════════════════════════════════════════
+
+🎯 Current Focus:
+Task #104: Integration tests (Story #34)
+Progress: ███░░░░░░░ 33% | 2h/6h complete
+Started: 2 hours ago | Branch: task-104-integration
+
+📋 Your Active Items:
+1. Task #104: Integration tests - 33% (In Progress)
+2. Task #105: Documentation - 0% (Assigned, Not Started)
+3. Story #34: Password Reset - 75% (Owner)
+
+⏱️ Time Tracking:
+Today: 2h logged (6h remaining)
+This Week: 28h logged (12h remaining)
+Sprint: 80% capacity used
+
+📅 Upcoming:
+• Task #105: Documentation (3h) - Start after #104
+• Code Review: PR #457 waiting
+• Story #38: Planning needed
+
+[Press Enter to update progress]
+```
+
+### 4. Quick Filters
+
+```bash
+# By status
+/azure:active-work --status="In Progress"
+
+# By priority
+/azure:active-work --priority=1
+
+# By type
+/azure:active-work --type=story
+
+# By time
+/azure:active-work --started-today
+/azure:active-work --overdue
+```
+
+## Smart Features
+
+### Stale Detection
+- Flag items active >5 days
+- Suggest intervention
+- Recommend breakdown
+
+### Load Balancing
+- Identify overloaded members
+- Suggest redistribution
+- Show available capacity
+
+### Risk Assessment
+- Calculate completion probability
+- Flag at-risk items
+- Suggest mitigation

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

@@ -0,0 +1,143 @@
+# Azure DevOps Command Aliases
+
+Quick shortcuts for frequently used Azure DevOps commands.
+
+## User Story Aliases
+
+```bash
+# Short forms
+/az:us-new      → /azure:us-new
+/az:us          → /azure:us-list
+/az:story       → /azure:us-show
+/az:parse       → /azure:us-parse
+
+# Common workflows
+/az:new-story   → /azure:us-new
+/az:stories     → /azure:us-list
+/az:import      → /azure:import-us
+```
+
+## Task Aliases
+
+```bash
+# Short forms
+/az:task        → /azure:task-list
+/az:start       → /azure:task-start
+/az:done        → /azure:task-close
+/az:t           → /azure:task-show
+
+# Workflow shortcuts
+/az:begin       → /azure:task-start
+/az:finish      → /azure:task-close
+/az:complete    → /azure:task-close --create-pr
+/az:my-tasks    → /azure:task-list --assigned-to=me
+```
+
+## Sprint & Daily Aliases
+
+```bash
+# Daily workflow
+/az:daily       → /azure:standup
+/az:standup     → /azure:standup
+/az:sprint      → /azure:sprint-status
+/az:next        → /azure:next-task
+/az:blocked     → /azure:blocked-items
+
+# Status checks
+/az:status      → /azure:sprint-status
+/az:active      → /azure:active-work
+/az:my-work     → /azure:active-work --user=me
+```
+
+## Feature Aliases
+
+```bash
+# Feature management
+/az:feature     → /azure:feature-list
+/az:epic        → /azure:feature-new
+/az:decompose   → /azure:feature-decompose
+/az:breakdown   → /azure:feature-decompose
+```
+
+## Quick Access Aliases
+
+```bash
+# Most used commands
+/az:s           → /azure:search
+/az:?           → /azure:help
+/az:init        → /azure:init
+/az:sync        → /azure:sync-all
+
+# Productivity shortcuts
+/az:now         → /azure:next-task --auto-start
+/az:today       → /azure:standup --user=me
+/az:update      → /azure:sync-all
+```
+
+## Workflow Combinations
+
+```bash
+# Morning routine
+/az:morning     → /azure:standup && /azure:next-task
+
+# End of day
+/az:eod         → /azure:standup --summary && /azure:sync-all
+
+# Sprint planning
+/az:plan        → /azure:sprint-status && /azure:feature-decompose
+
+# Quick status
+/az:check       → /azure:active-work && /azure:blocked-items
+```
+
+## Custom Team Aliases
+
+Add your team-specific aliases here:
+
+```bash
+# Example team shortcuts
+/az:team-standup    → /azure:standup --team=dev
+/az:qa-tasks        → /azure:task-list --type=bug --assigned-to=qa
+/az:review          → /azure:task-list --needs-review
+```
+
+## 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
+
+
+## Usage Examples
+
+```bash
+# Start your day
+/az:morning         # Shows standup and suggests next task
+
+# Quick task workflow
+/az:next           # Get recommended task
+/az:start 102      # Start working on it
+/az:done 102       # Complete with PR
+
+# Check status
+/az:sprint         # Sprint dashboard
+/az:my-work        # Your active items
+/az:blocked        # See what's blocked
+```
+
+## Tips
+
+- Use TAB completion with aliases
+- Chain commands with && for workflows
+- Create team-specific aliases in this file
+- Aliases work in all contexts where commands work

package/packages/plugin-pm/commands/azure/blocked-items.md

@@ -0,0 +1,287 @@
+---
+allowed-tools: Task, Bash, Read, Write, WebFetch, Glob, Grep
+---
+
+# Azure DevOps Blocked Items
+
+Identify and manage blocked work items with resolution tracking.
+
+**Usage**: `/azure:blocked-items [--resolve] [--escalate]`
+
+**Examples**:
+- `/azure:blocked-items` - List all blocked items
+- `/azure:blocked-items --resolve` - Interactive resolution mode
+- `/azure:blocked-items --escalate` - Escalate to management
+- `/azure:blocked-items --by-reason` - Group by blocker type
+
+## 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. Identify Blocked Items
+
+Query for items with:
+- Tags containing "blocked"
+- Comments mentioning blockers
+- Dependencies not met
+- Stale items (no progress >3 days)
+
+### 2. Blocker Dashboard
+
+```
+🚧 Blocked Items Dashboard
+═══════════════════════════════════════════════════════════════
+Total Blocked: 7 items | Impact: 45 story points | 3 people affected
+
+🔴 CRITICAL BLOCKERS (Immediate Action Required)
+────────────────────────────────────────────────────────────────
+
+Story #37: Search Feature Implementation
+Blocked: 3 days | Impact: 8 points | Owner: Lisa
+Reason: Search API not deployed to staging
+Dependencies: Backend team API deployment
+Resolution: Contact Backend Team Lead
+Escalation: Required if not resolved by EOD
+
+Tasks Affected:
+  └── #371: Search UI (Lisa) - Cannot start
+  └── #372: Search tests (Lisa) - Cannot start
+  └── #373: Integration (Team) - Cannot start
+
+⚠️ HIGH PRIORITY BLOCKERS
+────────────────────────────────────────────────────────────────
+
+Task #104: Integration Tests
+Blocked: 4 hours | Impact: Story #34 completion | Owner: John
+Reason: Test environment database connection failing
+Dependencies: DevOps team
+Resolution: Ticket #OPS-234 opened
+Status: DevOps investigating, ETA 2 hours
+
+Task #215: Bug Fix
+Blocked: 1 day | Impact: Production hotfix | Owner: Unassigned
+Reason: Cannot reproduce issue, need more info from customer
+Dependencies: Customer Support
+Resolution: Awaiting customer response
+Action: Follow up with support team
+
+🟡 MEDIUM PRIORITY BLOCKERS
+────────────────────────────────────────────────────────────────
+
+Story #35: User Profile
+Blocked: 2 hours | Impact: 5 points | Owner: Sarah
+Reason: Waiting for design review
+Dependencies: UX team
+Resolution: Meeting scheduled 2 PM today
+Status: Will unblock after meeting
+
+📊 BLOCKER ANALYSIS
+────────────────────────────────────────────────────────────────
+
+By Type:
+  External Dependencies: 3 (43%)
+  Technical Issues: 2 (29%)
+  Missing Information: 1 (14%)
+  Resource Availability: 1 (14%)
+
+By Team:
+  Backend Team: 2 blockers
+  DevOps: 2 blockers
+  UX/Design: 1 blocker
+  Customer Support: 1 blocker
+  External Vendor: 1 blocker
+
+By Age:
+  < 1 day: 3 items
+  1-3 days: 2 items
+  > 3 days: 2 items (escalation needed)
+
+Impact on Sprint:
+  Stories at risk: 3 (21 points)
+  Sprint completion risk: HIGH
+  Recommended action: Defer Story #37
+
+📈 BLOCKER TRENDS
+────────────────────────────────────────────────────────────────
+
+This Sprint vs Last Sprint:
+  Total Blockers: 7 vs 4 (↑ 75%)
+  Avg Resolution Time: 18h vs 12h (↑ 50%)
+  Most Common: External deps (was Technical)
+
+Recurring Blockers:
+  • Test environment (3rd sprint in a row)
+  • API dependencies (2nd sprint)
+  • Design review delays (every sprint)
+
+🎯 RESOLUTION ACTIONS
+────────────────────────────────────────────────────────────────
+
+Immediate Actions:
+1. [CRITICAL] Escalate Story #37 to management
+2. [HIGH] Follow up on test environment fix
+3. [MEDIUM] Attend design review at 2 PM
+
+Assigned Actions:
+  John → Check OPS-234 ticket status
+  PM → Decide on Story #37 deferral
+  Sarah → Prepare for design review
+
+Preventive Actions:
+  • Schedule recurring design reviews
+  • Improve test environment monitoring
+  • Create dependency checklist
+
+⚡ Quick Actions:
+────────────────────────────────────────────────────────────────
+[1] Update blocker status
+[2] Escalate critical items
+[3] Send blocker report
+[4] Create resolution tickets
+[5] Show resolution history
+[6] Contact blocker owners
+
+Select (1-6): _
+```
+
+### 3. Resolution Tracking
+
+```
+🔧 Blocker Resolution Tracker
+═══════════════════════════════════════════════════════════════
+
+Active Resolutions:
+┌──────┬────────────────┬───────────┬─────────┬──────────────┐
+│ Item │ Blocker        │ Owner     │ ETA     │ Status       │
+├──────┼────────────────┼───────────┼─────────┼──────────────┤
+│ #104 │ Test env       │ DevOps    │ 2h      │ In Progress  │
+│ #37  │ API deploy     │ Backend   │ EOD     │ Escalated    │
+│ #35  │ Design review  │ UX Team   │ 2 PM    │ Scheduled    │
+│ #215 │ Customer info  │ Support   │ Unknown │ Waiting      │
+└──────┴────────────────┴───────────┴─────────┴──────────────┘
+
+Resolution History (Last 7 days):
+  ✅ Resolved: 12 blockers
+  ⏱️ Avg Time: 14 hours
+  🏆 Fastest: 2 hours (Database access)
+  😞 Slowest: 4 days (Vendor API)
+```
+
+### 4. Escalation Template
+
+When `--escalate` is used:
+
+```
+📧 Escalation Email Draft
+────────────────────────────────────────────────────────────────
+To: management@company.com
+Subject: Sprint 2 - Critical Blockers Requiring Escalation
+
+Critical Blockers Summary:
+- 7 items blocked (45 story points)
+- 3 team members affected
+- Sprint completion at risk
+
+Immediate Escalation Required:
+1. Story #37 (8 pts): Search API deployment blocked 3 days
+   Owner: Backend Team
+   Impact: Full feature cannot be delivered
+   
+Action Requested:
+- Authorize emergency deployment or
+- Approve deferral to Sprint 3
+
+Please respond by EOD today.
+
+[Send] [Edit] [Cancel]
+```
+
+### 5. Interactive Resolution Mode
+
+```
+🔧 Blocker Resolution Wizard
+────────────────────────────────────────────────────────────────
+
+Select blocked item to resolve:
+1. Story #37: Search API not deployed
+2. Task #104: Test environment down
+3. Task #215: Missing customer info
+
+Selection: 1
+
+Story #37 Resolution Options:
+a) Contact responsible team
+b) Find alternative solution
+c) Escalate to management
+d) Defer to next sprint
+e) Remove from sprint
+
+Choose action: c
+
+Escalating to management...
+✅ Escalation email sent to PM and Tech Lead
+✅ Slack notification sent to #blockers channel
+✅ Calendar invite sent for emergency meeting
+✅ Blocker tagged as "escalated" in Azure DevOps
+
+Next blocker? (y/n): _
+```
+
+## Smart Features
+
+### Auto-Detection
+- Identify stale items
+- Find hidden blockers
+- Predict future blocks
+
+### Resolution Patterns
+- Learn from history
+- Suggest solutions
+- Auto-assign resolvers
+
+### Impact Analysis
+- Calculate sprint risk
+- Show dependency chains
+- Prioritize unblocking
+
+## Notifications
+
+```yaml
+notifications:
+  new_blocker:
+    channel: "#dev-blockers"
+    mentions: ["@pm", "@techlead"]
+  
+  resolution:
+    channel: "#dev-general"
+    celebrate: true
+  
+  escalation:
+    email: "management@company.com"
+    urgent: true
+```