@e0ipso/ai-task-manager 1.18.4 → 1.18.5

package/package.json

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

package/templates/ai-task-manager/config/scripts/set-approval-method.cjs

@@ -0,0 +1,90 @@
+#!/usr/bin/env node
+
+const fs = require('fs');
+const path = require('path');
+
+/**
+ * Update or add approval_method field in a plan file's YAML frontmatter
+ * @param {string} filePath - Path to the plan file
+ * @param {string} approvalMethod - Approval method value ('auto' or 'manual')
+ * @returns {boolean} True if successful, false otherwise
+ */
+function setApprovalMethod(filePath, approvalMethod) {
+  // Validate inputs
+  if (!filePath) {
+    throw new Error('File path is required');
+  }
+
+  if (!approvalMethod || !['auto', 'manual'].includes(approvalMethod)) {
+    throw new Error('Approval method must be "auto" or "manual"');
+  }
+
+  // Check file exists
+  if (!fs.existsSync(filePath)) {
+    throw new Error(`File not found: ${filePath}`);
+  }
+
+  // Read file content
+  const content = fs.readFileSync(filePath, 'utf8');
+
+  // Parse frontmatter - handle both empty and non-empty frontmatter
+  const frontmatterRegex = /^---\r?\n([\s\S]*?)\r?\n---(?:\r?\n([\s\S]*))?$/;
+  const match = content.match(frontmatterRegex);
+
+  if (!match) {
+    throw new Error('No frontmatter found in file');
+  }
+
+  const frontmatterContent = match[1] || '';
+  const bodyContent = match[2] || '';
+  const frontmatterLines = frontmatterContent ? frontmatterContent.split('\n') : [];
+
+  // Update or add approval_method field
+  let approvalMethodFound = false;
+  const updatedFrontmatter = frontmatterLines.map(line => {
+    const trimmed = line.trim();
+    if (trimmed.startsWith('approval_method:')) {
+      approvalMethodFound = true;
+      return `approval_method: ${approvalMethod}`;
+    }
+    return line;
+  });
+
+  // Add approval_method if not found
+  if (!approvalMethodFound) {
+    updatedFrontmatter.push(`approval_method: ${approvalMethod}`);
+  }
+
+  // Reconstruct file
+  const updated = '---\n' + updatedFrontmatter.join('\n') + '\n---\n' + bodyContent;
+
+  // Write back to file
+  fs.writeFileSync(filePath, updated, 'utf8');
+
+  return true;
+}
+
+// Main execution with error handling
+try {
+  const args = process.argv.slice(2);
+
+  if (args.length < 2) {
+    console.error('Usage: set-approval-method.cjs <file-path> <approval-method>');
+    console.error('  file-path: Path to the plan file');
+    console.error('  approval-method: "auto" or "manual"');
+    process.exit(1);
+  }
+
+  const [filePath, approvalMethod] = args;
+
+  // Resolve relative paths
+  const resolvedPath = path.isAbsolute(filePath) ? filePath : path.resolve(process.cwd(), filePath);
+
+  setApprovalMethod(resolvedPath, approvalMethod);
+
+  console.log(`✓ Successfully set approval_method to "${approvalMethod}" in ${path.basename(resolvedPath)}`);
+  process.exit(0);
+} catch (error) {
+  console.error(`✗ Error: ${error.message}`);
+  process.exit(1);
+}

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

@@ -42,13 +42,15 @@ Use your internal Todo task tool to track the workflow execution:
 
 #### Step 1: Determine Next Plan ID
 
-Before creating the plan, determine what the next plan ID will be:
+Before creating the plan, determine what the next plan ID will be and store it persistently:
 
 ```bash
-node .ai/task-manager/config/scripts/get-next-plan-id.cjs
+PLAN_ID=$(node .ai/task-manager/config/scripts/get-next-plan-id.cjs)
+echo "$PLAN_ID" > /tmp/full-workflow-plan-id-$$.txt
+echo "Next plan ID: $PLAN_ID"
 ```
 
-Store this ID for later validation and use.
+This stores the plan ID in a temporary file that persists across all workflow steps.
 
 #### Step 2: Execute Plan Creation
 
@@ -60,8 +62,12 @@ Use the SlashCommand tool to execute plan creation with the user's prompt:
 
 **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])"
+After plan creation completes, retrieve the plan ID and provide a progress update:
+
+```bash
+PLAN_ID=$(cat /tmp/full-workflow-plan-id-$$.txt)
+echo "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.
 
@@ -70,46 +76,55 @@ After plan creation completes, provide minimal progress update:
 Verify the plan was created successfully and set it to automated workflow mode:
 
 ```bash
+# Retrieve the plan ID from temp file
+PLAN_ID=$(cat /tmp/full-workflow-plan-id-$$.txt)
+
 # 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]$" {} \;)
+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."
+  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
+node .ai/task-manager/config/scripts/set-approval-method.cjs "$PLAN_FILE" auto
 ```
 
 **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:
+Retrieve the plan ID and use the SlashCommand tool to generate tasks:
 
+```bash
+PLAN_ID=$(cat /tmp/full-workflow-plan-id-$$.txt)
+echo "Generating tasks for plan $PLAN_ID"
 ```
-/tasks:generate-tasks [plan-id]
+
+Now use the SlashCommand tool with the plan ID from above:
+
+```
+/tasks:generate-tasks [plan-id-from-above]
 ```
 
-After task generation completes, provide minimal progress update:
-"Step 2/4: Tasks generated for plan [plan-id]"
+After task generation completes, provide minimal progress update referencing the plan ID.
 
 #### Step 5: Execute Blueprint
 
-Use the SlashCommand tool to execute the blueprint:
+Retrieve the plan ID and use the SlashCommand tool to execute the blueprint:
 
+```bash
+PLAN_ID=$(cat /tmp/full-workflow-plan-id-$$.txt)
+echo "Executing blueprint for plan $PLAN_ID"
 ```
-/tasks:execute-blueprint [plan-id]
+
+Now use the SlashCommand tool with the plan ID from above:
+
+```
+/tasks:execute-blueprint [plan-id-from-above]
 ```
 
 After blueprint execution completes, provide minimal progress update:
@@ -119,22 +134,29 @@ Note: The execute-blueprint command automatically archives the plan upon success
 
 #### Step 6: Generate Execution Summary
 
-After all steps complete successfully, generate a comprehensive summary:
-
-```
-✅ Full workflow completed successfully!
+After all steps complete successfully, retrieve the plan details and generate a summary:
 
-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
+```bash
+PLAN_ID=$(cat /tmp/full-workflow-plan-id-$$.txt)
+PLAN_DIR=$(find .ai/task-manager/archive -type d -name "${PLAN_ID}--*" 2>/dev/null | head -n 1)
+PLAN_NAME=$(basename "$PLAN_DIR")
+
+echo "✅ Full workflow completed successfully!"
+echo ""
+echo "Plan: $PLAN_NAME"
+echo "Location: .ai/task-manager/archive/$PLAN_NAME/"
+echo ""
+echo "Status: Archived and ready for review"
+echo ""
+echo "📋 Next Steps:"
+echo "- Review the implementation in the archived plan"
+echo "- Check the execution summary in the plan document"
+echo "- Verify all validation gates passed"
+echo ""
+echo "Plan document: .ai/task-manager/archive/$PLAN_NAME/plan-$PLAN_NAME.md"
+
+# Clean up temp file
+rm -f /tmp/full-workflow-plan-id-$$.txt
 ```
 
 ### Error Handling
@@ -143,10 +165,12 @@ 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:
+4. Read the plan ID from temp file if needed: `cat /tmp/full-workflow-plan-id-$$.txt`
+5. 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
+6. Clean up temp file: `rm -f /tmp/full-workflow-plan-id-$$.txt`
 
 ### Output Requirements