claude-autopm 2.7.0 → 2.8.2

package/autopm/.claude/commands/pm/search.md

@@ -1,28 +0,0 @@
----
-allowed-tools: Bash
----
-
-Run `node .claude/scripts/pm/search.js $ARGUMENTS` using the Bash tool and show me the complete output.
-
-- DO NOT truncate.
-- DO NOT collapse.
-- DO NOT abbreviate.
-- Show ALL lines in full.
-## 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
-
-
-- DO NOT print any other comments.

package/autopm/.claude/commands/pm/standup.md

@@ -1,28 +0,0 @@
----
-allowed-tools: Bash
----
-
-Run `node .claude/scripts/pm/standup.js` using the Bash tool and show me the complete output.
-
-- DO NOT truncate.
-- DO NOT collapse.
-- DO NOT abbreviate.
-- Show ALL lines in full.
-## 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
-
-
-- DO NOT print any other comments.

package/autopm/.claude/commands/pm/status.md

@@ -1,28 +0,0 @@
----
-allowed-tools: Bash
----
-
-Run `node .claude/scripts/pm/status.js` using the Bash tool and show me the complete output.
-
-- DO NOT truncate.
-- DO NOT collapse.
-- DO NOT abbreviate.
-- Show ALL lines in full.
-## 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
-
-
-- DO NOT print any other comments.

package/autopm/.claude/commands/pm/sync.md

@@ -1,99 +0,0 @@
----
-allowed-tools: Bash, Read, Write, LS
----
-
-# Sync
-
-Full bidirectional sync between local and GitHub.
-
-## Usage
-```
-/pm:sync [epic_name]
-```
-
-If epic_name provided, sync only that epic. Otherwise sync all.
-
-## 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. Pull from GitHub
-
-Get current state of all issues:
-```bash
-# Get all epic and task issues
-gh issue list --label "epic" --limit 1000 --json number,title,state,body,labels,updatedAt
-gh issue list --label "task" --limit 1000 --json number,title,state,body,labels,updatedAt
-```
-
-### 2. Update Local from GitHub
-
-For each GitHub issue:
-- Find corresponding local file by issue number
-- Compare states:
-  - If GitHub state newer (updatedAt > local updated), update local
-  - If GitHub closed but local open, close local
-  - If GitHub reopened but local closed, reopen local
-- Update frontmatter to match GitHub state
-
-### 3. Push Local to GitHub
-
-For each local task/epic:
-- If has GitHub URL but GitHub issue not found, it was deleted - mark local as archived
-- If no GitHub URL, create new issue (like epic-sync)
-- If local updated > GitHub updatedAt, push changes:
-  ```bash
-  gh issue edit {number} --body-file {local_file}
-  ```
-
-### 4. Handle Conflicts
-
-If both changed (local and GitHub updated since last sync):
-- Show both versions
-- Ask user: "Local and GitHub both changed. Keep: (local/github/merge)?"
-- Apply user's choice
-
-### 5. Update Sync Timestamps
-
-Update all synced files with last_sync timestamp.
-
-### 6. Output
-
-```
-🔄 Sync Complete
-
-Pulled from GitHub:
-  Updated: {count} files
-  Closed: {count} issues
-  
-Pushed to GitHub:
-  Updated: {count} issues
-  Created: {count} new issues
-  
-Conflicts resolved: {count}
-
-Status:
-  ✅ All files synced
-  {or list any sync failures}
-```
-
-## Important Notes
-
-Follow `/rules/github-operations.md` for GitHub commands.
-Follow `/rules/frontmatter-operations.md` for local updates.
-Always backup before sync in case of issues.

package/autopm/.claude/commands/pm/test-reference-update.md

@@ -1,151 +0,0 @@
----
-allowed-tools: Bash, Read, Write
----
-
-# Test Reference Update
-
-Test the task reference update logic used in epic-sync.
-
-## Usage
-```
-/pm:test-reference-update
-```
-
-## 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. Create Test Files
-
-Create test task files with references:
-```bash
-mkdir -p /tmp/test-refs
-cd /tmp/test-refs
-
-# Create task 001
-cat > 001.md << 'EOF'
----
-name: Task One
-status: open
-depends_on: []
-parallel: true
-conflicts_with: [002, 003]
----
-# Task One
-This is task 001.
-EOF
-
-# Create task 002
-cat > 002.md << 'EOF'
----
-name: Task Two
-status: open
-depends_on: [001]
-parallel: false
-conflicts_with: [003]
----
-# Task Two
-This is task 002, depends on 001.
-EOF
-
-# Create task 003
-cat > 003.md << 'EOF'
----
-name: Task Three
-status: open
-depends_on: [001, 002]
-parallel: false
-conflicts_with: []
----
-# Task Three
-This is task 003, depends on 001 and 002.
-EOF
-```
-
-### 2. Create Mappings
-
-Simulate the issue creation mappings:
-```bash
-# Simulate task -> issue number mapping
-cat > /tmp/task-mapping.txt << 'EOF'
-001.md:42
-002.md:43
-003.md:44
-EOF
-
-# Create old -> new ID mapping
-> /tmp/id-mapping.txt
-while IFS=: read -r task_file task_number; do
-  old_num=$(basename "$task_file" .md)
-  echo "$old_num:$task_number" >> /tmp/id-mapping.txt
-done < /tmp/task-mapping.txt
-
-echo "ID Mapping:"
-cat /tmp/id-mapping.txt
-```
-
-### 3. Update References
-
-Process each file and update references:
-```bash
-while IFS=: read -r task_file task_number; do
-  echo "Processing: $task_file -> $task_number.md"
-  
-  # Read the file content
-  content=$(cat "$task_file")
-  
-  # Update references
-  while IFS=: read -r old_num new_num; do
-    content=$(echo "$content" | sed "s/\b$old_num\b/$new_num/g")
-  done < /tmp/id-mapping.txt
-  
-  # Write to new file
-  new_name="${task_number}.md"
-  echo "$content" > "$new_name"
-  
-  echo "Updated content preview:"
-  grep -E "depends_on:|conflicts_with:" "$new_name"
-  echo "---"
-done < /tmp/task-mapping.txt
-```
-
-### 4. Verify Results
-
-Check that references were updated correctly:
-```bash
-echo "=== Final Results ==="
-for file in 42.md 43.md 44.md; do
-  echo "File: $file"
-  grep -E "name:|depends_on:|conflicts_with:" "$file"
-  echo ""
-done
-```
-
-Expected output:
-- 42.md should have conflicts_with: [43, 44]
-- 43.md should have depends_on: [42] and conflicts_with: [44]
-- 44.md should have depends_on: [42, 43]
-
-### 5. Cleanup
-
-```bash
-cd -
-rm -rf /tmp/test-refs
-rm -f /tmp/task-mapping.txt /tmp/id-mapping.txt
-echo "✅ Test complete and cleaned up"
-```

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

@@ -1,28 +0,0 @@
----
-allowed-tools: Bash
----
-
-Run `node .claude/scripts/pm/validate.js` using the Bash tool and show me the complete output.
-
-- DO NOT truncate.
-- DO NOT collapse.
-- DO NOT abbreviate.
-- Show ALL lines in full.
-## 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
-
-
-- DO NOT print any other comments.

package/autopm/.claude/commands/pm/what-next.md

@@ -1,28 +0,0 @@
----
-allowed-tools: Bash
----
-
-Run `node .claude/scripts/pm/what-next.js` using the Bash tool and show me the complete output.
-
-- DO NOT truncate.
-- DO NOT collapse.
-- DO NOT abbreviate.
-- Show ALL lines in full.
-## 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
-
-
-- DO NOT print any other comments.

package/autopm/.claude/commands/python/api-scaffold.md

@@ -1,50 +0,0 @@
----
-allowed-tools: Task, Read, Write, Edit, MultiEdit, Bash, Glob, Grep
----
-
-# Python API Scaffolding
-
-Creates a complete FastAPI project structure with modern Python tooling.
-
-**Usage**: `/python:api-scaffold [project-name] [--db=postgresql|mysql|sqlite] [--auth=jwt|oauth2]`
-
-## Required Documentation Access
-
-**MANDATORY:** Before scaffolding Python APIs, query Context7 for best practices:
-
-**Documentation Queries:**
-- `mcp://context7/python/api-scaffolding` - api scaffolding best practices
-- `mcp://context7/fastapi/structure` - structure best practices
-- `mcp://context7/api-design/rest` - rest best practices
-- `mcp://context7/python/best-practices` - best practices 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**: `/python:api-scaffold task-manager --db=postgresql --auth=jwt`
-
-**What this does**:
-- Creates complete FastAPI project structure
-- Sets up database integration with SQLAlchemy
-- Implements authentication system
-- Configures modern Python tooling (uv, ruff, mypy)
-- Adds comprehensive testing setup
-- Creates Docker configuration
-
-Use the python-backend-engineer agent to create a complete FastAPI project scaffold.
-
-Requirements for the agent:
-- Create modern project structure with proper FastAPI organization
-- Include SQLAlchemy models with async support
-- Add Pydantic schemas for request/response validation
-- Implement authentication and authorization system
-- Set up database migration with Alembic
-- Configure comprehensive testing with pytest
-- Add modern Python tooling configuration (uv, ruff, mypy)
-- Include Docker configuration and deployment setup
-- Ensure type hints throughout and async/await patterns
-- Add error handling, input validation, and security best practices

package/autopm/.claude/commands/python/docs-query.md

@@ -1,48 +0,0 @@
----
-allowed-tools: Task, Read, WebFetch, Glob, Grep
----
-
-# Python Documentation Query
-
-Queries latest Python/FastAPI documentation via context7 before implementation.
-
-**Usage**: `/python:docs-query [--topic=fastapi|sqlalchemy|pydantic|uv|pytest] [--pattern=search-pattern] [--examples]`
-
-## Required Documentation Access
-
-**MANDATORY:** Before Python API development, query Context7 for best practices:
-
-**Documentation Queries:**
-- `mcp://context7/python/api-development` - api development best practices
-- `mcp://context7/fastapi/best-practices` - best practices best practices
-- `mcp://context7/python/documentation` - documentation best practices
-- `mcp://context7/api-design/rest` - rest 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**: 
-- `/python:docs-query --topic=fastapi --pattern=authentication`
-- `/python:docs-query --topic=sqlalchemy --pattern=async --examples`
-- `/python:docs-query --topic=pydantic --examples`
-
-**What this does**:
-- Queries context7 for latest Python framework documentation
-- Searches for specific patterns, methods, or concepts
-- Returns relevant examples and best practices
-- Provides version compatibility information
-- Shows security recommendations and performance tips
-
-Use the python-backend-engineer agent to query documentation and provide implementation guidance.
-
-Requirements for the agent:
-- Query MCP context7 documentation servers for specified topics
-- Search documentation using provided patterns or keywords
-- Extract relevant code examples and implementation patterns
-- Verify version compatibility and security recommendations
-- Format results with clear examples and explanations
-- Include links to full documentation sections when available

package/autopm/.claude/commands/react/app-scaffold.md

@@ -1,50 +0,0 @@
----
-allowed-tools: Task, Read, Write, Edit, MultiEdit, Bash, Glob, Grep
----
-
-# React Application Scaffolding
-
-Creates a complete React application with TypeScript and modern tooling.
-
-**Usage**: `/react:app-scaffold [app-name] [--framework=vite|next] [--styling=tailwind|styled] [--state=zustand|redux]`
-
-## Required Documentation Access
-
-**MANDATORY:** Before scaffolding React applications, query Context7 for best practices:
-
-**Documentation Queries:**
-- `mcp://context7/react/project-setup` - project setup best practices
-- `mcp://context7/react/application-structure` - application structure best practices
-- `mcp://context7/frontend/tooling` - tooling best practices
-- `mcp://context7/react/best-practices` - best practices 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**: `/react:app-scaffold dashboard-app --framework=vite --styling=tailwind --state=zustand`
-
-**What this does**:
-- Creates complete React application structure
-- Sets up TypeScript configuration
-- Implements styling system (Tailwind CSS or styled-components)
-- Configures state management solution
-- Adds testing setup (Vitest + React Testing Library)
-- Creates Docker configuration for containerization
-- Sets up ESLint + Prettier for code quality
-
-Use the react-frontend-engineer agent to create a complete React application scaffold.
-
-Requirements for the agent:
-- Create modern project structure with proper React organization
-- Include TypeScript configuration with strict mode
-- Add component library structure with examples
-- Implement state management setup
-- Configure build tools (Vite or Next.js)
-- Add comprehensive testing setup
-- Include accessibility utilities and patterns
-- Ensure responsive design setup
-- Add proper error boundaries and loading states