claude-autopm 2.7.0 → 2.8.2

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

@@ -1,262 +0,0 @@
----
-allowed-tools: Task, Bash, Read, Write, WebFetch, Glob, Grep
----
-
-# Azure DevOps Next Task
-
-Get AI-powered recommendation for the next task to work on based on priorities, dependencies, and capacity.
-
-**Usage**: `/azure:next-task [--user=<email>] [--auto-start]`
-
-**Examples**:
-- `/azure:next-task` - Get your next recommended task
-- `/azure:next-task --auto-start` - Get and immediately start the task
-- `/azure:next-task --user=sarah@example.com` - Recommend for specific user
-
-## 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. Analyze Context
-
-Use azure-devops-specialist agent to analyze:
-- Current sprint goals
-- User's active tasks
-- Task dependencies
-- Priority scores
-- Team capacity
-- Blockers
-
-### 2. Recommendation Algorithm
-
-Score tasks based on:
-- **Priority**: Critical > High > Medium > Low
-- **Dependencies**: Unblocked tasks first
-- **Sprint goals**: Align with sprint objectives
-- **Story completion**: Prefer finishing stories
-- **Skills match**: Match user expertise
-- **Time available**: Fit within capacity
-
-### 3. Display Recommendation
-
-```
-🎯 Next Task Recommendation
-═══════════════════════════════════════════════════════════
-
-Based on your current context, I recommend:
-
-📋 Task #104: Integration tests
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-Parent Story: #34 - Implement user password reset
-Estimated Time: 4h remaining
-Priority: High
-Status: In Progress (33% complete)
-
-📊 Why this task?
-────────────────────────────────────────────────────────────
-✓ Continues your current work (already 33% done)
-✓ High priority - blocks Story #34 completion
-✓ No dependencies - can start immediately
-✓ Fits your available time (4h task, 8h capacity)
-✓ Aligns with sprint goal (complete Story #34)
-✓ You have context from Task #102, #103
-
-📈 Impact of completing this:
-────────────────────────────────────────────────────────────
-• Story #34 will be 80% complete
-• Unblocks Task #105 (Documentation)
-• Moves sprint progress to 65%
-• Keeps team on track for sprint goal
-
-🔄 Alternative recommendations:
-────────────────────────────────────────────────────────────
-2. Task #220: Update API docs (2h) - Quick win
-3. Task #301: Bug fix (3h) - High priority
-4. Task #105: Documentation (3h) - If #104 blocked
-
-⚡ Quick Actions:
-────────────────────────────────────────────────────────────
-[1] Start Task #104 now
-[2] View task details
-[3] Check dependencies
-[4] See alternative tasks
-[5] Skip and get next recommendation
-
-Select (1-5): _
-```
-
-### 4. Auto-Start Mode
-
-If `--auto-start` flag is used:
-
-```
-🚀 Auto-starting recommended task...
-
-✅ Task #104 started!
-- Status: Active
-- Branch created: task-104-integration-tests
-- Assigned to: You
-- Timer started
-
-Opening work environment...
-- Work file: .claude/azure/tasks/104/work.md
-- Parent story: Loaded
-- Test files: Located at tests/integration/
-
-Ready to work! Good luck with integration tests!
-```
-
-### 5. No Tasks Available
-
-When no suitable tasks:
-
-```
-📭 No immediate tasks available
-
-Current situation:
-- All high-priority tasks are blocked
-- Your current tasks are waiting for review
-- No unassigned tasks match your skills
-
-Suggestions:
-1. Help unblock Task #215 (waiting for API specs)
-2. Review PR #457 (Sarah's code)
-3. Start planning next sprint
-4. Update documentation
-5. Pair with team member
-
-Would you like to:
-[1] View blocked tasks
-[2] See all available tasks
-[3] Check other team members' needs
-[4] Start sprint planning
-
-Select (1-4): _
-```
-
-### 6. Smart Context Features
-
-#### Continuation Detection
-If user has in-progress work:
-```
-💡 You have an in-progress task!
-
-Task #102: Implementation (60% complete)
-Last worked: 2 hours ago
-Recommendation: Continue this task
-
-Resume work? (y/n): _
-```
-
-#### End-of-Sprint Mode
-When sprint is ending:
-```
-⏰ Sprint ends in 1 day!
-
-Focusing on sprint completion:
-1. Task #104 (4h) - Must complete for Story #34
-2. Task #215 (1h) - Quick fix, high impact
-3. Skip Task #305 - Save for next sprint
-
-Start sprint-critical Task #104? (y/n): _
-```
-
-#### Skill-Based Matching
-```
-🎯 Matched to your expertise:
-
-Task #401: React component optimization
-Why: You completed 5 similar React tasks
-Success rate: 95% on React tasks
-Estimated time: 3h (based on your history)
-```
-
-### 7. Team Coordination
-
-Show when pairing would help:
-
-```
-👥 Pairing Opportunity!
-
-Task #104: Integration tests
-Sarah is also available and has context
-Pair programming would reduce time by 40%
-
-Invite Sarah to pair? (y/n): _
-```
-
-### 8. Learning Opportunities
-
-Suggest growth tasks:
-
-```
-📚 Learning Opportunity!
-
-Task #501: GraphQL implementation
-- New technology for you
-- Mike can mentor (he's available)
-- Good for skill development
-- Medium priority, good timing
-
-Take on this growth task? (y/n): _
-```
-
-## Configuration
-
-`.claude/azure/next-task-config.yml`:
-```yaml
-recommendation:
-  algorithm: "smart" # smart, priority, random
-  consider_skills: true
-  consider_capacity: true
-  prefer_story_completion: true
-  growth_tasks_weight: 0.2
-  
-filters:
-  min_priority: 3
-  max_hours: 8
-  exclude_types: ["research"]
-```
-
-## Analytics
-
-Track recommendation success:
-
-```
-📊 Recommendation Analytics (Last 30 days)
-
-Acceptance rate: 78%
-Completion rate: 92%
-Average time saved: 1.2h/task
-Most declined reason: "Already working on something"
-
-Top patterns:
-- Morning: Prefer complex tasks
-- Afternoon: Prefer quick wins
-- Friday: Prefer documentation
-```

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

@@ -1,160 +0,0 @@
----
-allowed-tools: Task, Bash, Read, Write, WebFetch, Glob, Grep
----
-
-# Azure DevOps Search
-
-Search work items across Azure DevOps with advanced filters.
-
-**Usage**: `/azure:search <query> [--type=<type>] [--field=<field>]`
-
-**Examples**:
-- `/azure:search "password reset"` - Search all items
-- `/azure:search "bug" --type=task` - Search tasks only
-- `/azure:search "john" --field=assigned-to` - Search by assignee
-
-## 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. Search Interface
-
-```
-🔍 Azure DevOps Search
-═══════════════════════════════════════════════════════════════
-
-Query: "password reset"
-Filters: All types, All fields, Active items
-
-Searching... Found 8 results
-
-📋 Results:
-─────────────────────────────────────────────────────────────
-
-USER STORIES (2)
-► #34 Implement user password reset [Active]
-  Relevance: ████████████ 100%
-  Assigned: john@example.com | Sprint 2
-  
-► #89 Forgot password flow [Closed]
-  Relevance: ████████░░░░ 65%
-  Closed: 2 months ago
-
-TASKS (5)
-► #102 Implementation - password reset logic [Active]
-  Relevance: ████████████ 100%
-  Parent: Story #34 | Assigned: john
-  
-► #103 Unit tests for password reset [Done]
-  Relevance: ██████████░░ 85%
-  Parent: Story #34 | Completed: Yesterday
-  
-► #104 Integration tests - password flow [Active]
-  Relevance: ████████░░░░ 70%
-  Parent: Story #34 | 33% complete
-
-BUGS (1)
-► #456 Password reset email not sending [Fixed]
-  Relevance: ██████░░░░░░ 50%
-  Fixed: Last week | Version: 1.2.3
-
-📊 Search Summary:
-- User Stories: 2 (1 active)
-- Tasks: 5 (2 active)
-- Bugs: 1 (0 active)
-
-Refine search:
-[1] Filter by type
-[2] Filter by status
-[3] Filter by date
-[4] New search
-[5] Export results
-
-Select (1-5): _
-```
-
-### 2. Advanced Query Syntax
-
-```
-Supported queries:
-- Exact match: "exact phrase"
-- Wildcard: pass*
-- Field search: assigned:john
-- Operators: AND, OR, NOT
-- Date: created:>2024-01-01
-- State: state:active
-- Tags: tag:security
-
-Examples:
-/azure:search "state:active AND assigned:@me"
-/azure:search "created:>7d AND type:bug"
-/azure:search "tag:security OR tag:auth"
-```
-
-### 3. Quick Filters
-
-```
-🔍 Quick Search Templates:
-
-[1] My active items
-[2] Unassigned tasks
-[3] Overdue items
-[4] Recent changes (last 7d)
-[5] High priority bugs
-[6] Blocked items
-[7] Items without estimates
-[8] Custom query
-
-Select template: _
-```
-
-### 4. Search Results Actions
-
-```
-Select item for actions:
-► #34 Implement user password reset
-
-Actions:
-[1] View details (/azure:us-show 34)
-[2] Edit (/azure:us-edit 34)
-[3] Start work (/azure:us-start 34)
-[4] View in browser
-[5] Copy link
-[6] Back to results
-
-Select: _
-```
-
-### 5. Export Options
-
-```
-Export search results:
-- CSV: search-results.csv
-- JSON: search-results.json
-- Markdown: search-results.md
-- HTML: search-results.html
-
-Include:
-✓ Title and ID
-✓ Status
-✓ Assigned To
-✓ Dates
-□ Description
-□ Comments
-□ History
-```

package/autopm/.claude/commands/azure/sprint-status.md

@@ -1,235 +0,0 @@
----
-allowed-tools: Task, Bash, Read, Write, WebFetch, Glob, Grep
----
-
-# Azure DevOps Sprint Status
-
-Comprehensive sprint dashboard with burndown, velocity, and team performance metrics.
-
-**Usage**: `/azure:sprint-status [sprint-name] [--format=<type>]`
-
-**Examples**:
-- `/azure:sprint-status` - Current sprint status
-- `/azure:sprint-status "Sprint 2"` - Specific sprint
-- `/azure:sprint-status --format=burndown` - Focus on burndown chart
-- `/azure:sprint-status --format=executive` - Executive summary
-
-## 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. Sprint Overview Dashboard
-
-```
-🏃 Sprint 2 Status - Day 8 of 10
-═══════════════════════════════════════════════════════════════
-
-📊 SPRINT HEALTH: ⚠️ AT RISK
-────────────────────────────────────────────────────────────────
-
-Overall Progress: ████████████░░░░░░░░ 62%
-Story Points: 21/34 completed
-Tasks: 18/42 completed
-Hours: 84/156 completed
-
-🎯 Sprint Goals:
-────────────────────────────────────────────────────────────────
-1. ✅ Complete authentication system (Done)
-2. 🔄 Implement password reset (75% - On Track)
-3. ⚠️ Launch user profile (40% - At Risk)
-4. ❌ Search functionality (10% - Will Not Complete)
-
-📈 Burndown Chart:
-────────────────────────────────────────────────────────────────
-Hours
-160 |■ Ideal
-140 |■■■.
-120 |■■■■■■..
-100 |■■■■■■■■■... (Ideal)
- 80 |■■■■■■■■■■■■■■.. 
- 60 |■■■■■■■■■■■■■■■■■■ (Actual)
- 40 |■■■■■■■■■■■■■■■■■■■■■
- 20 |■■■■■■■■■■■■■■■■■■■■■■■■
-  0 +──────────────────────────→
-    M  T  W  T  F  M  T  W  T  F
-    1  2  3  4  5  6  7  8  9  10
-                        ↑
-                      Today
-
-Status: 12 hours behind ideal
-Projection: Need 36h/day to complete (have 29h capacity)
-
-📋 User Stories Status:
-────────────────────────────────────────────────────────────────
- ID | Title                      | Points | Progress | Status
-----+----------------------------+--------+----------+----------
- 34 | Password Reset             | 8      | 75%      | On Track
- 35 | User Profile               | 5      | 40%      | At Risk
- 36 | OAuth Integration          | 13     | 90%      | On Track
- 37 | Search Feature             | 8      | 10%      | Blocked
-
-👥 Team Performance:
-────────────────────────────────────────────────────────────────
-         | Assigned | Complete | In Prog | Capacity | Utilization
----------+----------+----------+---------+----------+------------
-John     | 8 tasks  | 5        | 2       | 32h/40h  | 80%
-Sarah    | 7 tasks  | 4        | 2       | 28h/32h  | 88%
-Mike     | 6 tasks  | 3        | 1       | 30h/40h  | 75%
-Lisa     | 5 tasks  | 4        | 1       | 16h/24h  | 67%
----------+----------+----------+---------+----------+------------
-Total    | 26       | 16       | 6       | 106/136h | 78%
-
-🚧 Blockers & Risks:
-────────────────────────────────────────────────────────────────
-🔴 CRITICAL:
-• Story #37: Search API not ready (blocking 8 points)
-
-⚠️ HIGH:
-• Test environment unstable (affecting 3 people)
-• Story #35: Needs 2 more days but only 1.5 available
-
-🟡 MEDIUM:
-• PR review backlog: 4 PRs waiting >24h
-• Mike at risk of burnout (88% capacity)
-
-🎬 Key Actions Needed:
-────────────────────────────────────────────────────────────────
-1. ⚡ Move Story #37 to next sprint (PM decision needed)
-2. ⚡ Add Sarah to help with Story #35
-3. ⚡ Schedule emergency fix for test environment
-4. ⚡ Clear PR backlog today
-
-📊 Velocity Metrics:
-────────────────────────────────────────────────────────────────
-Current Sprint: 21 points (tracking for 26)
-Last 3 Sprints: 28, 31, 29 (avg: 29.3)
-Velocity Trend: ↘️ Declining
-
-Team capacity next sprint: -2 developers (vacation)
-Recommended load: 24 points maximum
-```
-
-### 2. Burndown Focus View
-
-```
-📉 Sprint 2 Burndown Analysis
-═══════════════════════════════════════════════════════════════
-
-Remaining Work Trend:
-Day 1: 156h ████████████████████████████████
-Day 2: 148h ███████████████████████████████
-Day 3: 135h ████████████████████████████
-Day 4: 128h ██████████████████████████
-Day 5: 115h ████████████████████████
-Day 6: 102h █████████████████████
-Day 7: 89h  ██████████████████
-Day 8: 72h  ███████████████ ← Current
-Day 9: ?    Projected: 45h
-Day 10: ?   Projected: 18h (Need: 0h)
-
-⚠️ Gap Analysis:
-- Behind by: 12 hours
-- Daily burn rate needed: 36h
-- Current burn rate: 24h
-- Gap: -12h/day
-
-Recovery Options:
-1. Reduce scope by 18h (Move 2-3 tasks)
-2. Add overtime (not recommended)
-3. Defer Story #37 (saves 24h)
-```
-
-### 3. Executive Summary
-
-```
-📊 Sprint 2 - Executive Summary
-═══════════════════════════════════════════════════════════════
-
-SPRINT STATUS: ⚠️ AT RISK
-
-Completion Forecast: 76% of committed work
-Key Deliverables:
-  ✅ Authentication system - COMPLETE
-  ⚠️ Password reset - 75% (will complete)
-  ⚠️ User profile - 40% (at risk)
-  ❌ Search feature - 10% (defer to Sprint 3)
-
-Financial Impact:
-- Sprint Budget: $45,000
-- Burn Rate: $4,500/day
-- At Risk Value: $12,000 (Story #37)
-
-Recommendations:
-1. Defer search feature (Story #37)
-2. Reallocate resources to Story #35
-3. Plan 24 points for Sprint 3 (team capacity reduced)
-
-Next Sprint Planning: Thursday 2 PM
-Sprint Review: Friday 3 PM
-Retrospective: Friday 4 PM
-```
-
-### 4. Quick Actions Menu
-
-```
-⚡ Quick Actions:
-[1] Update task hours
-[2] Move story to next sprint
-[3] Assign resources
-[4] Export report
-[5] Send to Slack
-[6] View detailed metrics
-
-Select (1-6): _
-```
-
-## Export Formats
-
-- `--format=burndown` - Burndown chart focus
-- `--format=executive` - Executive summary
-- `--format=team` - Team performance
-- `--format=risks` - Blockers and risks
-- `--format=pdf` - Full PDF report
-- `--format=json` - Raw data for dashboards
-
-## Automated Alerts
-
-```yaml
-alerts:
-  behind_schedule:
-    threshold: 10%
-    action: notify_pm
-  
-  blocked_stories:
-    threshold: 2
-    action: escalate
-  
-  capacity_exceeded:
-    threshold: 90%
-    action: warn_team
-```