claude-autopm 2.7.0 → 2.8.2

package/autopm/.claude/commands/azure/us-show.md

@@ -1,188 +0,0 @@
----
-allowed-tools: Task, Bash, Read, Write, WebFetch, Glob, Grep
----
-
-# Azure DevOps User Story Show
-
-Display detailed information about a specific User Story.
-
-**Usage**: `/azure:us-show <story-id> [--format=<type>]`
-
-**Examples**:
-- `/azure:us-show 34`
-- `/azure:us-show 34 --format=json`
-- `/azure:us-show 34 --include-tasks`
-- `/azure:us-show 34 --history`
-
-## 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. Fetch User Story Details
-
-Use azure-devops-specialist agent to get full work item:
-- All fields and metadata
-- Child tasks
-- Parent feature/epic
-- Related work items
-- Comments and history
-
-### 2. Display Format
-
-```
-═══════════════════════════════════════════════════════════════
-📋 User Story #34
-═══════════════════════════════════════════════════════════════
-
-Title: Implement user password reset
-State: 🔄 Active
-URL: https://dev.azure.com/rafal0387/Speacher/_workitems/edit/34
-
-📝 Details
-─────────────────────────────────────────────────────────────
-Description:
-As a registered user, I want to reset my password when I forget it,
-so that I can regain access to my account without contacting support.
-
-Acceptance Criteria:
-✓ User can initiate password reset from login page
-✓ System sends reset link to registered email address
-✓ Reset link expires after 24 hours
-✓ User can set new password meeting security requirements
-✓ System confirms successful password reset via email
-✓ Old password becomes invalid immediately after reset
-
-📊 Metadata
-─────────────────────────────────────────────────────────────
-Story Points: 8
-Priority: 2 (High)
-Value Area: Business
-Risk: Medium
-Effort: 8
-Business Value: 85
-
-👤 Assignment
-─────────────────────────────────────────────────────────────
-Assigned To: john@example.com
-Created By: rafal@lagowski.es
-Created Date: 2025-01-10T15:51:05.667Z
-Modified Date: 2025-01-10T16:45:23.123Z
-
-📍 Organization
-─────────────────────────────────────────────────────────────
-Area Path: Speacher\Security
-Iteration Path: Speacher\Sprint 2
-Tags: security, authentication, mvp
-
-🔗 Relationships
-─────────────────────────────────────────────────────────────
-Parent Feature: #25 - Authentication System
-Child Tasks: 6 tasks (27h total)
-  ├── #101 ✅ Technical Design (4h)
-  ├── #102 ✅ Implementation (12h)
-  ├── #103 ✅ Unit tests (4h)
-  ├── #104 🔄 Integration tests (6h)
-  ├── #105 🆕 Documentation (3h)
-  └── #106 🆕 Code review (2h)
-
-Related Items:
-  → #35 User Profile (depends on this)
-  ← #32 API Gateway setup (blocks this)
-
-📈 Progress
-─────────────────────────────────────────────────────────────
-Tasks: ████████████░░░░░░░░ 60% (3/5 completed)
-Hours: ███████████░░░░░░░░░ 55% (15h/27h)
-Sprint Progress: Day 3 of 10
-
-💬 Recent Activity
-─────────────────────────────────────────────────────────────
-• 2h ago: Sarah started integration tests (Task #104)
-• 5h ago: John completed implementation (Task #102)
-• Yesterday: Priority changed from 3 to 2
-• 2 days ago: Moved to Sprint 2
-• 3 days ago: Story created and parsed into tasks
-
-📎 Attachments
-─────────────────────────────────────────────────────────────
-• mockup-password-reset.png (125 KB)
-• security-requirements.pdf (89 KB)
-• email-templates.html (12 KB)
-
-🔧 Actions
-─────────────────────────────────────────────────────────────
-[1] Edit story (/azure:us-edit 34)
-[2] View tasks (/azure:task-list 34)
-[3] Update status (/azure:us-status 34)
-[4] Add comment
-[5] Export to JSON/CSV
-[6] Open in browser
-
-Select action (1-6) or press Enter to exit: _
-```
-
-### 3. Compact Mode
-
-For quick overview (default when listing multiple):
-
-```
-📋 #34: Implement user password reset
-Status: Active | Points: 8 | Assigned: john@example.com
-Progress: 60% tasks, 55% hours | Sprint 2
-Next: Complete integration tests (#104)
-```
-
-### 4. Export Formats
-
-Support various export formats:
-
-```bash
-# JSON format for integration
-/azure:us-show 34 --format=json > story-34.json
-
-# Markdown for documentation
-/azure:us-show 34 --format=markdown > STORY-34.md
-
-# CSV for reporting
-/azure:us-show 34 --format=csv > story-34.csv
-```
-
-### 5. Include Options
-
-- `--include-tasks`: Show all child tasks
-- `--include-comments`: Show all comments
-- `--include-history`: Show change history
-- `--include-attachments`: List attachments
-- `--include-links`: Show all links
-- `--full`: Include everything
-
-## Error Handling
-
-- Story not found: Suggest similar IDs
-- No permission: Show access request info
-- API timeout: Use cached data if available

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

@@ -1,320 +0,0 @@
----
-allowed-tools: Task, Bash, Read, Write, WebFetch, Glob, Grep
----
-
-# Azure DevOps User Story Status
-
-Show comprehensive status of User Stories with task progress and metrics.
-
-**Usage**: `/azure:us-status [user-story-id] [--sprint=<name>] [--format=<type>]`
-
-**Examples**:
-- `/azure:us-status` - Status of all active User Stories
-- `/azure:us-status 34` - Detailed status of specific User Story
-- `/azure:us-status --sprint="Sprint 1"` - Sprint-specific status
-- `/azure:us-status --format=burndown` - Show burndown chart
-
-## 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 Mode
-
-Determine display based on arguments:
-- **No args**: Show all active stories dashboard
-- **Story ID**: Deep dive into specific story
-- **Sprint filter**: Sprint-focused view
-- **Format option**: Specialized visualizations
-
-### 2. Status Displays
-
-#### Single User Story Status
-
-```
-📊 User Story #34: Implement user password reset
-Status: 🔄 Active | Sprint: Sprint 1 | Points: 8
-
-📈 Progress Overview
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-Tasks:     ████████████░░░░░░░░  60% (3/5 completed)
-Hours:     ███████████░░░░░░░░░░  55% (15h/27h completed)
-Quality:   ████████████████████░  95% (tests passing)
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-📋 Task Breakdown:
-┌─────┬──────────────────────┬────────┬──────────┬────────┬─────────┐
-│ ID  │ Task                 │ Status │ Assignee │ Hours  │ Branch  │
-├─────┼──────────────────────┼────────┼──────────┼────────┼─────────┤
-│ 101 │ Technical Design     │ ✅     │ John     │ 4h/4h  │ merged  │
-│ 102 │ Implementation       │ ✅     │ John     │ 10h/12h│ merged  │
-│ 103 │ Unit tests          │ ✅     │ Sarah    │ 4h/4h  │ merged  │
-│ 104 │ Integration tests    │ 🔄     │ Sarah    │ 2h/6h  │ task-104│
-│ 105 │ Documentation       │ 🆕     │ -        │ 0h/3h  │ -       │
-└─────┴──────────────────────┴────────┴──────────┴────────┴─────────┘
-
-⏰ Timeline:
-- Started: 3 days ago
-- Est. Completion: 2 days
-- Velocity: 5h/day
-- Risk: Low ✅
-
-🔗 Dependencies:
-- Blocking: None
-- Blocked by: API Gateway setup (#32)
-
-💬 Recent Activity:
-- 2h ago: Sarah started integration tests
-- 5h ago: John completed implementation
-- Yesterday: Code review approved
-
-⚡ Recommended Actions:
-1. Complete integration tests (Task #104)
-2. Start documentation while tests run
-3. Schedule demo for stakeholders
-```
-
-#### Sprint Dashboard View
-
-```
-🏃 Sprint 1 Status Dashboard
-Days: 5/10 | Capacity: 45% used
-
-User Stories Progress:
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-#34 Password Reset    ████████████░░░░░  70% [8pts]
-#35 User Profile      ██████░░░░░░░░░░░  35% [5pts]
-#36 OAuth Login       ████████████████░  90% [13pts]
-#37 Search Feature    ██░░░░░░░░░░░░░░░  10% [8pts]
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-📊 Sprint Metrics:
-┌────────────────┬───────┬────────┬─────────┐
-│ Metric         │ Plan  │ Actual │ Status  │
-├────────────────┼───────┼────────┼─────────┤
-│ Story Points   │ 34    │ 15     │ ⚠️ Behind│
-│ Tasks Complete │ 20    │ 12     │ ⚠️ At Risk│
-│ Hours Burned   │ 100h  │ 45h    │ ✅ On Track│
-│ Defects Found  │ <5    │ 2      │ ✅ Good  │
-└────────────────┴───────┴────────┴─────────┘
-
-👥 Team Performance:
-- John: 3 tasks complete, 2 in progress
-- Sarah: 2 tasks complete, 1 in progress
-- Mike: 1 task complete, 3 in progress
-- Unassigned: 8 tasks
-
-⚠️ Risks & Blockers:
-1. OAuth integration delayed (external dependency)
-2. Search feature needs design review
-3. Mike overloaded - consider redistribution
-```
-
-#### Burndown Chart
-
-```
-📉 Sprint Burndown Chart
-
-Hours
-120 |■
-110 |■■
-100 |■■■ (Ideal)
- 90 |■■■■■.
- 80 |■■■■■■■■..
- 70 |■■■■■■■■■■■...
- 60 |■■■■■■■■■■■■■■■.. (Actual)
- 50 |■■■■■■■■■■■■■■■■■■■
- 40 |■■■■■■■■■■■■■■■■■■■■■
- 30 |■■■■■■■■■■■■■■■■■■■■■■■
- 20 |■■■■■■■■■■■■■■■■■■■■■■■■■
- 10 |■■■■■■■■■■■■■■■■■■■■■■■■■■■
-  0 +────────────────────────────→
-    M  T  W  T  F  M  T  W  T  F
-    ↑
-    Today
-
-Status: Slightly behind ideal pace
-Projection: May need 1 extra day or scope reduction
-```
-
-### 3. Detailed Metrics
-
-#### Velocity Analysis
-
-```
-📈 Velocity Trends
-
-Story Points/Sprint
-20 |      ■
-18 |    ■ ■
-16 |    ■ ■ ■
-14 |  ■ ■ ■ ■
-12 |■ ■ ■ ■ ■ (avg: 15)
-10 |■ ■ ■ ■ ■
- 8 |■ ■ ■ ■ ■
-   └──────────────→
-   S1 S2 S3 S4 S5
-
-Current Sprint: Tracking at 13 points
-Recommendation: Realistic capacity is 15 points
-```
-
-#### Quality Metrics
-
-```
-✅ Quality Dashboard
-
-Test Coverage: ████████████████░░░░ 82%
-Code Reviews:  ████████████████████ 100%
-Bug Density:   ████░░░░░░░░░░░░░░░░ 2/story (Good)
-Tech Debt:     ██████░░░░░░░░░░░░░░ 30% (Manage)
-
-Recent Issues:
-- 🐛 Bug #451: Login timeout (Fixed)
-- 🐛 Bug #452: Validation error (In Progress)
-- 💡 Improvement: Refactor auth service
-```
-
-### 4. Forecast & Predictions
-
-```
-🔮 Completion Forecast
-
-Based on current velocity:
-- Story #34: Complete by Thursday ✅
-- Story #35: At risk - needs 2 more devs
-- Story #36: On track for Friday
-- Story #37: Won't complete this sprint ❌
-
-Recommendations:
-1. Move Story #37 to next sprint
-2. Add Sarah to Story #35
-3. Schedule sprint review for Friday PM
-```
-
-### 5. Export Formats
-
-Support multiple export formats:
-
-```bash
-# Export as CSV
-/azure:us-status --format=csv > sprint-status.csv
-
-# Export as JSON for dashboards
-/azure:us-status --format=json > status.json
-
-# Generate HTML report
-/azure:us-status --format=html > report.html
-
-# Markdown for documentation
-/azure:us-status --format=markdown > STATUS.md
-```
-
-### 6. Integration Status
-
-Show CI/CD and PR status:
-
-```
-🔄 Integration Status
-
-Story #34: Password Reset
-├── PR #456: ✅ Merged
-├── PR #457: 👀 In Review (2 approvals needed)
-├── PR #458: 🚧 Draft
-│
-├── CI/CD Pipeline:
-│   ├── Build: ✅ Passing
-│   ├── Tests: ✅ 157/157 passing
-│   ├── Security: ⚠️ 1 medium issue
-│   └── Deploy: ⏸️ Waiting
-│
-└── Environments:
-    ├── Dev: ✅ Deployed (v1.2.3-rc1)
-    ├── Staging: ⏳ Scheduled for tonight
-    └── Prod: 📅 Planned for Monday
-```
-
-### 7. Alerts & Notifications
-
-Highlight important status changes:
-
-```
-🔔 Alerts
-
-⚠️ HIGH: Story #35 blocked by external API
-⏰ MEDIUM: Story #36 review needed today
-📌 LOW: Update estimates for Story #37
-
-Would you like to:
-1. View blocker details
-2. Send review reminder
-3. Re-estimate story
-4. Dismiss alerts
-
-Select (1-4): _
-```
-
-## Smart Features
-
-### Predictive Analytics
-- Estimate completion dates
-- Identify at-risk stories
-- Suggest resource reallocation
-
-### Automated Recommendations
-- Next best action for each story
-- Optimal task assignments
-- Risk mitigation strategies
-
-### Historical Comparison
-- Compare with previous sprints
-- Track improvement trends
-- Identify recurring issues
-
-## Error Handling
-
-- **No stories found**: Check filters and sprint
-- **API timeout**: Use cached data if available
-- **Invalid sprint**: List available sprints
-
-## Configuration
-
-Support custom status views:
-
-```yaml
-# .claude/azure/status-config.yml
-views:
-  default:
-    show_burndown: true
-    show_velocity: true
-    alert_threshold: 80
-  
-  executive:
-    summary_only: true
-    show_risks: true
-    export_format: pdf
-```

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

@@ -1,86 +0,0 @@
----
-allowed-tools: Task, Bash, Read, Write, WebFetch, Glob, Grep
----
-
-# Azure DevOps Validate
-
-Validate work item structure and relationships for consistency.
-
-**Usage**: `/azure:validate [--fix] [--type=<type>]`
-
-**Examples**:
-- `/azure:validate` - Check all items
-- `/azure:validate --fix` - Auto-fix issues
-- `/azure:validate --type=story` - Validate stories only
-
-## 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
-
-### Validation Report
-
-```
-🔍 Azure DevOps Validation Report
-═══════════════════════════════════════════════════════════════
-
-Checking work item integrity...
-
-✅ PASSED (45 items)
-─────────────────────────────────────────────────────────────
-✓ All tasks have parent stories
-✓ All stories have valid estimates
-✓ No duplicate work items
-✓ All required fields populated
-
-⚠️ WARNINGS (8 items)
-─────────────────────────────────────────────────────────────
-• Story #34: Missing acceptance criteria
-• Task #102: No remaining hours set
-• Task #105: Not assigned
-• Feature #27: No target date
-
-❌ ERRORS (3 items)
-─────────────────────────────────────────────────────────────
-• Task #108: Orphaned (parent deleted)
-• Story #39: Invalid state transition
-• Task #112: Circular dependency
-
-📋 Recommendations:
-─────────────────────────────────────────────────────────────
-1. Add acceptance criteria to Story #34
-2. Assign Task #105 to team member
-3. Delete orphaned Task #108
-4. Fix Story #39 state
-
-Auto-fix available for 2 issues.
-Run with --fix? (y/n): _
-```
-
-### Validation Rules
-
-```
-Checking:
-✓ Parent-child relationships
-✓ Required fields
-✓ State transitions
-✓ Estimate ranges
-✓ Date consistency
-✓ Assignment validity
-✓ Dependency cycles
-✓ Duplicate detection
-```

package/autopm/.claude/commands/azure/work-item-sync.md

@@ -1,47 +0,0 @@
----
-allowed-tools: Task, Bash, Read, Write, Edit, WebFetch, Glob, Grep
----
-
-# Azure DevOps Work Item Synchronization
-
-Synchronizes GitHub Issues with Azure DevOps Work Items bidirectionally.
-
-**Usage**: `/azure:work-item-sync [--direction=both|github-to-azure|azure-to-github] [--project=project-name] [--area-path=area]`
-
-## 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
-
-
-**Example**: `/azure:work-item-sync --direction=both --project=MyProject --area-path=MyProject\Team1`
-
-**What this does**:
-- Authenticates with Azure DevOps using PAT
-- Fetches GitHub Issues and Azure DevOps Work Items
-- Maps fields between systems (title, description, labels, assignees, status)
-- Creates missing work items/issues in target systems
-- Updates existing items with latest changes
-- Maintains relationship links and sync metadata
-
-Use the azure-devops-specialist agent to implement bidirectional synchronization between GitHub Issues and Azure DevOps Work Items.
-
-Requirements for the agent:
-- Set up Azure DevOps REST API authentication using Personal Access Token
-- Implement GitHub Issues API integration using GitHub CLI or REST API
-- Create field mapping between GitHub Issues and Azure DevOps Work Items
-- Handle bidirectional synchronization with conflict resolution
-- Maintain sync metadata to track relationships and prevent duplicates
-- Implement proper error handling and retry logic for API failures
-- Add progress reporting and detailed logging of sync operations

package/autopm/.claude/commands/cloud/infra-deploy.md

@@ -1,38 +0,0 @@
----
-allowed-tools: Task, Read, Write, Edit, MultiEdit, Bash, Glob, Grep
----
-
-# Cloud Infrastructure Deployment
-
-Deploys infrastructure to cloud providers using Terraform.
-
-**Usage**: `/cloud:infra-deploy [--provider=aws|azure|gcp] [--env=dev|staging|prod] [--services=compute,storage,database]`
-
-## Required Documentation Access
-
-**MANDATORY:** Before deploying infrastructure, query Context7 for best practices:
-
-**Documentation Queries:**
-- `mcp://context7/infrastructure/deployment` - deployment best practices
-- `mcp://context7/cloud/best-practices` - best practices best practices
-- `mcp://context7/devops/automation` - automation best practices
-- `mcp://context7/infrastructure/configuration` - configuration 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
-
-
-**Example**: `/cloud:infra-deploy --provider=aws --env=staging --services=eks,rds,s3`
-
-**What this does**:
-- Creates Terraform modules for selected cloud
-- Configures provider and backend
-- Sets up networking and security
-- Deploys requested services
-- Implements cost optimization
-- Adds monitoring and alerting
-
-Use the appropriate cloud architect agent (aws-cloud-architect, azure-cloud-architect, or gcp-cloud-architect) based on provider.