claude-autopm 2.7.0 → 2.8.2

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

@@ -1,263 +0,0 @@
----
-allowed-tools: Task, Bash, Read, Write, WebFetch, Glob, Grep
----
-
-# Azure DevOps Task List
-
-List Tasks from User Story or across the project.
-
-**Usage**: `/azure:task-list [user-story-id] [--status=<state>] [--assigned-to=<user>]`
-
-**Examples**:
-- `/azure:task-list` - List all tasks in current sprint
-- `/azure:task-list 34` - List tasks for User Story #34
-- `/azure:task-list --assigned-to=me` - List my tasks
-- `/azure:task-list --status=Active` - List active tasks
-
-## 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 Detection
-
-Determine query based on arguments:
-- **No args**: Show current sprint tasks
-- **Number arg**: Show tasks for that User Story
-- **Filters only**: Show filtered tasks across project
-
-### 2. Execute Query
-
-Use azure-devops-specialist agent with WIQL:
-
-#### For User Story Tasks
-
-```sql
-SELECT [System.Id], [System.Title], [System.State], 
-       [System.AssignedTo], [Microsoft.VSTS.Scheduling.RemainingWork]
-FROM workitemLinks
-WHERE Source.[System.Id] = {story_id}
-  AND [System.Links.LinkType] = 'System.LinkTypes.Hierarchy-Forward'
-  AND Target.[System.WorkItemType] = 'Task'
-ORDER BY Target.[System.Id]
-```
-
-#### For My Tasks
-
-```sql
-SELECT [System.Id], [System.Title], [System.State],
-       [Microsoft.VSTS.Scheduling.RemainingWork], [System.Parent]
-FROM workitems
-WHERE [System.WorkItemType] = 'Task'
-  AND [System.AssignedTo] = @Me
-  AND [System.State] <> 'Closed'
-ORDER BY [System.State], [System.Id]
-```
-
-### 3. Display Formats
-
-#### User Story Task View
-
-```
-📋 Tasks for User Story #34: Implement user password reset
-
-Progress: ████████░░░░░░░░ 45% (12h/27h completed)
-
-| ID  | Task                        | Status | Assigned  | Hours | Branch           |
-|-----|----------------------------|--------|-----------|-------|------------------|
-| 101 | Technical Design           | ✅     | John      | 0/4h  | merged           |
-| 102 | Implementation             | 🔄     | John      | 8/12h | task-102-impl    |
-| 103 | Unit tests                 | 🆕     | -         | 4h    | -                |
-| 104 | Integration tests          | 🆕     | -         | 6h    | -                |
-| 105 | Documentation              | 🆕     | -         | 3h    | -                |
-| 106 | Code review                | 🆕     | -         | 2h    | -                |
-
-📊 Summary:
-- Total: 6 tasks (27h estimated)
-- Completed: 1 (4h)
-- In Progress: 1 (12h remaining)
-- Not Started: 4 (11h)
-
-🚀 Ready to start:
-- Task #103: Unit tests (4h) - No dependencies
-- Task #104: Integration tests (6h) - Blocked by #102
-
-Commands:
-- Start task: /azure:task-start <id>
-- Update task: /azure:task-edit <id>
-- View details: /azure:task-show <id>
-```
-
-#### My Tasks View
-
-```
-👤 My Active Tasks
-
-🔄 In Progress:
-| ID  | Task                  | Story              | Hours | Started    | Branch        |
-|-----|--------------------- |-------------------|-------|------------|---------------|
-| 102 | Implementation       | #34 Password Reset | 8/12h | 2 hours ago| task-102-impl |
-| 215 | Fix validation bug   | #41 Form Updates   | 1/2h  | Yesterday  | bug-215-fix   |
-
-📋 Assigned to Me:
-| ID  | Task                  | Story              | Hours | Priority | Due     |
-|-----|--------------------- |-------------------|-------|----------|---------|
-| 103 | Unit tests           | #34 Password Reset | 4h    | High     | Today   |
-| 220 | Update API docs      | #42 API v2         | 2h    | Medium   | Tomorrow|
-| 225 | Review PR #456       | #43 Refactoring    | 1h    | Low      | This week|
-
-⏱️ Time Tracking:
-- Today: 3h logged
-- This week: 18h logged
-- Sprint capacity: 22h/40h used
-
-💡 Recommendations:
-- Complete Task #215 (only 1h remaining)
-- Start Task #103 after finishing #102
-- You have 18h capacity remaining this sprint
-```
-
-#### Sprint Board View
-
-```
-🏃 Sprint 1 Task Board
-
-To Do (8)          | In Progress (3)      | In Review (2)    | Done (5)
--------------------|---------------------|------------------|------------------
-#103 Unit tests    | #102 Implementation | #99 API changes  | #95 Setup
-#104 Integration   | #215 Bug fix        | #101 Design doc  | #96 Config
-#105 Documentation | #218 UI updates     |                  | #97 Database
-#106 Code review   |                     |                  | #98 Auth flow
-...                |                     |                  | #100 Logging
-
-📊 Sprint Metrics:
-- Velocity: 18h completed / 65h total
-- Burn rate: 3.6h/day
-- Days remaining: 5
-- On track: ⚠️ Slightly behind
-
-🎯 Focus Areas:
-- 2 tasks in review need attention
-- 3 tasks blocked by dependencies
-- Consider pulling task from backlog
-```
-
-### 4. Filtering & Sorting
-
-Support multiple filters:
-
-```bash
-# Complex query examples
-/azure:task-list --status=Active --assigned-to=me --sort=priority
-/azure:task-list --sprint="Sprint 1" --hours=">4"
-/azure:task-list --parent-story=34,35,36 --status=New
-/azure:task-list --blocked=true
-/azure:task-list --due=today
-```
-
-### 5. Task Dependencies
-
-Show task relationships:
-
-```
-🔗 Task Dependencies for Story #34
-
-┌─────────────┐
-│ #101 Design │ ✅
-└─────┬───────┘
-      ↓
-┌─────────────────┐
-│ #102 Implement  │ 🔄
-└─────┬───────────┘
-      ├──────────┐
-      ↓          ↓
-┌──────────┐ ┌──────────────┐
-│ #103 Unit│ │ #104 Integ.  │
-└──────────┘ └──────────────┘
-      ↓          ↓
-      └────┬─────┘
-           ↓
-    ┌──────────┐
-    │ #105 Docs│
-    └──────────┘
-           ↓
-    ┌──────────────┐
-    │ #106 Review  │
-    └──────────────┘
-```
-
-### 6. Quick Actions
-
-Provide quick action commands:
-
-```
-⚡ Quick Actions:
-1. Start next available task
-2. Update all my task hours
-3. Close completed tasks
-4. Generate status report
-5. Export to CSV
-
-Select action (1-5): _
-```
-
-### 7. Export Options
-
-```bash
-# Export task list
-/azure:task-list 34 --export=csv > tasks.csv
-/azure:task-list --assigned-to=me --export=json > my-tasks.json
-```
-
-## Smart Features
-
-### Auto-recommendations
-- Suggest next task based on dependencies
-- Warn about overdue tasks
-- Highlight blockers
-
-### Time Estimates
-- Show if on track for sprint
-- Calculate completion date
-- Suggest task redistribution
-
-### Integration Status
-- Show linked PRs
-- Display test results
-- Link to builds
-
-## Error Handling
-
-- **No tasks found**: Suggest checking filters
-- **Story not found**: List available stories
-- **Connection error**: Check credentials
-
-## Local Cache
-
-- Cache results for 5 minutes
-- Sync with local task files
-- Offline mode support

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

@@ -1,84 +0,0 @@
----
-allowed-tools: Task, Bash, Read, Write, Edit, WebFetch, Glob, Grep
----
-
-# Azure DevOps Task New
-
-Create a new Task under a User Story.
-
-**Usage**: `/azure:task-new <story-id> <task-title>`
-
-**Examples**:
-- `/azure:task-new 34 "Add input validation"`
-- `/azure:task-new 34 "Write unit tests" --hours=4`
-- `/azure:task-new 34 "Fix bug" --assigned-to=john@example.com`
-
-## 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 Task Creation
-
-```
-📝 Creating new Task for Story #34
-
-Task Title: Add input validation
-
-Task Details:
-Description: [Validate email format and password strength]
-Activity Type: [Development]
-Original Estimate: [4] hours
-Assigned To: [john@example.com]
-Priority: [2]
-
-Confirm creation? (y/n): _
-```
-
-### 2. Create Task
-
-Use azure-devops-specialist agent to create task with parent link:
-
-```json
-{
-  "op": "add",
-  "path": "/fields/System.Title",
-  "value": "Add input validation"
-},
-{
-  "op": "add",
-  "path": "/relations/-",
-  "value": {
-    "rel": "System.LinkTypes.Hierarchy-Reverse",
-    "url": "story_url"
-  }
-}
-```
-
-### 3. Success Output
-
-```
-✅ Task created successfully!
-
-Task #106: Add input validation
-Parent: Story #34 - Password Reset
-Hours: 4h
-Assigned: john@example.com
-Status: To Do
-
-Next: /azure:task-start 106
-```

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

@@ -1,79 +0,0 @@
----
-allowed-tools: Task, Bash, Read, Write, Edit, WebFetch, Glob, Grep
----
-
-# Azure DevOps Task Reopen
-
-Reopen a closed task that needs additional work.
-
-**Usage**: `/azure:task-reopen <task-id> [--reason=<text>]`
-
-**Examples**:
-- `/azure:task-reopen 102`
-- `/azure:task-reopen 102 --reason="Bug found in implementation"`
-
-## 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
-
-### Reopen Process
-
-```
-⚠️ Reopening Task #102
-
-Current Status: Closed
-Completed: 2 days ago
-By: john@example.com
-
-Reason for reopening: Bug found in implementation
-
-This will:
-- Change status to "To Do" or "In Progress"
-- Reset completion date
-- Add reopening note to history
-- Notify original assignee
-
-Confirm reopen? (y/n): _
-```
-
-### Update Task
-
-```json
-{
-  "op": "replace",
-  "path": "/fields/System.State",
-  "value": "To Do"
-},
-{
-  "op": "add",
-  "path": "/fields/System.History",
-  "value": "Reopened: Bug found in implementation"
-}
-```
-
-### Success Output
-
-```
-✅ Task #102 reopened
-
-Status: To Do → In Progress
-Assigned: john@example.com (notified)
-Reason: Bug found in implementation
-
-Next: /azure:task-start 102
-```

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

@@ -1,126 +0,0 @@
----
-allowed-tools: Task, Bash, Read, Write, WebFetch, Glob, Grep
----
-
-# Azure DevOps Task Show
-
-Display detailed information about a specific Task.
-
-**Usage**: `/azure:task-show <task-id> [--format=<type>]`
-
-**Examples**:
-- `/azure:task-show 102`
-- `/azure:task-show 102 --include-history`
-- `/azure:task-show 102 --format=json`
-
-## 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
-
-### Display Format
-
-```
-═══════════════════════════════════════════════════════════════
-⚙️ Task #102
-═══════════════════════════════════════════════════════════════
-
-Title: Implementation - Core password reset logic
-State: 🔄 In Progress
-URL: https://dev.azure.com/rafal0387/Speacher/_workitems/edit/102
-
-📝 Details
-─────────────────────────────────────────────────────────────
-Description:
-Implement the core password reset functionality including:
-- Token generation and validation
-- Email service integration
-- Password complexity validation
-- Database updates
-- Security logging
-
-Activity: Development
-Original Estimate: 12h
-Remaining Work: 8h
-Completed Work: 4h
-
-👤 Assignment
-─────────────────────────────────────────────────────────────
-Assigned To: john@example.com
-Created: 2025-01-08 09:00 AM
-Started: 2025-01-09 10:00 AM
-Last Updated: 2 hours ago
-
-📍 Context
-─────────────────────────────────────────────────────────────
-Parent Story: #34 - Implement user password reset
-Sprint: Sprint 2 (Day 8/10)
-Area: Speacher\Security
-Priority: High
-
-🔗 Dependencies
-─────────────────────────────────────────────────────────────
-Blocks:
-  → Task #103: Unit tests
-  → Task #104: Integration tests
-  
-Blocked by:
-  ← Task #101: Technical Design (✅ Complete)
-
-📊 Progress
-─────────────────────────────────────────────────────────────
-Progress: ████████░░░░░░░░ 33% (4h/12h)
-Velocity: 2h/day
-Est. Completion: 2 days
-
-Git Branch: task-102-implementation
-Commits: 8
-Files Changed: 12
-Lines: +456 -123
-
-💬 Recent Activity
-─────────────────────────────────────────────────────────────
-• 2h ago: John logged 2 hours of work
-• 4h ago: Status changed to In Progress
-• Yesterday: Branch created and pushed
-• 2 days ago: Task assigned to John
-
-📎 Attachments
-─────────────────────────────────────────────────────────────
-• technical-design.md (8 KB)
-• api-spec.yaml (4 KB)
-
-🔧 Quick Actions
-─────────────────────────────────────────────────────────────
-[1] Edit task (/azure:task-edit 102)
-[2] Log time
-[3] Add comment
-[4] View parent story (/azure:us-show 34)
-[5] Close task (/azure:task-close 102)
-
-Select (1-5): _
-```