claude-autopm 2.7.0 → 2.8.2

package/autopm/.claude/commands/github/workflow-create.md

@@ -1,42 +0,0 @@
----
-allowed-tools: Task, Read, Write, Edit, MultiEdit, Bash, Glob, Grep
----
-
-# GitHub Workflow Creation
-
-Creates GitHub Actions workflows for CI/CD pipelines.
-
-**Usage**: `/github:workflow-create [--type=ci|cd|release] [--stack=node|python|dotnet] [--deploy-to=aws|azure|gcp]`
-
-## Required Documentation Access
-
-**MANDATORY:** Before creating GitHub workflows, query Context7 for best practices:
-
-**Documentation Queries:**
-- `mcp://context7/github/workflows` - workflows best practices
-- `mcp://context7/ci-cd/github-actions` - github actions best practices
-- `mcp://context7/devops/pipeline-design` - pipeline design best practices
-- `mcp://context7/ci-cd/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**: `/github:workflow-create --type=ci --stack=node --deploy-to=aws`
-
-**What this does**:
-- Creates .github/workflows directory structure
-- Generates workflow YAML with best practices
-- Configures secrets and environment variables
-- Sets up caching for dependencies
-- Implements matrix testing strategies
-- Adds deployment stages if needed
-
-Use the github-operations-specialist agent to create comprehensive GitHub Actions workflows.
-
-**CRITICAL INSTRUCTION FOR AGENT:**
-The generated workflow MUST adhere to the Kubernetes-native CI/CD strategy for `containerd` runners.
-Refer to the rules in `.claude/rules/ci-cd-kubernetes-strategy.md` for specific implementation details (use `kubectl` and `nerdctl`, not Docker services).

package/autopm/.claude/commands/infrastructure/ssh-security.md

@@ -1,65 +0,0 @@
----
-name: ssh-security-and-operations
-type: epic-management
-category: infrastructure
----
-
-# SSH Security and Operations Command
-
-Set up secure SSH configurations, key management, and remote operations.
-
-## Command
-```
-/infra:ssh-security
-```
-
-## Purpose
-Use the ssh-operations-expert agent to create secure SSH configurations, implement key rotation strategies, and set up remote management workflows.
-
-## Parameters
-- `scope`: Configuration scope (client, server, both)
-- `security_level`: Security hardening level (basic, advanced, paranoid)
-- `key_management`: Key management strategy (manual, automated, ca-based)
-- `features`: Additional features (tunneling, jump-hosts, automation)
-
-## Agent Usage
-```
-Use the ssh-operations-expert agent to create comprehensive SSH security and operations setup.
-```
-
-## Expected Outcome
-- Hardened SSH client/server configurations
-- SSH key generation and management scripts
-- Automated key rotation workflows
-- Tunnel and port forwarding setup
-- Jump host and bastion configuration
-- Remote operations and automation scripts
-- Security audit and monitoring tools
-
-## Example Usage
-```
-## Required Documentation Access
-
-**MANDATORY:** Before SSH security hardening, query Context7 for best practices:
-
-**Documentation Queries:**
-- `mcp://context7/security/ssh-hardening` - ssh hardening best practices
-- `mcp://context7/security/authentication` - authentication best practices
-- `mcp://context7/infrastructure/security` - security best practices
-- `mcp://context7/security/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
-
-
-Task: Set up secure SSH infrastructure with key rotation, jump hosts, and automated remote operations
-Agent: ssh-operations-expert
-Parameters: scope=both, security_level=advanced, key_management=automated, features=tunneling,jump-hosts,automation
-```
-
-## Related Agents
-- bash-scripting-expert: For automation scripts
-- terraform-infrastructure-expert: For infrastructure automation

package/autopm/.claude/commands/infrastructure/traefik-setup.md

@@ -1,65 +0,0 @@
----
-name: traefik-reverse-proxy-setup
-type: epic-management
-category: infrastructure
----
-
-# Traefik Reverse Proxy Setup Command
-
-Configure Traefik reverse proxy with SSL termination, load balancing, and service discovery.
-
-## Command
-```
-/infra:traefik-setup
-```
-
-## Purpose
-Use the traefik-proxy-expert agent to create a complete Traefik reverse proxy configuration with SSL automation, load balancing, and microservices routing.
-
-## Parameters
-- `environment`: Target environment (development, staging, production)
-- `ssl`: SSL configuration (letsencrypt, custom-certs, self-signed)
-- `discovery`: Service discovery method (docker, kubernetes, file)
-- `features`: Additional features (dashboard, metrics, rate-limiting, auth)
-
-## Agent Usage
-```
-Use the traefik-proxy-expert agent to create a comprehensive Traefik reverse proxy setup.
-```
-
-## Expected Outcome
-- Complete Traefik configuration (traefik.yml)
-- Docker Compose setup with Traefik service
-- SSL certificate automation
-- Service discovery configuration
-- Load balancing and health checks
-- Security middleware and authentication
-- Monitoring and logging setup
-
-## Example Usage
-```
-## Required Documentation Access
-
-**MANDATORY:** Before Traefik setup, query Context7 for best practices:
-
-**Documentation Queries:**
-- `mcp://context7/infrastructure/reverse-proxy` - reverse proxy best practices
-- `mcp://context7/traefik/configuration` - configuration best practices
-- `mcp://context7/devops/networking` - networking best practices
-- `mcp://context7/security/tls` - tls 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
-
-
-Task: Set up Traefik reverse proxy for microservices with Let's Encrypt SSL and Docker discovery
-Agent: traefik-proxy-expert
-Parameters: environment=production, ssl=letsencrypt, discovery=docker, features=dashboard,metrics,auth
-```
-
-## Related Agents
-- docker-containerization-expert: For container configuration
-- kubernetes-orchestrator: For K8s integration

package/autopm/.claude/commands/kubernetes/deploy.md

@@ -1,37 +0,0 @@
----
-allowed-tools: Task, Read, Write, Edit, MultiEdit, Bash, Glob, Grep
----
-
-# Kubernetes Deployment
-
-Deploys applications to Kubernetes clusters.
-
-**Usage**: `/kubernetes:deploy [app-name] [--chart=helm|kustomize] [--namespace=default] [--gitops=argocd|flux]`
-
-## Required Documentation Access
-
-**MANDATORY:** Before Kubernetes deployment, query Context7 for best practices:
-
-**Documentation Queries:**
-- `mcp://context7/kubernetes/deployment` - deployment best practices
-- `mcp://context7/kubernetes/best-practices` - best practices best practices
-- `mcp://context7/devops/container-orchestration` - container orchestration 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**: `/kubernetes:deploy my-app --chart=helm --namespace=production --gitops=argocd`
-
-**What this does**:
-- Creates Kubernetes manifests or Helm charts
-- Configures deployments with best practices
-- Sets up services and ingress
-- Implements autoscaling and monitoring
-- Configures GitOps if requested
-- Adds security policies
-
-Use the kubernetes-orchestrator agent to deploy applications to Kubernetes.

package/autopm/.claude/commands/playwright/test-scaffold.md

@@ -1,38 +0,0 @@
----
-allowed-tools: Task, Read, Write, Edit, MultiEdit, Bash, Glob, Grep
----
-
-# Playwright Test Scaffolding
-
-Creates Playwright test suite with Page Object Model.
-
-**Usage**: `/playwright:test-scaffold [app-name] [--framework=react|vue|angular] [--auth=yes|no]`
-
-## Required Documentation Access
-
-**MANDATORY:** Before scaffolding Playwright tests, query Context7 for best practices:
-
-**Documentation Queries:**
-- `mcp://context7/playwright/scaffolding` - scaffolding best practices
-- `mcp://context7/testing/e2e` - e2e best practices
-- `mcp://context7/testing/page-objects` - page objects best practices
-- `mcp://context7/playwright/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**: `/playwright:test-scaffold my-app --framework=react --auth=yes`
-
-**What this does**:
-- Creates Playwright configuration
-- Sets up Page Object Model structure
-- Generates test helpers and fixtures
-- Configures browsers and devices
-- Adds visual regression setup
-- Creates CI/CD integration scripts
-
-Use the frontend-testing-engineer agent to create comprehensive E2E test suite.

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

@@ -1,28 +0,0 @@
----
-allowed-tools: Bash
----
-
-Run `node .claude/scripts/pm/blocked.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/clean.md

@@ -1,119 +0,0 @@
----
-allowed-tools: Bash, Read, Write, LS
----
-
-# Clean
-
-Clean up completed work and archive old epics.
-
-## Usage
-```
-/pm:clean [--dry-run]
-```
-
-Options:
-- `--dry-run` - Show what would be cleaned without doing it
-
-## 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. Identify Completed Epics
-
-Find epics with:
-- `status: completed` in frontmatter
-- All tasks closed
-- Last update > 30 days ago
-
-### 2. Identify Stale Work
-
-Find:
-- Progress files for closed issues
-- Update directories for completed work
-- Orphaned task files (epic deleted)
-- Empty directories
-
-### 3. Show Cleanup Plan
-
-```
-🧹 Cleanup Plan
-
-Completed Epics to Archive:
-  {epic_name} - Completed {days} days ago
-  {epic_name} - Completed {days} days ago
-  
-Stale Progress to Remove:
-  {count} progress files for closed issues
-  
-Empty Directories:
-  {list_of_empty_dirs}
-  
-Space to Recover: ~{size}KB
-
-{If --dry-run}: This is a dry run. No changes made.
-{Otherwise}: Proceed with cleanup? (yes/no)
-```
-
-### 4. Execute Cleanup
-
-If user confirms:
-
-**Archive Epics:**
-```bash
-mkdir -p .claude/epics/.archived
-mv .claude/epics/{completed_epic} .claude/epics/.archived/
-```
-
-**Remove Stale Files:**
-- Delete progress files for closed issues > 30 days
-- Remove empty update directories
-- Clean up orphaned files
-
-**Create Archive Log:**
-Create `.claude/epics/.archived/archive-log.md`:
-```markdown
-# Archive Log
-
-## {current_date}
-- Archived: {epic_name} (completed {date})
-- Removed: {count} stale progress files
-- Cleaned: {count} empty directories
-```
-
-### 5. Output
-
-```
-✅ Cleanup Complete
-
-Archived:
-  {count} completed epics
-  
-Removed:
-  {count} stale files
-  {count} empty directories
-  
-Space recovered: {size}KB
-
-System is clean and organized.
-```
-
-## Important Notes
-
-Always offer --dry-run to preview changes.
-Never delete PRDs or incomplete work.
-Keep archive log for history.

package/autopm/.claude/commands/pm/context-create.md

@@ -1,136 +0,0 @@
----
-allowed-tools: Bash, Read, Write, Glob
----
-
-# Context Create
-
-Initialize project context documentation for AI agent memory.
-
-## Required Documentation Access
-
-**MANDATORY:** Before creating context, query Context7 for best practices:
-
-**Documentation Queries:**
-- `mcp://context7/documentation/project-context` - Project documentation standards
-- `mcp://context7/agile/project-setup` - Project initialization best practices
-- `mcp://context7/knowledge-management/technical-documentation` - Documentation organization patterns
-
-**Why This is Required:**
-- Ensures context follows industry standards
-- Provides templates aligned with best practices
-- Establishes effective knowledge management patterns
-
-## Instructions
-
-Create comprehensive project context in `.claude/context/` directory.
-
-### 1. Check if context already exists
-
-```bash
-if [ -d ".claude/context" ]; then
-  echo "⚠️  Context already exists. Use /pm:context-update to modify."
-  exit 1
-fi
-```
-
-### 2. Create context directory structure
-
-```bash
-mkdir -p .claude/context
-```
-
-### 3. Copy and customize templates
-
-**Read templates from AutoPM installation:**
-- `.claude/templates/context-templates/project-brief.md.template`
-- `.claude/templates/context-templates/tech-context.md.template`
-- `.claude/templates/context-templates/progress.md.template`
-- `.claude/templates/context-templates/project-structure.md.template`
-
-### 4. Auto-populate with project information
-
-**Analyze project and pre-fill templates:**
-
-1. **Read package.json** for tech stack:
-   - Extract dependencies and devDependencies
-   - Determine Node.js version from engines
-   - Identify testing framework (Jest, Mocha, etc.)
-   - Detect package manager from lock files
-
-2. **Read README.md** for project description:
-   - Extract project name and description
-   - Identify key features and objectives
-   - Find usage examples
-
-3. **Detect directory structure:**
-   - Scan top-level directories
-   - Identify common patterns (src/, test/, docs/, etc.)
-   - Map key configuration files
-
-4. **Initialize progress:**
-   - Set initial phase as "Setup" or "Development"
-   - Mark context creation as first completed task
-   - Set progress to appropriate starting percentage
-
-### 5. Create context README
-
-Write `.claude/context/README.md`:
-
-```markdown
-# Project Context
-
-This directory maintains comprehensive project information for AI agents.
-
-## Files
-- **project-brief.md**: Project scope and objectives
-- **tech-context.md**: Technology stack and dependencies
-- **progress.md**: Current status and next steps
-- **project-structure.md**: Directory layout and key files
-
-## Usage
-- `/pm:context-prime`: Load context for new session
-- `/pm:context-update`: Update after changes
-- `/pm:context`: View current context
-
-## Maintenance
-Keep these files updated as the project evolves. Run `/pm:context-update` after:
-- Adding new dependencies
-- Completing major tasks
-- Changing project structure
-- Updating technical stack
-```
-
-### 6. Write populated templates
-
-Create the following files in `.claude/context/`:
-- `project-brief.md` (populated from README and package.json)
-- `tech-context.md` (populated from package.json and file detection)
-- `progress.md` (initialized with setup phase)
-- `project-structure.md` (populated from directory scan)
-
-### 7. Confirm creation
-
-Display success message:
-
-```
-✅ Context created in .claude/context/
-
-📝 Files created:
-   - project-brief.md (auto-populated from README)
-   - tech-context.md (auto-populated from package.json)
-   - progress.md (initialized)
-   - project-structure.md (auto-populated from directory scan)
-   - README.md (usage guide)
-
-💡 Next steps:
-   1. Review and customize the context files
-   2. Run /pm:context-prime to load context into session
-   3. Update regularly with /pm:context-update
-```
-
-## Output Format
-
-Return a structured summary of:
-- Files created with auto-populated content preview
-- Any information that couldn't be auto-detected
-- Recommendations for manual customization

package/autopm/.claude/commands/pm/context-prime.md

@@ -1,170 +0,0 @@
----
-allowed-tools: Read, Bash
----
-
-# Context Prime
-
-Load project context into current AI session for better understanding and continuity.
-
-## Required Documentation Access
-
-**MANDATORY:** Before priming context, query Context7 for best practices:
-
-**Documentation Queries:**
-- `mcp://context7/knowledge-management/context-loading` - Context loading patterns
-- `mcp://context7/ai/prompt-engineering` - Effective context management for AI
-
-**Why This is Required:**
-- Ensures optimal context loading for AI comprehension
-- Provides strategies for maintaining session continuity
-
-## Instructions
-
-Load comprehensive project context into the current AI session.
-
-### 1. Verify context exists
-
-```bash
-if [ ! -d ".claude/context" ]; then
-  echo "❌ Context not found. Run /pm:context-create first."
-  exit 1
-fi
-```
-
-### 2. Read all context files
-
-Read in order:
-1. `.claude/context/project-brief.md` - Project overview and objectives
-2. `.claude/context/tech-context.md` - Technical stack and dependencies
-3. `.claude/context/project-structure.md` - Directory layout and organization
-4. `.claude/context/progress.md` - Current status and next steps
-
-### 3. Process and internalize context
-
-**Parse key information:**
-
-From **project-brief.md**:
-- Project name and description
-- Primary objectives and goals
-- Target users and stakeholders
-- Key constraints and limitations
-- Success criteria
-
-From **tech-context.md**:
-- Technology stack (frontend, backend, database, infrastructure)
-- Development environment (Node.js version, package manager, testing framework)
-- Key dependencies and their purposes
-- Architecture patterns in use
-- Development practices
-
-From **project-structure.md**:
-- Directory layout and organization
-- Key files and their purposes
-- Module structure
-- Configuration files
-
-From **progress.md**:
-- Current phase and progress percentage
-- Completed tasks
-- In-progress tasks
-- Next steps
-- Any blockers
-
-### 4. Display loaded context summary
-
-Present a comprehensive summary:
-
-```
-📋 Project Context Loaded
-
-══════════════════════════════════════════════════════════════════
-
-PROJECT: [Project Name]
-PHASE: [Current Phase] | PROGRESS: [X]%
-LAST UPDATED: [Date from progress.md]
-
-══════════════════════════════════════════════════════════════════
-
-🎯 OBJECTIVES
-  - [Primary goal]
-  - [Secondary goal]
-  - [Tertiary goal]
-
-🔧 TECH STACK
-  - Frontend: [Technologies]
-  - Backend: [Technologies]
-  - Database: [Database]
-  - Testing: [Framework]
-
-📁 STRUCTURE
-  [Brief structure overview]
-
-✅ COMPLETED
-  - [Recent completed task 1]
-  - [Recent completed task 2]
-
-🚧 IN PROGRESS
-  - [Current task 1]
-  - [Current task 2]
-
-⏭️  NEXT STEPS
-  1. [Next action 1]
-  2. [Next action 2]
-
-⚠️  BLOCKERS
-  - [Blocker 1, if any]
-
-══════════════════════════════════════════════════════════════════
-
-✅ Context loaded. AI agent now has project memory.
-
-💡 TIP: Run /pm:context-update after significant changes to keep context current.
-```
-
-### 5. Internal context retention
-
-**CRITICAL:** After displaying the summary, the AI agent should:
-
-1. **Retain project identity**: Remember project name, goals, and constraints
-2. **Understand technical environment**: Keep tech stack and dependencies in mind
-3. **Maintain progress awareness**: Know what's done, what's in progress, what's next
-4. **Respect project structure**: Work within established organization patterns
-5. **Align with practices**: Follow development practices outlined in context
-
-This context should guide all subsequent interactions in the session:
-- Suggestions should align with project objectives
-- Recommendations should fit the tech stack
-- Changes should consider current progress
-- Code should match project structure
-
-### 6. Confirmation
-
-Return structured confirmation:
-
-```json
-{
-  "status": "loaded",
-  "project": "[Project Name]",
-  "phase": "[Current Phase]",
-  "progress": "[X]%",
-  "filesRead": [
-    "project-brief.md",
-    "tech-context.md",
-    "project-structure.md",
-    "progress.md"
-  ],
-  "keyTakeaways": [
-    "[Important point 1]",
-    "[Important point 2]",
-    "[Important point 3]"
-  ]
-}
-```
-
-## Output Format
-
-Return:
-- Formatted context summary (as shown above)
-- Key information highlighted
-- Current focus areas
-- Recommendations based on loaded context