claude-autopm 2.8.2 → 2.8.3

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

@@ -0,0 +1,93 @@
+---
+allowed-tools: Task, Bash, Read, Write, Edit, Glob, Grep
+---
+
+# Azure DevOps Clean
+
+Clean up completed items and optimize work item structure.
+
+**Usage**: `/azure:clean [--archive] [--older-than=<days>]`
+
+**Examples**:
+- `/azure:clean` - Clean completed items
+- `/azure:clean --archive` - Archive to file
+- `/azure:clean --older-than=30` - Clean items older than 30 days
+
+## 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
+
+### Cleanup Process
+
+```
+🧹 Azure DevOps Cleanup
+═══════════════════════════════════════════════════════════════
+
+Analyzing completed items...
+
+Items to clean:
+─────────────────────────────────────────────────────────────
+Completed Stories (30+ days old):
+  • #12: Old login system (45 days)
+  • #15: Legacy API (38 days)
+  • #18: Deprecated feature (35 days)
+
+Completed Tasks (30+ days old):
+  • 25 tasks from completed stories
+
+Closed Bugs (60+ days old):
+  • 12 bugs marked as Won't Fix or Duplicate
+
+Total: 40 items (freeing ~2GB cache)
+
+Actions:
+[1] Archive to .claude/azure/archive/2025-01.json
+[2] Delete from local cache only
+[3] Delete from Azure DevOps (requires confirmation)
+[4] Skip cleanup
+
+Choose: 1
+
+Archiving...
+✓ Archived 40 items to archive/2025-01.json
+✓ Removed from active cache
+✓ Cache optimized: 2GB → 500MB
+
+📊 Cleanup Summary:
+- Stories: 3 archived
+- Tasks: 25 archived
+- Bugs: 12 archived
+- Space saved: 1.5GB
+- Performance improved: +30%
+```
+
+### Archive Structure
+
+```json
+{
+  "archive_date": "2025-01-10",
+  "items_count": 40,
+  "stories": [...],
+  "tasks": [...],
+  "bugs": [...],
+  "metadata": {
+    "oldest_item": "2024-11-01",
+    "newest_item": "2024-12-10"
+  }
+}
+```

package/packages/plugin-pm/commands/azure/docs-query.md

@@ -0,0 +1,48 @@
+---
+allowed-tools: Task, Read, WebFetch, Glob, Grep
+---
+
+# Azure DevOps Documentation Query
+
+Queries latest Azure DevOps documentation via context7 before integration work.
+
+**Usage**: `/azure:docs-query [--topic=rest-api|pipelines|work-items|extensions] [--version=latest|7.0|6.0] [--examples]`
+
+## 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
+
+
+**Examples**: 
+- `/azure:docs-query --topic=rest-api --version=latest`
+- `/azure:docs-query --topic=work-items --examples`
+- `/azure:docs-query --topic=pipelines --examples`
+
+**What this does**:
+- Queries context7 for latest Azure DevOps documentation
+- Retrieves API endpoints, schemas, and authentication methods  
+- Returns relevant examples and integration patterns
+- Provides version compatibility and feature availability info
+- Shows security best practices and rate limiting guidelines
+
+Use the azure-devops-specialist agent to query documentation and provide integration guidance.
+
+Requirements for the agent:
+- Query MCP context7 documentation servers for Azure DevOps topics
+- Retrieve latest API versions, endpoints, and authentication patterns
+- Extract relevant integration examples and configuration samples
+- Verify feature availability across different Azure DevOps tiers
+- Format results with clear API examples and authentication code
+- Include security recommendations and rate limiting best practices

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

@@ -0,0 +1,380 @@
+---
+allowed-tools: Task, Bash, Read, Write, Edit, WebFetch, Glob, Grep
+---
+
+# Azure DevOps Feature Decompose
+
+Break down a Feature/Epic into User Stories with comprehensive planning.
+
+**Usage**: `/azure:feature-decompose <feature-id|feature-name>`
+
+**Examples**:
+- `/azure:feature-decompose 25` - Decompose Feature #25
+- `/azure:feature-decompose authentication-system` - Create and decompose new feature
+
+## 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 decomposing Azure features, query Context7 for best practices:
+
+**Documentation Queries:**
+- `mcp://context7/agile/feature-breakdown` - feature breakdown best practices
+- `mcp://context7/azure-devops/features` - features best practices
+- `mcp://context7/agile/task-sizing` - task sizing best practices
+- `mcp://context7/project-management/work-breakdown` - work breakdown 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 Analysis
+
+If numeric ID provided:
+- Fetch existing Feature/Epic from Azure DevOps
+- Analyze description and requirements
+
+If name provided:
+- Create new Feature/Epic first
+- Guide through feature definition
+
+### 2. Decomposition Strategy
+
+#### Interactive Discovery
+
+```
+🎯 Feature: Authentication System
+
+Let's break this down into User Stories.
+
+What types of users will interact with this feature?
+1. End Users (customers)
+2. Administrators
+3. Support Staff
+4. System/API consumers
+5. All of the above
+
+Select user types (comma-separated): _
+
+What are the key capabilities needed?
+[ ] User registration
+[ ] Login/logout
+[ ] Password management
+[ ] Multi-factor authentication
+[ ] Social login (OAuth)
+[ ] Role-based access control
+[ ] Session management
+[ ] API authentication
+[ ] Audit logging
+[ ] Account lockout/security
+
+Select capabilities (comma-separated): _
+```
+
+### 3. Generate User Stories
+
+Based on selections, create stories:
+
+#### Story Templates
+
+**Registration Flow:**
+```yaml
+Title: "As a new user, I want to register an account"
+Description: Complete registration flow with email verification
+Acceptance Criteria:
+  - User can enter email and password
+  - Email verification sent
+  - Account activated after verification
+  - Welcome email sent
+Story Points: 5
+Priority: 1
+```
+
+**Login Flow:**
+```yaml
+Title: "As a registered user, I want to log in securely"
+Description: Secure login with remember me option
+Acceptance Criteria:
+  - Email/password authentication
+  - Remember me checkbox
+  - Failed attempt tracking
+  - Account lockout after N attempts
+Story Points: 8
+Priority: 1
+```
+
+**Password Reset:**
+```yaml
+Title: "As a user, I want to reset my forgotten password"
+Description: Self-service password reset via email
+Acceptance Criteria:
+  - Reset link via email
+  - Secure token validation
+  - Password complexity requirements
+  - Confirmation of reset
+Story Points: 5
+Priority: 2
+```
+
+### 4. Story Mapping
+
+Create visual story map:
+
+```
+📊 Authentication System - Story Map
+
+User Journey →
+┌─────────────┬──────────────┬──────────────┬──────────────┐
+│ Discovery   │ Registration │ Usage        │ Management   │
+├─────────────┼──────────────┼──────────────┼──────────────┤
+│             │ ▢ Register   │ ▢ Login      │ ▢ Profile    │ MVP
+│             │   account    │              │   update     │
+│             │              │ ▢ Logout     │              │
+│             │ ▢ Verify     │              │ ▢ Password   │
+│             │   email      │              │   change     │
+├─────────────┼──────────────┼──────────────┼──────────────┤
+│             │ ▢ Social     │ ▢ Remember   │ ▢ MFA setup  │ Release 2
+│             │   signup     │   me         │              │
+│             │              │              │ ▢ Security   │
+│             │              │ ▢ SSO login  │   settings   │
+├─────────────┼──────────────┼──────────────┼──────────────┤
+│ ▢ Landing   │ ▢ Bulk       │ ▢ API auth   │ ▢ Audit      │ Release 3
+│   page      │   import     │              │   logs       │
+│             │              │ ▢ Session    │              │
+│             │              │   management │ ▢ Compliance │
+└─────────────┴──────────────┴──────────────┴──────────────┘
+
+Total Stories: 15
+MVP Stories: 6 (26 points)
+Total Points: 89
+```
+
+### 5. Dependency Mapping
+
+Identify dependencies between stories:
+
+```
+🔗 Story Dependencies
+
+┌─────────────────┐
+│ Database Schema │
+└────────┬────────┘
+         ↓
+┌─────────────────┐     ┌──────────────┐
+│ User Registration├────→│ Email Service│
+└────────┬────────┘     └──────────────┘
+         ↓
+┌─────────────────┐
+│   User Login    │
+└────────┬────────┘
+         ├──────────────┐
+         ↓              ↓
+┌──────────────┐  ┌──────────────┐
+│Password Reset│  │ User Profile │
+└──────────────┘  └──────┬───────┘
+                         ↓
+                  ┌──────────────┐
+                  │  MFA Setup   │
+                  └──────────────┘
+```
+
+### 6. Create in Azure DevOps
+
+Use azure-devops-specialist agent to create:
+
+1. **Create Feature/Epic:**
+```json
+{
+  "op": "add",
+  "path": "/fields/System.Title",
+  "value": "Authentication System"
+}
+```
+
+2. **Create User Stories with hierarchy:**
+```json
+{
+  "op": "add",
+  "path": "/relations/-",
+  "value": {
+    "rel": "System.LinkTypes.Hierarchy-Reverse",
+    "url": "feature_url"
+  }
+}
+```
+
+3. **Set dependencies between stories**
+
+4. **Assign to iterations based on priority**
+
+### 7. Output Summary
+
+```
+✅ Feature Decomposition Complete!
+
+📦 Feature: Authentication System (#25)
+URL: https://dev.azure.com/{org}/{project}/_workitems/edit/25
+
+📋 Created User Stories:
+
+Release 1 (MVP) - Sprint 1-2:
+  #41 User Registration (5 pts) - Priority 1
+  #42 Email Verification (3 pts) - Priority 1
+  #43 User Login (8 pts) - Priority 1
+  #44 Logout (2 pts) - Priority 2
+  #45 Password Reset (5 pts) - Priority 2
+  #46 Profile Management (3 pts) - Priority 3
+
+Release 2 - Sprint 3-4:
+  #47 Social Login (8 pts) - Priority 2
+  #48 Remember Me (2 pts) - Priority 3
+  #49 MFA Setup (13 pts) - Priority 2
+  #50 SSO Integration (13 pts) - Priority 3
+
+Release 3 - Sprint 5-6:
+  #51 API Authentication (8 pts) - Priority 3
+  #52 Session Management (5 pts) - Priority 3
+  #53 Audit Logging (5 pts) - Priority 3
+  #54 Compliance Reports (8 pts) - Priority 4
+
+📊 Summary:
+- Total User Stories: 14
+- Total Story Points: 89
+- Estimated Sprints: 6
+- Team Capacity Needed: 2-3 developers
+
+📈 Breakdown by Priority:
+- Priority 1: 3 stories (16 pts)
+- Priority 2: 4 stories (23 pts)
+- Priority 3: 6 stories (34 pts)
+- Priority 4: 1 story (8 pts)
+
+🎯 Next Steps:
+1. Review and prioritize stories with Product Owner
+2. Assign stories to Sprint 1
+3. Parse first story into tasks: /azure:us-parse 41
+4. Create technical design documents
+5. Set up development environment
+
+📁 Documentation saved:
+.claude/azure/features/authentication-system.md
+
+Would you like to:
+1. Start parsing the first User Story
+2. Adjust priorities
+3. View detailed story map
+4. Export to different format
+
+Select (1-4): _
+```
+
+### 8. Templates Library
+
+Offer pre-built feature templates:
+
+```
+📚 Feature Templates Available:
+
+1. Authentication System (14 stories, 89 pts)
+2. E-commerce Checkout (12 stories, 76 pts)
+3. Search & Filtering (8 stories, 55 pts)
+4. Notification System (10 stories, 68 pts)
+5. Admin Dashboard (15 stories, 102 pts)
+6. Payment Integration (11 stories, 84 pts)
+7. User Onboarding (7 stories, 42 pts)
+8. API Gateway (9 stories, 71 pts)
+
+Select template (1-8) or 'custom' for interactive: _
+```
+
+### 9. Estimation Assistance
+
+Help with story point estimation:
+
+```
+📏 Story Point Estimation Helper
+
+Analyzing: "User Login" story
+
+Complexity Factors:
+- UI Work: Medium (login form, validation)
+- Backend: Medium (auth service, JWT)
+- Database: Low (user lookup)
+- Integration: Medium (session management)
+- Testing: Medium (security tests needed)
+
+Similar Stories from History:
+- "User Profile Update" - 5 points (simpler)
+- "Password Reset" - 5 points (similar)
+- "OAuth Integration" - 13 points (more complex)
+
+Suggested Points: 8
+Confidence: High (based on 15 similar stories)
+
+Accept suggestion? (y/n/adjust): _
+```
+
+## Smart Features
+
+### AI-Powered Suggestions
+- Analyze feature description
+- Suggest missing user stories
+- Identify common patterns
+
+### Risk Assessment
+- Highlight complex stories
+- Flag dependencies
+- Suggest mitigation strategies
+
+### Capacity Planning
+- Calculate team bandwidth
+- Suggest sprint allocation
+- Identify resource gaps
+
+## Error Handling
+
+- **Feature not found**: Offer to create new
+- **Insufficient details**: Guide through discovery
+- **Capacity exceeded**: Suggest phasing options
+
+## Local Tracking
+
+Save decomposition to `.claude/azure/features/{name}.md`:
+
+```markdown
+# Feature: Authentication System
+
+Created: 2024-01-10
+Feature ID: #25
+Total Points: 89
+
+## User Stories
+
+### MVP (26 points)
+1. [#41] User Registration (5 pts)
+2. [#42] Email Verification (3 pts)
+...
+
+## Dependencies
+- Email service required by Day 1
+- Database schema must be complete
+...
+
+## Risks
+- OAuth provider integration complexity
+- MFA vendor selection pending
+...
+```

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

@@ -0,0 +1,61 @@
+---
+allowed-tools: Task, Bash, Read, Write, WebFetch, Glob, Grep
+---
+
+# Azure DevOps Feature List
+
+List all Features/Epics with filtering and sorting options.
+
+**Usage**: `/azure:feature-list [--status=<state>] [--quarter=<Q>]`
+
+**Examples**:
+- `/azure:feature-list` - All features
+- `/azure:feature-list --status=Active` - Active features
+- `/azure:feature-list --quarter=Q1` - Q1 features
+
+## 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 Format
+
+```
+📦 Features/Epics Overview
+═══════════════════════════════════════════════════════════════
+
+| ID | Feature | Status | Progress | Points | Value | Target | Owner |
+|----|---------|--------|----------|--------|-------|--------|-------|
+| 25 | Authentication | 🔄 Active | 82% | 89 | 85 | Q1 | Product |
+| 26 | Payment Gateway | 📅 Planned | 0% | 55 | 92 | Q2 | - |
+| 27 | Search System | 🆕 New | 10% | 34 | 70 | Q1 | Tech |
+| 28 | Analytics | ✅ Done | 100% | 21 | 60 | Q1 | Data |
+
+📊 Summary:
+- Active: 1 (89 points)
+- Planned: 1 (55 points)
+- New: 1 (34 points)
+- Done: 1 (21 points)
+
+Total Value: 307
+Q1 Capacity: 144/150 points (96%)
+
+🎯 Recommendations:
+- Feature #25 needs attention (behind schedule)
+- Feature #26 ready to start
+- Consider deferring Feature #27 to Q2
+```

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

@@ -0,0 +1,115 @@
+---
+allowed-tools: Task, Bash, Read, Write, Edit, WebFetch, Glob, Grep
+---
+
+# Azure DevOps Feature New
+
+Create a new Feature/Epic in Azure DevOps with comprehensive planning.
+
+**Usage**: `/azure:feature-new <feature-name>`
+
+**Examples**:
+- `/azure:feature-new authentication-system`
+- `/azure:feature-new payment-integration`
+
+## 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. Interactive Feature Creation
+
+```
+🎯 Creating new Feature: authentication-system
+
+Feature Planning:
+─────────────────────────────────────────────────
+Title: Authentication System
+Description: [Complete user authentication and authorization system]
+Business Value: [85/100]
+Time Criticality: [High/Medium/Low]
+Effort (Story Points): [89]
+Target Date: [End of Q1]
+Risk: [Medium]
+
+Key Capabilities:
+□ User registration
+□ Login/logout
+□ Password management
+□ Multi-factor auth
+□ Role-based access
+□ Session management
+
+Dependencies:
+- Database schema
+- Email service
+- Security audit
+
+Confirm creation? (y/n): _
+```
+
+### 2. Create Feature
+
+Use azure-devops-specialist agent:
+
+```json
+{
+  "op": "add",
+  "path": "/fields/System.Title",
+  "value": "Authentication System"
+},
+{
+  "op": "add",
+  "path": "/fields/Microsoft.VSTS.Common.BusinessValue",
+  "value": 85
+},
+{
+  "op": "add",
+  "path": "/fields/Microsoft.VSTS.Scheduling.Effort",
+  "value": 89
+}
+```
+
+### 3. Success Output
+
+```
+✅ Feature #25 created successfully!
+
+Authentication System
+Business Value: 85
+Effort: 89 points
+Risk: Medium
+
+Next steps:
+1. Decompose into stories: /azure:feature-decompose 25
+2. Assign to team
+3. Schedule planning session
+
+View: https://dev.azure.com/{org}/{project}/_workitems/edit/25
+```
+
+### 4. Auto-Decomposition Option
+
+```
+Would you like to:
+[1] Decompose into User Stories now
+[2] Schedule planning session
+[3] Add team members
+[4] Exit
+
+Select: _
+```