πŸ“¦ Installation & Setup

AI Task Manager initializes quickly with a single command, creating all necessary configuration files and directory structure for your project.

Prerequisites

  • Node.js: Version 14.0 or higher
  • npm: Comes with Node.js
  • AI Assistant: Active subscription to Claude, Gemini, or access to Open Code

Installation

No global installation required. Use npx to run AI Task Manager directly:

npx @e0ipso/ai-task-manager init --assistants claude

Assistant Configuration

The --assistants flag is required when initializing. You must specify which AI assistant(s) you want to configure.

Single Assistant Setup

# Claude only (for use with claude.ai/code)
npx @e0ipso/ai-task-manager init --assistants claude

# Gemini only (for use with Gemini CLI)
npx @e0ipso/ai-task-manager init --assistants gemini

# Open Code only (for open source assistants)
npx @e0ipso/ai-task-manager init --assistants opencode

Multiple Assistants

Configure multiple assistants for team flexibility:

npx @e0ipso/ai-task-manager init --assistants claude,gemini,opencode

All assistants share the same task management structure (plans, tasks, configurations) while using assistant-specific command formats.

Custom Destination Directory

By default, AI Task Manager initializes in the current working directory. Use --destination-directory to specify an alternative location:

npx @e0ipso/ai-task-manager init \
  --assistants claude \
  --destination-directory /path/to/project

Directory Structure

When you initialize, the following structure is created:

project-root/
β”œβ”€β”€ .ai/
β”‚   └── task-manager/              # Shared configuration files
β”‚       β”œβ”€β”€ plans/                 # Active plans (empty initially)
β”‚       β”œβ”€β”€ archive/               # Completed plans (empty initially)
β”‚       β”œβ”€β”€ config/
β”‚       β”‚   β”œβ”€β”€ TASK_MANAGER.md   # Project context (customize this!)
β”‚       β”‚   β”œβ”€β”€ hooks/             # Lifecycle hooks
β”‚       β”‚   β”‚   β”œβ”€β”€ PRE_PLAN.md
β”‚       β”‚   β”‚   β”œβ”€β”€ PRE_PHASE.md
β”‚       β”‚   β”‚   β”œβ”€β”€ POST_PHASE.md
β”‚       β”‚   β”‚   β”œβ”€β”€ POST_PLAN.md
β”‚       β”‚   β”‚   β”œβ”€β”€ POST_TASK_GENERATION_ALL.md
β”‚       β”‚   β”‚   β”œβ”€β”€ PRE_TASK_ASSIGNMENT.md
β”‚       β”‚   β”‚   └── POST_ERROR_DETECTION.md
β”‚       β”‚   β”œβ”€β”€ templates/         # Customizable templates
β”‚       β”‚   β”‚   β”œβ”€β”€ PLAN_TEMPLATE.md
β”‚       β”‚   β”‚   β”œβ”€β”€ TASK_TEMPLATE.md
β”‚       β”‚   β”‚   β”œβ”€β”€ BLUEPRINT_TEMPLATE.md
β”‚       β”‚   β”‚   └── EXECUTION_SUMMARY_TEMPLATE.md
β”‚       β”‚   └── scripts/           # ID generation scripts
β”‚       β”‚       β”œβ”€β”€ get-next-plan-id.cjs
β”‚       β”‚       └── get-next-task-id.cjs
β”‚       └── .init-metadata.json    # File conflict detection tracking
β”œβ”€β”€ .claude/                       # Claude files (if --assistants claude)
β”‚   └── commands/tasks/
β”‚       β”œβ”€β”€ create-plan.md
β”‚       β”œβ”€β”€ generate-tasks.md
β”‚       β”œβ”€β”€ execute-blueprint.md
β”‚       β”œβ”€β”€ execute-task.md
β”‚       └── fix-broken-tests.md
β”œβ”€β”€ .gemini/                       # Gemini files (if --assistants gemini)
β”‚   └── commands/tasks/
β”‚       β”œβ”€β”€ create-plan.toml       # TOML format for Gemini
β”‚       β”œβ”€β”€ generate-tasks.toml
β”‚       β”œβ”€β”€ execute-blueprint.toml
β”‚       β”œβ”€β”€ execute-task.toml
β”‚       └── fix-broken-tests.toml
└── .opencode/                     # Open Code files (if --assistants opencode)
    └── commands/tasks/
        β”œβ”€β”€ create-plan.md
        β”œβ”€β”€ generate-tasks.md
        β”œβ”€β”€ execute-blueprint.md
        β”œβ”€β”€ execute-task.md
        └── fix-broken-tests.md

Updating Configuration

Re-running init

Re-run the init command to update configuration files to the latest version:

npx @e0ipso/ai-task-manager init --assistants claude

File Conflict Detection automatically:

  • Compares current files to original versions using SHA-256 hashes
  • Prompts if you’ve customized files (shows unified diff)
  • Updates unchanged files automatically
  • Preserves your customizations

Force Mode

Bypass conflict detection prompts (useful for automation):

npx @e0ipso/ai-task-manager init --assistants claude --force

Warning: Force mode overwrites ALL files, including your customizations. Back up custom hooks and templates first!

Protected Files

The config/scripts/ directory is never overwritten by init, even in force mode. Your custom ID generation logic is always preserved.

Verification

Verify successful installation:

1. Check Directory Structure

ls -la .ai/task-manager/

You should see: plans/, archive/, config/

2. Check Assistant Commands

For Claude:

ls -la .claude/commands/tasks/

For Gemini:

ls -la .gemini/commands/tasks/

3. Test Status Command

npx @e0ipso/ai-task-manager status

Should show: β€œNo active plans found” (until you create your first plan)

Customizing for Your Project

After installation, customize these files for your specific needs:

Essential Customizations

  1. .ai/task-manager/config/TASK_MANAGER.md
    • Add project context (tech stack, coding standards, architecture decisions)
    • Include links to design docs, API specs, or style guides
    • Document project-specific conventions
  2. .ai/task-manager/config/hooks/POST_PHASE.md
    • Add your quality gates (linting, tests, coverage thresholds)
    • Include deployment steps (staging, production)
    • Add notification steps (Slack, email, dashboard updates)

Advanced Customizations

See the Customization Guide for:

  • Template modifications
  • Hook customization examples
  • Real-world scenarios (React projects, API projects, monorepos)

Next Steps

Ready to create your first plan:

# In your AI assistant (Claude, Gemini, or Open Code):
/tasks:create-plan "Your project description here"