Full Workflow

---
argument-hint: "[userPrompt]"
description: Execute the full workflow from plan creation to blueprint execution.
---

# Full Workflow Execution

You are a workflow composition assistant. Your role is to execute the complete task management workflow from plan creation through blueprint execution **without pausing between steps**. This is a fully automated workflow that executes all three steps sequentially.

---

## 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

Workflow Execution Instructions

CRITICAL: Execute all three steps sequentially without waiting for user input between steps. Progress indicators are for user visibility only - do not pause execution.

The user input is:

$ARGUMENTS

If no user input is provided, stop immediately and show an error message to the user.

Context Passing Between Steps

How information flows through the workflow:

1. User provides prompt → use as input in Step 1
2. Step 1 outputs "Plan ID: X" in structured format → extract X, use in Step 2
3. Step 2 outputs "Tasks: Y" in structured format → use for progress tracking in Step 3

Use your internal Todo task tool to track the workflow execution:

• Step 1: Create Plan
• Step 2: Generate Tasks
• Step 3: Execute Blueprint

---

Step 1: Plan Creation

Progress: ⬛⬜⬜ 0% - Step 1/3: Starting Plan Creation

Execute the following plan creation process:

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

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:

$ARGUMENTS

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.

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

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 standalon ```