claude-autopm 1.21.0 → 1.22.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (134) hide show
  1. package/autopm/.claude/agents/cloud/gcp-cloud-functions-engineer.md +5 -10
  2. package/autopm/.claude/agents/cloud/gemini-api-expert.md +1 -1
  3. package/autopm/.claude/agents/cloud/openai-python-expert.md +1 -1
  4. package/autopm/.claude/agents/cloud/terraform-infrastructure-expert.md +7 -11
  5. package/autopm/.claude/agents/core/mcp-manager.md +7 -0
  6. package/autopm/.claude/agents/data/airflow-orchestration-expert.md +1 -1
  7. package/autopm/.claude/agents/data/kedro-pipeline-expert.md +1 -1
  8. package/autopm/.claude/agents/data/langgraph-workflow-expert.md +1 -1
  9. package/autopm/.claude/agents/databases/bigquery-expert.md +1 -1
  10. package/autopm/.claude/agents/databases/cosmosdb-expert.md +1 -1
  11. package/autopm/.claude/agents/databases/mongodb-expert.md +1 -1
  12. package/autopm/.claude/agents/databases/postgresql-expert.md +1 -1
  13. package/autopm/.claude/agents/databases/redis-expert.md +1 -1
  14. package/autopm/.claude/agents/decision-matrices/playwright-testing-selection.md +6 -0
  15. package/autopm/.claude/agents/decision-matrices/python-backend-selection.md +7 -0
  16. package/autopm/.claude/agents/decision-matrices/ui-framework-selection.md +7 -0
  17. package/autopm/.claude/agents/devops/azure-devops-specialist.md +1 -1
  18. package/autopm/.claude/agents/devops/github-operations-specialist.md +7 -0
  19. package/autopm/.claude/agents/devops/mcp-context-manager.md +7 -0
  20. package/autopm/.claude/agents/devops/ssh-operations-expert.md +1 -1
  21. package/autopm/.claude/agents/devops/traefik-proxy-expert.md +1 -1
  22. package/autopm/.claude/agents/frameworks/nats-messaging-expert.md +1 -1
  23. package/autopm/.claude/agents/frameworks/react-frontend-engineer.md +1 -1
  24. package/autopm/.claude/agents/languages/bash-scripting-expert.md +1 -1
  25. package/autopm/.claude/agents/languages/javascript-frontend-engineer.md +1 -1
  26. package/autopm/.claude/agents/languages/nodejs-backend-engineer.md +9 -6
  27. package/autopm/.claude/agents/languages/python-backend-engineer.md +1 -1
  28. package/autopm/.claude/commands/ai/langgraph-workflow.md +17 -0
  29. package/autopm/.claude/commands/ai/openai-chat.md +17 -0
  30. package/autopm/.claude/commands/azure/active-work.md +17 -0
  31. package/autopm/.claude/commands/azure/aliases.md +17 -0
  32. package/autopm/.claude/commands/azure/blocked-items.md +17 -0
  33. package/autopm/.claude/commands/azure/clean.md +17 -0
  34. package/autopm/.claude/commands/azure/docs-query.md +17 -0
  35. package/autopm/.claude/commands/azure/feature-decompose.md +17 -0
  36. package/autopm/.claude/commands/azure/feature-list.md +17 -0
  37. package/autopm/.claude/commands/azure/feature-new.md +17 -0
  38. package/autopm/.claude/commands/azure/feature-show.md +17 -0
  39. package/autopm/.claude/commands/azure/feature-start.md +17 -0
  40. package/autopm/.claude/commands/azure/fix-integration-example.md +17 -0
  41. package/autopm/.claude/commands/azure/help.md +17 -0
  42. package/autopm/.claude/commands/azure/import-us.md +17 -0
  43. package/autopm/.claude/commands/azure/init.md +17 -0
  44. package/autopm/.claude/commands/azure/next-task.md +17 -0
  45. package/autopm/.claude/commands/azure/search.md +17 -0
  46. package/autopm/.claude/commands/azure/sprint-status.md +17 -0
  47. package/autopm/.claude/commands/azure/standup.md +17 -0
  48. package/autopm/.claude/commands/azure/sync-all.md +17 -0
  49. package/autopm/.claude/commands/azure/task-analyze.md +17 -0
  50. package/autopm/.claude/commands/azure/task-close.md +17 -0
  51. package/autopm/.claude/commands/azure/task-edit.md +17 -0
  52. package/autopm/.claude/commands/azure/task-list.md +17 -0
  53. package/autopm/.claude/commands/azure/task-new.md +17 -0
  54. package/autopm/.claude/commands/azure/task-reopen.md +17 -0
  55. package/autopm/.claude/commands/azure/task-show.md +17 -0
  56. package/autopm/.claude/commands/azure/task-start.md +17 -0
  57. package/autopm/.claude/commands/azure/task-status.md +17 -0
  58. package/autopm/.claude/commands/azure/task-sync.md +17 -0
  59. package/autopm/.claude/commands/azure/us-edit.md +17 -0
  60. package/autopm/.claude/commands/azure/us-list.md +17 -0
  61. package/autopm/.claude/commands/azure/us-new.md +17 -0
  62. package/autopm/.claude/commands/azure/us-parse.md +17 -0
  63. package/autopm/.claude/commands/azure/us-show.md +17 -0
  64. package/autopm/.claude/commands/azure/us-status.md +17 -0
  65. package/autopm/.claude/commands/azure/validate.md +17 -0
  66. package/autopm/.claude/commands/azure/work-item-sync.md +17 -0
  67. package/autopm/.claude/commands/cloud/infra-deploy.md +17 -0
  68. package/autopm/.claude/commands/config/toggle-features.md +15 -0
  69. package/autopm/.claude/commands/context/create.md +16 -0
  70. package/autopm/.claude/commands/context/prime.md +16 -0
  71. package/autopm/.claude/commands/context/update.md +16 -0
  72. package/autopm/.claude/commands/github/workflow-create.md +17 -0
  73. package/autopm/.claude/commands/infrastructure/ssh-security.md +17 -0
  74. package/autopm/.claude/commands/infrastructure/traefik-setup.md +17 -0
  75. package/autopm/.claude/commands/kubernetes/deploy.md +16 -0
  76. package/autopm/.claude/commands/mcp/context-setup.md +17 -0
  77. package/autopm/.claude/commands/mcp/docs-refresh.md +17 -0
  78. package/autopm/.claude/commands/playwright/test-scaffold.md +17 -0
  79. package/autopm/.claude/commands/pm/blocked.md +17 -0
  80. package/autopm/.claude/commands/pm/clean.md +17 -0
  81. package/autopm/.claude/commands/pm/context.md +17 -0
  82. package/autopm/.claude/commands/pm/epic-close.md +17 -0
  83. package/autopm/.claude/commands/pm/epic-decompose.md +16 -0
  84. package/autopm/.claude/commands/pm/epic-edit.md +17 -0
  85. package/autopm/.claude/commands/pm/epic-list.md +17 -0
  86. package/autopm/.claude/commands/pm/epic-merge.md +17 -0
  87. package/autopm/.claude/commands/pm/epic-oneshot.md +17 -0
  88. package/autopm/.claude/commands/pm/epic-refresh.md +17 -0
  89. package/autopm/.claude/commands/pm/epic-show.md +17 -0
  90. package/autopm/.claude/commands/pm/epic-split.md +17 -0
  91. package/autopm/.claude/commands/pm/epic-start.md +17 -0
  92. package/autopm/.claude/commands/pm/epic-status.md +17 -0
  93. package/autopm/.claude/commands/pm/epic-sync-modular.md +17 -0
  94. package/autopm/.claude/commands/pm/epic-sync-original.md +17 -0
  95. package/autopm/.claude/commands/pm/epic-sync.md +17 -0
  96. package/autopm/.claude/commands/pm/help.md +17 -0
  97. package/autopm/.claude/commands/pm/import.md +17 -0
  98. package/autopm/.claude/commands/pm/in-progress.md +17 -0
  99. package/autopm/.claude/commands/pm/init.md +17 -0
  100. package/autopm/.claude/commands/pm/issue-analyze.md +17 -0
  101. package/autopm/.claude/commands/pm/issue-close.md +17 -0
  102. package/autopm/.claude/commands/pm/issue-edit.md +17 -0
  103. package/autopm/.claude/commands/pm/issue-reopen.md +17 -0
  104. package/autopm/.claude/commands/pm/issue-show.md +17 -0
  105. package/autopm/.claude/commands/pm/issue-start.md +16 -0
  106. package/autopm/.claude/commands/pm/issue-status.md +17 -0
  107. package/autopm/.claude/commands/pm/issue-sync.md +17 -0
  108. package/autopm/.claude/commands/pm/next.md +17 -0
  109. package/autopm/.claude/commands/pm/prd-edit.md +17 -0
  110. package/autopm/.claude/commands/pm/prd-list.md +17 -0
  111. package/autopm/.claude/commands/pm/prd-new.md +16 -0
  112. package/autopm/.claude/commands/pm/prd-parse.md +17 -0
  113. package/autopm/.claude/commands/pm/prd-status.md +17 -0
  114. package/autopm/.claude/commands/pm/search.md +17 -0
  115. package/autopm/.claude/commands/pm/standup.md +17 -0
  116. package/autopm/.claude/commands/pm/status.md +17 -0
  117. package/autopm/.claude/commands/pm/sync.md +17 -0
  118. package/autopm/.claude/commands/pm/test-reference-update.md +17 -0
  119. package/autopm/.claude/commands/pm/validate.md +17 -0
  120. package/autopm/.claude/commands/pm/what-next.md +17 -0
  121. package/autopm/.claude/commands/python/api-scaffold.md +17 -0
  122. package/autopm/.claude/commands/python/docs-query.md +17 -0
  123. package/autopm/.claude/commands/react/app-scaffold.md +17 -0
  124. package/autopm/.claude/commands/testing/prime.md +17 -0
  125. package/autopm/.claude/commands/testing/run.md +17 -0
  126. package/autopm/.claude/commands/ui/bootstrap-scaffold.md +17 -0
  127. package/autopm/.claude/commands/ui/tailwind-system.md +17 -0
  128. package/autopm/.claude/hooks/context7-reminder.md +29 -0
  129. package/autopm/.claude/hooks/pre-agent-context7.js +224 -0
  130. package/autopm/.claude/hooks/pre-command-context7.js +229 -0
  131. package/autopm/.claude/hooks/unified-context7-enforcement.sh +38 -0
  132. package/autopm/.claude/rules/context7-enforcement.md +327 -0
  133. package/package.json +1 -1
  134. package/scripts/add-context7-to-commands.js +351 -0
@@ -8,4 +8,21 @@ Run `node .claude/scripts/pm/epic-status.js $ARGUMENTS` using the Bash tool and
8
8
  - DO NOT collapse.
9
9
  - DO NOT abbreviate.
10
10
  - Show ALL lines in full.
11
+ ## Required Documentation Access
12
+
13
+ **MANDATORY:** Before project management workflows, query Context7 for best practices:
14
+
15
+ **Documentation Queries:**
16
+ - `mcp://context7/agile/epic-management` - epic management best practices
17
+ - `mcp://context7/project-management/issue-tracking` - issue tracking best practices
18
+ - `mcp://context7/agile/task-breakdown` - task breakdown best practices
19
+ - `mcp://context7/project-management/workflow` - workflow best practices
20
+
21
+ **Why This is Required:**
22
+ - Ensures adherence to current industry standards and best practices
23
+ - Prevents outdated or incorrect implementation patterns
24
+ - Provides access to latest framework/tool documentation
25
+ - Reduces errors from stale knowledge or assumptions
26
+
27
+
11
28
  - DO NOT print any other comments.
@@ -11,6 +11,23 @@ Push epic and tasks to GitHub as issues using modular scripts.
11
11
  /pm:epic-sync <feature_name>
12
12
  ```
13
13
 
14
+ ## Required Documentation Access
15
+
16
+ **MANDATORY:** Before project management workflows, query Context7 for best practices:
17
+
18
+ **Documentation Queries:**
19
+ - `mcp://context7/agile/epic-management` - epic management best practices
20
+ - `mcp://context7/project-management/issue-tracking` - issue tracking best practices
21
+ - `mcp://context7/agile/task-breakdown` - task breakdown best practices
22
+ - `mcp://context7/project-management/workflow` - workflow best practices
23
+
24
+ **Why This is Required:**
25
+ - Ensures adherence to current industry standards and best practices
26
+ - Prevents outdated or incorrect implementation patterns
27
+ - Provides access to latest framework/tool documentation
28
+ - Reduces errors from stale knowledge or assumptions
29
+
30
+
14
31
  ## Quick Check
15
32
 
16
33
  ```bash
@@ -11,6 +11,23 @@ Push epic and tasks to GitHub as issues.
11
11
  /pm:epic-sync <feature_name>
12
12
  ```
13
13
 
14
+ ## Required Documentation Access
15
+
16
+ **MANDATORY:** Before project management workflows, query Context7 for best practices:
17
+
18
+ **Documentation Queries:**
19
+ - `mcp://context7/agile/epic-management` - epic management best practices
20
+ - `mcp://context7/project-management/issue-tracking` - issue tracking best practices
21
+ - `mcp://context7/agile/task-breakdown` - task breakdown best practices
22
+ - `mcp://context7/project-management/workflow` - workflow best practices
23
+
24
+ **Why This is Required:**
25
+ - Ensures adherence to current industry standards and best practices
26
+ - Prevents outdated or incorrect implementation patterns
27
+ - Provides access to latest framework/tool documentation
28
+ - Reduces errors from stale knowledge or assumptions
29
+
30
+
14
31
  ## Quick Check
15
32
 
16
33
  ```bash
@@ -26,6 +26,23 @@ This orchestration script automatically runs all 4 steps:
26
26
  3. Renames files to issue numbers
27
27
  4. Updates all references
28
28
 
29
+ ## Required Documentation Access
30
+
31
+ **MANDATORY:** Before project management workflows, query Context7 for best practices:
32
+
33
+ **Documentation Queries:**
34
+ - `mcp://context7/agile/epic-management` - epic management best practices
35
+ - `mcp://context7/project-management/issue-tracking` - issue tracking best practices
36
+ - `mcp://context7/agile/task-breakdown` - task breakdown best practices
37
+ - `mcp://context7/project-management/workflow` - workflow best practices
38
+
39
+ **Why This is Required:**
40
+ - Ensures adherence to current industry standards and best practices
41
+ - Prevents outdated or incorrect implementation patterns
42
+ - Provides access to latest framework/tool documentation
43
+ - Reduces errors from stale knowledge or assumptions
44
+
45
+
29
46
  ## Quick Check
30
47
 
31
48
  ```bash
@@ -8,4 +8,21 @@ Run `node .claude/scripts/pm/help.js` using the Bash tool and show me the comple
8
8
  - DO NOT collapse.
9
9
  - DO NOT abbreviate.
10
10
  - Show ALL lines in full.
11
+ ## Required Documentation Access
12
+
13
+ **MANDATORY:** Before project management workflows, query Context7 for best practices:
14
+
15
+ **Documentation Queries:**
16
+ - `mcp://context7/agile/epic-management` - epic management best practices
17
+ - `mcp://context7/project-management/issue-tracking` - issue tracking best practices
18
+ - `mcp://context7/agile/task-breakdown` - task breakdown best practices
19
+ - `mcp://context7/project-management/workflow` - workflow best practices
20
+
21
+ **Why This is Required:**
22
+ - Ensures adherence to current industry standards and best practices
23
+ - Prevents outdated or incorrect implementation patterns
24
+ - Provides access to latest framework/tool documentation
25
+ - Reduces errors from stale knowledge or assumptions
26
+
27
+
11
28
  - DO NOT print any other comments.
@@ -16,6 +16,23 @@ Options:
16
16
  - `--label` - Import only issues with specific label
17
17
  - No args - Import all untracked issues
18
18
 
19
+ ## Required Documentation Access
20
+
21
+ **MANDATORY:** Before project management workflows, query Context7 for best practices:
22
+
23
+ **Documentation Queries:**
24
+ - `mcp://context7/agile/epic-management` - epic management best practices
25
+ - `mcp://context7/project-management/issue-tracking` - issue tracking best practices
26
+ - `mcp://context7/agile/task-breakdown` - task breakdown best practices
27
+ - `mcp://context7/project-management/workflow` - workflow best practices
28
+
29
+ **Why This is Required:**
30
+ - Ensures adherence to current industry standards and best practices
31
+ - Prevents outdated or incorrect implementation patterns
32
+ - Provides access to latest framework/tool documentation
33
+ - Reduces errors from stale knowledge or assumptions
34
+
35
+
19
36
  ## Instructions
20
37
 
21
38
  ### 1. Fetch GitHub Issues
@@ -8,4 +8,21 @@ Run `node .claude/scripts/pm/in-progress.js` using the Bash tool and show me the
8
8
  - DO NOT collapse.
9
9
  - DO NOT abbreviate.
10
10
  - Show ALL lines in full.
11
+ ## Required Documentation Access
12
+
13
+ **MANDATORY:** Before project management workflows, query Context7 for best practices:
14
+
15
+ **Documentation Queries:**
16
+ - `mcp://context7/agile/epic-management` - epic management best practices
17
+ - `mcp://context7/project-management/issue-tracking` - issue tracking best practices
18
+ - `mcp://context7/agile/task-breakdown` - task breakdown best practices
19
+ - `mcp://context7/project-management/workflow` - workflow best practices
20
+
21
+ **Why This is Required:**
22
+ - Ensures adherence to current industry standards and best practices
23
+ - Prevents outdated or incorrect implementation patterns
24
+ - Provides access to latest framework/tool documentation
25
+ - Reduces errors from stale knowledge or assumptions
26
+
27
+
11
28
  - DO NOT print any other comments.
@@ -8,4 +8,21 @@ Run `node .claude/scripts/pm/init.js` using the Bash tool and show me the comple
8
8
  - DO NOT collapse.
9
9
  - DO NOT abbreviate.
10
10
  - Show ALL lines in full.
11
+ ## Required Documentation Access
12
+
13
+ **MANDATORY:** Before project management workflows, query Context7 for best practices:
14
+
15
+ **Documentation Queries:**
16
+ - `mcp://context7/agile/epic-management` - epic management best practices
17
+ - `mcp://context7/project-management/issue-tracking` - issue tracking best practices
18
+ - `mcp://context7/agile/task-breakdown` - task breakdown best practices
19
+ - `mcp://context7/project-management/workflow` - workflow best practices
20
+
21
+ **Why This is Required:**
22
+ - Ensures adherence to current industry standards and best practices
23
+ - Prevents outdated or incorrect implementation patterns
24
+ - Provides access to latest framework/tool documentation
25
+ - Reduces errors from stale knowledge or assumptions
26
+
27
+
11
28
  - DO NOT print any other comments.
@@ -11,6 +11,23 @@ Analyze an issue to identify parallel work streams for maximum efficiency.
11
11
  /pm:issue-analyze <issue_number>
12
12
  ```
13
13
 
14
+ ## Required Documentation Access
15
+
16
+ **MANDATORY:** Before analyzing issues, query Context7 for best practices:
17
+
18
+ **Documentation Queries:**
19
+ - `mcp://context7/agile/issue-analysis` - Issue analysis and breakdown patterns
20
+ - `mcp://context7/agile/parallel-work` - Parallel work stream identification
21
+ - `mcp://context7/project-management/task-dependencies` - Dependency analysis
22
+ - `mcp://context7/agile/estimation` - Effort estimation techniques
23
+ - `mcp://context7/collaboration/conflict-resolution` - File conflict detection
24
+
25
+ **Why This is Required:**
26
+ - Ensures accurate parallel work stream identification
27
+ - Applies proven patterns for conflict risk assessment
28
+ - Validates dependency analysis against best practices
29
+ - Prevents inefficient parallelization strategies
30
+
14
31
  ## Quick Check
15
32
 
16
33
  1. **Find local task file:**
@@ -11,6 +11,23 @@ Mark an issue as complete and close it on GitHub.
11
11
  /pm:issue-close <issue_number> [completion_notes]
12
12
  ```
13
13
 
14
+ ## Required Documentation Access
15
+
16
+ **MANDATORY:** Before project management workflows, query Context7 for best practices:
17
+
18
+ **Documentation Queries:**
19
+ - `mcp://context7/agile/epic-management` - epic management best practices
20
+ - `mcp://context7/project-management/issue-tracking` - issue tracking best practices
21
+ - `mcp://context7/agile/task-breakdown` - task breakdown best practices
22
+ - `mcp://context7/project-management/workflow` - workflow best practices
23
+
24
+ **Why This is Required:**
25
+ - Ensures adherence to current industry standards and best practices
26
+ - Prevents outdated or incorrect implementation patterns
27
+ - Provides access to latest framework/tool documentation
28
+ - Reduces errors from stale knowledge or assumptions
29
+
30
+
14
31
  ## Instructions
15
32
 
16
33
  ### 1. Find Local Task File
@@ -11,6 +11,23 @@ Edit issue details locally and on GitHub.
11
11
  /pm:issue-edit <issue_number>
12
12
  ```
13
13
 
14
+ ## Required Documentation Access
15
+
16
+ **MANDATORY:** Before project management workflows, query Context7 for best practices:
17
+
18
+ **Documentation Queries:**
19
+ - `mcp://context7/agile/epic-management` - epic management best practices
20
+ - `mcp://context7/project-management/issue-tracking` - issue tracking best practices
21
+ - `mcp://context7/agile/task-breakdown` - task breakdown best practices
22
+ - `mcp://context7/project-management/workflow` - workflow best practices
23
+
24
+ **Why This is Required:**
25
+ - Ensures adherence to current industry standards and best practices
26
+ - Prevents outdated or incorrect implementation patterns
27
+ - Provides access to latest framework/tool documentation
28
+ - Reduces errors from stale knowledge or assumptions
29
+
30
+
14
31
  ## Instructions
15
32
 
16
33
  ### 1. Get Current Issue State
@@ -11,6 +11,23 @@ Reopen a closed issue.
11
11
  /pm:issue-reopen <issue_number> [reason]
12
12
  ```
13
13
 
14
+ ## Required Documentation Access
15
+
16
+ **MANDATORY:** Before project management workflows, query Context7 for best practices:
17
+
18
+ **Documentation Queries:**
19
+ - `mcp://context7/agile/epic-management` - epic management best practices
20
+ - `mcp://context7/project-management/issue-tracking` - issue tracking best practices
21
+ - `mcp://context7/agile/task-breakdown` - task breakdown best practices
22
+ - `mcp://context7/project-management/workflow` - workflow best practices
23
+
24
+ **Why This is Required:**
25
+ - Ensures adherence to current industry standards and best practices
26
+ - Prevents outdated or incorrect implementation patterns
27
+ - Provides access to latest framework/tool documentation
28
+ - Reduces errors from stale knowledge or assumptions
29
+
30
+
14
31
  ## Instructions
15
32
 
16
33
  ### 1. Find Local Task File
@@ -11,6 +11,23 @@ Display issue and sub-issues with detailed information.
11
11
  /pm:issue-show <issue_number>
12
12
  ```
13
13
 
14
+ ## Required Documentation Access
15
+
16
+ **MANDATORY:** Before project management workflows, query Context7 for best practices:
17
+
18
+ **Documentation Queries:**
19
+ - `mcp://context7/agile/epic-management` - epic management best practices
20
+ - `mcp://context7/project-management/issue-tracking` - issue tracking best practices
21
+ - `mcp://context7/agile/task-breakdown` - task breakdown best practices
22
+ - `mcp://context7/project-management/workflow` - workflow best practices
23
+
24
+ **Why This is Required:**
25
+ - Ensures adherence to current industry standards and best practices
26
+ - Prevents outdated or incorrect implementation patterns
27
+ - Provides access to latest framework/tool documentation
28
+ - Reduces errors from stale knowledge or assumptions
29
+
30
+
14
31
  ## Instructions
15
32
 
16
33
  Run `node .claude/scripts/pm/issue-show.js $ARGUMENTS` using the Bash tool and show me the complete output.
@@ -33,6 +33,22 @@ Begin work on a GitHub issue with parallel agents based on work stream analysis.
33
33
  ` ``
34
34
  If no analysis exists and no --analyze flag, stop execution.
35
35
 
36
+ ## Required Documentation Access
37
+
38
+ **MANDATORY:** Before starting work on issues, query Context7 for best practices:
39
+
40
+ **Documentation Queries:**
41
+ - `mcp://context7/agile/issue-planning` - Issue planning and breakdown
42
+ - `mcp://context7/tdd/workflow` - Test-Driven Development workflow
43
+ - `mcp://context7/git/branching` - Git branching strategies
44
+ - `mcp://context7/collaboration/parallel-work` - Parallel development patterns
45
+
46
+ **Why This is Required:**
47
+ - Ensures work follows current TDD best practices
48
+ - Applies proven patterns for parallel development
49
+ - Validates task coordination strategies
50
+ - Prevents common pitfalls in distributed work
51
+
36
52
  ## ⚠️ TDD REMINDER - READ THIS FIRST
37
53
 
38
54
  **CRITICAL: This project follows Test-Driven Development (TDD).**
@@ -11,6 +11,23 @@ Check issue status (open/closed) and current state.
11
11
  /pm:issue-status <issue_number>
12
12
  ```
13
13
 
14
+ ## Required Documentation Access
15
+
16
+ **MANDATORY:** Before project management workflows, query Context7 for best practices:
17
+
18
+ **Documentation Queries:**
19
+ - `mcp://context7/agile/epic-management` - epic management best practices
20
+ - `mcp://context7/project-management/issue-tracking` - issue tracking best practices
21
+ - `mcp://context7/agile/task-breakdown` - task breakdown best practices
22
+ - `mcp://context7/project-management/workflow` - workflow best practices
23
+
24
+ **Why This is Required:**
25
+ - Ensures adherence to current industry standards and best practices
26
+ - Prevents outdated or incorrect implementation patterns
27
+ - Provides access to latest framework/tool documentation
28
+ - Reduces errors from stale knowledge or assumptions
29
+
30
+
14
31
  ## Instructions
15
32
 
16
33
  You are checking the current status of a GitHub issue and providing a quick status report for: **Issue #$ARGUMENTS**
@@ -11,6 +11,23 @@ Push local updates as GitHub issue comments for transparent audit trail.
11
11
  /pm:issue-sync <issue_number>
12
12
  ```
13
13
 
14
+ ## Required Documentation Access
15
+
16
+ **MANDATORY:** Before project management workflows, query Context7 for best practices:
17
+
18
+ **Documentation Queries:**
19
+ - `mcp://context7/agile/epic-management` - epic management best practices
20
+ - `mcp://context7/project-management/issue-tracking` - issue tracking best practices
21
+ - `mcp://context7/agile/task-breakdown` - task breakdown best practices
22
+ - `mcp://context7/project-management/workflow` - workflow best practices
23
+
24
+ **Why This is Required:**
25
+ - Ensures adherence to current industry standards and best practices
26
+ - Prevents outdated or incorrect implementation patterns
27
+ - Provides access to latest framework/tool documentation
28
+ - Reduces errors from stale knowledge or assumptions
29
+
30
+
14
31
  ## Quick Check
15
32
 
16
33
  ```bash
@@ -8,4 +8,21 @@ Run `node .claude/scripts/pm/next.js` using the Bash tool and show me the comple
8
8
  - DO NOT collapse.
9
9
  - DO NOT abbreviate.
10
10
  - Show ALL lines in full.
11
+ ## Required Documentation Access
12
+
13
+ **MANDATORY:** Before project management workflows, query Context7 for best practices:
14
+
15
+ **Documentation Queries:**
16
+ - `mcp://context7/agile/epic-management` - epic management best practices
17
+ - `mcp://context7/project-management/issue-tracking` - issue tracking best practices
18
+ - `mcp://context7/agile/task-breakdown` - task breakdown best practices
19
+ - `mcp://context7/project-management/workflow` - workflow best practices
20
+
21
+ **Why This is Required:**
22
+ - Ensures adherence to current industry standards and best practices
23
+ - Prevents outdated or incorrect implementation patterns
24
+ - Provides access to latest framework/tool documentation
25
+ - Reduces errors from stale knowledge or assumptions
26
+
27
+
11
28
  - DO NOT print any other comments.
@@ -11,6 +11,23 @@ Edit an existing Product Requirements Document.
11
11
  /pm:prd-edit <feature_name>
12
12
  ```
13
13
 
14
+ ## Required Documentation Access
15
+
16
+ **MANDATORY:** Before project management workflows, query Context7 for best practices:
17
+
18
+ **Documentation Queries:**
19
+ - `mcp://context7/agile/epic-management` - epic management best practices
20
+ - `mcp://context7/project-management/issue-tracking` - issue tracking best practices
21
+ - `mcp://context7/agile/task-breakdown` - task breakdown best practices
22
+ - `mcp://context7/project-management/workflow` - workflow best practices
23
+
24
+ **Why This is Required:**
25
+ - Ensures adherence to current industry standards and best practices
26
+ - Prevents outdated or incorrect implementation patterns
27
+ - Provides access to latest framework/tool documentation
28
+ - Reduces errors from stale knowledge or assumptions
29
+
30
+
14
31
  ## Instructions
15
32
 
16
33
  ### 1. Read Current PRD
@@ -8,4 +8,21 @@ Run `node .claude/scripts/pm/prd-list.js` using the Bash tool and show me the co
8
8
  - DO NOT collapse.
9
9
  - DO NOT abbreviate.
10
10
  - Show ALL lines in full.
11
+ ## Required Documentation Access
12
+
13
+ **MANDATORY:** Before project management workflows, query Context7 for best practices:
14
+
15
+ **Documentation Queries:**
16
+ - `mcp://context7/agile/epic-management` - epic management best practices
17
+ - `mcp://context7/project-management/issue-tracking` - issue tracking best practices
18
+ - `mcp://context7/agile/task-breakdown` - task breakdown best practices
19
+ - `mcp://context7/project-management/workflow` - workflow best practices
20
+
21
+ **Why This is Required:**
22
+ - Ensures adherence to current industry standards and best practices
23
+ - Prevents outdated or incorrect implementation patterns
24
+ - Provides access to latest framework/tool documentation
25
+ - Reduces errors from stale knowledge or assumptions
26
+
27
+
11
28
  - DO NOT print any other comments.
@@ -11,6 +11,22 @@ Launch interactive brainstorming session for new product requirement document.
11
11
  /pm:prd-new <feature_name>
12
12
  ```
13
13
 
14
+ ## Required Documentation Access
15
+
16
+ **MANDATORY:** Before creating PRDs, query Context7 for best practices:
17
+
18
+ **Documentation Queries:**
19
+ - `mcp://context7/product-management/prd-templates` - PRD structure and templates
20
+ - `mcp://context7/product-management/requirements` - Requirements gathering
21
+ - `mcp://context7/agile/user-stories` - User story best practices
22
+ - `mcp://context7/product-management/success-metrics` - Defining success criteria
23
+
24
+ **Why This is Required:**
25
+ - Ensures PRDs follow industry-standard formats
26
+ - Applies proven requirements gathering techniques
27
+ - Validates completeness of product specifications
28
+ - Prevents missing critical sections (acceptance criteria, success metrics, etc.)
29
+
14
30
  ## Instructions
15
31
 
16
32
  Run `node .claude/scripts/pm/prd-new.js $ARGUMENTS` using the Bash tool and show me the complete output.
@@ -11,6 +11,23 @@ Convert PRD to technical implementation epic.
11
11
  /pm:prd-parse <feature_name>
12
12
  ```
13
13
 
14
+ ## Required Documentation Access
15
+
16
+ **MANDATORY:** Before converting PRDs to epics, query Context7 for best practices:
17
+
18
+ **Documentation Queries:**
19
+ - `mcp://context7/product-management/prd-to-epic` - PRD to epic conversion patterns
20
+ - `mcp://context7/agile/epic-structure` - Epic structure and organization
21
+ - `mcp://context7/architecture/technical-design` - Technical architecture decisions
22
+ - `mcp://context7/project-management/task-breakdown` - Task breakdown strategies
23
+ - `mcp://context7/agile/estimation` - Effort estimation and timeline planning
24
+
25
+ **Why This is Required:**
26
+ - Ensures proper PRD-to-epic translation following industry standards
27
+ - Applies proven architecture decision frameworks
28
+ - Validates task breakdown completeness and accuracy
29
+ - Prevents missing critical technical considerations
30
+
14
31
  ## Instructions
15
32
 
16
33
  Run `node .claude/scripts/pm/prd-parse.js $ARGUMENTS` using the Bash tool and show me the complete output.
@@ -8,4 +8,21 @@ Run `node .claude/scripts/pm/prd-status.js` using the Bash tool and show me the
8
8
  - DO NOT collapse.
9
9
  - DO NOT abbreviate.
10
10
  - Show ALL lines in full.
11
+ ## Required Documentation Access
12
+
13
+ **MANDATORY:** Before project management workflows, query Context7 for best practices:
14
+
15
+ **Documentation Queries:**
16
+ - `mcp://context7/agile/epic-management` - epic management best practices
17
+ - `mcp://context7/project-management/issue-tracking` - issue tracking best practices
18
+ - `mcp://context7/agile/task-breakdown` - task breakdown best practices
19
+ - `mcp://context7/project-management/workflow` - workflow best practices
20
+
21
+ **Why This is Required:**
22
+ - Ensures adherence to current industry standards and best practices
23
+ - Prevents outdated or incorrect implementation patterns
24
+ - Provides access to latest framework/tool documentation
25
+ - Reduces errors from stale knowledge or assumptions
26
+
27
+
11
28
  - DO NOT print any other comments.
@@ -8,4 +8,21 @@ Run `node .claude/scripts/pm/search.js $ARGUMENTS` using the Bash tool and show
8
8
  - DO NOT collapse.
9
9
  - DO NOT abbreviate.
10
10
  - Show ALL lines in full.
11
+ ## Required Documentation Access
12
+
13
+ **MANDATORY:** Before project management workflows, query Context7 for best practices:
14
+
15
+ **Documentation Queries:**
16
+ - `mcp://context7/agile/epic-management` - epic management best practices
17
+ - `mcp://context7/project-management/issue-tracking` - issue tracking best practices
18
+ - `mcp://context7/agile/task-breakdown` - task breakdown best practices
19
+ - `mcp://context7/project-management/workflow` - workflow best practices
20
+
21
+ **Why This is Required:**
22
+ - Ensures adherence to current industry standards and best practices
23
+ - Prevents outdated or incorrect implementation patterns
24
+ - Provides access to latest framework/tool documentation
25
+ - Reduces errors from stale knowledge or assumptions
26
+
27
+
11
28
  - DO NOT print any other comments.
@@ -8,4 +8,21 @@ Run `node .claude/scripts/pm/standup.js` using the Bash tool and show me the com
8
8
  - DO NOT collapse.
9
9
  - DO NOT abbreviate.
10
10
  - Show ALL lines in full.
11
+ ## Required Documentation Access
12
+
13
+ **MANDATORY:** Before project management workflows, query Context7 for best practices:
14
+
15
+ **Documentation Queries:**
16
+ - `mcp://context7/agile/epic-management` - epic management best practices
17
+ - `mcp://context7/project-management/issue-tracking` - issue tracking best practices
18
+ - `mcp://context7/agile/task-breakdown` - task breakdown best practices
19
+ - `mcp://context7/project-management/workflow` - workflow best practices
20
+
21
+ **Why This is Required:**
22
+ - Ensures adherence to current industry standards and best practices
23
+ - Prevents outdated or incorrect implementation patterns
24
+ - Provides access to latest framework/tool documentation
25
+ - Reduces errors from stale knowledge or assumptions
26
+
27
+
11
28
  - DO NOT print any other comments.
@@ -8,4 +8,21 @@ Run `node .claude/scripts/pm/status.js` using the Bash tool and show me the comp
8
8
  - DO NOT collapse.
9
9
  - DO NOT abbreviate.
10
10
  - Show ALL lines in full.
11
+ ## Required Documentation Access
12
+
13
+ **MANDATORY:** Before project management workflows, query Context7 for best practices:
14
+
15
+ **Documentation Queries:**
16
+ - `mcp://context7/agile/epic-management` - epic management best practices
17
+ - `mcp://context7/project-management/issue-tracking` - issue tracking best practices
18
+ - `mcp://context7/agile/task-breakdown` - task breakdown best practices
19
+ - `mcp://context7/project-management/workflow` - workflow best practices
20
+
21
+ **Why This is Required:**
22
+ - Ensures adherence to current industry standards and best practices
23
+ - Prevents outdated or incorrect implementation patterns
24
+ - Provides access to latest framework/tool documentation
25
+ - Reduces errors from stale knowledge or assumptions
26
+
27
+
11
28
  - DO NOT print any other comments.
@@ -13,6 +13,23 @@ Full bidirectional sync between local and GitHub.
13
13
 
14
14
  If epic_name provided, sync only that epic. Otherwise sync all.
15
15
 
16
+ ## Required Documentation Access
17
+
18
+ **MANDATORY:** Before project management workflows, query Context7 for best practices:
19
+
20
+ **Documentation Queries:**
21
+ - `mcp://context7/agile/epic-management` - epic management best practices
22
+ - `mcp://context7/project-management/issue-tracking` - issue tracking best practices
23
+ - `mcp://context7/agile/task-breakdown` - task breakdown best practices
24
+ - `mcp://context7/project-management/workflow` - workflow best practices
25
+
26
+ **Why This is Required:**
27
+ - Ensures adherence to current industry standards and best practices
28
+ - Prevents outdated or incorrect implementation patterns
29
+ - Provides access to latest framework/tool documentation
30
+ - Reduces errors from stale knowledge or assumptions
31
+
32
+
16
33
  ## Instructions
17
34
 
18
35
  ### 1. Pull from GitHub
@@ -11,6 +11,23 @@ Test the task reference update logic used in epic-sync.
11
11
  /pm:test-reference-update
12
12
  ```
13
13
 
14
+ ## Required Documentation Access
15
+
16
+ **MANDATORY:** Before project management workflows, query Context7 for best practices:
17
+
18
+ **Documentation Queries:**
19
+ - `mcp://context7/agile/epic-management` - epic management best practices
20
+ - `mcp://context7/project-management/issue-tracking` - issue tracking best practices
21
+ - `mcp://context7/agile/task-breakdown` - task breakdown best practices
22
+ - `mcp://context7/project-management/workflow` - workflow best practices
23
+
24
+ **Why This is Required:**
25
+ - Ensures adherence to current industry standards and best practices
26
+ - Prevents outdated or incorrect implementation patterns
27
+ - Provides access to latest framework/tool documentation
28
+ - Reduces errors from stale knowledge or assumptions
29
+
30
+
14
31
  ## Instructions
15
32
 
16
33
  ### 1. Create Test Files