claude-autopm 1.20.1 → 1.22.0

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

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

@@ -11,6 +11,23 @@ Push epic and tasks to GitHub as issues using modular scripts.
 /pm:epic-sync <feature_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
 
 ```bash

package/autopm/.claude/commands/pm/epic-sync-original.md

@@ -11,6 +11,23 @@ Push epic and tasks to GitHub as issues.
 /pm:epic-sync <feature_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
 
 ```bash

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

@@ -11,6 +11,38 @@ Push epic and tasks to GitHub as issues using modular scripts.
 /pm:epic-sync <feature_name>
 ```
 
+## Quick Start
+
+The simplest way to sync an epic to GitHub:
+
+```bash
+# Full automated sync (recommended)
+bash .claude/scripts/pm/epic-sync.sh "$ARGUMENTS"
+```
+
+This orchestration script automatically runs all 4 steps:
+1. Creates epic issue
+2. Creates task issues
+3. Renames files to issue numbers
+4. Updates all references
+
+## 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
 
 ```bash
@@ -32,7 +64,14 @@ If no tasks found: "❌ No tasks to sync. Run: /pm:epic-decompose $ARGUMENTS"
 
 ## Instructions
 
-The epic sync process is now modularized into 4 specialized scripts that handle different aspects of the synchronization. Each script is designed for reliability, testability, and maintainability.
+**⚡ Quick Command:**
+```bash
+bash .claude/scripts/pm/epic-sync.sh "$ARGUMENTS"
+```
+
+The epic sync process is modularized into 4 specialized scripts that handle different aspects of the synchronization. Each script is designed for reliability, testability, and maintainability.
+
+The orchestration script (`.claude/scripts/pm/epic-sync.sh`) automatically runs all 4 steps in sequence. The individual scripts are documented below for reference and debugging.
 
 ### Processing Mode Detection
 
@@ -158,13 +197,24 @@ echo "✅ Created branch: epic/$ARGUMENTS"
 
 ## Complete Workflow Examples
 
-### Single Epic Workflow
+### Single Epic Workflow (Automated - Recommended)
+
+The **easiest way** is to use the orchestration script that handles everything:
+
+```bash
+# One command does it all!
+bash .claude/scripts/pm/epic-sync.sh "$ARGUMENTS"
+```
+
+This automatically runs all 4 steps and provides a complete summary.
+
+### Single Epic Workflow (Manual Steps)
 
-Here's the complete modular epic sync workflow for a single epic:
+If you need to run steps individually for debugging:
 
 ```bash
 #!/bin/bash
-# Complete epic sync using modular scripts
+# Complete epic sync using modular scripts (manual)
 
 EPIC_NAME="$ARGUMENTS"
 

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

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

@@ -16,6 +16,23 @@ Options:
 - `--label` - Import only issues with specific label
 - No args - Import all untracked issues
 
+## 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. Fetch GitHub Issues

package/autopm/.claude/commands/pm/in-progress.md

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

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

@@ -11,6 +11,23 @@ Analyze an issue to identify parallel work streams for maximum efficiency.
 /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:**

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

@@ -11,6 +11,23 @@ Mark an issue as complete and close it on GitHub.
 /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

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

@@ -11,6 +11,23 @@ Edit issue details locally and on GitHub.
 /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

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

@@ -11,6 +11,23 @@ Reopen a closed issue.
 /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

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

@@ -11,6 +11,23 @@ Display issue and sub-issues with detailed information.
 /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.

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

@@ -33,6 +33,22 @@ Begin work on a GitHub issue with parallel agents based on work stream analysis.
    ` ``
    If no analysis exists and no --analyze flag, stop execution.
 
+## Required Documentation Access
+
+**MANDATORY:** Before starting work on issues, query Context7 for best practices:
+
+**Documentation Queries:**
+- `mcp://context7/agile/issue-planning` - Issue planning and breakdown
+- `mcp://context7/tdd/workflow` - Test-Driven Development workflow
+- `mcp://context7/git/branching` - Git branching strategies
+- `mcp://context7/collaboration/parallel-work` - Parallel development patterns
+
+**Why This is Required:**
+- Ensures work follows current TDD best practices
+- Applies proven patterns for parallel development
+- Validates task coordination strategies
+- Prevents common pitfalls in distributed work
+
 ## ⚠️ TDD REMINDER - READ THIS FIRST
 
 **CRITICAL: This project follows Test-Driven Development (TDD).**

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

@@ -11,6 +11,23 @@ Check issue status (open/closed) and current state.
 /pm:issue-status <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
 
 You are checking the current status of a GitHub issue and providing a quick status report for: **Issue #$ARGUMENTS**

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

@@ -11,6 +11,23 @@ Push local updates as GitHub issue comments for transparent audit trail.
 /pm:issue-sync <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
+
+
 ## Quick Check
 
 ```bash

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

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

@@ -11,6 +11,23 @@ Edit an existing Product Requirements Document.
 /pm:prd-edit <feature_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 PRD

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

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

@@ -11,6 +11,22 @@ Launch interactive brainstorming session for new product requirement document.
 /pm:prd-new <feature_name>
 ```
 
+## Required Documentation Access
+
+**MANDATORY:** Before creating PRDs, query Context7 for best practices:
+
+**Documentation Queries:**
+- `mcp://context7/product-management/prd-templates` - PRD structure and templates
+- `mcp://context7/product-management/requirements` - Requirements gathering
+- `mcp://context7/agile/user-stories` - User story best practices
+- `mcp://context7/product-management/success-metrics` - Defining success criteria
+
+**Why This is Required:**
+- Ensures PRDs follow industry-standard formats
+- Applies proven requirements gathering techniques
+- Validates completeness of product specifications
+- Prevents missing critical sections (acceptance criteria, success metrics, etc.)
+
 ## Instructions
 
 Run `node .claude/scripts/pm/prd-new.js $ARGUMENTS` using the Bash tool and show me the complete output.

package/autopm/.claude/commands/pm/prd-parse.md

@@ -11,6 +11,23 @@ Convert PRD to technical implementation epic.
 /pm:prd-parse <feature_name>
 ```
 
+## Required Documentation Access
+
+**MANDATORY:** Before converting PRDs to epics, query Context7 for best practices:
+
+**Documentation Queries:**
+- `mcp://context7/product-management/prd-to-epic` - PRD to epic conversion patterns
+- `mcp://context7/agile/epic-structure` - Epic structure and organization
+- `mcp://context7/architecture/technical-design` - Technical architecture decisions
+- `mcp://context7/project-management/task-breakdown` - Task breakdown strategies
+- `mcp://context7/agile/estimation` - Effort estimation and timeline planning
+
+**Why This is Required:**
+- Ensures proper PRD-to-epic translation following industry standards
+- Applies proven architecture decision frameworks
+- Validates task breakdown completeness and accuracy
+- Prevents missing critical technical considerations
+
 ## Instructions
 
 Run `node .claude/scripts/pm/prd-parse.js $ARGUMENTS` using the Bash tool and show me the complete output.

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

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

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

@@ -8,4 +8,21 @@ Run `node .claude/scripts/pm/standup.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/status.md

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