task-o-matic 0.0.1

package/dist/lib/task-execution.d.ts

@@ -0,0 +1,3 @@
+import { ExecuteTaskOptions } from "../types";
+export declare function executeTask(options: ExecuteTaskOptions): Promise<void>;
+//# sourceMappingURL=task-execution.d.ts.map

package/dist/lib/task-execution.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"task-execution.d.ts","sourceRoot":"","sources":["../../src/lib/task-execution.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,kBAAkB,EAAgB,MAAM,UAAU,CAAC;AA2H5D,wBAAsB,WAAW,CAAC,OAAO,EAAE,kBAAkB,GAAG,OAAO,CAAC,IAAI,CAAC,CA4D5E"}

package/dist/lib/task-execution.js

@@ -0,0 +1,130 @@
+"use strict";
+var __importDefault = (this && this.__importDefault) || function (mod) {
+    return (mod && mod.__esModule) ? mod : { "default": mod };
+};
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.executeTask = executeTask;
+const tasks_1 = require("../services/tasks");
+const executor_factory_1 = require("./executors/executor-factory");
+const validation_1 = require("./validation");
+const chalk_1 = __importDefault(require("chalk"));
+async function executeSingleTask(taskId, tool, dry) {
+    // Load task
+    const task = await tasks_1.taskService.getTask(taskId);
+    if (!task) {
+        throw new Error(`Task with ID ${taskId} not found`);
+    }
+    console.log(chalk_1.default.blue(`🎯 ${dry ? "DRY RUN" : "Executing"} task: ${task.title} (${taskId})`));
+    // Build execution message
+    let executionMessage;
+    const planData = await tasks_1.taskService.getTaskPlan(taskId);
+    if (planData) {
+        executionMessage = `Execute this task plan:\n\n${planData.plan}`;
+    }
+    else {
+        executionMessage = `Execute this task: ${task.title}\n\nDescription: ${task.description || "No description"}`;
+    }
+    if (!dry) {
+        //   console.log(chalk.yellow(`📝 Message that would be sent:`));
+        //   console.log(chalk.cyan(executionMessage));
+        // } else {
+        // Update task status to in-progress
+        await tasks_1.taskService.setTaskStatus(taskId, "in-progress");
+        console.log(chalk_1.default.yellow("⏳ Task status updated to in-progress"));
+    }
+    try {
+        // Create executor and run
+        const executor = executor_factory_1.ExecutorFactory.create(tool);
+        console.log(chalk_1.default.cyan(`🔧 Using executor: ${executor.name}`));
+        await executor.execute(executionMessage, dry);
+        if (!dry) {
+            // Update task status to completed
+            await tasks_1.taskService.setTaskStatus(taskId, "completed");
+            console.log(chalk_1.default.green("✅ Task execution completed successfully"));
+        }
+    }
+    catch (error) {
+        if (!dry) {
+            // Update task status back to todo on failure
+            await tasks_1.taskService.setTaskStatus(taskId, "todo");
+            console.log(chalk_1.default.red("❌ Task execution failed, status reset to todo"));
+        }
+        throw error;
+    }
+}
+async function executeTaskWithSubtasks(taskId, tool, dry) {
+    const task = await tasks_1.taskService.getTask(taskId);
+    if (!task) {
+        throw new Error(`Task with ID ${taskId} not found`);
+    }
+    // Get subtasks
+    const subtasks = await tasks_1.taskService.getSubtasks(taskId);
+    if (subtasks.length === 0) {
+        // No subtasks, execute this task directly
+        await executeSingleTask(taskId, tool, dry);
+        return;
+    }
+    // Has subtasks - execute them one by one
+    console.log(chalk_1.default.blue(`📋 Task has ${subtasks.length} subtasks, executing recursively...`));
+    for (let i = 0; i < subtasks.length; i++) {
+        const subtask = subtasks[i];
+        console.log(chalk_1.default.cyan(`\n[${i + 1}/${subtasks.length}] Executing subtask: ${subtask.title} (${subtask.id})`));
+        try {
+            await executeTaskWithSubtasks(subtask.id, tool, dry);
+        }
+        catch (error) {
+            console.error(chalk_1.default.red(`❌ Failed to execute subtask ${subtask.id}: ${error instanceof Error ? error.message : "Unknown error"}`));
+            throw error;
+        }
+    }
+    // After all subtasks are done, mark the main task as completed
+    if (!dry) {
+        await tasks_1.taskService.setTaskStatus(taskId, "completed");
+        console.log(chalk_1.default.green(`✅ Main task ${task.title} completed after all subtasks`));
+    }
+    else {
+        console.log(chalk_1.default.cyan(`🔍 DRY RUN - Main task ${task.title} would be completed after all subtasks`));
+    }
+}
+async function executeTask(options) {
+    const { taskId, tool = "opencode", message, dry = false, validate = [], } = options;
+    // If custom message is provided, execute just this task (ignore subtasks)
+    if (message) {
+        const task = await tasks_1.taskService.getTask(taskId);
+        if (!task) {
+            throw new Error(`Task with ID ${taskId} not found`);
+        }
+        console.log(chalk_1.default.blue(`🎯 ${dry ? "DRY RUN - Would execute" : "Executing"} task with custom message: ${task.title} (${taskId})`));
+        if (dry) {
+            console.log(chalk_1.default.yellow(`📝 Custom message that would be sent:`));
+            console.log(chalk_1.default.cyan(message));
+        }
+        else {
+            await tasks_1.taskService.setTaskStatus(taskId, "in-progress");
+            console.log(chalk_1.default.yellow("⏳ Task status updated to in-progress"));
+        }
+        try {
+            const executor = executor_factory_1.ExecutorFactory.create(tool);
+            console.log(chalk_1.default.cyan(`🔧 Using executor: ${executor.name}`));
+            await executor.execute(message, dry);
+            if (!dry) {
+                await tasks_1.taskService.setTaskStatus(taskId, "completed");
+                console.log(chalk_1.default.green("✅ Task execution completed successfully"));
+            }
+            // Run validations after task completion
+            await (0, validation_1.runValidations)(validate, dry);
+        }
+        catch (error) {
+            if (!dry) {
+                await tasks_1.taskService.setTaskStatus(taskId, "todo");
+                console.log(chalk_1.default.red("❌ Task execution failed, status reset to todo"));
+            }
+            throw error;
+        }
+        return;
+    }
+    // No custom message - execute recursively with subtasks
+    await executeTaskWithSubtasks(taskId, tool, dry);
+    // Run validations after all subtasks complete
+    await (0, validation_1.runValidations)(validate, dry);
+}

package/dist/lib/validation.d.ts

@@ -0,0 +1,4 @@
+import { AIConfig } from '../types';
+export declare function isValidAIProvider(provider: string): provider is NonNullable<AIConfig['provider']>;
+export declare function runValidations(validations: string[], dry: boolean): Promise<void>;
+//# sourceMappingURL=validation.d.ts.map

package/dist/lib/validation.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"validation.d.ts","sourceRoot":"","sources":["../../src/lib/validation.ts"],"names":[],"mappings":"AAGA,OAAO,EAAE,QAAQ,EAAE,MAAM,UAAU,CAAC;AAIpC,wBAAgB,iBAAiB,CAAC,QAAQ,EAAE,MAAM,GAAG,QAAQ,IAAI,WAAW,CAAC,QAAQ,CAAC,UAAU,CAAC,CAAC,CAEjG;AAED,wBAAsB,cAAc,CAAC,WAAW,EAAE,MAAM,EAAE,EAAE,GAAG,EAAE,OAAO,GAAG,OAAO,CAAC,IAAI,CAAC,CA6CvF"}

package/dist/lib/validation.js

@@ -0,0 +1,52 @@
+"use strict";
+var __importDefault = (this && this.__importDefault) || function (mod) {
+    return (mod && mod.__esModule) ? mod : { "default": mod };
+};
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.isValidAIProvider = isValidAIProvider;
+exports.runValidations = runValidations;
+const child_process_1 = require("child_process");
+const util_1 = require("util");
+const chalk_1 = __importDefault(require("chalk"));
+const execAsync = (0, util_1.promisify)(child_process_1.exec);
+function isValidAIProvider(provider) {
+    return ['openrouter', 'openai', 'anthropic', 'custom'].includes(provider);
+}
+async function runValidations(validations, dry) {
+    if (validations.length === 0) {
+        return;
+    }
+    if (dry) {
+        console.log(chalk_1.default.yellow('🔍 DRY RUN - Validations that would run:'));
+        validations.forEach(cmd => console.log(chalk_1.default.cyan(`  ${cmd}`)));
+        return;
+    }
+    console.log(chalk_1.default.blue(`🧪 Running ${validations.length} validation${validations.length > 1 ? 's' : ''}...`));
+    for (let i = 0; i < validations.length; i++) {
+        const validation = validations[i];
+        console.log(chalk_1.default.blue(`🧪 Running validation [${i + 1}/${validations.length}]: ${validation}`));
+        try {
+            const { stdout, stderr } = await execAsync(validation);
+            console.log(chalk_1.default.green(`✅ Validation passed: ${validation}`));
+            // Show stdout if there's any output
+            if (stdout && stdout.trim()) {
+                console.log(chalk_1.default.gray(`   Output: ${stdout.trim()}`));
+            }
+        }
+        catch (error) {
+            console.error(chalk_1.default.red(`❌ Validation failed: ${validation}`));
+            // Show error details
+            if (error.stdout && error.stdout.trim()) {
+                console.error(chalk_1.default.yellow(`   stdout: ${error.stdout.trim()}`));
+            }
+            if (error.stderr && error.stderr.trim()) {
+                console.error(chalk_1.default.red(`   stderr: ${error.stderr.trim()}`));
+            }
+            if (error.message) {
+                console.error(chalk_1.default.red(`   Error: ${error.message}`));
+            }
+            process.exit(1);
+        }
+    }
+    console.log(chalk_1.default.green(`🎉 All ${validations.length} validation${validations.length > 1 ? 's' : ''} passed!`));
+}

package/dist/mcp/prompts.d.ts

@@ -0,0 +1,3 @@
+import { McpServer } from "@modelcontextprotocol/sdk/server/mcp";
+export declare function registerMcpPrompts(server: McpServer): void;
+//# sourceMappingURL=prompts.d.ts.map

package/dist/mcp/prompts.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"prompts.d.ts","sourceRoot":"","sources":["../../src/mcp/prompts.ts"],"names":[],"mappings":"AAEA,OAAO,EAAE,SAAS,EAAE,MAAM,sCAAsC,CAAC;AAEjE,wBAAgB,kBAAkB,CAAC,MAAM,EAAE,SAAS,QAEnD"}

package/dist/mcp/prompts.js

@@ -0,0 +1,7 @@
+"use strict";
+// MCP prompt definitions will be implemented here.
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.registerMcpPrompts = registerMcpPrompts;
+function registerMcpPrompts(server) {
+    // Example: server.registerPrompt(...);
+}

package/dist/mcp/resources.d.ts

@@ -0,0 +1,3 @@
+import { McpServer } from "@modelcontextprotocol/sdk/server/mcp";
+export declare function registerMcpResources(server: McpServer): void;
+//# sourceMappingURL=resources.d.ts.map

package/dist/mcp/resources.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"resources.d.ts","sourceRoot":"","sources":["../../src/mcp/resources.ts"],"names":[],"mappings":"AAEA,OAAO,EAAE,SAAS,EAAE,MAAM,sCAAsC,CAAC;AAEjE,wBAAgB,oBAAoB,CAAC,MAAM,EAAE,SAAS,QAErD"}

package/dist/mcp/resources.js

@@ -0,0 +1,7 @@
+"use strict";
+// MCP resource definitions will be implemented here.
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.registerMcpResources = registerMcpResources;
+function registerMcpResources(server) {
+    // Example: server.registerResource(...);
+}

package/dist/mcp/server.d.ts

@@ -0,0 +1,3 @@
+#!/usr/bin/env node
+export {};
+//# sourceMappingURL=server.d.ts.map

package/dist/mcp/server.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"server.d.ts","sourceRoot":"","sources":["../../src/mcp/server.ts"],"names":[],"mappings":""}

package/dist/mcp/server.js

@@ -0,0 +1,25 @@
+#!/usr/bin/env node
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+const mcp_1 = require("@modelcontextprotocol/sdk/server/mcp");
+const stdio_1 = require("@modelcontextprotocol/sdk/server/stdio");
+const tools_1 = require("./tools");
+const resources_1 = require("./resources");
+const prompts_1 = require("./prompts");
+const mcpServer = new mcp_1.McpServer({
+    name: "task-o-matic-mcp-server",
+    version: "0.1.0",
+});
+// Register all tools, resources, and prompts
+(0, tools_1.registerMcpTools)(mcpServer);
+(0, resources_1.registerMcpResources)(mcpServer);
+(0, prompts_1.registerMcpPrompts)(mcpServer);
+async function main() {
+    const transport = new stdio_1.StdioServerTransport();
+    await mcpServer.connect(transport);
+    console.error("task-o-matic MCP server is running...");
+}
+main().catch((error) => {
+    console.error("Server error:", error);
+    process.exit(1);
+});

package/dist/mcp/tools.d.ts

@@ -0,0 +1,3 @@
+import { McpServer } from "@modelcontextprotocol/sdk/server/mcp";
+export declare function registerMcpTools(server: McpServer): void;
+//# sourceMappingURL=tools.d.ts.map

package/dist/mcp/tools.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"tools.d.ts","sourceRoot":"","sources":["../../src/mcp/tools.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,SAAS,EAAE,MAAM,sCAAsC,CAAC;AAKjE,wBAAgB,gBAAgB,CAAC,MAAM,EAAE,SAAS,QAyGjD"}

package/dist/mcp/tools.js

@@ -0,0 +1,99 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.registerMcpTools = registerMcpTools;
+const zod_1 = require("zod");
+const tasks_1 = require("../services/tasks");
+const config_1 = require("../lib/config");
+function registerMcpTools(server) {
+    server.registerTool("get_project_info", {
+        title: "Get Project Info",
+        description: "Gets information about the current task-o-matic project, including AI configuration.",
+        inputSchema: {},
+    }, async () => {
+        try {
+            const config = config_1.configManager.getConfig();
+            const projectPath = config_1.configManager.getWorkingDirectory();
+            const info = {
+                projectPath,
+                aiConfig: config.ai,
+            };
+            return {
+                content: [
+                    {
+                        type: "text",
+                        text: JSON.stringify(info, null, 2),
+                    },
+                ],
+            };
+        }
+        catch (err) {
+            const error = err;
+            return {
+                content: [{ type: "text", text: `Error: ${error.message}` }],
+                isError: true,
+            };
+        }
+    });
+    server.registerTool("list_tasks", {
+        title: "List Tasks",
+        description: "List all tasks for the current project. Can filter by status.",
+        inputSchema: {
+            filterByStatus: zod_1.z.enum(["todo", "in-progress", "completed"]).optional(),
+        },
+    }, async (input) => {
+        try {
+            const tasks = await tasks_1.taskService.listTasks({
+                status: input.filterByStatus
+            });
+            return {
+                content: [
+                    {
+                        type: "text",
+                        text: JSON.stringify(tasks, null, 2),
+                    },
+                ],
+            };
+        }
+        catch (err) {
+            const error = err;
+            return {
+                content: [{ type: "text", text: `Error: ${error.message}` }],
+                isError: true,
+            };
+        }
+    });
+    server.registerTool("create_task", {
+        title: "Create Task",
+        description: "Creates a new task.",
+        inputSchema: {
+            taskTitle: zod_1.z.string(),
+            taskContent: zod_1.z.string().optional(),
+            effort: zod_1.z.enum(["small", "medium", "large"]).optional(),
+            aiEnhance: zod_1.z.boolean().optional(),
+        },
+    }, async (input) => {
+        try {
+            const result = await tasks_1.taskService.createTask({
+                title: input.taskTitle,
+                content: input.taskContent,
+                effort: input.effort,
+                aiEnhance: input.aiEnhance,
+            });
+            return {
+                content: [
+                    {
+                        type: "text",
+                        text: `Task created successfully with ID: ${result.task.id}`,
+                    },
+                ],
+            };
+        }
+        catch (err) {
+            const error = err;
+            return {
+                content: [{ type: "text", text: `Error: ${error.message}` }],
+                isError: true,
+            };
+        }
+    });
+}

package/dist/prompts/documentation-detection.d.ts

@@ -0,0 +1,2 @@
+export declare const DOCUMENTATION_DETECTION_PROMPT = "You are an expert developer. Your job is to analyze a task and fetch relevant documentation using Context7 and create a dedicated documentation for the task.\n\nDo not create a plan, i want a documentation for the actual task using the knowledge you gained from the research.\n\n## Task:\n**Title**: {TASK_TITLE}\n**Description**: {TASK_DESCRIPTION}\n\n## Current Stack:\n{STACK_INFO}\n\n## Already Researched:\n{EXISTING_RESEARCH}\n\n## Instructions:\n1. Identify technologies/libraries mentioned in the task that need documentation\n2. Skip anything already covered in existing research\n3. Use Context7 to resolve library names and fetch documentation\n4. Create a focused documentation only on what's actually needed for this specific task\n\nGet the documentation libraries needed for this task.";
+//# sourceMappingURL=documentation-detection.d.ts.map

package/dist/prompts/documentation-detection.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"documentation-detection.d.ts","sourceRoot":"","sources":["../../src/prompts/documentation-detection.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,8BAA8B,qyBAoBW,CAAC"}

package/dist/prompts/documentation-detection.js

@@ -0,0 +1,24 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.DOCUMENTATION_DETECTION_PROMPT = void 0;
+exports.DOCUMENTATION_DETECTION_PROMPT = `You are an expert developer. Your job is to analyze a task and fetch relevant documentation using Context7 and create a dedicated documentation for the task.
+
+Do not create a plan, i want a documentation for the actual task using the knowledge you gained from the research.
+
+## Task:
+**Title**: {TASK_TITLE}
+**Description**: {TASK_DESCRIPTION}
+
+## Current Stack:
+{STACK_INFO}
+
+## Already Researched:
+{EXISTING_RESEARCH}
+
+## Instructions:
+1. Identify technologies/libraries mentioned in the task that need documentation
+2. Skip anything already covered in existing research
+3. Use Context7 to resolve library names and fetch documentation
+4. Create a focused documentation only on what's actually needed for this specific task
+
+Get the documentation libraries needed for this task.`;

package/dist/prompts/index.d.ts

@@ -0,0 +1,7 @@
+export * from './prd-parsing';
+export * from './task-breakdown';
+export * from './task-enhancement';
+export * from './prd-rework';
+export * from './documentation-detection';
+export * from './task-planning';
+//# sourceMappingURL=index.d.ts.map

package/dist/prompts/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/prompts/index.ts"],"names":[],"mappings":"AAAA,cAAc,eAAe,CAAC;AAC9B,cAAc,kBAAkB,CAAC;AACjC,cAAc,oBAAoB,CAAC;AACnC,cAAc,cAAc,CAAC;AAC7B,cAAc,2BAA2B,CAAC;AAC1C,cAAc,iBAAiB,CAAC"}

package/dist/prompts/index.js

@@ -0,0 +1,22 @@
+"use strict";
+var __createBinding = (this && this.__createBinding) || (Object.create ? (function(o, m, k, k2) {
+    if (k2 === undefined) k2 = k;
+    var desc = Object.getOwnPropertyDescriptor(m, k);
+    if (!desc || ("get" in desc ? !m.__esModule : desc.writable || desc.configurable)) {
+      desc = { enumerable: true, get: function() { return m[k]; } };
+    }
+    Object.defineProperty(o, k2, desc);
+}) : (function(o, m, k, k2) {
+    if (k2 === undefined) k2 = k;
+    o[k2] = m[k];
+}));
+var __exportStar = (this && this.__exportStar) || function(m, exports) {
+    for (var p in m) if (p !== "default" && !Object.prototype.hasOwnProperty.call(exports, p)) __createBinding(exports, m, p);
+};
+Object.defineProperty(exports, "__esModule", { value: true });
+__exportStar(require("./prd-parsing"), exports);
+__exportStar(require("./task-breakdown"), exports);
+__exportStar(require("./task-enhancement"), exports);
+__exportStar(require("./prd-rework"), exports);
+__exportStar(require("./documentation-detection"), exports);
+__exportStar(require("./task-planning"), exports);

package/dist/prompts/prd-parsing.d.ts

@@ -0,0 +1,3 @@
+export declare const PRD_PARSING_PROMPT = "\nYou are an AI assistant specialized in analyzing Product Requirements Documents (PRDs) and generating a structured, logically ordered, dependency-aware and sequenced list of development phases in JSON format.\n\n## \uD83C\uDFD7\uFE0F IMPORTANT: PROJECT INFRASTRUCTURE IS READY\nThis project is **already bootstrapped and configured**. The foundation is complete and ready for development. **DO NOT** create tasks for setting up the basic infrastructure.\n\nAnalyze the provided PRD content and generate an appropriate number of top-level development phases. Each phase should represent 1-3 weeks of focused development work and focus on the most direct and effective way to implement the requirements without unnecessary complexity or overengineering.\n\nIf the complexity or the level of detail of the PRD is high, generate more phases relative to the complexity of the PRD. Let the PRD content determine the appropriate number of phases - there is no fixed target.\n\n## CRITICAL: Task ID and Dependency Format\nYou MUST generate unique task IDs and reference them properly in dependencies:\n\n1. **Task ID Generation**: \n   - Each task must have an \"id\" field with simple numeric format: \"1\", \"2\", \"3\", etc.\n   - IDs must be sequential starting from \"1\"\n   - Each task ID must be unique\n   - NO prefixes like \"task-\" - use simple numbers only\n\n2. **Dependency References**:\n   - Dependencies MUST reference the exact task IDs (not titles)\n   - Use format: [\"1\", \"2\", \"3\"]\n   - NEVER use task titles in dependencies\n   - Only reference tasks that appear EARLIER in the list\n   - Ensure all dependency references are valid\n\n## \uD83D\uDCCB Phase Sizing (1-3 WEEKS per phase):\n- **Small**: 1 week (5-7 days) - Focused module with clear boundaries\n- **Medium**: 2 weeks (8-12 days) - Complex feature with multiple components  \n- **Large**: 3 weeks (13-15 days) - Major system with integrations and polish\n\n## \uD83C\uDFAF PHASE EXAMPLES (1-3 WEEKS EACH):\n\u2705 \"User Authentication & Profile Management\" - Complete user system with registration, login, profiles, and security\n\u2705 \"Interactive Map & Location Services\" - Full mapping functionality with search, geolocation, and place markers\n\u2705 \"Rating & Review System\" - Complete rating workflow with reviews, scores, and moderation\n\u2705 \"Content Management System\" - Full CRUD system for managing content with validation and permissions\n\n## \u274C FORBIDDEN MICRO-TASKS (THESE ARE IMPLEMENTATION DETAILS, NOT PHASES):\n- \"Implement API endpoint\" (this is a planning step)\n- \"Build UI component\" (this is a planning step)  \n- \"Create database schema\" (this is a planning step)\n- \"Setup authentication\" (this is part of a larger phase)\n\n## \u2705 Guidelines:\n1. Create an appropriate number of phases based on PRD complexity\n2. Each phase should be atomic and focused on a major feature area\n3. Order phases logically - consider dependencies and implementation sequence\n4. Early phases should focus on foundation and core functionality first, then advanced features\n5. Include clear technical considerations for each phase\n6. Set appropriate dependency IDs (a phase can only depend on phases with lower IDs)\n7. Assign effort based on the scope and complexity of work involved\n8. Include detailed implementation guidance in the description\n9. If the PRD contains specific requirements for libraries, frameworks, or tech stacks, STRICTLY ADHERE to these requirements\n10. Focus on filling in any gaps left by the PRD while preserving all explicit requirements\n11. Always aim to provide the most direct path to implementation, avoiding over-engineering\n\n## \u2705 Dependency Validation Rules:\n- Task \"1\" must have no dependencies (it's the first task)\n- Task N can only depend on tasks 1 through (N-1)\n- No circular dependencies allowed\n- No forward references\n- Every task must have a unique sequential ID\n\nFormat your response as JSON:\n{\n  \"tasks\": [\n    {\n      \"id\": \"1\",\n      \"title\": \"User Authentication & Security System\",\n      \"description\": \"Implement complete user authentication system including registration, login/logout, password reset, session management, security measures, and user profile functionality with proper validation and error handling\",\n      \"effort\": \"medium\",\n      \"dependencies\": [],\n      \"technicalConsiderations\": \"Leverage existing Better-Auth integration and Convex backend for secure user management\"\n    },\n    {\n      \"id\": \"2\", \n      \"title\": \"Core Business Data Management\",\n      \"description\": \"Set up database schemas, models, and business logic for the main application entities including data validation, relationships, and core CRUD operations\",\n      \"effort\": \"medium\", \n      \"dependencies\": [\"1\"],\n      \"technicalConsiderations\": \"Design efficient Convex schemas with proper indexing and relationships\"\n    }\n  ]\n}\n\n## Technology Stack\n{STACK_INFO}\n\nPRD to parse:\n{PRD_CONTENT}\n";
+export declare const PRD_PARSING_SYSTEM_PROMPT = "\nYou are an AI assistant specialized in analyzing Product Requirements Documents (PRDs) and generating a structured, logically ordered, dependency-aware and sequenced list of development phases in JSON format.\n\n## CRITICAL INSTRUCTION: Create Appropriate-Sized Phases\nYou MUST generate development phases that represent 1-3 weeks of focused work each. The number of phases should be determined by the PRD complexity, not by arbitrary targets.\n\n## CRITICAL INSTRUCTION: Task ID Generation and Dependencies\nYou MUST generate unique task IDs and use them for dependencies:\n\n1. **Generate Task IDs**: \n   - Each task needs an \"id\" field: \"1\", \"2\", \"3\", etc.\n   - IDs must be sequential and unique\n   - Start with \"1\"\n   - NO prefixes like \"task-\" - use simple numbers only\n\n2. **Dependency References**:\n   - Use the exact task IDs in dependencies arrays\n   - NEVER use task titles\n   - Only reference earlier tasks (lower numbers)\n   - Validate that all dependency references exist\n\n3. **Required Fields for Each Task**:\n   - id: \"N\" format (required)\n   - title: string (required)\n   - description: string (required)\n   - effort: \"small\"|\"medium\"|\"large\" (required - based on 1-3 week duration)\n   - dependencies: array of task IDs (required)\n   - technicalConsiderations: string (optional)\n\n## Phase Analysis Guidelines:\n1. **Scope Appropriately**: Each phase should represent 1-3 weeks of substantial development work\n2. **Business-Focused**: Phase titles should reflect business value and user-facing features\n3. **Logical Sequencing**: Order phases based on dependencies and implementation priorities\n4. **Complexity-Based**: More complex PRDs should result in more phases, simpler PRDs in fewer phases\n5. **Direct Implementation**: Focus on the most direct path to implementing requirements\n\n## FORBIDDEN MICRO-TASKS (DO NOT CREATE):\n- Individual API endpoints, UI components, database schemas\n- Technical implementation details that belong in planning\n- Tasks that take less than 1 week to complete\n\n## REQUIRED PHASE EXAMPLES (1-3 WEEKS EACH):\n- \"User Authentication & Profile Management\" \u2192 Complete user system\n- \"Interactive Map & Location Services\" \u2192 Full mapping functionality\n- \"Rating & Review System\" \u2192 Complete rating workflow\n- \"Content Management System\" \u2192 Full CRUD for content\n\n## Dependency Validation Rules:\n- Task \"1\" MUST have empty dependencies array: []\n- Task N can only reference tasks 1 through (N-1)\n- No circular dependencies\n- No forward references\n- All dependency references must be valid task IDs\n- Every task must have a unique sequential ID\n- Verify all referenced IDs exist in the tasks array\n\n## Quality Standards:\n- Each phase should be atomic and focused on a major feature area\n- Include detailed implementation guidance in descriptions\n- Consider the existing technology stack and infrastructure\n- Ensure phases build upon each other logically\n- Focus on business value and user-facing outcomes\n\n## Output Validation:\nBefore returning your response, verify:\n1. Every task represents 1-3 weeks of substantial work\n2. Tasks are major phases, not implementation details\n3. Every task has a unique sequential ID (\"1\", \"2\", \"3\", etc.)\n4. All dependency arrays contain valid task IDs (not titles)\n5. No task depends on itself or a later task\n6. Task \"1\" has no dependencies\n7. All referenced task IDs exist in the tasks array\n8. JSON structure is valid and parseable\n9. All required fields are present for each task\n10. The number of tasks is appropriate for the PRD complexity\n\nReturn only valid JSON that can be parsed. Ensure all required fields are present and properly formatted.\n";
+//# sourceMappingURL=prd-parsing.d.ts.map

package/dist/prompts/prd-parsing.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"prd-parsing.d.ts","sourceRoot":"","sources":["../../src/prompts/prd-parsing.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,kBAAkB,i8JA0F9B,CAAC;AAEF,eAAO,MAAM,yBAAyB,+qHA6ErC,CAAC"}

package/dist/prompts/prd-parsing.js

@@ -0,0 +1,172 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.PRD_PARSING_SYSTEM_PROMPT = exports.PRD_PARSING_PROMPT = void 0;
+exports.PRD_PARSING_PROMPT = `
+You are an AI assistant specialized in analyzing Product Requirements Documents (PRDs) and generating a structured, logically ordered, dependency-aware and sequenced list of development phases in JSON format.
+
+## 🏗️ IMPORTANT: PROJECT INFRASTRUCTURE IS READY
+This project is **already bootstrapped and configured**. The foundation is complete and ready for development. **DO NOT** create tasks for setting up the basic infrastructure.
+
+Analyze the provided PRD content and generate an appropriate number of top-level development phases. Each phase should represent 1-3 weeks of focused development work and focus on the most direct and effective way to implement the requirements without unnecessary complexity or overengineering.
+
+If the complexity or the level of detail of the PRD is high, generate more phases relative to the complexity of the PRD. Let the PRD content determine the appropriate number of phases - there is no fixed target.
+
+## CRITICAL: Task ID and Dependency Format
+You MUST generate unique task IDs and reference them properly in dependencies:
+
+1. **Task ID Generation**: 
+   - Each task must have an "id" field with simple numeric format: "1", "2", "3", etc.
+   - IDs must be sequential starting from "1"
+   - Each task ID must be unique
+   - NO prefixes like "task-" - use simple numbers only
+
+2. **Dependency References**:
+   - Dependencies MUST reference the exact task IDs (not titles)
+   - Use format: ["1", "2", "3"]
+   - NEVER use task titles in dependencies
+   - Only reference tasks that appear EARLIER in the list
+   - Ensure all dependency references are valid
+
+## 📋 Phase Sizing (1-3 WEEKS per phase):
+- **Small**: 1 week (5-7 days) - Focused module with clear boundaries
+- **Medium**: 2 weeks (8-12 days) - Complex feature with multiple components  
+- **Large**: 3 weeks (13-15 days) - Major system with integrations and polish
+
+## 🎯 PHASE EXAMPLES (1-3 WEEKS EACH):
+✅ "User Authentication & Profile Management" - Complete user system with registration, login, profiles, and security
+✅ "Interactive Map & Location Services" - Full mapping functionality with search, geolocation, and place markers
+✅ "Rating & Review System" - Complete rating workflow with reviews, scores, and moderation
+✅ "Content Management System" - Full CRUD system for managing content with validation and permissions
+
+## ❌ FORBIDDEN MICRO-TASKS (THESE ARE IMPLEMENTATION DETAILS, NOT PHASES):
+- "Implement API endpoint" (this is a planning step)
+- "Build UI component" (this is a planning step)  
+- "Create database schema" (this is a planning step)
+- "Setup authentication" (this is part of a larger phase)
+
+## ✅ Guidelines:
+1. Create an appropriate number of phases based on PRD complexity
+2. Each phase should be atomic and focused on a major feature area
+3. Order phases logically - consider dependencies and implementation sequence
+4. Early phases should focus on foundation and core functionality first, then advanced features
+5. Include clear technical considerations for each phase
+6. Set appropriate dependency IDs (a phase can only depend on phases with lower IDs)
+7. Assign effort based on the scope and complexity of work involved
+8. Include detailed implementation guidance in the description
+9. If the PRD contains specific requirements for libraries, frameworks, or tech stacks, STRICTLY ADHERE to these requirements
+10. Focus on filling in any gaps left by the PRD while preserving all explicit requirements
+11. Always aim to provide the most direct path to implementation, avoiding over-engineering
+
+## ✅ Dependency Validation Rules:
+- Task "1" must have no dependencies (it's the first task)
+- Task N can only depend on tasks 1 through (N-1)
+- No circular dependencies allowed
+- No forward references
+- Every task must have a unique sequential ID
+
+Format your response as JSON:
+{
+  "tasks": [
+    {
+      "id": "1",
+      "title": "User Authentication & Security System",
+      "description": "Implement complete user authentication system including registration, login/logout, password reset, session management, security measures, and user profile functionality with proper validation and error handling",
+      "effort": "medium",
+      "dependencies": [],
+      "technicalConsiderations": "Leverage existing Better-Auth integration and Convex backend for secure user management"
+    },
+    {
+      "id": "2", 
+      "title": "Core Business Data Management",
+      "description": "Set up database schemas, models, and business logic for the main application entities including data validation, relationships, and core CRUD operations",
+      "effort": "medium", 
+      "dependencies": ["1"],
+      "technicalConsiderations": "Design efficient Convex schemas with proper indexing and relationships"
+    }
+  ]
+}
+
+## Technology Stack
+{STACK_INFO}
+
+PRD to parse:
+{PRD_CONTENT}
+`;
+exports.PRD_PARSING_SYSTEM_PROMPT = `
+You are an AI assistant specialized in analyzing Product Requirements Documents (PRDs) and generating a structured, logically ordered, dependency-aware and sequenced list of development phases in JSON format.
+
+## CRITICAL INSTRUCTION: Create Appropriate-Sized Phases
+You MUST generate development phases that represent 1-3 weeks of focused work each. The number of phases should be determined by the PRD complexity, not by arbitrary targets.
+
+## CRITICAL INSTRUCTION: Task ID Generation and Dependencies
+You MUST generate unique task IDs and use them for dependencies:
+
+1. **Generate Task IDs**: 
+   - Each task needs an "id" field: "1", "2", "3", etc.
+   - IDs must be sequential and unique
+   - Start with "1"
+   - NO prefixes like "task-" - use simple numbers only
+
+2. **Dependency References**:
+   - Use the exact task IDs in dependencies arrays
+   - NEVER use task titles
+   - Only reference earlier tasks (lower numbers)
+   - Validate that all dependency references exist
+
+3. **Required Fields for Each Task**:
+   - id: "N" format (required)
+   - title: string (required)
+   - description: string (required)
+   - effort: "small"|"medium"|"large" (required - based on 1-3 week duration)
+   - dependencies: array of task IDs (required)
+   - technicalConsiderations: string (optional)
+
+## Phase Analysis Guidelines:
+1. **Scope Appropriately**: Each phase should represent 1-3 weeks of substantial development work
+2. **Business-Focused**: Phase titles should reflect business value and user-facing features
+3. **Logical Sequencing**: Order phases based on dependencies and implementation priorities
+4. **Complexity-Based**: More complex PRDs should result in more phases, simpler PRDs in fewer phases
+5. **Direct Implementation**: Focus on the most direct path to implementing requirements
+
+## FORBIDDEN MICRO-TASKS (DO NOT CREATE):
+- Individual API endpoints, UI components, database schemas
+- Technical implementation details that belong in planning
+- Tasks that take less than 1 week to complete
+
+## REQUIRED PHASE EXAMPLES (1-3 WEEKS EACH):
+- "User Authentication & Profile Management" → Complete user system
+- "Interactive Map & Location Services" → Full mapping functionality
+- "Rating & Review System" → Complete rating workflow
+- "Content Management System" → Full CRUD for content
+
+## Dependency Validation Rules:
+- Task "1" MUST have empty dependencies array: []
+- Task N can only reference tasks 1 through (N-1)
+- No circular dependencies
+- No forward references
+- All dependency references must be valid task IDs
+- Every task must have a unique sequential ID
+- Verify all referenced IDs exist in the tasks array
+
+## Quality Standards:
+- Each phase should be atomic and focused on a major feature area
+- Include detailed implementation guidance in descriptions
+- Consider the existing technology stack and infrastructure
+- Ensure phases build upon each other logically
+- Focus on business value and user-facing outcomes
+
+## Output Validation:
+Before returning your response, verify:
+1. Every task represents 1-3 weeks of substantial work
+2. Tasks are major phases, not implementation details
+3. Every task has a unique sequential ID ("1", "2", "3", etc.)
+4. All dependency arrays contain valid task IDs (not titles)
+5. No task depends on itself or a later task
+6. Task "1" has no dependencies
+7. All referenced task IDs exist in the tasks array
+8. JSON structure is valid and parseable
+9. All required fields are present for each task
+10. The number of tasks is appropriate for the PRD complexity
+
+Return only valid JSON that can be parsed. Ensure all required fields are present and properly formatted.
+`;