@compass-ai/nova 1.0.74 → 1.0.76

package/dist/prompts/utils.js

@@ -1,114 +0,0 @@
-/**
- * Utility functions for prompt handling.
- *
- * Contains shared helper functions used across prompt modules.
- */
-/**
- * Interpolates template variables in a string.
- * Replaces {{variable}} patterns with corresponding values.
- *
- * @param template - The template string containing {{variable}} patterns
- * @param variables - Object containing variable names and their values
- * @returns The interpolated string
- *
- * @example
- * ```ts
- * const result = interpolateTemplate(
- *   'Hello {{name}}, welcome to {{place}}!',
- *   { name: 'Alice', place: 'Wonderland' }
- * );
- * // Result: 'Hello Alice, welcome to Wonderland!'
- * ```
- */
-export function interpolateTemplate(template, variables) {
-    let result = template;
-    for (const [key, value] of Object.entries(variables)) {
-        const regex = new RegExp(`\\{\\{${key}\\}\\}`, 'g');
-        result = result.replace(regex, value);
-    }
-    return result;
-}
-/**
- * Strips common indentation from a multi-line template string.
- * Useful for maintaining readability in code while producing clean output.
- *
- * @param str - The multi-line string to dedent
- * @returns The dedented string
- */
-export function dedent(str) {
-    const lines = str.split('\n');
-    // Find minimum indentation (ignoring empty lines)
-    let minIndent = Infinity;
-    for (const line of lines) {
-        if (line.trim().length === 0)
-            continue;
-        const indent = line.match(/^\s*/)?.[0].length ?? 0;
-        minIndent = Math.min(minIndent, indent);
-    }
-    if (minIndent === Infinity || minIndent === 0) {
-        return str;
-    }
-    // Remove the common indentation
-    return lines.map((line) => line.slice(minIndent)).join('\n');
-}
-/**
- * Joins multiple prompt sections with double newlines.
- * Filters out empty or undefined sections.
- *
- * @param sections - Array of prompt sections to join
- * @returns The joined prompt string
- */
-export function joinPromptSections(...sections) {
-    return sections.filter((s) => s && s.trim().length > 0).join('\n\n');
-}
-/**
- * Wraps content in a labeled section for prompts.
- *
- * @param label - The section label/header
- * @param content - The content for the section
- * @param headerStyle - Style of the header ('##' for markdown, etc.)
- * @returns Formatted section string
- */
-export function createPromptSection(label, content, headerStyle = '##') {
-    if (!content || content.trim().length === 0) {
-        return '';
-    }
-    return `${headerStyle} ${label}\n${content}`;
-}
-/**
- * Truncates text to a maximum length with ellipsis.
- *
- * @param text - The text to truncate
- * @param maxLength - Maximum length before truncation
- * @returns Truncated text with '...' if needed
- */
-export function truncateForPrompt(text, maxLength) {
-    if (text.length <= maxLength) {
-        return text;
-    }
-    return text.substring(0, maxLength - 3) + '...';
-}
-/**
- * Formats a list of items as a markdown list for prompts.
- *
- * @param items - Array of items to format
- * @param style - List style ('bullet' for '-', 'numbered' for '1.')
- * @returns Formatted list string
- */
-export function formatPromptList(items, style = 'bullet') {
-    return items
-        .map((item, index) => style === 'bullet' ? `- ${item}` : `${index + 1}. ${item}`)
-        .join('\n');
-}
-/**
- * Wraps code in a markdown code block.
- *
- * @param code - The code to wrap
- * @param language - Optional language identifier
- * @returns Formatted code block string
- */
-export function wrapCodeBlock(code, language) {
-    const lang = language || '';
-    return `\`\`\`${lang}\n${code}\n\`\`\``;
-}
-//# sourceMappingURL=utils.js.map

package/dist/prompts/utils.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"utils.js","sourceRoot":"","sources":["../../src/prompts/utils.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAEH;;;;;;;;;;;;;;;;GAgBG;AACH,MAAM,UAAU,mBAAmB,CACjC,QAAgB,EAChB,SAAiC;IAEjC,IAAI,MAAM,GAAG,QAAQ,CAAC;IAEtB,KAAK,MAAM,CAAC,GAAG,EAAE,KAAK,CAAC,IAAI,MAAM,CAAC,OAAO,CAAC,SAAS,CAAC,EAAE,CAAC;QACrD,MAAM,KAAK,GAAG,IAAI,MAAM,CAAC,SAAS,GAAG,QAAQ,EAAE,GAAG,CAAC,CAAC;QACpD,MAAM,GAAG,MAAM,CAAC,OAAO,CAAC,KAAK,EAAE,KAAK,CAAC,CAAC;IACxC,CAAC;IAED,OAAO,MAAM,CAAC;AAChB,CAAC;AAED;;;;;;GAMG;AACH,MAAM,UAAU,MAAM,CAAC,GAAW;IAChC,MAAM,KAAK,GAAG,GAAG,CAAC,KAAK,CAAC,IAAI,CAAC,CAAC;IAE9B,kDAAkD;IAClD,IAAI,SAAS,GAAG,QAAQ,CAAC;IACzB,KAAK,MAAM,IAAI,IAAI,KAAK,EAAE,CAAC;QACzB,IAAI,IAAI,CAAC,IAAI,EAAE,CAAC,MAAM,KAAK,CAAC;YAAE,SAAS;QACvC,MAAM,MAAM,GAAG,IAAI,CAAC,KAAK,CAAC,MAAM,CAAC,EAAE,CAAC,CAAC,CAAC,CAAC,MAAM,IAAI,CAAC,CAAC;QACnD,SAAS,GAAG,IAAI,CAAC,GAAG,CAAC,SAAS,EAAE,MAAM,CAAC,CAAC;IAC1C,CAAC;IAED,IAAI,SAAS,KAAK,QAAQ,IAAI,SAAS,KAAK,CAAC,EAAE,CAAC;QAC9C,OAAO,GAAG,CAAC;IACb,CAAC;IAED,gCAAgC;IAChC,OAAO,KAAK,CAAC,GAAG,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,IAAI,CAAC,KAAK,CAAC,SAAS,CAAC,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;AAC/D,CAAC;AAED;;;;;;GAMG;AACH,MAAM,UAAU,kBAAkB,CAAC,GAAG,QAAuC;IAC3E,OAAO,QAAQ,CAAC,MAAM,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,IAAI,CAAC,CAAC,IAAI,EAAE,CAAC,MAAM,GAAG,CAAC,CAAC,CAAC,IAAI,CAAC,MAAM,CAAC,CAAC;AACvE,CAAC;AAED;;;;;;;GAOG;AACH,MAAM,UAAU,mBAAmB,CACjC,KAAa,EACb,OAAe,EACf,cAAmC,IAAI;IAEvC,IAAI,CAAC,OAAO,IAAI,OAAO,CAAC,IAAI,EAAE,CAAC,MAAM,KAAK,CAAC,EAAE,CAAC;QAC5C,OAAO,EAAE,CAAC;IACZ,CAAC;IAED,OAAO,GAAG,WAAW,IAAI,KAAK,KAAK,OAAO,EAAE,CAAC;AAC/C,CAAC;AAED;;;;;;GAMG;AACH,MAAM,UAAU,iBAAiB,CAAC,IAAY,EAAE,SAAiB;IAC/D,IAAI,IAAI,CAAC,MAAM,IAAI,SAAS,EAAE,CAAC;QAC7B,OAAO,IAAI,CAAC;IACd,CAAC;IACD,OAAO,IAAI,CAAC,SAAS,CAAC,CAAC,EAAE,SAAS,GAAG,CAAC,CAAC,GAAG,KAAK,CAAC;AAClD,CAAC;AAED;;;;;;GAMG;AACH,MAAM,UAAU,gBAAgB,CAC9B,KAAe,EACf,QAA+B,QAAQ;IAEvC,OAAO,KAAK;SACT,GAAG,CAAC,CAAC,IAAI,EAAE,KAAK,EAAE,EAAE,CACnB,KAAK,KAAK,QAAQ,CAAC,CAAC,CAAC,KAAK,IAAI,EAAE,CAAC,CAAC,CAAC,GAAG,KAAK,GAAG,CAAC,KAAK,IAAI,EAAE,CAC3D;SACA,IAAI,CAAC,IAAI,CAAC,CAAC;AAChB,CAAC;AAED;;;;;;GAMG;AACH,MAAM,UAAU,aAAa,CAAC,IAAY,EAAE,QAAiB;IAC3D,MAAM,IAAI,GAAG,QAAQ,IAAI,EAAE,CAAC;IAC5B,OAAO,SAAS,IAAI,KAAK,IAAI,UAAU,CAAC;AAC1C,CAAC"}

package/dist/prompts/workflow.d.ts

@@ -1,241 +0,0 @@
-/**
- * Workflow prompts for the planning and execution system.
- *
- * These templates are used for LLM interactions during the workflow phases.
- * Templates use {{variable}} syntax for interpolation.
- *
- * The classification prompts are designed to be domain-agnostic, supporting both
- * development tasks and productivity automation via MCP tools.
- */
-import type { PersonalityMode } from '../types/session.js';
-/**
- * Prompt template for context analysis - analyzes codebase structure
- * to understand its architecture and find relevant files.
- *
- * Variables:
- * - {{userRequest}} - The user's request
- * - {{projectType}} - Type of project (Node.js, React, etc.)
- * - {{languages}} - Languages detected in the project
- * - {{projectRoot}} - Root directory of the project
- * - {{directoryTree}} - Directory structure
- */
-export declare const CONTEXT_ANALYSIS_PROMPT = "\nYou are analyzing a codebase to understand its structure and find files relevant to a user request.\n\n## User Request\n{{userRequest}}\n\n## Project Information\n- Type: {{projectType}}\n- Languages: {{languages}}\n- Root: {{projectRoot}}\n\n## Directory Structure\n{{directoryTree}}\n\n## Task\nAnalyze the project structure and identify:\n1. Which areas of the codebase are likely affected (UI, backend, database, tests, etc.)\n2. Key files that should be examined\n3. Potential dependencies or related files\n4. Any configuration that might need updating\n\nProvide a structured analysis.\n";
-/**
- * Prompt template for complexity assessment - determines the best execution approach.
- *
- * Variables:
- * - {{userRequest}} - The user's request
- * - {{filesCount}} - Number of files potentially affected
- * - {{affectedAreas}} - Areas of the codebase affected
- * - {{recentChanges}} - Recent changes in the codebase
- */
-export declare const COMPLEXITY_ASSESSMENT_PROMPT = "\nYou are assessing the complexity of a development task to determine the best execution approach.\n\n## User Request\n{{userRequest}}\n\n## Context Summary\n- Files potentially affected: {{filesCount}}\n- Areas affected: {{affectedAreas}}\n- Recent changes in codebase: {{recentChanges}}\n\n## Assessment Criteria\n\n**Simple/Direct Mode** - Execute immediately without planning:\n- 1-3 files affected\n- Less than 50 lines changed\n- Clear, unambiguous requirements\n- No architectural changes\n- No breaking changes\n\n**Clarification Needed** - Requires user input first:\n- Ambiguous requirements\n- Multiple valid approaches\n- User preferences needed\n- Missing information\n\n**Plan Mode Required** - Needs detailed implementation plan:\n- 4+ files affected\n- 100+ lines of changes\n- Architectural changes\n- Breaking changes possible\n- Cross-cutting concerns\n\n## Task\nAnalyze the request and determine:\n1. Which mode is appropriate\n2. Key complexity factors\n3. If clarification needed, what questions to ask\n4. Estimated effort level\n";
-/**
- * Prompt template for plan generation - creates detailed implementation plans.
- *
- * Variables:
- * - {{userRequest}} - The user's request
- * - {{contextSummary}} - Summary of the gathered context
- * - {{clarificationSummary}} - Summary of user clarifications (if any)
- */
-export declare const PLAN_GENERATION_PROMPT = "\nYou are creating a detailed implementation plan for a development task.\n\n## User Request\n{{userRequest}}\n\n## Context\n{{contextSummary}}\n\n## Clarification Answers (if any)\n{{clarificationSummary}}\n\n## Requirements\nGenerate a comprehensive implementation plan with:\n\n1. **Problem Statement** - Clear description of what we're building and why\n\n2. **Requirements Analysis**\n   - Extract explicit requirements from user request\n   - Infer implicit requirements\n   - Reference clarification answers where applicable\n\n3. **Edge Cases** - Identify potential edge cases and how to handle them\n\n4. **Impact Assessment**\n   - Files to create/modify/delete\n   - Dependencies affected\n   - Breaking changes if any\n   - Migration needs\n\n5. **Task Breakdown**\n   For each task include:\n   - Clear description\n   - Target files and specific code sections\n   - Dependencies on other tasks\n   - Verification criteria\n\n6. **Risk Analysis**\n   - Potential issues\n   - Mitigation strategies\n   - Rollback approach\n\n7. **Testing Requirements**\n   - Unit tests needed\n   - Integration tests needed\n   - Manual testing steps\n\nEnsure tasks are ordered by dependencies and each task is atomic and independently verifiable.\n";
-/**
- * Prompt template for verification - verifies implementation matches its plan.
- *
- * Variables:
- * - {{planSummary}} - Summary of the original plan
- * - {{executionResults}} - Results of the implementation
- * - {{diffSummary}} - Summary of changes made
- */
-export declare const VERIFICATION_PROMPT = "\nYou are verifying that an implementation matches its plan.\n\n## Original Plan\n{{planSummary}}\n\n## Implementation Results\n{{executionResults}}\n\n## Changes Made\n{{diffSummary}}\n\n## Verification Tasks\n1. Verify each planned task was completed correctly\n2. Check for orphaned or incomplete code\n3. Verify all requirements are addressed\n4. Check alignment with clarification answers\n5. Identify any deviations from the plan\n\nProvide a detailed verification report.\n";
-/**
- * Prompt template for LLM-based complexity classification decision.
- *
- * This prompt presents all gathered factors and heuristic analysis to the LLM,
- * allowing it to make the final decision about execution mode with full context.
- *
- * Variables:
- * - {{userRequest}} - The user's request
- * - {{filesAffected}} - Number of files potentially affected
- * - {{linesChanged}} - Estimated lines to be changed
- * - {{requirementsClear}} - Whether requirements are clear (true/false)
- * - {{architecturalChange}} - Whether this involves architectural changes
- * - {{breakingChanges}} - Whether this may cause breaking changes
- * - {{crossCuttingConcerns}} - Whether multiple subsystems are affected
- * - {{createsAbstractions}} - Whether new abstractions will be created
- * - {{requiresMigration}} - Whether data migration is needed
- * - {{implementationApproaches}} - Number of valid implementation approaches
- * - {{riskLevel}} - Risk level (1-10)
- * - {{heuristicMode}} - What the rule-based system suggests
- * - {{heuristicConfidence}} - Confidence of heuristic suggestion (0-100)
- * - {{heuristicReasoning}} - Reasoning from heuristic analysis
- * - {{affectedAreas}} - Codebase areas affected
- * - {{relevantFiles}} - Key files identified
- */
-export declare const LLM_COMPLEXITY_CLASSIFICATION_PROMPT = "You are determining the appropriate execution mode for a development task.\n\n## Execution Modes\n\n**DIRECT** - Execute immediately without planning:\n- Simple, focused changes (1-3 files, <50 lines)\n- Clear, unambiguous requirements with single obvious approach\n- No architectural impact, no breaking changes\n- Low risk (e.g., typo fixes, simple bug fixes, adding logs)\n- **Requests to understand, explain, or analyze existing code** - the codebase needs to be explored thoroughly\n\n**NO_ACTION** - Nothing needs to be done:\n- The requested feature/change is already fully implemented in the codebase\n- The request doesn't make sense given the current code structure or project context\n- The request conflicts with existing functionality or architecture in a way that makes it invalid\n- **NOT for requests to understand, explain, analyze, or explore existing code** - those need DIRECT mode to properly search the codebase\n- When using this mode: provide clear explanation of why no action is needed, and offer a helpful follow-up question or tip to guide the user\n\n**TODO_LIST** - Create a simple task checklist:\n- Medium complexity tasks (2-8 files, 30-200 lines)\n- Requirements are clear OR sufficient code context is available to proceed\n- No architectural changes or breaking changes\n- Multiple sequential steps that benefit from tracking\n- Moderate risk level (not too simple, not too complex)\n- PREFER this mode when code snippets/files have been analyzed and provide sufficient context\n- Good for: adding a feature across a few files, implementing a well-defined component, updating multiple related files\n\n**PLAN** - Requires detailed implementation plan:\n- Large refactoring across many existing files (4+ files, 100+ lines)\n- Architectural modifications to existing systems\n- Breaking changes or migrations of existing data/APIs\n- High risk changes to production code\n- Cross-cutting concerns affecting multiple existing subsystems\n\n**PLAN_ADOPT** - User has already provided a structured plan:\n- Input contains numbered steps, ordered tasks, or a clear implementation sequence\n- Often comes from user approving/refining a previous LLM suggestion\n- Indicators: \"1.\", \"2.\", \"3.\" sequence, bullet points with specific actions, task lists\n- Your job: validate feasibility, enrich with technical details, format to schema\n- PRESERVE user's task order and descriptions - do NOT regenerate or reorder\n- Use this when the user's input already IS the plan, not just a request FOR a plan\n\n## Important Guidance\n- **TODO_LIST is the balanced default** for medium-complexity tasks when code context is available. It provides structure without over-planning.\n- **Default to DIRECT for simple tasks** and TODO_LIST for multi-step tasks - the agentic loop has AskUserQuestion tool available for questions during execution\n- For **new programs/scripts**: Use TODO_LIST if the request is reasonably specific\n- PLAN is mainly for **modifying existing complex codebases** with architectural changes, not for greenfield development\n- When in doubt between TODO_LIST and PLAN, prefer TODO_LIST if there are no architectural changes\n- **PLAN_ADOPT saves time** when users provide structured input - don't regenerate what they've already defined\n\n## User Request\n{{userRequest}}\n\n## Analyzed Complexity Factors\n| Factor | Value |\n|--------|-------|\n| Files likely affected | {{filesAffected}} |\n| Estimated lines changed | {{linesChanged}} |\n| Requirements clear | {{requirementsClear}} |\n| Context sufficiency | {{contextSufficiency}} |\n| Architectural change | {{architecturalChange}} |\n| Breaking changes | {{breakingChanges}} |\n| Cross-cutting concerns | {{crossCuttingConcerns}} |\n| Creates abstractions | {{createsAbstractions}} |\n| Requires migration | {{requiresMigration}} |\n| Implementation approaches | {{implementationApproaches}} |\n| Risk level | {{riskLevel}}/10 |\n\n## Heuristic Analysis (Rule-Based)\n- **Suggested Mode**: {{heuristicMode}}\n- **Confidence**: {{heuristicConfidence}}%\n- **Reasoning**: {{heuristicReasoning}}\n\n## Codebase Context\n- **Affected Areas**: {{affectedAreas}}\n- **Key Files**: {{relevantFiles}}\n\n## Your Task\nAnalyze the request and factors above. Consider:\n1. Does the heuristic suggestion make sense, or does context warrant a different mode?\n2. **Context sufficiency is key**: If context sufficiency is \"medium\" or \"high\", prefer TODO_LIST.\n3. Are there nuances the rules might miss (e.g., security implications, hidden complexity)?\n4. Default to DIRECT for simple tasks, TODO_LIST for multi-step tasks, PLAN only for genuine architectural complexity\n\n## Reasoning Guidelines\nYour reasoning should be **concise and actionable**:\n- State the key insight about what's needed to proceed\n- Do NOT list multiple interpretations (\"The user could mean: (1)..., (2)..., (3)...\")\n- Do NOT enumerate possibilities or reflect on ambiguity\n- Focus on **what information is missing** or **why the chosen mode is appropriate**\n\n## Response Format\n\n**CRITICAL**: You MUST respond with ONLY valid JSON wrapped in a markdown code block. Your response will be parsed with JSON.parse().\n\n```json\n{\n  \"mode\": \"TODO_LIST\",\n  \"confidence\": 80,\n  \"reasoning\": \"Medium complexity task with clear implementation path.\",\n  \"agreesWithHeuristic\": true\n}\n```\n\n**Field Requirements:**\n- **mode** (required): Exactly one of: \"NO_ACTION\", \"DIRECT\", \"TODO_LIST\", \"PLAN\", \"PLAN_ADOPT\"\n- **confidence** (required): Number 0-100 (integer, no quotes)\n- **reasoning** (required): String with 1-2 concise sentences\n- **agreesWithHeuristic** (required): Boolean (true or false, no quotes)\n- **noActionExplanation** (conditional): String, ONLY if mode is \"NO_ACTION\"\n- **adoptedPlanSummary** (conditional): String, ONLY if mode is \"PLAN_ADOPT\"\n\n**Common Mistakes:**\n- Do NOT use \"DIRECT\" | \"TODO_LIST\" - choose ONE mode\n- Do NOT use <number> or <boolean> - use actual values\n- Do NOT include conditional fields unless their condition applies";
-/**
- * Classifier-specific personality guidelines.
- * These are lighter-weight than the main prompt personalities, focused on
- * how the classifier should reason and communicate its analysis.
- */
-export declare const CLASSIFIER_PERSONALITY_GUIDELINES: Record<PersonalityMode, string>;
-/**
- * Gets the classifier personality guidelines for a given mode.
- */
-export declare function getClassifierPersonalityGuidelines(mode: PersonalityMode): string;
-/**
- * System prompt for LLM-first classification.
- * This establishes the LLM's role as a task complexity analyzer.
- *
- * Contains all static content that can be cached:
- * - Role definition
- * - Execution mode definitions
- * - Decision guidelines
- * - Response format specification
- * - Personality guidelines (interpolated)
- * - Directory structure (interpolated)
- *
- * Variables:
- * - {{personalityGuidelines}} - Communication style based on personality mode
- * - {{directoryTree}} - Directory structure of the project
- */
-export declare const LLM_FIRST_CLASSIFICATION_SYSTEM_PROMPT = "You are a task complexity analyzer for a CLI assistant that handles both development tasks and productivity automation.\n\nYour role is to examine user requests and available context to determine the optimal execution approach.\n\n{{personalityGuidelines}}\n\n## Available External Tools\n{{availableMCPTools}}\n\n## Available Sub-Agents\n{{availableSubAgents}}\n\n## System Information\n{{systemInfo}}\n\n## Execution Modes\n\n**NO_ACTION** - Nothing needs to be done:\n- The requested feature/change is already fully implemented\n- The request doesn't make sense given the current context\n- **IMPORTANT**: Do NOT use NO_ACTION just because there are no relevant code files. If the request can be accomplished via available MCP tools, use DIRECT or TODO_LIST instead.\n- **NOT for requests to understand, explain, analyze, or explore** - those need DIRECT mode\n- When using this mode: provide clear explanation of why no action is needed, and offer a helpful follow-up question or tip to guide the user\n\n**DIRECT** - Execute immediately without planning:\n- Simple, focused tasks with clear implementation path\n- Examples for code: renaming a variable, fixing a typo, adding a log statement\n- Examples for external tools: creating a single meeting, sending an email, running a web search\n- **Requests to understand, explain, or analyze existing content**\n- Clear implementation path, no design decisions needed\n\n**TODO_LIST** - Create a simple task checklist:\n- Medium complexity tasks (3-6 files or multiple steps)\n- Clear requirements with straightforward implementation\n- No architectural changes, but multiple steps to track\n- Good for: well-defined features, multi-step workflows, sequential tasks\n\n**PLAN** - Requires detailed implementation plan:\n- Genuinely complex architectural changes\n- Multiple interdependent systems affected\n- Breaking changes or risky modifications\n- Complex coordination required across multiple components\n\n**PLAN_ADOPT** - User has already provided a structured plan:\n- Input contains numbered steps, ordered tasks, or a clear implementation sequence\n- Often comes from user approving/refining a previous LLM suggestion\n- Indicators: \"1.\", \"2.\", \"3.\" sequence, \"first... then... finally\", bullet points with specific actions, task lists\n- Your job: validate feasibility, enrich with technical details (file paths, IDs, dependencies), format to schema\n- PRESERVE user's task order and descriptions - do NOT regenerate or reorder unless dependencies are clearly wrong\n- Use this when the user's input already IS the plan, not just a request FOR a plan\n\n**SPAWN_AGENT** - Delegate to a specialized sub-agent:\n- Task matches the specialization of an available sub-agent (see Available Sub-Agents section above)\n- Sub-agent can handle the task more efficiently than the main agentic loop\n- Examples: codebase exploration, code review, debugging, planning\n- Benefits: reduced context usage, specialized expertise, isolated execution\n- When using this mode: specify which agent to spawn and provide a refined task description\n- The sub-agent will be invoked automatically via the spawn_task tool\n\n## Decision Guidelines\n\n### For Code Tasks:\n- **Don't be fooled by file count.** 20 files with the same simple change = DIRECT. 3 files with complex interdependencies = PLAN.\n- **Look at the actual code.** Are these files genuinely interconnected, or just keyword matches?\n- **When in doubt:** prefer TODO_LIST/DIRECT. The agent has AskUserQuestion tool for questions during execution.\n\n### For External Tool Tasks (MCP/automation):\n- If the task can be accomplished with available MCP tools, it's a valid task\n- Simple single-action tasks (create meeting, send email) = DIRECT\n- Multi-step workflows = TODO_LIST\n\n### General:\n- **Default to DIRECT or TODO_LIST** - The agent can ask questions during execution via AskUserQuestion tool as needed\n- **TODO_LIST** is great for medium-complexity tasks with clear requirements - simpler than PLAN but provides tracking\n- **PLAN is for genuine complexity**, not bureaucratic overhead\n- **PLAN_ADOPT saves time** when users provide structured input - don't regenerate what they've already defined\n\n## Response Format\n\nRespond with JSON conforming to the provided schema. Include only fields relevant to the chosen mode.\n\n## Project Directory Structure\n{{directoryTree}}";
-/**
- * User prompt template for LLM-first classification.
- *
- * Contains only the request-specific, dynamic data. All static instructions
- * (mode definitions, guidelines, response format) are in the system prompt
- * for better caching and token efficiency.
- *
- * Variables:
- * - {{userRequest}} - The user's request
- * - {{projectType}} - Type of project
- * - {{languages}} - Languages in the project
- * - {{fileCount}} - Total files gathered
- * - {{affectedAreas}} - Detected codebase areas
- */
-export declare const LLM_FIRST_CLASSIFICATION_PROMPT = "## User Request\n{{userRequest}}\n\n## Project Context\n- **Type:** {{projectType}}\n- **Languages:** {{languages}}\n- **Files gathered:** {{fileCount}}\n- **Affected Areas:** {{affectedAreas}}";
-/**
- * Prompt template for rollback analysis - analyzes rollback strategy.
- *
- * Variables:
- * - {{planSummary}} - Summary of the plan
- * - {{fileOperations}} - File operations performed
- * - {{commits}} - Git commits made
- */
-export declare const ROLLBACK_ANALYSIS_PROMPT = "\nAnalyze the rollback strategy for this implementation plan.\n\n## Plan Summary\n{{planSummary}}\n\n## File Operations\n{{fileOperations}}\n\n## Git Commits\n{{commits}}\n\n## Task\nDetermine the safest rollback approach:\n1. Order of operations to undo changes\n2. Data migration reversals if applicable\n3. Dependencies to consider\n4. Potential data loss warnings\n";
-/**
- * All workflow prompt templates exported as a collection.
- */
-export declare const WORKFLOW_PROMPTS: {
-    contextAnalysis: string;
-    complexityAssessment: string;
-    llmComplexityClassification: string;
-    llmFirstClassification: string;
-    llmFirstClassificationSystem: string;
-    classifierPersonalityGuidelines: Record<PersonalityMode, string>;
-    planGeneration: string;
-    verification: string;
-    rollbackAnalysis: string;
-};
-/**
- * Helper functions for workflow prompts
- */
-export declare const WorkflowPromptHelpers: {
-    /**
-     * Interpolates the context analysis prompt with variables.
-     */
-    buildContextAnalysisPrompt: (variables: {
-        userRequest: string;
-        projectType: string;
-        languages: string;
-        projectRoot: string;
-        directoryTree: string;
-    }) => string;
-    /**
-     * Interpolates the complexity assessment prompt with variables.
-     */
-    buildComplexityAssessmentPrompt: (variables: {
-        userRequest: string;
-        filesCount: string;
-        affectedAreas: string;
-        recentChanges: string;
-    }) => string;
-    /**
-     * Interpolates the plan generation prompt with variables.
-     */
-    buildPlanGenerationPrompt: (variables: {
-        userRequest: string;
-        contextSummary: string;
-        clarificationSummary: string;
-    }) => string;
-    /**
-     * Interpolates the verification prompt with variables.
-     */
-    buildVerificationPrompt: (variables: {
-        planSummary: string;
-        executionResults: string;
-        diffSummary: string;
-    }) => string;
-    /**
-     * Interpolates the rollback analysis prompt with variables.
-     */
-    buildRollbackAnalysisPrompt: (variables: {
-        planSummary: string;
-        fileOperations: string;
-        commits: string;
-    }) => string;
-    /**
-     * Interpolates the LLM complexity classification prompt with all factors.
-     */
-    buildLLMComplexityClassificationPrompt: (variables: {
-        userRequest: string;
-        filesAffected: string;
-        linesChanged: string;
-        requirementsClear: string;
-        contextSufficiency: string;
-        architecturalChange: string;
-        breakingChanges: string;
-        crossCuttingConcerns: string;
-        createsAbstractions: string;
-        requiresMigration: string;
-        implementationApproaches: string;
-        riskLevel: string;
-        heuristicMode: string;
-        heuristicConfidence: string;
-        heuristicReasoning: string;
-        affectedAreas: string;
-        relevantFiles: string;
-    }) => string;
-    /**
-     * Interpolates the LLM-first classification user prompt.
-     * Contains only dynamic data - all static instructions are in the system prompt.
-     */
-    buildLLMFirstClassificationPrompt: (variables: {
-        userRequest: string;
-        projectType: string;
-        languages: string;
-        fileCount: string;
-        affectedAreas: string;
-    }) => string;
-    /**
-     * Builds the complete system prompt for LLM-first classification.
-     * Includes personality guidelines for consistent tone with the main assistant.
-     */
-    /**
-     * Gathers current system information for injection into the prompt.
-     */
-    getSystemInfo(workingDirectory?: string): string;
-    /**
-     * Builds the complete system prompt for LLM-first classification.
-     * Includes personality guidelines for consistent tone with the main assistant.
-     */
-    buildClassifierSystemPrompt: (options: {
-        personalityMode?: PersonalityMode;
-        directoryTree?: string;
-        availableMCPTools?: string;
-        availableSubAgents?: string;
-        workingDirectory?: string;
-    }) => string;
-};
-//# sourceMappingURL=workflow.d.ts.map

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

@@ -1 +0,0 @@
-{"version":3,"file":"workflow.d.ts","sourceRoot":"","sources":["../../src/prompts/workflow.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AAGH,OAAO,KAAK,EAAE,eAAe,EAAE,MAAM,qBAAqB,CAAC;AAM3D;;;;;;;;;;GAUG;AACH,eAAO,MAAM,uBAAuB,ylBAsBnC,CAAC;AAEF;;;;;;;;GAQG;AACH,eAAO,MAAM,4BAA4B,miCAuCxC,CAAC;AAEF;;;;;;;GAOG;AACH,eAAO,MAAM,sBAAsB,ouCAgDlC,CAAC;AAEF;;;;;;;GAOG;AACH,eAAO,MAAM,mBAAmB,qeAoB/B,CAAC;AAEF;;;;;;;;;;;;;;;;;;;;;;;GAuBG;AACH,eAAO,MAAM,oCAAoC,08LAmHkB,CAAC;AAMpE;;;;GAIG;AACH,eAAO,MAAM,iCAAiC,EAAE,MAAM,CAAC,eAAe,EAAE,MAAM,CAmB7E,CAAC;AAEF;;GAEG;AACH,wBAAgB,kCAAkC,CAAC,IAAI,EAAE,eAAe,GAAG,MAAM,CAEhF;AAMD;;;;;;;;;;;;;;;GAeG;AACH,eAAO,MAAM,sCAAsC,6zIAkFjC,CAAC;AAEnB;;;;;;;;;;;;;GAaG;AACH,eAAO,MAAM,+BAA+B,sMAOJ,CAAC;AAEzC;;;;;;;GAOG;AACH,eAAO,MAAM,wBAAwB,sXAkBpC,CAAC;AAEF;;GAEG;AACH,eAAO,MAAM,gBAAgB;;;;;;;;;;CAU5B,CAAC;AAEF;;GAEG;AACH,eAAO,MAAM,qBAAqB;IAChC;;OAEG;4CACqC;QACtC,WAAW,EAAE,MAAM,CAAC;QACpB,WAAW,EAAE,MAAM,CAAC;QACpB,SAAS,EAAE,MAAM,CAAC;QAClB,WAAW,EAAE,MAAM,CAAC;QACpB,aAAa,EAAE,MAAM,CAAC;KACvB,KAAG,MAAM;IAEV;;OAEG;iDAC0C;QAC3C,WAAW,EAAE,MAAM,CAAC;QACpB,UAAU,EAAE,MAAM,CAAC;QACnB,aAAa,EAAE,MAAM,CAAC;QACtB,aAAa,EAAE,MAAM,CAAC;KACvB,KAAG,MAAM;IAEV;;OAEG;2CACoC;QACrC,WAAW,EAAE,MAAM,CAAC;QACpB,cAAc,EAAE,MAAM,CAAC;QACvB,oBAAoB,EAAE,MAAM,CAAC;KAC9B,KAAG,MAAM;IAEV;;OAEG;yCACkC;QACnC,WAAW,EAAE,MAAM,CAAC;QACpB,gBAAgB,EAAE,MAAM,CAAC;QACzB,WAAW,EAAE,MAAM,CAAC;KACrB,KAAG,MAAM;IAEV;;OAEG;6CACsC;QACvC,WAAW,EAAE,MAAM,CAAC;QACpB,cAAc,EAAE,MAAM,CAAC;QACvB,OAAO,EAAE,MAAM,CAAC;KACjB,KAAG,MAAM;IAEV;;OAEG;wDACiD;QAClD,WAAW,EAAE,MAAM,CAAC;QACpB,aAAa,EAAE,MAAM,CAAC;QACtB,YAAY,EAAE,MAAM,CAAC;QACrB,iBAAiB,EAAE,MAAM,CAAC;QAC1B,kBAAkB,EAAE,MAAM,CAAC;QAC3B,mBAAmB,EAAE,MAAM,CAAC;QAC5B,eAAe,EAAE,MAAM,CAAC;QACxB,oBAAoB,EAAE,MAAM,CAAC;QAC7B,mBAAmB,EAAE,MAAM,CAAC;QAC5B,iBAAiB,EAAE,MAAM,CAAC;QAC1B,wBAAwB,EAAE,MAAM,CAAC;QACjC,SAAS,EAAE,MAAM,CAAC;QAClB,aAAa,EAAE,MAAM,CAAC;QACtB,mBAAmB,EAAE,MAAM,CAAC;QAC5B,kBAAkB,EAAE,MAAM,CAAC;QAC3B,aAAa,EAAE,MAAM,CAAC;QACtB,aAAa,EAAE,MAAM,CAAC;KACvB,KAAG,MAAM;IAEV;;;OAGG;mDAC4C;QAC7C,WAAW,EAAE,MAAM,CAAC;QACpB,WAAW,EAAE,MAAM,CAAC;QACpB,SAAS,EAAE,MAAM,CAAC;QAClB,SAAS,EAAE,MAAM,CAAC;QAClB,aAAa,EAAE,MAAM,CAAC;KACvB,KAAG,MAAM;IAEV;;;OAGG;IACH;;OAEG;qCAC8B,MAAM,GAAG,MAAM;IAoChD;;;OAGG;2CACoC;QACrC,eAAe,CAAC,EAAE,eAAe,CAAC;QAClC,aAAa,CAAC,EAAE,MAAM,CAAC;QACvB,iBAAiB,CAAC,EAAE,MAAM,CAAC;QAC3B,kBAAkB,CAAC,EAAE,MAAM,CAAC;QAC5B,gBAAgB,CAAC,EAAE,MAAM,CAAC;KAC3B,KAAG,MAAM;CAkBX,CAAC"}