claude-autopm 1.21.0 → 1.22.1

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

@@ -13,6 +13,23 @@ Validate work item structure and relationships for consistency.
 - `/azure:validate --fix` - Auto-fix issues
 - `/azure:validate --type=story` - Validate stories only
 
+## 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
 
 ### Validation Report

package/autopm/.claude/commands/azure/work-item-sync.md

@@ -8,6 +8,23 @@ Synchronizes GitHub Issues with Azure DevOps Work Items bidirectionally.
 
 **Usage**: `/azure:work-item-sync [--direction=both|github-to-azure|azure-to-github] [--project=project-name] [--area-path=area]`
 
+## 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
+
+
 **Example**: `/azure:work-item-sync --direction=both --project=MyProject --area-path=MyProject\Team1`
 
 **What this does**:

package/autopm/.claude/commands/cloud/infra-deploy.md

@@ -8,6 +8,23 @@ Deploys infrastructure to cloud providers using Terraform.
 
 **Usage**: `/cloud:infra-deploy [--provider=aws|azure|gcp] [--env=dev|staging|prod] [--services=compute,storage,database]`
 
+## Required Documentation Access
+
+**MANDATORY:** Before deploying infrastructure, query Context7 for best practices:
+
+**Documentation Queries:**
+- `mcp://context7/infrastructure/deployment` - deployment best practices
+- `mcp://context7/cloud/best-practices` - best practices best practices
+- `mcp://context7/devops/automation` - automation best practices
+- `mcp://context7/infrastructure/configuration` - configuration 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**: `/cloud:infra-deploy --provider=aws --env=staging --services=eks,rds,s3`
 
 **What this does**:

package/autopm/.claude/commands/config/toggle-features.md

@@ -9,6 +9,21 @@ This command allows you to toggle development features on/off in your ClaudeAuto
 ```bash
 /config:toggle-features
 ```
+## Required Documentation Access
+
+**MANDATORY:** Before configuration management, query Context7 for best practices:
+
+**Documentation Queries:**
+- `mcp://context7/configuration-management/best-practices` - best practices best practices
+- `mcp://context7/devops/feature-flags` - feature flags 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
+
+
 
 ### What It Does
 

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

@@ -6,6 +6,22 @@ allowed-tools: Bash, Read, Write, LS
 
 This command creates the initial project context documentation in `.claude/context/` by analyzing the current project state and establishing comprehensive baseline documentation.
 
+## Required Documentation Access
+
+**MANDATORY:** Before AI context management, query Context7 for best practices:
+
+**Documentation Queries:**
+- `mcp://context7/ai/context-management` - context management best practices
+- `mcp://context7/llm/prompt-engineering` - prompt engineering best practices
+- `mcp://context7/ai/rag-systems` - rag systems 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
+
+
 ## Required Rules
 
 **IMPORTANT:** Before executing this command, read and follow:

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

@@ -34,6 +34,22 @@ Do not bother the user with preflight checks progress ("I'm not going to ...").
 - Run: `git branch --show-current 2>/dev/null` to get current branch
 - Note if not in git repository (context may be less complete)
 
+## Required Documentation Access
+
+**MANDATORY:** Before AI context management, query Context7 for best practices:
+
+**Documentation Queries:**
+- `mcp://context7/ai/context-management` - context management best practices
+- `mcp://context7/llm/prompt-engineering` - prompt engineering best practices
+- `mcp://context7/ai/rag-systems` - rag systems 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. Context Loading Sequence

package/autopm/.claude/commands/context/update.md

@@ -6,6 +6,22 @@ allowed-tools: Bash, Read, Write, LS
 
 This command updates the project context documentation in `.claude/context/` to reflect the current state of the project. Run this at the end of each development session to keep context accurate.
 
+## Required Documentation Access
+
+**MANDATORY:** Before AI context management, query Context7 for best practices:
+
+**Documentation Queries:**
+- `mcp://context7/ai/context-management` - context management best practices
+- `mcp://context7/llm/prompt-engineering` - prompt engineering best practices
+- `mcp://context7/ai/rag-systems` - rag systems 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
+
+
 ## Required Rules
 
 **IMPORTANT:** Before executing this command, read and follow:

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

@@ -8,6 +8,23 @@ 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**:

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

@@ -32,6 +32,23 @@ Use the ssh-operations-expert agent to create comprehensive SSH security and ope
 
 ## 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

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

@@ -32,6 +32,23 @@ Use the traefik-proxy-expert agent to create a comprehensive Traefik reverse pro
 
 ## 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

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

@@ -8,6 +8,22 @@ 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**:

package/autopm/.claude/commands/mcp/context-setup.md

@@ -8,6 +8,23 @@ Configures Model Context Protocol (MCP) servers and context sharing between agen
 
 **Usage**: `/mcp:context-setup [--server=context7|filesystem|custom] [--pool-name=pool] [--agents=agent1,agent2] [--max-size=100MB]`
 
+## Required Documentation Access
+
+**MANDATORY:** Before MCP server setup and documentation, query Context7 for best practices:
+
+**Documentation Queries:**
+- `mcp://context7/mcp/protocol` - protocol best practices
+- `mcp://context7/mcp/servers` - servers best practices
+- `mcp://context7/ai/context-management` - context management best practices
+- `mcp://context7/mcp/integration` - integration 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**: `/mcp:context-setup --server=context7 --pool-name=project-context --agents=python-backend-engineer,azure-devops-specialist --max-size=50MB`
 
 **What this does**:

package/autopm/.claude/commands/mcp/docs-refresh.md

@@ -8,6 +8,23 @@ Refreshes documentation cache from context7 for specified agents and technologie
 
 **Usage**: `/mcp:docs-refresh [--agent=agent-name] [--tech=technology] [--force] [--validate]`
 
+## Required Documentation Access
+
+**MANDATORY:** Before MCP server setup and documentation, query Context7 for best practices:
+
+**Documentation Queries:**
+- `mcp://context7/mcp/protocol` - protocol best practices
+- `mcp://context7/mcp/servers` - servers best practices
+- `mcp://context7/ai/context-management` - context management best practices
+- `mcp://context7/mcp/integration` - integration 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**: 
 - `/mcp:docs-refresh --agent=python-backend-engineer --tech=fastapi`
 - `/mcp:docs-refresh --tech=azure-devops --force`

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

@@ -8,6 +8,23 @@ 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**:

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

@@ -8,4 +8,21 @@ Run `node .claude/scripts/pm/blocked.js` using the Bash tool and show me the com
 - 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

@@ -14,6 +14,23 @@ Clean up completed work and archive old epics.
 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

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

@@ -8,4 +8,21 @@ Run `node .claude/scripts/pm/context.js` using the Bash tool and show me the com
 - 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/epic-close.md

@@ -11,6 +11,23 @@ Mark an epic as complete when all tasks are done.
 /pm:epic-close <epic_name>
 ```
 
+## 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. Verify All Tasks Complete

package/autopm/.claude/commands/pm/epic-decompose.md

@@ -11,6 +11,22 @@ Break epic into concrete, actionable tasks.
 /pm:epic-decompose <feature_name>
 ```
 
+## Required Documentation Access
+
+**MANDATORY:** Before decomposing epics, query Context7 for best practices:
+
+**Documentation Queries:**
+- `mcp://context7/agile/epic-decomposition` - Epic breakdown best practices
+- `mcp://context7/agile/task-sizing` - Task estimation and sizing
+- `mcp://context7/agile/user-stories` - User story formats (INVEST criteria)
+- `mcp://context7/project-management/task-breakdown` - Work breakdown structure
+
+**Why This is Required:**
+- Ensures tasks follow industry-standard decomposition patterns
+- Applies current best practices for task sizing and dependencies
+- Validates task structure against proven methodologies
+- Prevents common anti-patterns in task breakdown
+
 ## Required Rules
 
 **IMPORTANT:** Before executing this command, read and follow:

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

@@ -11,6 +11,23 @@ Edit epic details after creation.
 /pm:epic-edit <epic_name>
 ```
 
+## 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. Read Current Epic

package/autopm/.claude/commands/pm/epic-list.md

@@ -8,6 +8,23 @@ Run `node .claude/scripts/pm/epic-list.js` using the Bash tool and show me the c
 - DO NOT truncate.
 - DO NOT collapse.
 - DO NOT abbreviate.
+## 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
+
+
 - Show ALL lines in full.
 - DO NOT print any other comments.
 

package/autopm/.claude/commands/pm/epic-merge.md

@@ -11,6 +11,23 @@ Merge completed epic branch back to main branch.
 /pm:epic-merge <epic_name>
 ```
 
+## 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
+
+
 ## Quick Check
 
 1. **Verify branch exists:**

package/autopm/.claude/commands/pm/epic-oneshot.md

@@ -24,6 +24,23 @@ See `.claude/rules/tdd.enforcement.md` for complete requirements.
 
 ---
 
+## 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. Validate Prerequisites

package/autopm/.claude/commands/pm/epic-refresh.md

@@ -11,6 +11,23 @@ Update epic progress based on task states.
 /pm:epic-refresh <epic_name>
 ```
 
+## 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. Count Task Status

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

@@ -8,4 +8,21 @@ Run `node .claude/scripts/pm/epic-show.js $ARGUMENTS` using the Bash tool and sh
 - 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/epic-split.md

@@ -7,6 +7,23 @@ Automatically split a PRD into multiple logical epics based on content analysis.
 /pm:epic-split <feature_name>
 ```
 
+## Required Documentation Access
+
+**MANDATORY:** Before splitting PRDs into epics, query Context7 for best practices:
+
+**Documentation Queries:**
+- `mcp://context7/agile/epic-splitting` - Epic decomposition strategies
+- `mcp://context7/project-management/dependency-mapping` - Dependency analysis patterns
+- `mcp://context7/agile/priority-frameworks` - Priority assessment (P0, P1, P2)
+- `mcp://context7/architecture/component-analysis` - Component identification
+- `mcp://context7/agile/parallel-planning` - Parallel work planning
+
+**Why This is Required:**
+- Ensures logical epic boundaries following proven patterns
+- Applies industry-standard dependency mapping techniques
+- Validates priority assignments against frameworks (MoSCoW, RICE)
+- Prevents inefficient epic structures and bottlenecks
+
 ## Description
 This command analyzes a PRD and automatically splits it into multiple epics based on:
 - Technical components (frontend, backend, infrastructure)

package/autopm/.claude/commands/pm/epic-start.md

@@ -11,6 +11,23 @@ Launch parallel agents to work on epic tasks using the unified branch strategy.
 /pm:epic-start <epic_name>
 ```
 
+## 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
+
+
 ## Quick Check
 
 1. **Verify epic exists:**