@e0ipso/ai-task-manager 1.17.1 → 1.18.0
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
|
@@ -34,13 +34,57 @@ You are the orchestrator responsible for executing all tasks defined in the exec
|
|
|
34
34
|
- Validation gates document: `/config/hooks/POST_PHASE.md`
|
|
35
35
|
|
|
36
36
|
### Input Error Handling
|
|
37
|
-
|
|
37
|
+
|
|
38
|
+
If the plan does not exist, stop immediately and show an error to the user.
|
|
39
|
+
|
|
40
|
+
**Note**: If tasks or the execution blueprint section are missing, they will be automatically generated before execution begins (see Task and Blueprint Validation below).
|
|
41
|
+
|
|
42
|
+
### Task and Blueprint Validation
|
|
43
|
+
|
|
44
|
+
Before proceeding with execution, validate that tasks exist and the execution blueprint has been generated. If either is missing, automatically invoke task generation.
|
|
45
|
+
|
|
46
|
+
**Validation Steps:**
|
|
47
|
+
|
|
48
|
+
1. **Locate the plan document**:
|
|
49
|
+
```bash
|
|
50
|
+
PLAN_FILE=$(find .ai/task-manager/{plans,archive} -name "plan-[0-9][0-9]*--*.md" -type f -exec grep -l "^id: \?$1$" {} \;)
|
|
51
|
+
PLAN_DIR=$(dirname "$PLAN_FILE")
|
|
52
|
+
```
|
|
53
|
+
|
|
54
|
+
2. **Check for task files**:
|
|
55
|
+
```bash
|
|
56
|
+
TASK_COUNT=$(ls "$PLAN_DIR"/tasks/*.md 2>/dev/null | wc -l)
|
|
57
|
+
```
|
|
58
|
+
|
|
59
|
+
3. **Check for execution blueprint section**:
|
|
60
|
+
```bash
|
|
61
|
+
BLUEPRINT_EXISTS=$(grep -q "^## Execution Blueprint" "$PLAN_FILE" && echo "yes" || echo "no")
|
|
62
|
+
```
|
|
63
|
+
|
|
64
|
+
4. **Automatic task generation**:
|
|
65
|
+
|
|
66
|
+
If either `$TASK_COUNT` is 0 or `$BLUEPRINT_EXISTS` is "no":
|
|
67
|
+
- Display notification to user: "⚠️ Tasks or execution blueprint not found. Generating tasks automatically..."
|
|
68
|
+
- Use the SlashCommand tool to invoke task generation:
|
|
69
|
+
```
|
|
70
|
+
/tasks:generate-tasks $1
|
|
71
|
+
```
|
|
72
|
+
- If generation fails: Halt execution with clear error message:
|
|
73
|
+
```
|
|
74
|
+
❌ Error: Automatic task generation failed.
|
|
75
|
+
|
|
76
|
+
Please run the following command manually to generate tasks:
|
|
77
|
+
/tasks:generate-tasks $1
|
|
78
|
+
```
|
|
79
|
+
|
|
80
|
+
**After successful validation or generation**, proceed with the execution process below.
|
|
38
81
|
|
|
39
82
|
## Execution Process
|
|
40
83
|
|
|
41
84
|
Use your internal Todo task tool to track the execution of all phases, and the final update of the plan with the summary. Example:
|
|
42
85
|
|
|
43
86
|
- [ ] Create feature branch from the main branch.
|
|
87
|
+
- [ ] Validate or auto-generate tasks and execution blueprint if missing.
|
|
44
88
|
- [ ] Execute .ai/task-manager/config/hooks/PRE_PHASE.md hook before Phase 1.
|
|
45
89
|
- [ ] Phase 1: Execute 1 task(s) in parallel.
|
|
46
90
|
- [ ] Execute .ai/task-manager/config/hooks/POST_PHASE.md hook after Phase 1.
|