@e0ipso/ai-task-manager 1.36.1 → 1.38.0

package/templates/ai-task-manager/config/scripts/validate-plan-blueprint.cjs

@@ -1,138 +0,0 @@
-#!/usr/bin/env node
-
-const fs = require('fs');
-const path = require('path');
-const sharedUtils = require('./shared-utils.cjs');
-const {
-  findTaskManagerRoot,
-  findPlanById,
-  countTasks,
-  checkBlueprintExists,
-  getAllPlans,
-  validatePlanFile,
-  checkStandardRootShortcut,
-  resolvePlan
-} = sharedUtils;
-
-/**
- * Error logging utility
- * @private
- * @param {string} message - Error message
- * @param {...any} args - Additional arguments to log
- */
-function _errorLog(message, ...args) {
-  console.error(`[ERROR] ${message}`, ...args);
-}
-
-/**
- * List available plans for error messaging
- * @private
- * @param {string} [taskManagerRoot] - Optional task manager root path
- * @returns {string[]} Array of plan directory names
- */
-function _listAvailablePlans(taskManagerRoot) {
-  const plans = getAllPlans(taskManagerRoot);
-  return plans
-    .map(p => p.name)
-    .sort((a, b) => {
-      const aIdMatch = a.match(/^(\d+)--/);
-      const bIdMatch = b.match(/^(\d+)--/);
-      if (!aIdMatch || !bIdMatch) return 0;
-      return parseInt(aIdMatch[1], 10) - parseInt(bIdMatch[1], 10);
-    });
-}
-
-/**
- * Validate plan blueprint and output JSON or specific field
- * @private
- * @param {string|number} inputId - Plan ID or absolute path to validate
- * @param {string} [fieldName] - Optional field name to extract (planFile, planDir, taskCount, blueprintExists, taskManagerRoot, planId)
- * @param {string} [startPath] - Optional start path for finding task manager root
- */
-function _validatePlanBlueprint(inputId, fieldName, startPath = process.cwd()) {
-  if (!inputId) {
-    _errorLog('Plan ID or absolute path is required');
-    _errorLog('');
-    _errorLog('Usage: node validate-plan-blueprint.cjs <plan-id-or-path> [field-name]');
-    _errorLog('');
-    _errorLog('Examples:');
-    _errorLog('  node validate-plan-blueprint.cjs 47                  # Output full JSON');
-    _errorLog('  node validate-plan-blueprint.cjs /path/to/plan.md    # Output full JSON for specific file');
-    _errorLog('  node validate-plan-blueprint.cjs 47 planFile         # Output just the plan file path');
-    _errorLog('  node validate-plan-blueprint.cjs 47 blueprintExists  # Output yes/no');
-    process.exit(1);
-  }
-
-  // Check if input is numeric (allowing padded zeros) - if not a number or path, it's invalid
-  const numericInput = parseInt(inputId, 10);
-  const isNumeric = !isNaN(numericInput);
-  const isAbsolutePath = inputId.startsWith('/');
-
-  if (!isNumeric && !isAbsolutePath) {
-    _errorLog(`Invalid plan ID: "${inputId}" is not a valid number`);
-    process.exit(1);
-  }
-
-  const resolved = resolvePlan(inputId, startPath);
-
-  if (!resolved) {
-    _errorLog(`Plan ID ${inputId} not found or invalid`);
-    _errorLog('');
-
-    const tmRoot = findTaskManagerRoot(startPath);
-    const availablePlans = _listAvailablePlans(tmRoot);
-    if (availablePlans.length > 0) {
-      _errorLog('Available plans:');
-      availablePlans.forEach(plan => {
-        _errorLog(`  ${plan}`);
-      });
-    }
-
-    process.exit(1);
-  }
-
-  const {
-    planFile,
-    planDir,
-    taskManagerRoot,
-    planId
-  } = resolved;
-
-  const taskCount = countTasks(planDir);
-  const blueprintExists = checkBlueprintExists(planFile);
-
-  const result = {
-    planFile,
-    planDir,
-    taskManagerRoot,
-    planId,
-    taskCount,
-    blueprintExists: blueprintExists ? 'yes' : 'no'
-  };
-
-  // If field name is provided, output just that field
-  if (fieldName) {
-    const validFields = ['planFile', 'planDir', 'taskCount', 'blueprintExists', 'taskManagerRoot', 'planId'];
-    if (!validFields.includes(fieldName)) {
-      _errorLog(`Invalid field name: ${fieldName}`);
-      _errorLog(`Valid fields: ${validFields.join(', ')}`);
-      process.exit(1);
-    }
-    // Use process.stdout.write to avoid util.inspect colorization
-    process.stdout.write(String(result[fieldName]) + '\n');
-  } else {
-    // Output full JSON
-    console.log(JSON.stringify(result, null, 2));
-  }
-}
-
-// Main execution
-if (require.main === module) {
-  const planId = process.argv[2];
-  const fieldName = process.argv[3];
-  _validatePlanBlueprint(planId, fieldName);
-}
-
-module.exports = {
-  _validatePlanBlueprint
-};

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

@@ -1,174 +0,0 @@
-<!-- Based on create-plan.md — keep in sync with changes to the original. -->
----
-argument-hint: "[userPrompt]"
-description: Create a comprehensive plan without user interaction, resolving ambiguities autonomously.
----
-# Comprehensive Plan Creation (Autonomous Mode)
-
-You are a strategic planning specialist who creates actionable plan documents that balance comprehensive context with
-disciplined scope control. Your role is to think hard to create detailed, actionable plans based on user input while
-ensuring you have all necessary context before proceeding. Use the plan-creator sub-agent for this if it is available.
-
-**AUTONOMOUS MODE**: This command runs without user interaction. You must resolve all ambiguities by inspecting the
-codebase, documentation, and project context. Do NOT ask the user any questions or wait for user input at any point.
-
----
-
-Use tools for the planning. You are encouraged to write your own specialized tools to research, analyze, and debug
-any work order from the user. You are not restricted to the stack of the current project to create your own
-specialized tools.
-
-## Find the AI Task Manager root
-
-```bash
-if [ ! -f /tmp/find-ai-task-manager-root.js ]; then
-  cat << 'EOF' > /tmp/find-ai-task-manager-root.js
-const fs = require('fs');
-const path = require('path');
-
-const findRoot = (currentDir) => {
-  const taskManagerPath = path.join(currentDir, '.ai/task-manager');
-  const metadataPath = path.join(taskManagerPath, '.init-metadata.json');
-
-  try {
-    if (fs.existsSync(metadataPath) && JSON.parse(fs.readFileSync(metadataPath, 'utf8')).version) {
-      console.log(path.resolve(taskManagerPath));
-      process.exit(0);
-    }
-  } catch (e) {
-    // Continue searching
-  }
-
-  const parentDir = path.dirname(currentDir);
-  if (parentDir.length < currentDir.length) {
-    findRoot(parentDir);
-  } else {
-    process.exit(1);
-  }
-};
-
-findRoot(process.cwd());
-EOF
-fi
-
-root=$(node /tmp/find-ai-task-manager-root.js)
-
-if [ -z "$root" ]; then
-    echo "Error: Could not find task manager root directory (.ai/task-manager)"
-    exit 1
-fi
-```
-
-## Instructions
-
-Include $root/.ai/task-manager/config/TASK_MANAGER.md for the directory structure of tasks.
-
-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.
-
-### Process Checklist
-
-Use your internal Todo task tool to track the following plan generation:
-
-- [ ] Read and execute $root/.ai/task-manager/config/hooks/PRE_PLAN.md
-- [ ] User input and context analysis
-- [ ] Autonomous clarification (resolve gaps via codebase inspection)
-- [ ] Plan generation
-- [ ] Read and execute $root/.ai/task-manager/config/hooks/POST_PLAN.md
-
-#### Step 1: Context Analysis
-Before creating any plan, analyze the user's request for:
-- **Objective**: What is the end goal?
-- **Scope**: What are the boundaries and constraints?
-- **Resources**: What tools, libraries, or infrastructure are available?
-- **Success Criteria**: How will success be measured?
-- **Dependencies**: What prerequisites or blockers exist?
-- **Technical Requirements**: What technologies or skills are needed?
-
-#### Step 2: Autonomous Clarification Phase
-If any critical context is missing:
-1. Identify specific gaps in the information provided
-2. Attempt to resolve each gap by inspecting the codebase, documentation, README files, assistant documents (CLAUDE.md, GEMINI.md, AGENTS.md), configuration files, and any other available project context
-3. For gaps that cannot be resolved through codebase inspection, document your best-effort assumptions in the Plan Clarifications table with clear rationale
-4. Record all assumptions prominently so they can be reviewed later
-
-CRITICAL: Do NOT ask the user any questions. Do NOT wait for user input. You must resolve all ambiguity autonomously through codebase analysis and reasonable assumptions. If you cannot determine something, state your assumption and proceed.
-
-#### Step 3: Plan Generation
-Only after confirming sufficient context, create a plan according to the $root/.ai/task-manager/config/templates/PLAN_TEMPLATE.md
-
-##### CRITICAL: Output Format
-
-Remember that a plan needs to be reviewed by a human. Be concise and to the point. Also, include mermaid diagrams to illustrate the plan.
-
-**Output Behavior: CRITICAL - Structured Output for Command Coordination**
-
-Always end your output with a standardized summary in this exact format, for command coordination:
-
-```
----
-
-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.
-
-###### Patterns to Avoid
-Do not include the following in your plan output.
-- Avoid time estimations
-- Avoid task lists and mentions of phases (those are things we'll introduce later)
-- Avoid code examples
-
-###### Frontmatter Structure
-
-Example:
-```yaml
----
-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
----
-```
-
-The schema for this frontmatter is:
-```json
-{
-  "type": "object",
-  "required": ["id", "summary", "created"],
-  "properties": {
-    "id": {
-      "type": ["number"],
-      "description": "Unique identifier for the task. An integer."
-    },
-    "summary": {
-      "type": "string",
-      "description": "A summary of the plan"
-    },
-    "created": {
-      "type": "string",
-      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
-      "description": "Creation date in YYYY-MM-DD format"
-    }
-  },
-  "additionalProperties": false
-}
-```
-
-### Plan ID Generation
-
-Execute this script to determine the plan ID:
-
-```bash
-next_id=$(node $root/config/scripts/get-next-plan-id.cjs)
-```
-
-**Key formatting:**
-- **Front-matter**: Use numeric values (`id: 7`)
-- **Directory names**: Use zero-padded strings (`07--plan-name`)

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

@@ -1,175 +0,0 @@
----
-argument-hint: "[userPrompt]"
-description: Create a comprehensive plan to accomplish the request from the user.
----
-# Comprehensive Plan Creation
-
-You are a strategic planning specialist who creates actionable plan documents that balance comprehensive context with
-disciplined scope control. Your role is to think hard to create detailed, actionable plans based on user input while
-ensuring you have all necessary context before proceeding. Use the plan-creator sub-agent for this if it is available.
-
----
-
-Use tools for the planning. You are encouraged to write your own specialized tools to research, analyze, and debug
-any work order from the user. You are not restricted to the stack of the current project to create your own
-specialized tools.
-
-## Find the AI Task Manager root
-
-```bash
-if [ ! -f /tmp/find-ai-task-manager-root.js ]; then
-  cat << 'EOF' > /tmp/find-ai-task-manager-root.js
-const fs = require('fs');
-const path = require('path');
-
-const findRoot = (currentDir) => {
-  const taskManagerPath = path.join(currentDir, '.ai/task-manager');
-  const metadataPath = path.join(taskManagerPath, '.init-metadata.json');
-
-  try {
-    if (fs.existsSync(metadataPath) && JSON.parse(fs.readFileSync(metadataPath, 'utf8')).version) {
-      console.log(path.resolve(taskManagerPath));
-      process.exit(0);
-    }
-  } catch (e) {
-    // Continue searching
-  }
-
-  const parentDir = path.dirname(currentDir);
-  if (parentDir.length < currentDir.length) {
-    findRoot(parentDir);
-  } else {
-    process.exit(1);
-  }
-};
-
-findRoot(process.cwd());
-EOF
-fi
-
-root=$(node /tmp/find-ai-task-manager-root.js)
-
-if [ -z "$root" ]; then
-    echo "Error: Could not find task manager root directory (.ai/task-manager)"
-    exit 1
-fi
-```
-
-## Instructions
-
-Include $root/.ai/task-manager/config/TASK_MANAGER.md for the directory structure of tasks.
-
-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.
-
-### Process Checklist
-
-Use your internal Todo task tool to track the following plan generation:
-
-- [ ] Read and execute $root/.ai/task-manager/config/hooks/PRE_PLAN.md
-- [ ] User input and context analysis
-- [ ] Clarification questions
-- [ ] Plan generation
-- [ ] Read and execute $root/.ai/task-manager/config/hooks/POST_PLAN.md
-
-#### Step 1: Context Analysis
-Before creating any plan, analyze the user's request for:
-- **Objective**: What is the end goal?
-- **Scope**: What are the boundaries and constraints?
-- **Resources**: What tools, libraries, or infrastructure are available?
-- **Success Criteria**: How will success be measured?
-- **Dependencies**: What prerequisites or blockers exist?
-- **Technical Requirements**: What technologies or skills are needed?
-
-#### Step 2: Clarification Phase
-If any critical context is missing:
-1. Identify specific gaps in the information provided
-2. Ask targeted follow-up questions
-3. Frame questions clearly with examples when helpful
-4. Be extra cautious. Users miss important context very often. Don't hesitate to ask for additional clarifications.
-5. Make sure to get explicit confirmation of weather the user wants to maintain backwards compatibility or not.
-
-Try to answer your own questions first by inspecting the codebase, docs, and assistant documents like CLAUDE.md, GEMINI.md, AGENTS.md ...
-
-IMPORTANT: Once you have the user's answers go back to Step 2. Do this in a loop until you have no more questions. Ask as many rounds of questions as necessary, it is very important you have all the information you need to achieve your task.
-
-#### Step 3: Plan Generation
-Step 3 starts only after all items in Step 2 have been executed.
-
-Only after confirming sufficient context, create a plan according to the $root/.ai/task-manager/config/templates/PLAN_TEMPLATE.md
-
-##### CRITICAL: Output Format
-
-Remember that a plan needs to be reviewed by a human. Be concise and to the point. Also, include mermaid diagrams to illustrate the plan.
-
-**Output Behavior: CRITICAL - Structured Output for Command Coordination**
-
-Always end your output with a standardized summary in this exact format, for command coordination:
-
-```
----
-
-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.
-
-###### Patterns to Avoid
-Do not include the following in your plan output.
-- Avoid time estimations
-- Avoid task lists and mentions of phases (those are things we'll introduce later)
-- Avoid code examples
-
-###### Frontmatter Structure
-
-Example:
-```yaml
----
-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
----
-```
-
-The schema for this frontmatter is:
-```json
-{
-  "type": "object",
-  "required": ["id", "summary", "created"],
-  "properties": {
-    "id": {
-      "type": ["number"],
-      "description": "Unique identifier for the task. An integer."
-    },
-    "summary": {
-      "type": "string",
-      "description": "A summary of the plan"
-    },
-    "created": {
-      "type": "string",
-      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
-      "description": "Creation date in YYYY-MM-DD format"
-    }
-  },
-  "additionalProperties": false
-}
-```
-
-### Plan ID Generation
-
-Execute this script to determine the plan ID:
-
-```bash
-next_id=$(node $root/config/scripts/get-next-plan-id.cjs)
-```
-
-**Key formatting:**
-- **Front-matter**: Use numeric values (`id: 7`)
-- **Directory names**: Use zero-padded strings (`07--plan-name`)