claude-autopm 2.8.2 → 2.8.3

package/packages/plugin-pm/commands/azure/task-start.md

@@ -0,0 +1,301 @@
+---
+allowed-tools: Task, Bash, Read, Write, Edit, WebFetch, Glob, Grep
+---
+
+# Azure DevOps Task Start
+
+Start working on a Task - update status, create branch, and set up work environment.
+
+**Usage**: `/azure:task-start <task-id> [--branch-name=<name>]`
+
+**Examples**:
+- `/azure:task-start 101` - Start task and auto-create branch
+- `/azure:task-start 101 --branch-name=fix-login-bug` - Start with custom branch name
+
+## 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
+
+**CRITICAL**: This command MUST use the azure-devops-specialist agent for all Azure DevOps operations.
+
+### Command Execution Pattern
+
+```bash
+# Use the Task tool to invoke the azure-devops-specialist agent
+Task(subagent_type="azure-devops-specialist", 
+     description="Start Azure DevOps Task",
+     prompt="Start working on Azure DevOps Task ID: **$ARGUMENTS**
+     
+Follow the complete workflow:
+1. Preflight checks and task validation
+2. Task activation and status updates
+3. Development environment setup
+4. Context preparation and documentation
+5. Progress tracking and confirmation")
+```
+
+### Agent Instructions
+
+#### 1. Preflight Checks
+
+1. **Validate Task ID:**
+   - Verify task exists in Azure DevOps
+   - Check current status (should be "New" or "To Do")
+   - If already "Active", ask: "Task already in progress. Continue anyway?"
+
+2. **Get Task Details:**
+   - Fetch task title, description, parent User Story
+   - Display current assignee and remaining hours
+   - Show related tasks if any
+
+#### 2. Task Activation Process
+
+Execute the following Azure DevOps operations:
+
+#### Update Task Status
+
+```json
+[
+  {
+    "op": "replace",
+    "path": "/fields/System.State",
+    "value": "Active"
+  },
+  {
+    "op": "add",
+    "path": "/fields/System.AssignedTo",
+    "value": "{current_user_email}"
+  },
+  {
+    "op": "add",
+    "path": "/fields/Microsoft.VSTS.Common.ActivatedDate",
+    "value": "{current_datetime}"
+  }
+]
+```
+
+#### Record Work Started
+
+Add a comment to track start:
+```json
+{
+  "text": "Work started on this task at {timestamp}\nBranch: {branch_name}\nEstimated hours: {remaining_hours}"
+}
+```
+
+### 3. Development Environment Setup
+
+#### Create Git Branch
+
+```bash
+# Generate branch name if not provided
+if [ -z "$BRANCH_NAME" ]; then
+  BRANCH_NAME="task-{task_id}-{sanitized_title}"
+fi
+
+# Create and checkout branch
+git checkout -b $BRANCH_NAME
+
+# Push branch with upstream tracking
+git push -u origin $BRANCH_NAME
+```
+
+#### Create Work Directory Structure
+
+```bash
+# Create task work directory
+mkdir -p .claude/azure/tasks/{task_id}
+
+# Create task tracking file
+cat > .claude/azure/tasks/{task_id}/work.md << EOF
+# Task #{task_id}: {title}
+
+## Status
+- Started: {timestamp}
+- Branch: {branch_name}
+- Assignee: {user}
+
+## Parent User Story
+- ID: {story_id}
+- Title: {story_title}
+
+## Work Log
+- {timestamp}: Task started
+
+## Notes
+[Add implementation notes here]
+
+## Test Coverage
+[ ] Unit tests
+[ ] Integration tests
+[ ] Manual testing
+
+## Checklist
+[ ] Implementation complete
+[ ] Tests passing
+[ ] Code reviewed
+[ ] Documentation updated
+EOF
+```
+
+### 4. Context Preparation
+
+#### Fetch Related Information
+
+1. **Parent User Story details:**
+   - Acceptance criteria
+   - Technical notes
+   - Dependencies
+
+2. **Related code files:**
+   - Previous commits for similar tasks
+   - Existing implementation patterns
+   - Test files to update
+
+3. **Documentation:**
+   - API specs if applicable
+   - Architecture diagrams
+   - Coding standards
+
+### 5. Task Board Update
+
+Show current sprint task board:
+
+```
+🏃 Sprint 1 - Your Active Tasks
+
+Currently Working On:
+┌─────────────────────────────────────────┐
+│ Task #101: Technical Design (4h)        │
+│ Parent: US#34 - Password Reset          │
+│ Branch: task-101-technical-design       │
+│ Started: 10 minutes ago                 │
+└─────────────────────────────────────────┘
+
+Up Next:
+- Task #102: Implementation (12h)
+- Task #103: Unit tests (4h)
+
+📊 Your Sprint Progress:
+Tasks: 1/5 active, 0/5 completed
+Hours: 4h in progress, 28h remaining
+```
+
+### 6. Success Output
+
+```
+✅ Task #$ARGUMENTS started successfully!
+
+📋 Task Details:
+- Title: {task_title}
+- Remaining Hours: {hours}h
+- Parent Story: #{story_id} - {story_title}
+
+🔧 Development Setup:
+- Branch created: {branch_name}
+- Status: Active
+- Assigned to: You
+
+📁 Work tracking:
+.claude/azure/tasks/{task_id}/work.md
+
+🔗 Azure DevOps:
+https://dev.azure.com/{org}/{project}/_workitems/edit/{task_id}
+
+💡 Next steps:
+1. Review acceptance criteria from parent story
+2. Update technical design if needed
+3. Begin implementation
+4. Track progress: /azure:task-update {task_id} --hours-remaining=3
+5. When complete: /azure:task-close {task_id}
+
+🚀 Ready to code! Good luck with {task_title}!
+```
+
+### 7. Integration Features
+
+#### Link to IDE
+
+If VS Code integration available:
+```bash
+# Open relevant files in VS Code
+code .claude/azure/tasks/{task_id}/work.md
+code {related_files}
+```
+
+#### Set up Testing
+
+```bash
+# Create test file structure if needed
+touch tests/test_task_{task_id}.py
+echo "# Tests for Task #{task_id}" > tests/test_task_{task_id}.py
+```
+
+#### Time Tracking
+
+Start a time tracking session:
+```bash
+# Create time tracking entry
+echo "{timestamp_start}|IN_PROGRESS|{task_id}" >> .claude/azure/time-tracking.log
+```
+
+### 8. Smart Features
+
+#### Auto-assign if Unassigned
+- Automatically assign to current user
+- Update Azure DevOps assignment
+
+#### Parent Story Status Check
+- If parent story not "Active", offer to activate it
+- Check for blocking dependencies
+
+#### Related Tasks Detection
+- Find tasks that might block this one
+- Suggest parallel tasks that could be started
+
+## Error Handling
+
+- **Task not found**: Show similar task IDs
+- **Already active**: Show who's working on it
+- **No permission**: Guide to request access
+- **Git conflicts**: Help resolve branch issues
+
+## Hooks
+
+Support for custom hooks:
+- `pre-task-start`: Run before starting task
+- `post-task-start`: Run after task started
+
+Example: `.claude/hooks/pre-task-start.sh`
+```bash
+#!/bin/bash
+# Ensure latest code
+git pull origin main
+# Run linters
+npm run lint
+```

package/packages/plugin-pm/commands/azure/task-status.md

@@ -0,0 +1,65 @@
+---
+allowed-tools: Task, Bash, Read, Write, WebFetch, Glob, Grep
+---
+
+# Azure DevOps Task Status
+
+Show status overview of tasks for a story or sprint.
+
+**Usage**: `/azure:task-status [story-id] [--sprint=<name>]`
+
+**Examples**:
+- `/azure:task-status 34` - Tasks for Story #34
+- `/azure:task-status --sprint="Sprint 2"` - All sprint tasks
+- `/azure:task-status --my-tasks` - Your task status
+
+## 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
+
+```
+📊 Task Status Overview - Story #34
+═══════════════════════════════════════════════════════════════
+
+Progress: ████████████░░░░░░░░ 60% (3/5 tasks)
+Hours: ███████████░░░░░░░░░ 55% (15h/27h)
+
+Task Breakdown:
+✅ Completed: 3 tasks (15h)
+🔄 In Progress: 1 task (4h remaining)
+🆕 Not Started: 1 task (8h)
+🚫 Blocked: 0 tasks
+
+| Status | Task | Hours | Assigned | Health |
+|--------|------|-------|----------|--------|
+| ✅ | #101 Technical Design | 4h/4h | John | ✓ |
+| ✅ | #102 Implementation | 12h/12h | John | ✓ |
+| ✅ | #103 Unit tests | 4h/4h | Sarah | ✓ |
+| 🔄 | #104 Integration tests | 2h/6h | Sarah | ⚠️ |
+| 🆕 | #105 Documentation | 0h/3h | - | - |
+
+⚠️ Attention Needed:
+- Task #104 behind schedule
+- Task #105 not assigned
+
+Est. Completion: 2 days
+Sprint Ends: 2 days
+Risk: Medium
+```

package/packages/plugin-pm/commands/azure/task-sync.md

@@ -0,0 +1,67 @@
+---
+allowed-tools: Task, Bash, Read, Write, Edit, WebFetch, Glob, Grep
+---
+
+# Azure DevOps Task Sync
+
+Synchronize tasks between local cache and Azure DevOps.
+
+**Usage**: `/azure:task-sync [story-id] [--direction=both]`
+
+**Examples**:
+- `/azure:task-sync` - Sync all tasks
+- `/azure:task-sync 34` - Sync tasks for Story #34
+- `/azure:task-sync --direction=pull` - Only pull from Azure
+
+## 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
+
+### Sync Process
+
+```
+🔄 Task Synchronization
+═══════════════════════════════════════════════════════════════
+
+Analyzing differences...
+
+Local → Azure (Push):
+- Task #102: Hours updated (8h → 6h)
+- Task #103: Status changed (Active → Done)
+
+Azure → Local (Pull):
+- Task #104: New assignee (john → sarah)
+- Task #105: New task created
+- Task #106: Deleted in Azure
+
+Conflicts (1):
+- Task #102: Hours differ (Local: 6h, Azure: 7h)
+  [1] Keep local (6h)
+  [2] Keep Azure (7h)
+  [3] Skip this task
+  
+Choose: _
+
+Syncing...
+✓ Pushed 2 changes to Azure
+✓ Pulled 3 changes from Azure
+✓ Resolved 1 conflict
+
+Cache updated: .claude/azure/cache/
+Last sync: 2025-01-10T16:00:00Z
+```

package/packages/plugin-pm/commands/azure/us-edit.md

@@ -0,0 +1,164 @@
+---
+allowed-tools: Task, Bash, Read, Write, Edit, WebFetch, Glob, Grep
+---
+
+# Azure DevOps User Story Edit
+
+Edit User Story fields and properties in Azure DevOps.
+
+**Usage**: `/azure:us-edit <story-id> [--field=value]`
+
+**Examples**:
+- `/azure:us-edit 34 --title="Updated title"`
+- `/azure:us-edit 34 --points=13 --priority=1`
+- `/azure:us-edit 34 --status=Active --assigned-to=john@example.com`
+- `/azure:us-edit 34 --description="New description" --sprint="Sprint 2"`
+
+## 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. Parse Edit Arguments
+
+Extract field updates from arguments:
+- `--title`: Story title
+- `--description`: Full description
+- `--acceptance-criteria`: Acceptance criteria
+- `--points`: Story points
+- `--priority`: Priority (1-4)
+- `--status`: State (New, Active, Resolved, Closed)
+- `--assigned-to`: Assignee email
+- `--sprint`: Iteration path
+- `--area`: Area path
+- `--tags`: Comma-separated tags
+
+### 2. Interactive Edit Mode
+
+If no fields specified, enter interactive mode:
+
+```
+📝 Editing User Story #34: Implement user password reset
+
+Current values shown in [brackets]. Press Enter to keep current value.
+
+Title [Implement user password reset]: 
+Description [As a user, I want...]: 
+Story Points [8]: 13
+Priority [2]: 1
+Status [New]: Active
+Assigned To [Unassigned]: john@example.com
+Sprint [Backlog]: Sprint 2
+Area [Speacher]: Speacher\Security
+Tags []: security, high-priority
+
+Confirm changes? (y/n): _
+```
+
+### 3. Update via Azure DevOps API
+
+Use azure-devops-specialist agent to update:
+
+```json
+[
+  {
+    "op": "replace",
+    "path": "/fields/System.Title",
+    "value": "{new_title}"
+  },
+  {
+    "op": "replace",
+    "path": "/fields/Microsoft.VSTS.Scheduling.StoryPoints",
+    "value": {story_points}
+  },
+  {
+    "op": "replace",
+    "path": "/fields/System.State",
+    "value": "{state}"
+  }
+]
+```
+
+### 4. Success Output
+
+```
+✅ User Story #34 updated successfully!
+
+📋 Changed fields:
+- Title: "Implement user password reset" → "Implement secure password reset"
+- Story Points: 8 → 13
+- Priority: 2 → 1
+- Status: New → Active
+- Assigned To: Unassigned → john@example.com
+- Sprint: Backlog → Sprint 2
+
+🔗 View in Azure DevOps:
+https://dev.azure.com/{org}/{project}/_workitems/edit/34
+
+📊 Impact:
+- Sprint capacity: 45/50 points (was 40/50)
+- Tasks affected: 6 child tasks
+- Dependencies: May affect Story #35
+
+Next steps:
+- Update child tasks: /azure:task-list 34
+- Notify team: /azure:notify-team 34
+- View status: /azure:us-status 34
+```
+
+## Bulk Edit Mode
+
+Edit multiple stories:
+
+```bash
+# Edit multiple stories
+/azure:us-edit 34,35,36 --sprint="Sprint 2"
+
+# Edit all stories in sprint
+/azure:us-edit --sprint="Sprint 1" --set-priority=2
+
+# Edit by query
+/azure:us-edit --query="status=New" --assigned-to=me
+```
+
+## Field Validation
+
+- Story points: 0, 1, 2, 3, 5, 8, 13, 20, 40, 100
+- Priority: 1 (Critical), 2 (High), 3 (Medium), 4 (Low)
+- Status transitions must be valid
+- Assignee must exist in project
+
+## History Tracking
+
+Add comment with changes:
+```
+Changes made via AutoPM Azure integration:
+- Updated story points: 8 → 13
+- Changed priority: 2 → 1
+- Reassigned to john@example.com
+Reason: Sprint planning adjustment
+```