@e0ipso/ai-task-manager 1.5.0 → 1.6.1

package/LICENSE

@@ -1,68 +1,21 @@
-PROPRIETARY SOFTWARE LICENSE WITH REVOCATION RIGHTS
-
-Copyright (c) 2025 Mateu Aguiló Bosch
-
-NOTICE: This is proprietary software with revocable usage rights.
-
-1. GRANT OF LICENSE
-   Subject to the terms and conditions of this License, the copyright holder
-   hereby grants you a free, non-exclusive, non-transferable, revocable right
-   to use, run, and operate this software ("Software") for any lawful purpose.
-
-2. REVOCATION RIGHTS
-   The copyright holder reserves the absolute right to revoke this license at
-   any time, for any reason or no reason, with or without cause, by providing
-   written notice to you. Such notice may be provided through:
-   - Direct communication to known users
-   - Public announcement on the project repository
-   - Update to this LICENSE file
-
-3. NOTICE PERIOD
-   Upon issuance of a revocation notice, you will have thirty (30) days
-   ("Notice Period") to cease all use of the Software and remove all copies
-   from your systems.
-
-4. CONDITIONS FOR REVOCATION
-   While the copyright holder may revoke this license at their sole discretion,
-   revocation may particularly occur in cases of:
-   - Violation of applicable laws or regulations
-   - Use of the Software in a manner harmful to others
-   - Commercial use without separate commercial license
-   - Any use deemed inappropriate by the copyright holder
-
-5. POST-REVOCATION OBLIGATIONS
-   After the Notice Period expires, you must:
-   - Immediately cease all use of the Software
-   - Delete all copies of the Software from all systems under your control
-   - Certify destruction of copies if requested by the copyright holder
-
-6. NO WARRANTY
-   THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-   IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-   FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
-
-7. LIMITATION OF LIABILITY
-   IN NO EVENT SHALL THE COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR
-   OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
-   ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
-   DEALINGS IN THE SOFTWARE.
-
-8. ENTIRE AGREEMENT
-   This License constitutes the entire agreement between you and the copyright
-   holder relating to the Software and supersedes all prior or contemporaneous
-   understandings.
-
-9. SEVERABILITY
-   If any provision of this License is held to be unenforceable, such provision
-   shall be reformed only to the extent necessary to make it enforceable.
-
-10. GOVERNING LAW
-    This License shall be governed by the laws of the jurisdiction in which
-    the copyright holder resides, without regard to its conflict of law
-    provisions.
-
-By using this Software, you acknowledge that you have read, understood, and
-agree to be bound by the terms and conditions of this License.
-
-For commercial licensing or other arrangements, please contact the copyright
-holder directly.
+MIT License
+
+Copyright (c) 2025 Mateu Aguil� Bosch
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -3,84 +3,22 @@
 [![npm version](https://img.shields.io/npm/v/@e0ipso/ai-task-manager.svg)](https://www.npmjs.com/package/@e0ipso/ai-task-manager)
 [![License](https://img.shields.io/badge/License-Proprietary-red.svg)](LICENSE)
 
-## 🔥 **Use Your Existing AI Subscription**
+AI-powered task management that creates structured workflows within your existing AI subscriptions. Supports Claude Code, Gemini CLI, and Open Code through custom slash commands.
 
-**Unlike Aider, Taskmaster, and Cursor**, AI Task Manager works **within** your existing AI subscription interfaces (Claude Pro/Max, Gemini, etc.). This is NOT another AI agent that requires API keys - it creates slash commands that run inside your AI tools you already pay for.
+💰 Unlike projects such as **Plandex**, **Claude Task Master**, and **Conductor Tasks** that require API keys with pay-per-token pricing, **AI Task Manager** works within your existing AI subscription interface. Simply log in to your Claude or Gemini account and use the slash commands - **no API keys or additional costs required**.
 
-### 🏗️ **How This Actually Works**
+## How It Works
 
-This tool creates **custom slash commands** (like `/tasks:create-plan`, `/tasks:generate-tasks`) that integrate directly into:
+This tool creates custom slash commands (like `/tasks:create-plan`, `/tasks:generate-tasks`) that integrate directly into:
 - **Claude Code**: Works with your Claude Pro/Max subscription via [claude.ai/code](https://claude.ai/code)
-- **Gemini CLI**: Uses your existing Gemini subscription
+- **Gemini CLI**: Uses your existing Gemini subscription  
 - **Open Code**: Leverages your preferred open-source setup
 
-### 💰 **Billing Model Comparison**
-
-| Tool  | Additional API Costs | Total for Subscription Users |
-|------|---------------------|------------------------------|
-| **AI Task Manager**  | **$0** | **$0** (uses existing subscription) |
-| **Plandex Cloud**  | Included credits | *$45/month* |
-| **Plandex (BYOK)**  | Unpredictable (API usage) | *Unpredictable costs* |
-| **Claude Task Master** | Unpredictable (API usage) | *Unpredictable costs* |
-| **Conductor Tasks**  | Unpredictable (API usage) | *Unpredictable costs* |
-| **Shrimp Task Manager**  | Unpredictable (API usage) | *Unpredictable costs* |
-
-<details>
-<summary>📋 More Details</summary>
-
-| Tool | Stars | Type | Key Features | Documentation |
-|------|-------|------|--------------|---------------|
-| **AI Task Manager** | New | Task Management System | ✅ Plans→Tasks→Execution workflow<br>✅ Native slash commands<br>✅ No API keys needed | This README |
-| **[Plandex](https://github.com/plandex-ai/plandex)** | 14k+ | AI Coding Agent | ✅ Handles 2M token context<br>✅ Multi-file editing<br>⚠️ Terminal-based (not in IDE) | [Docs](https://docs.plandex.ai/) |
-| **[Claude Task Master](https://github.com/eyaltoledano/claude-task-master)** | 4.2k+ | Task Management  | ✅ PRD→Tasks workflow<br>✅ MCP integration<br>⚠️ Requires API keys | [Tutorial](https://github.com/eyaltoledano/claude-task-master/blob/main/docs/tutorial.md) |
-| **[Conductor Tasks](https://github.com/hridaya423/conductor-tasks)** | 38 | Visual Task Manager  | ✅ Kanban boards<br>✅ Dependency trees<br>⚠️ Requires API keys | [GitHub](https://github.com/hridaya423/conductor-tasks) |
-| **[Shrimp Task Manager](https://github.com/cjo4m06/mcp-shrimp-task-manager)** | 70+ | Chain-of-Thought Tasks  | ✅ Chain-of-thought focus<br>✅ Persistent memory<br>⚠️ Requires API keys | [Docs](https://github.com/cjo4m06/mcp-shrimp-task-manager/tree/main/docs) |
-
-</details>
-
-### ⚡ **Predictable Costs**
-
-Because this works within your existing AI interface:
-- **No surprise API bills** - you already know what your AI subscription costs
-- **No rate limiting issues** - uses your subscription's limits
-- **No API key management** - just type slash commands
-- **Full model access** - get the latest models as soon as they're available in your subscription
-
-AI-powered task management that creates structured workflows within your existing AI subscriptions. Supports Claude Code, Gemini CLI, and Open Code through custom slash commands.
-
-### 🎯 Key Differentiators
-
-**1. Zero Additional Costs**: AI Task Manager is the **only tool** that works within your existing AI subscriptions (Claude Pro/Max, Gemini, etc.) without any API fees or additional subscriptions.
-
-**2. Native Integration**: Unlike terminal-based tools (Plandex) or MCP servers requiring complex setup, AI Task Manager creates simple slash commands that work directly in your AI interface (claude.ai/code, Gemini CLI, etc.).
-
-**3. Complete Workflow**: Full planning → task generation → execution workflow, matching enterprise tools like Claude Task Master but without the API key requirement.
-
-**4. Predictable Costs**: No surprise API bills. You already know what your AI subscription costs - there's nothing extra to pay.
-
 ## ✨ Features
 
 - 🤝 **Multi-Assistant Support**: Configure support for Claude, Gemini, and Open Code
 - 📋 **Template System**: Built-in templates for different project types (basic, development, research)
 
-## 💰 Intelligent Token Usage
-
-**One of the key benefits of this project is dramatically reducing AI costs by using the right model for the right task.**
-
-The AI Task Manager leverages a **staged refinement approach** that maximizes the value of expensive, high-capability models while delegating execution to faster, cheaper models:
-
-### 🧠 Use Premium Models for Complex Analysis
-- **Planning Phase** (`/tasks:create-plan`): Deploy your most capable models (Claude Opus, GPT-5, etc.) for deep requirement analysis, architecture decisions, and strategic planning
-- **Task Generation** (`/tasks:generate-tasks`): Leverage advanced reasoning for complex decomposition, dependency mapping, and scope optimization
-
-### ⚡ Use Fast Models for Execution
-- **Blueprint Execution** (`/tasks:execute-blueprint`): Switch to faster, cost-effective models (Gemini 2.0 Flash, Claude Haiku) for task execution
-- **Individual Tasks**: Sub-agents can also choose to use simpler models since most complexity is resolved during planning
-
-### 💡 Why This Works
-The heavy cognitive lifting happens during plan creation and task generation. By the time you reach execution, the blueprint documents are detailed and specific enough that simpler models can reliably implement them. This approach can **reduce your AI costs** and be **significantly faster** compared to using premium models for all phases.
-
-_The more complex your project, the greater the savings._
 
 ## 🚀 Quick Start
 
@@ -180,12 +118,4 @@ Review and tweak the `.ai/task-manager/TASK_MANAGER.md` and `.ai/task-manager/co
 
 ## 📄 License
 
-⚖️ **Proprietary Software with Revocation Rights.**
-
-This software is free to use, run, and operate for any lawful purposes. The
-author can revoke the license to use it at any time and by any reason. A license
-revocation notice may be provided through:
-
-- 📧 Direct communication to known users
-- 📢 Public announcement on the project repository
-- 📝 Update to the LICENSE file
+⚖️ **Open Source MIT License**

package/package.json

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

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

@@ -20,6 +20,15 @@ If no user input is provided stop immediately and show an error message to the u
 
 ### Process
 
+Use your internal Todo task tool to track the plan generation. Example:
+
+- [ ] User input and context analysis
+- [ ] Clarification questions
+- [ ] Plan generation: Executive Summary
+- [ ] Plan generation: Detailed Steps
+- [ ] Plan generation: Risk Considerations
+- [ ] Plan generation: Success Metrics
+
 #### Step 1: Context Analysis
 Before creating any plan, analyze the user's request for:
 - **Objective**: What is the end goal?
@@ -35,15 +44,17 @@ If any critical context is missing:
 2. Ask targeted follow-up questions grouped by category
 3. Wait for user responses before proceeding to planning
 4. Frame questions clearly with examples when helpful
-5. Be extra cautious. Users miss important context very often. Extract it from them
+5. Be extra cautious. Users miss important context very often. Don't hesitate to ask for clarifications.
 
 Example clarifying questions:
-- "What is your primary goal with [specific aspect]?"
-- "Do you have any existing [resources/code/infrastructure] I should consider?"
-- "What is your timeline for completing this?"
-- "Are there specific constraints I should account for?"
-- "Do you want me to write tests for this?"
-- "Are there other systems, projects, or modules that perform a similar task?"
+- "Q: What is your primary goal with [specific aspect]?"
+- "Q: Do you have any existing [resources/code/infrastructure] I should consider?"
+- "Q: What is your timeline for completing this?"
+- "Q: Are there specific constraints I should account for?"
+- "Q: Do you want me to write tests for this?"
+- "Q: Are there other systems, projects, or modules that perform a similar task?"
+
+Try to answer your own questions first by inspecting the codebase, docs, and assistant documents like CLAUDE.md, GEMINI.md, AGENTS.md ...
 
 #### Step 3: Plan Generation
 Only after confirming sufficient context, create a plan that includes:
@@ -54,14 +65,7 @@ Only after confirming sufficient context, create a plan that includes:
 
 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.
 
-### Important Notes
-- Never generate a partial or assumed plan without adequate context
-- Prioritize accuracy over speed
-- Consider both technical and non-technical aspects
-- Adapt the plan format based on the task type (development, design, research, etc.)
-- DO NOT create or list any tasks or phases during the plan creation. This will be done in a later step. Stick to writing the PRD (Project Requirements Document).
-
-### Scope Control Guidelines
+##### Scope Control Guidelines
 **Critical: Implement ONLY what is explicitly requested**
 
 - **Minimal Viable Implementation**: Build exactly what the user asked for, nothing more
@@ -79,7 +83,7 @@ Remember that a plan needs to be reviewed by a human. Be concise and to the poin
 
 **When in doubt, ask**: "Is this feature explicitly mentioned in the user's request?"
 
-### Simplicity Principles
+##### Simplicity Principles
 **Favor maintainability over cleverness**
 
 - **Simple Solutions First**: Choose the most straightforward approach that meets requirements
@@ -91,23 +95,23 @@ Remember that a plan needs to be reviewed by a human. Be concise and to the poin
 
 **Remember**: A working simple solution is better than a complex "perfect" one.
 
-### Output Format
+##### Output Format
 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.
 
 Outside the plan document, be **extremely** concise. Just tell the user that you are done, and instruct them to review the plan document.
 
-#### Plan Template
+###### Plan Template
 
 Use the template in @.ai/task-manager/config/templates/PLAN_TEMPLATE.md
 
-#### Patterns to Avoid
+###### 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)
 
-#### Frontmatter Structure
+###### Frontmatter Structure
 
 Example:
 ```yaml
@@ -142,6 +146,13 @@ The schema for this frontmatter is:
 }
 ```
 
+### Critical Notes
+- Never generate a partial or assumed plan without adequate context
+- Prioritize accuracy over speed
+- Consider both technical and non-technical aspects
+- Use the plan template in .ai/task-manager/config/templates/PLAN_TEMPLATE.md
+- DO NOT create or list any tasks or phases during the plan creation. This will be done in a later step. Stick to writing the PRD (Project Requirements Document).
+
 ### Plan ID Generation
 
 **Auto-generate the next plan ID:**

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

@@ -24,10 +24,23 @@ If the plan does not exist, or the plan does not have an execution blueprint sec
 
 ## Execution Process
 
+Use your internal Todo task tool to track the execution of all phases, and the final update of the plan with the summary. Example:
+
+- [ ] Create feature branch from the main branch.
+- [ ] Phase 1: Execute 1 task(s) in parallel.
+- [ ] Execute POST_PHASE.md hook after Phase 1.
+- [ ] Phase 2: Execute 3 task(s) in parallel.
+- [ ] Execute POST_PHASE.md hook after Phase 2.
+- [ ] Phase 3: Execute 1 task(s) in parallel.
+- [ ] Execute POST_PHASE.md hook after Phase 3.
+- [ ] Update the Plan 7 with execution summary, and the archive it.
+
 ### Phase Pre-Execution
 
 Before starting execution check if you are in the `main` branch. If so, create a git branch to work on this blueprint use the plan name for the branch name.
 
+If there are unstaged changes in the `main` branch, do not create a feature branch.
+
 ### Phase Execution Workflow
 
 1. **Phase Initialization**

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

@@ -6,6 +6,15 @@ description: Execute a single task with dependency validation and status managem
 
 You are responsible for executing a single task within a plan while maintaining strict dependency validation and proper status management. Your role is to ensure the task is ready for execution, deploy the appropriate agent, and track execution progress.
 
+Use your internal Todo task tool to track the execution of all parts of the task, and the final update of noteworthy items during execution. Example:
+
+- [ ] Validate task: file, status, and dependencies.
+- [ ] Select the most appropriate sub-agent.
+- [ ] Set task status to in-progress.
+- [ ] Delegate task implementation to the sub-agent.
+- [ ] Update task status to completed or failed.
+- [ ] Update the task file with noteworthy events during execution.
+
 ## Critical Rules
 
 1. **Never skip dependency validation** - Task execution requires all dependencies to be completed