@e0ipso/ai-task-manager 1.1.3 → 1.1.4

package/README.md

@@ -1,51 +1,29 @@
-# AI Task Manager
+# 🤖 AI Task Manager
 
-AI-powered task management CLI tool to improve your context. It supports multiple coding assistants including Claude and Gemini for comprehensive development workflow integration.
-
-## Features
+[![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)
 
-- **Multi-Assistant Support**: Configure support for Claude, Gemini, or both assistants simultaneously
-- **Intelligent Directory Structure**: Organized file structure with assistant-specific directories
-- **Interactive CLI**: Enhanced user interface with colored output and progress indicators
-- **Template System**: Built-in templates for different project types (basic, development, research)
-- **Task Management**: Create, list, and manage tasks with status tracking
-- **Installation Management**: Comprehensive installation, verification, and repair capabilities
-- **Cross-Platform**: Works on Windows, macOS, and Linux
+AI-powered task management CLI tool to improve your context. It supports multiple coding assistants including Claude and Gemini for comprehensive development workflow integration.
 
-## Quick Start
+## ✨ Features
 
-### Installation
-```bash
-# Install globally
-npm install -g @e0ipso/ai-task-manager
+- 🤝 **Multi-Assistant Support**: Configure support for Claude, and Gemini
+- 📋 **Template System**: Built-in templates for different project types (basic, development, research)
 
-# Or use with npx (no installation required)
-npx @e0ipso/ai-task-manager --help
-```
+## 🚀 Quick Start
 
-### Initialize a New Workspace
+### 🏗️ Initialize a New Workspace
 
 The `--assistants` flag is **required** when initializing a workspace. You must specify which coding assistant(s) you want to configure support for.
 
-The `--destination-directory` flag allows you to specify an alternative directory for the workspace. By default, the workspace is initialized in the current working directory.
-
-```bash
-# Quick start with Claude
-npx @e0ipso/ai-task-manager init --assistants claude
-```
-
-If the script detects that any of the folders it needs to create already exist it merge the folder structures, but it will overwrite the files in them.
-
-## Assistant Selection
-
 AI Task Manager supports multiple coding assistants. You **must** specify which assistant(s) to use during initialization using the `--assistants` flag.
 
-### Supported Assistants
+🤖 Supported Assistants are
 
-- **Claude**: Anthropic's Claude AI assistant
-- **Gemini**: Google's Gemini AI assistant
+- 🎭 **Claude**: Anthropic's Claude AI assistant
+- 💎 **Gemini**: Google's Gemini AI assistant
 
-### Single Assistant Setup
+The `--destination-directory` flag allows you to specify an alternative directory for the workspace. By default, the workspace is initialized in the current working directory.
 
 ```bash
 # Claude only
@@ -53,16 +31,14 @@ npx @e0ipso/ai-task-manager init --assistants claude
 
 # Gemini only  
 npx @e0ipso/ai-task-manager init --assistants gemini
-```
 
-### Multiple Assistant Setup
-
-```bash
 # Both Claude and Gemini
 npx @e0ipso/ai-task-manager init --assistants claude,gemini
 ```
 
-### Directory Structure
+If the script detects that any of the folders it needs to create already exist it merge the folder structures, but it will overwrite the files in them.
+
+### 📂 Directory Structure
 
 When you initialize with assistant selection, the following directory structure is created:
 
@@ -88,25 +64,26 @@ project-root/
 └── project files...
 ```
 
-## Suggested Workflow
+## 💡 Suggested Workflow
 
-### One-time Setup
+### 📋 One-time Setup
 
 Review and tweak the `.ai/task-manager/TASK_MANAGER_INFO.md` and `.ai/task-manager/VALIDATION_GATES.md`. These files are yours to edit and should reflect your project's tech stack and goals.
 
-### Day-to-day Workflow
+### 🔄 Day-to-day Workflow
 
-1. Create a plan: `/tasks:create-plan Create an authentication workflow for the application using ...`
-2. Provide additional context if the assistant needs it.
-3. Manually review the plan and make the necessary edits. You might be tempted to skip this step, **do not skip this step**. Find the plan document in `.ai/task-manager/plans/01--authentication-workflow/plan-01--authentication-workflow.md`
-4. Create the tasks for the plan: `/tasks:generate-tasks 1`
-5. Review the list of tasks. This step is important to avoid scope creep and ensure the right things are to be built. Again, **do not skip this step**. Find the tasks in the folder `.ai/task-manager/plans/01--authentication-workflow/tasks/`
-6. Execute the tasks: `/tasks:execute-blueprint 1`
-7. Review the implementation and the generated tests.
+1. 📝 Create a plan: `/tasks:create-plan Create an authentication workflow for the application using ...`
+2. 💬 Provide additional context if the assistant needs it.
+3. ⚠️ Manually review the plan and make the necessary edits. You might be tempted to skip this step, **do not skip this step**. Find the plan document in `.ai/task-manager/plans/01--authentication-workflow/plan-01--authentication-workflow.md`
+4. 📋 Create the tasks for the plan: `/tasks:generate-tasks 1`
+5. 👀 Review the list of tasks. This step is important to avoid scope creep and ensure the right things are to be built. Again, **do not skip this step**. Find the tasks in the folder `.ai/task-manager/plans/01--authentication-workflow/tasks/`
+6. 🚀 Execute the tasks: `/tasks:execute-blueprint 1`
+7. ✅ Review the implementation and the generated tests.
 
-### Troubleshooting
+## 🔧 Troubleshooting
 
-#### Permission Errors
+<details>
+<summary>🚫 Permission Errors</summary>
 
 **Error**: File system permission errors during initialization
 
@@ -115,14 +92,16 @@ Review and tweak the `.ai/task-manager/TASK_MANAGER_INFO.md` and `.ai/task-manag
 - On Unix systems, check directory ownership: `ls -la`
 - Try running with appropriate permissions or in a user-owned directory
 
-## License
+</details>
+
+## 📄 License
 
-Proprietary Software with Revocation Rights.
+⚖️ **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
+- 📧 Direct communication to known users
+- 📢 Public announcement on the project repository
+- 📝 Update to the LICENSE file

package/package.json

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

package/templates/commands/tasks/generate-tasks.md

@@ -103,49 +103,12 @@ Tests that verify custom business logic, critical paths, and edge cases specific
 - Configuration files or static data
 - Obvious functionality that would break immediately if incorrect
 
-**Testing Anti-patterns to Avoid:**
-```javascript
-// DON'T: Testing library functionality
-test('useState updates state', () => {
-  // This tests React, not your code
-});
-
-// DON'T: Testing trivial getters
-test('getName returns name property', () => {
-  expect(user.getName()).toBe(user.name);
-});
-
-// DON'T: Comprehensive test suites for simple functions
-test('add function with 15 different number combinations', () => {
-  // Overkill for a simple addition function
-});
-```
-
-**Testing Positive Patterns:**
-```javascript
-// DO: Test business logic
-test('calculateOrderTotal applies correct discounts and tax', () => {
-  // Tests your specific calculation logic
-});
-
-// DO: Test critical paths
-test('payment processing handles failed transactions', () => {
-  // Tests important error handling
-});
-
-// DO: Test edge cases
-test('user registration handles duplicate emails', () => {
-  // Tests specific business rule
-});
-```
-
 **Test Task Creation Rules:**
 - Combine related test scenarios into single tasks (e.g., "Test user authentication flow" not separate tasks for login, logout, validation)
 - Focus on integration and critical path testing over unit test coverage
 - Avoid creating separate tasks for testing each CRUD operation individually
 - Question whether simple functions need dedicated test tasks
 
-
 ### Process
 
 #### Step 1: Task Decomposition
@@ -246,6 +209,8 @@ The schema for this frontmatter is:
 - [ ] Criterion 2
 - [ ] Criterion 3
 
+Use your internal TODO tool to track these and keep on track.
+
 ## Technical Requirements
 [Specific technical details, APIs, libraries, etc. - use this to infer appropriate skills]