claude-autopm 3.1.0 → 3.1.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.
package/package.json
CHANGED
|
@@ -6,6 +6,11 @@ allowed-tools: Bash, Read, Write, LS, Task
|
|
|
6
6
|
|
|
7
7
|
Break epic into concrete, actionable tasks.
|
|
8
8
|
|
|
9
|
+
**⚠️ IMPORTANT**: This is a Claude Code command file, not a standalone script.
|
|
10
|
+
- Execute via Claude Code as: `/pm:epic-decompose <feature_name>`
|
|
11
|
+
- Do NOT run as: `node .claude/scripts/pm/epic-decompose.js`
|
|
12
|
+
- This command has no standalone script equivalent
|
|
13
|
+
|
|
9
14
|
## Usage
|
|
10
15
|
|
|
11
16
|
**Single Epic:**
|
|
@@ -24,14 +24,10 @@ Begin work on a GitHub issue with parallel agents based on work stream analysis.
|
|
|
24
24
|
- If not found, search for file containing `github:.*issues/$ARGUMENTS` in frontmatter (old naming)
|
|
25
25
|
- If not found: "❌ No local task for issue #$ARGUMENTS. This issue may have been created outside the PM system."
|
|
26
26
|
|
|
27
|
-
3. **Check for analysis:**
|
|
28
|
-
`
|
|
29
|
-
|
|
30
|
-
|
|
31
|
-
Run: /pm:issue-analyze $ARGUMENTS first
|
|
32
|
-
Or: /pm:issue-start $ARGUMENTS --analyze to do both"
|
|
33
|
-
` ``
|
|
34
|
-
If no analysis exists and no --analyze flag, stop execution.
|
|
27
|
+
3. **Check for analysis (when NOT using --analyze flag):**
|
|
28
|
+
- If user didn't use `--analyze` flag, check if analysis file exists
|
|
29
|
+
- Analysis file location: `.claude/epics/{epic_name}/$ARGUMENTS-analysis.md`
|
|
30
|
+
- If no analysis AND no `--analyze` flag: Stop and suggest using `--analyze` flag
|
|
35
31
|
|
|
36
32
|
## Required Documentation Access
|
|
37
33
|
|
|
@@ -71,7 +67,25 @@ See `.claude/rules/tdd.enforcement.md` for complete TDD requirements.
|
|
|
71
67
|
|
|
72
68
|
## Instructions
|
|
73
69
|
|
|
74
|
-
###
|
|
70
|
+
### 0. Handle --analyze Flag (if provided)
|
|
71
|
+
|
|
72
|
+
If user provided `--analyze` flag, delegate to the Node.js script:
|
|
73
|
+
` ``bash
|
|
74
|
+
node packages/plugin-pm/scripts/pm/issue-start.cjs $ARGUMENTS --analyze
|
|
75
|
+
` ``
|
|
76
|
+
|
|
77
|
+
This script will:
|
|
78
|
+
1. Find the task file for the issue
|
|
79
|
+
2. Generate analysis file with parallel work streams
|
|
80
|
+
3. Create workspace structure
|
|
81
|
+
4. Launch parallel agents based on analysis
|
|
82
|
+
5. Handle all subsequent steps automatically
|
|
83
|
+
|
|
84
|
+
**STOP HERE** if using `--analyze` flag - the script handles everything.
|
|
85
|
+
|
|
86
|
+
---
|
|
87
|
+
|
|
88
|
+
### 1. Ensure Branch Exists (Non-analyze workflow)
|
|
75
89
|
|
|
76
90
|
Check if epic branch exists:
|
|
77
91
|
` ``bash
|