@e0ipso/ai-task-manager 1.18.4 → 1.18.6

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@e0ipso/ai-task-manager",
-  "version": "1.18.4",
+  "version": "1.18.6",
   "description": "Task management for AI coding assistants",
   "main": "dist/index.js",
   "bin": {

package/templates/ai-task-manager/config/templates/PLAN_TEMPLATE.md

@@ -2,7 +2,8 @@
 id: [PLAN-ID]
 summary: "[Brief one-line description of what this plan accomplishes]"
 created: [YYYY-MM-DD]
-approval_method: [auto|manual]  # Optional: Workflow approval mode (auto=automated, manual=requires review)
+approval_method_plan: [auto|manual]  # Workflow approval for plan review (default: manual)
+approval_method_tasks: [auto|manual]  # Workflow approval for task generation review (default: manual)
 ---
 
 # Plan: [Descriptive Plan Title]

package/templates/assistant/commands/tasks/create-plan.md

@@ -88,14 +88,18 @@ Structure your response as follows:
 - If context is insufficient: List specific clarifying questions
 - If context is sufficient: Provide the comprehensive plan using the structure above. Use the information in @TASK_MANAGER.md for the directory structure and additional information about plans.
 
-**Output Behavior:**
+**Output Behavior: CRITICAL - Structured Output for Command Coordination**
 
-Be extremely concise but helpful:
-- Tell the user that you are done
-- Instruct them to review the plan document with the file path
-- Example output: "Plan created. Please review: `.ai/task-manager/plans/40--plan-name/plan-40--plan-name.md`"
+Always end your output with a standardized summary in this exact format:
 
-**Note:** When this command is invoked by the full-workflow command, the full-workflow will modify the plan's `approval_method` field after creation to enable automated execution.
+```
+---
+Plan Summary:
+- Plan ID: [numeric-id]
+- Plan File: [full-path-to-plan-file]
+```
+
+This structured output enables automated workflow coordination and must be included even when running standalone.
 
 ###### Plan Template
 
@@ -114,11 +118,12 @@ Example:
 id: 1
 summary: "Implement a comprehensive CI/CD pipeline using GitHub Actions for automated linting, testing, semantic versioning, and NPM publishing"
 created: 2025-09-01
-approval_method: "manual"
+approval_method_plan: "manual"
+approval_method_tasks: "manual"
 ---
 ```
 
-**Important**: Always set `approval_method` to "manual" when creating a plan. The full-workflow command will modify this field to "auto" after creation if running in automated mode.
+**Important**: Always set both `approval_method_plan` and `approval_method_tasks` to "manual" when creating a plan. The full-workflow command will modify these fields to "auto" after creation if running in automated mode.
 
 The schema for this frontmatter is:
 ```json
@@ -139,10 +144,15 @@ The schema for this frontmatter is:
       "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
       "description": "Creation date in YYYY-MM-DD format"
     },
-    "approval_method": {
+    "approval_method_plan": {
+      "type": "string",
+      "enum": ["auto", "manual"],
+      "description": "Workflow approval mode for plan review: auto for automated workflows, manual for standalone execution"
+    },
+    "approval_method_tasks": {
       "type": "string",
       "enum": ["auto", "manual"],
-      "description": "Workflow approval mode: auto for automated workflows, manual for standalone execution"
+      "description": "Workflow approval mode for task generation review: auto when tasks auto-generated in workflow, manual for standalone execution"
     }
   },
   "additionalProperties": false

package/templates/assistant/commands/tasks/execute-blueprint.md

@@ -71,7 +71,12 @@ If either `$TASK_COUNT` is 0 or `$BLUEPRINT_EXISTS` is "no":
    ```
    /tasks:generate-tasks $1
    ```
-   - **CRITICAL**: After task generation completes successfully, you MUST immediately proceed with blueprint execution without waiting for user input. The workflow should continue seamlessly.
+   - **NEW STEP**: Immediately after task generation succeeds, set the approval_method_tasks field to auto:
+     ```bash
+     node .ai/task-manager/config/scripts/set-approval-method.cjs "$PLAN_FILE" auto tasks
+     ```
+   - This signals that tasks were auto-generated in workflow context and execution should continue without pause.
+   - **CRITICAL**: After setting the field, you MUST immediately proceed with blueprint execution without waiting for user input. The workflow should continue seamlessly.
    - If generation fails: Halt execution with clear error message:
      ```
      ❌ Error: Automatic task generation failed.
@@ -146,33 +151,57 @@ Read and execute .ai/task-manager/config/hooks/POST_ERROR_DETECTION.md
 
 **Extract approval method from plan metadata:**
 
-First, extract the approval_method from the plan document:
+First, extract both approval method fields from the plan document:
 
 ```bash
 # Find plan file by ID
 PLAN_FILE=$(find .ai/task-manager/{plans,archive} -name "plan-$1--*.md" -type f -exec grep -l "^id: \?$1$" {} \;)
 
-# Extract approval_method from YAML frontmatter
-APPROVAL_METHOD=$(sed -n '/^---$/,/^---$/p' "$PLAN_FILE" | grep '^approval_method:' | sed 's/approval_method: *//;s/"//g;s/'"'"'//g' | tr -d ' ')
+# Extract both approval method fields from YAML frontmatter
+APPROVAL_METHOD_PLAN=$(sed -n '/^---$/,/^---$/p' "$PLAN_FILE" | grep '^approval_method_plan:' | sed 's/approval_method_plan: *//;s/"//g' | tr -d " '")
+APPROVAL_METHOD_TASKS=$(sed -n '/^---$/,/^---$/p' "$PLAN_FILE" | grep '^approval_method_tasks:' | sed 's/approval_method_tasks: *//;s/"//g' | tr -d " '")
 
-# Default to "manual" if field doesn't exist (backward compatibility)
-APPROVAL_METHOD=${APPROVAL_METHOD:-manual}
+# Defaults to "manual" if fields don't exist
+APPROVAL_METHOD_PLAN=${APPROVAL_METHOD_PLAN:-manual}
+APPROVAL_METHOD_TASKS=${APPROVAL_METHOD_TASKS:-manual}
 ```
 
-Then adjust output based on the extracted approval method:
+Then adjust output based on the extracted approval methods:
 
-- **If `APPROVAL_METHOD="auto"` (automated workflow mode)**:
-  - Provide minimal progress updates at phase boundaries
-  - Do NOT instruct user to review implementation details
+- **If `APPROVAL_METHOD_PLAN="auto"` (automated workflow mode)**:
+  - During task auto-generation phase: Provide minimal progress updates
+  - Do NOT instruct user to review the plan or tasks being generated
   - Do NOT add any prompts that would pause execution
+
+- **If `APPROVAL_METHOD_TASKS="auto"` (tasks auto-generated in workflow)**:
+  - During task execution phase: Provide minimal progress updates at phase boundaries
+  - Do NOT instruct user to review implementation details
   - Example output: "Phase 1/3 completed. Proceeding to Phase 2."
 
-- **If `APPROVAL_METHOD="manual"` or empty (standalone mode)**:
+- **If `APPROVAL_METHOD_PLAN="manual"` or `APPROVAL_METHOD_TASKS="manual"` (standalone mode)**:
   - Provide detailed execution summary with phase results
   - List completed tasks and any noteworthy events
   - Instruct user to review the execution summary in the plan document
   - Example output: "Execution completed. Review summary: `.ai/task-manager/archive/[plan]/plan-[id].md`"
 
+**Note**: This command respects both approval method fields:
+- `approval_method_plan`: Used during auto-generation to determine if we're in automated workflow
+- `approval_method_tasks`: Used during execution to determine output verbosity
+
+**CRITICAL - Structured Output for Command Coordination:**
+
+Always end your output with a standardized summary in this exact format:
+
+```
+---
+Execution Summary:
+- Plan ID: [numeric-id]
+- Status: Archived
+- Location: .ai/task-manager/archive/[plan-id]--[plan-name]/
+```
+
+This structured output enables automated workflow coordination and must be included even when running standalone.
+
 ## Optimization Guidelines
 
 - **Maximize parallelism**: Always run all available tasks in a phase simultaneously

package/templates/assistant/commands/tasks/generate-tasks.md

@@ -306,23 +306,37 @@ First, extract the approval_method from the plan document:
 # Find plan file by ID
 PLAN_FILE=$(find .ai/task-manager/{plans,archive} -name "plan-$1--*.md" -type f -exec grep -l "^id: \?$1$" {} \;)
 
-# Extract approval_method from YAML frontmatter
-APPROVAL_METHOD=$(sed -n '/^---$/,/^---$/p' "$PLAN_FILE" | grep '^approval_method:' | sed 's/approval_method: *//;s/"//g;s/'"'"'//g' | tr -d ' ')
+# Extract approval_method_tasks from YAML frontmatter
+APPROVAL_METHOD_TASKS=$(sed -n '/^---$/,/^---$/p' "$PLAN_FILE" | grep '^approval_method_tasks:' | sed 's/approval_method_tasks: *//;s/"//g' | tr -d " '")
 
 # Default to "manual" if field doesn't exist (backward compatibility)
-APPROVAL_METHOD=${APPROVAL_METHOD:-manual}
+APPROVAL_METHOD_TASKS=${APPROVAL_METHOD_TASKS:-manual}
 ```
 
 Then adjust output based on the extracted approval method:
 
-- **If `APPROVAL_METHOD="auto"` (automated workflow mode)**:
+- **If `APPROVAL_METHOD_TASKS="auto"` (automated workflow mode)**:
   - Simply confirm task generation with task count
   - Do NOT instruct user to review the tasks
   - Do NOT add any prompts that would pause execution
   - Example output: "Tasks generated for plan [id]: [count] tasks created"
 
-- **If `APPROVAL_METHOD="manual"` or empty (standalone mode)**:
+- **If `APPROVAL_METHOD_TASKS="manual"` or empty (standalone mode)**:
   - Be concise but helpful
   - Tell the user that you are done
   - Instruct them to review the tasks with file paths
   - Example output: "Task generation complete. Review tasks in: `.ai/task-manager/plans/[plan-id]--[name]/tasks/`"
+
+**CRITICAL - Structured Output for Command Coordination:**
+
+Always end your output with a standardized summary in this exact format:
+
+```
+---
+Task Generation Summary:
+- Plan ID: [numeric-id]
+- Tasks: [count]
+- Status: Ready for execution
+```
+
+This structured output enables automated workflow coordination and must be included even when running standalone.

package/templates/assistant/commands/tasks/full-workflow.md

@@ -1,166 +0,0 @@
----
-argument-hint: [user-prompt]
-description: Execute the full workflow from plan creation to blueprint execution
----
-# Full Workflow Execution
-
-## Assistant Configuration
-
-Before proceeding with this command, you MUST load and respect the assistant's configuration:
-
-**Run the following scripts:**
-```bash
-ASSISTANT=$(node .ai/task-manager/config/scripts/detect-assistant.cjs)
-node .ai/task-manager/config/scripts/read-assistant-config.cjs "$ASSISTANT"
-```
-
-The output above contains your global and project-level configuration rules. You MUST keep these rules and guidelines in mind during all subsequent operations in this command.
-
----
-
-You are a workflow orchestration assistant. Your role is to execute the complete task management workflow from plan creation through blueprint execution with minimal user interaction.
-
-## Instructions
-
-The user input is:
-
-<user-input>
-$ARGUMENTS
-</user-input>
-
-If no user input is provided, stop immediately and show an error message to the user.
-
-### Workflow Execution Process
-
-Use your internal Todo task tool to track the workflow execution:
-
-- [ ] Execute /tasks:create-plan
-- [ ] Extract plan ID
-- [ ] Execute /tasks:generate-tasks
-- [ ] Execute /tasks:execute-blueprint
-- [ ] Generate execution summary
-
-#### Step 1: Determine Next Plan ID
-
-Before creating the plan, determine what the next plan ID will be:
-
-```bash
-node .ai/task-manager/config/scripts/get-next-plan-id.cjs
-```
-
-Store this ID for later validation and use.
-
-#### Step 2: Execute Plan Creation
-
-Use the SlashCommand tool to execute plan creation with the user's prompt:
-
-```
-/tasks:create-plan $ARGUMENTS
-```
-
-**Important**: The plan creation command may ask clarification questions. Wait for user responses before continuing. This is expected behavior and maintains quality control.
-
-After plan creation completes, provide minimal progress update:
-"Step 1/4: Plan created (ID: [plan-id])"
-
-**CRITICAL**: Do not wait for user approval or review of the plan. In full-workflow mode, plan validation is automated (Step 3 performs file existence checking only). Proceed immediately to Step 3 without waiting for user input.
-
-#### Step 3: Validate Plan Creation and Set Approval Method
-
-Verify the plan was created successfully and set it to automated workflow mode:
-
-```bash
-# Find the created plan file
-PLAN_FILE=$(find .ai/task-manager/plans -name "plan-[0-9][0-9]*--*.md" -type f -exec grep -l "^id: \?[plan-id]$" {} \;)
-
-# Verify plan exists
-if [ -z "$PLAN_FILE" ]; then
-  echo "❌ Error: Plan creation failed. Expected plan with ID [plan-id] not found."
-  exit 1
-fi
-
-# Set approval_method to auto for automated workflow execution
-# This ensures generate-tasks and execute-blueprint run without interruption
-if ! grep -q "^approval_method:" "$PLAN_FILE"; then
-  # Insert approval_method after the created: line in frontmatter
-  sed -i.bak '/^created:/a\
-approval_method: auto' "$PLAN_FILE" && rm -f "${PLAN_FILE}.bak"
-else
-  # Update existing approval_method to auto
-  sed -i.bak 's/^approval_method:.*/approval_method: auto/' "$PLAN_FILE" && rm -f "${PLAN_FILE}.bak"
-fi
-```
-
-**Note**: Setting `approval_method: auto` in the plan metadata signals to subordinate commands (generate-tasks, execute-blueprint) that they are running in automated workflow mode and should suppress interactive prompts for plan review. This metadata persists in the plan document and is reliably read by subsequent commands, eliminating dependency on environment variables.
-
-#### Step 4: Execute Task Generation
-
-Use the SlashCommand tool to generate tasks for the plan:
-
-```
-/tasks:generate-tasks [plan-id]
-```
-
-After task generation completes, provide minimal progress update:
-"Step 2/4: Tasks generated for plan [plan-id]"
-
-#### Step 5: Execute Blueprint
-
-Use the SlashCommand tool to execute the blueprint:
-
-```
-/tasks:execute-blueprint [plan-id]
-```
-
-After blueprint execution completes, provide minimal progress update:
-"Step 3/4: Blueprint execution completed"
-
-Note: The execute-blueprint command automatically archives the plan upon successful completion.
-
-#### Step 6: Generate Execution Summary
-
-After all steps complete successfully, generate a comprehensive summary:
-
-```
-✅ Full workflow completed successfully!
-
-Plan: [plan-id]--[plan-name]
-Location: .ai/task-manager/archive/[plan-id]--[plan-name]/
-
-Status: Archived and ready for review
-
-📋 Next Steps:
-- Review the implementation in the archived plan
-- Check the execution summary in the plan document
-- Verify all validation gates passed
-
-Plan document: .ai/task-manager/archive/[plan-id]--[plan-name]/plan-[plan-id]--[plan-name].md
-```
-
-### Error Handling
-
-If any step fails:
-1. Halt execution immediately
-2. Report clear error message indicating which step failed
-3. Preserve all created artifacts (plan, tasks) for manual review
-4. Provide guidance for manual continuation:
-   - If plan creation failed: Review error and retry
-   - If task generation failed: Run `/tasks:generate-tasks [plan-id]` manually after reviewing plan
-   - If blueprint execution failed: Review tasks and run `/tasks:execute-blueprint [plan-id]` manually
-
-### Output Requirements
-
-**During Execution:**
-- Minimal progress updates at each major step
-- Clear indication of current step (1/4, 2/4, etc.)
-
-**After Completion:**
-- Comprehensive summary with plan location
-- Status confirmation (Archived)
-- Next steps for user review
-- Direct link to plan document
-
-**On Error:**
-- Clear error message
-- Indication of which step failed
-- Manual recovery instructions