claude-autopm 2.7.0 → 2.8.2

package/autopm/.claude/commands/pm/issue-analyze.md

@@ -1,202 +0,0 @@
----
-allowed-tools: Bash, Read, Write, LS
----
-
-# Issue Analyze
-
-Analyze an issue to identify parallel work streams for maximum efficiency.
-
-## Usage
-```
-/pm:issue-analyze <issue_number>
-```
-
-## Required Documentation Access
-
-**MANDATORY:** Before analyzing issues, query Context7 for best practices:
-
-**Documentation Queries:**
-- `mcp://context7/agile/issue-analysis` - Issue analysis and breakdown patterns
-- `mcp://context7/agile/parallel-work` - Parallel work stream identification
-- `mcp://context7/project-management/task-dependencies` - Dependency analysis
-- `mcp://context7/agile/estimation` - Effort estimation techniques
-- `mcp://context7/collaboration/conflict-resolution` - File conflict detection
-
-**Why This is Required:**
-- Ensures accurate parallel work stream identification
-- Applies proven patterns for conflict risk assessment
-- Validates dependency analysis against best practices
-- Prevents inefficient parallelization strategies
-
-## Quick Check
-
-1. **Find local task file:**
-   - First check if `.claude/epics/*/$ARGUMENTS.md` exists (new naming convention)
-   - If not found, search for file containing `github:.*issues/$ARGUMENTS` in frontmatter (old naming)
-   - If not found: "❌ No local task for issue #$ARGUMENTS. Run: /pm:import first"
-
-2. **Check for existing analysis:**
-   ```bash
-   test -f .claude/epics/*/$ARGUMENTS-analysis.md && echo "⚠️ Analysis already exists. Overwrite? (yes/no)"
-   ```
-
-## Instructions
-
-### 1. Read Issue Context
-
-Get issue details from GitHub:
-```bash
-gh issue view $ARGUMENTS --json title,body,labels
-```
-
-Read local task file to understand:
-- Technical requirements
-- Acceptance criteria
-- Dependencies
-- Effort estimate
-
-### 2. Identify Parallel Work Streams
-
-Analyze the issue to identify independent work that can run in parallel:
-
-**Common Patterns:**
-- **Database Layer**: Schema, migrations, models
-- **Service Layer**: Business logic, data access
-- **API Layer**: Endpoints, validation, middleware
-- **UI Layer**: Components, pages, styles
-- **Test Layer**: Unit tests, integration tests
-- **Documentation**: API docs, README updates
-
-**Key Questions:**
-- What files will be created/modified?
-- Which changes can happen independently?
-- What are the dependencies between changes?
-- Where might conflicts occur?
-
-### 3. Create Analysis File
-
-Get current datetime: `date -u +"%Y-%m-%dT%H:%M:%SZ"`
-
-Create `.claude/epics/{epic_name}/$ARGUMENTS-analysis.md`:
-
-```markdown
----
-issue: $ARGUMENTS
-title: {issue_title}
-analyzed: {current_datetime}
-estimated_hours: {total_hours}
-parallelization_factor: {1.0-5.0}
----
-
-# Parallel Work Analysis: Issue #$ARGUMENTS
-
-## Overview
-{Brief description of what needs to be done}
-
-## Parallel Streams
-
-### Stream A: {Stream Name}
-**Scope**: {What this stream handles}
-**Files**:
-- {file_pattern_1}
-- {file_pattern_2}
-**Agent Type**: {backend|frontend|fullstack|database}-specialist
-**Can Start**: immediately
-**Estimated Hours**: {hours}
-**Dependencies**: none
-
-### Stream B: {Stream Name}
-**Scope**: {What this stream handles}
-**Files**:
-- {file_pattern_1}
-- {file_pattern_2}
-**Agent Type**: {agent_type}
-**Can Start**: immediately
-**Estimated Hours**: {hours}
-**Dependencies**: none
-
-### Stream C: {Stream Name}
-**Scope**: {What this stream handles}
-**Files**:
-- {file_pattern_1}
-**Agent Type**: {agent_type}
-**Can Start**: after Stream A completes
-**Estimated Hours**: {hours}
-**Dependencies**: Stream A
-
-## Coordination Points
-
-### Shared Files
-{List any files multiple streams need to modify}:
-- `src/types/index.ts` - Streams A & B (coordinate type updates)
-- `package.json` - Stream B (add dependencies)
-
-### Sequential Requirements
-{List what must happen in order}:
-1. Database schema before API endpoints
-2. API types before UI components
-3. Core logic before tests
-
-## Conflict Risk Assessment
-- **Low Risk**: Streams work on different directories
-- **Medium Risk**: Some shared type files, manageable with coordination
-- **High Risk**: Multiple streams modifying same core files
-
-## Parallelization Strategy
-
-**Recommended Approach**: {sequential|parallel|hybrid}
-
-{If parallel}: Launch Streams A, B simultaneously. Start C when A completes.
-{If sequential}: Complete Stream A, then B, then C.
-{If hybrid}: Start A & B together, C depends on A, D depends on B & C.
-
-## Expected Timeline
-
-With parallel execution:
-- Wall time: {max_stream_hours} hours
-- Total work: {sum_all_hours} hours
-- Efficiency gain: {percentage}%
-
-Without parallel execution:
-- Wall time: {sum_all_hours} hours
-
-## Notes
-{Any special considerations, warnings, or recommendations}
-```
-
-### 4. Validate Analysis
-
-Ensure:
-- All major work is covered by streams
-- File patterns don't unnecessarily overlap
-- Dependencies are logical
-- Agent types match the work type
-- Time estimates are reasonable
-
-### 5. Output
-
-```
-✅ Analysis complete for issue #$ARGUMENTS
-
-Identified {count} parallel work streams:
-  Stream A: {name} ({hours}h)
-  Stream B: {name} ({hours}h)
-  Stream C: {name} ({hours}h)
-  
-Parallelization potential: {factor}x speedup
-  Sequential time: {total}h
-  Parallel time: {reduced}h
-
-Files at risk of conflict:
-  {list shared files if any}
-
-Next: Start work with /pm:issue-start $ARGUMENTS
-```
-
-## Important Notes
-
-- Analysis is local only - not synced to GitHub
-- Focus on practical parallelization, not theoretical maximum
-- Consider agent expertise when assigning streams
-- Account for coordination overhead in estimates
-- Prefer clear separation over maximum parallelization

package/autopm/.claude/commands/pm/issue-close.md

@@ -1,119 +0,0 @@
----
-allowed-tools: Bash, Read, Write, LS
----
-
-# Issue Close
-
-Mark an issue as complete and close it on GitHub.
-
-## Usage
-```
-/pm:issue-close <issue_number> [completion_notes]
-```
-
-## Required Documentation Access
-
-**MANDATORY:** Before project management workflows, query Context7 for best practices:
-
-**Documentation Queries:**
-- `mcp://context7/agile/epic-management` - epic management best practices
-- `mcp://context7/project-management/issue-tracking` - issue tracking best practices
-- `mcp://context7/agile/task-breakdown` - task breakdown best practices
-- `mcp://context7/project-management/workflow` - workflow 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. Find Local Task File
-
-First check if `.claude/epics/*/$ARGUMENTS.md` exists (new naming).
-If not found, search for task file with `github:.*issues/$ARGUMENTS` in frontmatter (old naming).
-If not found: "❌ No local task for issue #$ARGUMENTS"
-
-### 2. Update Local Status
-
-Get current datetime: `date -u +"%Y-%m-%dT%H:%M:%SZ"`
-
-Update task file frontmatter:
-```yaml
-status: closed
-updated: {current_datetime}
-```
-
-### 3. Update Progress File
-
-If progress file exists at `.claude/epics/{epic}/updates/$ARGUMENTS/progress.md`:
-- Set completion: 100%
-- Add completion note with timestamp
-- Update last_sync with current datetime
-
-### 4. Close on GitHub
-
-Add completion comment and close:
-```bash
-# Add final comment
-echo "✅ Task completed
-
-$ARGUMENTS
-
----
-Closed at: {timestamp}" | gh issue comment $ARGUMENTS --body-file -
-
-# Close the issue
-gh issue close $ARGUMENTS
-```
-
-### 5. Update Epic Task List on GitHub
-
-Check the task checkbox in the epic issue:
-
-```bash
-# Get epic name from local task file path
-epic_name={extract_from_path}
-
-# Get epic issue number from epic.md
-epic_issue=$(grep 'github:' .claude/epics/$epic_name/epic.md | grep -oE '[0-9]+$')
-
-if [ ! -z "$epic_issue" ]; then
-  # Get current epic body
-  gh issue view $epic_issue --json body -q .body > /tmp/epic-body.md
-  
-  # Check off this task
-  sed -i "s/- \[ \] #$ARGUMENTS/- [x] #$ARGUMENTS/" /tmp/epic-body.md
-  
-  # Update epic issue
-  gh issue edit $epic_issue --body-file /tmp/epic-body.md
-  
-  echo "✓ Updated epic progress on GitHub"
-fi
-```
-
-### 6. Update Epic Progress
-
-- Count total tasks in epic
-- Count closed tasks
-- Calculate new progress percentage
-- Update epic.md frontmatter progress field
-
-### 7. Output
-
-```
-✅ Closed issue #$ARGUMENTS
-  Local: Task marked complete
-  GitHub: Issue closed & epic updated
-  Epic progress: {new_progress}% ({closed}/{total} tasks complete)
-  
-Next: Run /pm:next for next priority task
-```
-
-## Important Notes
-
-Follow `/rules/frontmatter-operations.md` for updates.
-Follow `/rules/github-operations.md` for GitHub commands.
-Always sync local state before GitHub.

package/autopm/.claude/commands/pm/issue-edit.md

@@ -1,93 +0,0 @@
----
-allowed-tools: Bash, Read, Write, LS
----
-
-# Issue Edit
-
-Edit issue details locally and on GitHub.
-
-## Usage
-```
-/pm:issue-edit <issue_number>
-```
-
-## Required Documentation Access
-
-**MANDATORY:** Before project management workflows, query Context7 for best practices:
-
-**Documentation Queries:**
-- `mcp://context7/agile/epic-management` - epic management best practices
-- `mcp://context7/project-management/issue-tracking` - issue tracking best practices
-- `mcp://context7/agile/task-breakdown` - task breakdown best practices
-- `mcp://context7/project-management/workflow` - workflow 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. Get Current Issue State
-
-```bash
-# Get from GitHub
-gh issue view $ARGUMENTS --json title,body,labels
-
-# Find local task file
-# Search for file with github:.*issues/$ARGUMENTS
-```
-
-### 2. Interactive Edit
-
-Ask user what to edit:
-- Title
-- Description/Body
-- Labels
-- Acceptance criteria (local only)
-- Priority/Size (local only)
-
-### 3. Update Local File
-
-Get current datetime: `date -u +"%Y-%m-%dT%H:%M:%SZ"`
-
-Update task file with changes:
-- Update frontmatter `name` if title changed
-- Update body content if description changed
-- Update `updated` field with current datetime
-
-### 4. Update GitHub
-
-If title changed:
-```bash
-gh issue edit $ARGUMENTS --title "{new_title}"
-```
-
-If body changed:
-```bash
-gh issue edit $ARGUMENTS --body-file {updated_task_file}
-```
-
-If labels changed:
-```bash
-gh issue edit $ARGUMENTS --add-label "{new_labels}"
-gh issue edit $ARGUMENTS --remove-label "{removed_labels}"
-```
-
-### 5. Output
-
-```
-✅ Updated issue #$ARGUMENTS
-  Changes:
-    {list_of_changes_made}
-  
-Synced to GitHub: ✅
-```
-
-## Important Notes
-
-Always update local first, then GitHub.
-Preserve frontmatter fields not being edited.
-Follow `/rules/frontmatter-operations.md`.

package/autopm/.claude/commands/pm/issue-reopen.md

@@ -1,87 +0,0 @@
----
-allowed-tools: Bash, Read, Write, LS
----
-
-# Issue Reopen
-
-Reopen a closed issue.
-
-## Usage
-```
-/pm:issue-reopen <issue_number> [reason]
-```
-
-## Required Documentation Access
-
-**MANDATORY:** Before project management workflows, query Context7 for best practices:
-
-**Documentation Queries:**
-- `mcp://context7/agile/epic-management` - epic management best practices
-- `mcp://context7/project-management/issue-tracking` - issue tracking best practices
-- `mcp://context7/agile/task-breakdown` - task breakdown best practices
-- `mcp://context7/project-management/workflow` - workflow 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. Find Local Task File
-
-Search for task file with `github:.*issues/$ARGUMENTS` in frontmatter.
-If not found: "❌ No local task for issue #$ARGUMENTS"
-
-### 2. Update Local Status
-
-Get current datetime: `date -u +"%Y-%m-%dT%H:%M:%SZ"`
-
-Update task file frontmatter:
-```yaml
-status: open
-updated: {current_datetime}
-```
-
-### 3. Reset Progress
-
-If progress file exists:
-- Keep original started date
-- Reset completion to previous value or 0%
-- Add note about reopening with reason
-
-### 4. Reopen on GitHub
-
-```bash
-# Reopen with comment
-echo "🔄 Reopening issue
-
-Reason: $ARGUMENTS
-
----
-Reopened at: {timestamp}" | gh issue comment $ARGUMENTS --body-file -
-
-# Reopen the issue
-gh issue reopen $ARGUMENTS
-```
-
-### 5. Update Epic Progress
-
-Recalculate epic progress with this task now open again.
-
-### 6. Output
-
-```
-🔄 Reopened issue #$ARGUMENTS
-  Reason: {reason_if_provided}
-  Epic progress: {updated_progress}%
-  
-Start work with: /pm:issue-start $ARGUMENTS
-```
-
-## Important Notes
-
-Preserve work history in progress files.
-Don't delete previous progress, just reset status.

package/autopm/.claude/commands/pm/issue-show.md

@@ -1,41 +0,0 @@
----
-allowed-tools: Bash, Read, LS
----
-
-# Issue Show
-
-Display issue and sub-issues with detailed information.
-
-## Usage
-```
-/pm:issue-show <issue_number>
-```
-
-## Required Documentation Access
-
-**MANDATORY:** Before project management workflows, query Context7 for best practices:
-
-**Documentation Queries:**
-- `mcp://context7/agile/epic-management` - epic management best practices
-- `mcp://context7/project-management/issue-tracking` - issue tracking best practices
-- `mcp://context7/agile/task-breakdown` - task breakdown best practices
-- `mcp://context7/project-management/workflow` - workflow 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
-
-Run `node .claude/scripts/pm/issue-show.js $ARGUMENTS` using the Bash tool and show me the complete output.
-
-This will display comprehensive information about the GitHub issue including:
-1. Issue details and status
-2. Local file mappings and task files
-3. Sub-issues and dependencies
-4. Recent activity and comments
-5. Progress tracking with acceptance criteria
-6. Quick action suggestions