@exaudeus/workrail 0.1.9 → 0.2.1

package/dist/application/decorators/simple-output-decorator.js

@@ -33,7 +33,7 @@ The MCP server is STATELESS. You MUST send required data with each request:
 **EXAMPLE - Loop Context:**
 \`\`\`json
 {
-  "workflowId": "coding-task-workflow",
+  "workflowId": "coding-task-workflow-with-loops",
   "completedSteps": ["phase-1", "phase-2", "loop-step-1"],
   "context": {
     // Required: condition/template variables

package/dist/application/services/workflow-service.d.ts

@@ -34,6 +34,8 @@ export declare class DefaultWorkflowService implements WorkflowService {
         context?: ConditionContext;
     }>;
     private buildStepPrompt;
+    private collectConditionVars;
+    private collectEqualsValues;
     private findLoopStepById;
     validateStepOutput(workflowId: string, stepId: string, output: string): Promise<{
         valid: boolean;

package/dist/application/services/workflow-service.js

@@ -189,6 +189,61 @@ class DefaultWorkflowService {
             }
             return this.getNextStep(workflowId, completedSteps, loopStartSizeCheck.context);
         }
+        if (!nextStep) {
+            const remainingConditionalSteps = workflow.steps.filter((step) => {
+                if (completed.includes(step.id))
+                    return false;
+                if (loopBodySteps.has(step.id))
+                    return false;
+                return !!step.runCondition;
+            });
+            if (remainingConditionalSteps.length > 0) {
+                const requiredVars = new Set();
+                const allowedValues = {};
+                for (const step of remainingConditionalSteps) {
+                    const condition = step.runCondition;
+                    this.collectConditionVars(condition, requiredVars);
+                    this.collectEqualsValues(condition, allowedValues);
+                }
+                const issues = [];
+                for (const variableName of requiredVars) {
+                    const currentValue = enhancedContext[variableName];
+                    const allowed = allowedValues[variableName]
+                        ? Array.from(allowedValues[variableName])
+                        : [];
+                    if (currentValue === undefined || currentValue === null || currentValue === '') {
+                        if (allowed.length > 0) {
+                            issues.push(`Set '${variableName}' to one of: ${allowed.map(v => `'${v}'`).join(', ')}`);
+                        }
+                        else {
+                            issues.push(`Provide a value for '${variableName}'`);
+                        }
+                    }
+                    else if (allowed.length > 0) {
+                        const matchesExactly = allowed.some(v => v === String(currentValue));
+                        const matchesCaseInsensitive = allowed.some(v => v.toLowerCase() === String(currentValue).toLowerCase());
+                        if (!matchesExactly) {
+                            if (matchesCaseInsensitive) {
+                                issues.push(`Normalize casing for '${variableName}': use one of ${allowed.map(v => `'${v}'`).join(', ')} (current '${currentValue}')`);
+                            }
+                            else {
+                                issues.push(`Adjust '${variableName}' to one of: ${allowed.map(v => `'${v}'`).join(', ')} (current '${currentValue}')`);
+                            }
+                        }
+                    }
+                }
+                if (issues.length > 0) {
+                    return {
+                        step: null,
+                        guidance: {
+                            prompt: `No eligible step due to unmet conditions. Please update context:\n- ${issues.join('\n- ')}`
+                        },
+                        isComplete: false,
+                        context: enhancedContext
+                    };
+                }
+            }
+        }
         const isComplete = !nextStep;
         let finalPrompt = 'Workflow complete.';
         if (nextStep) {
@@ -232,6 +287,46 @@ class DefaultWorkflowService {
         }
         return finalPrompt;
     }
+    collectConditionVars(condition, sink) {
+        if (!condition || typeof condition !== 'object')
+            return;
+        if (typeof condition.var === 'string' && condition.var.length > 0) {
+            sink.add(condition.var);
+        }
+        if (Array.isArray(condition.and)) {
+            for (const sub of condition.and)
+                this.collectConditionVars(sub, sink);
+        }
+        if (Array.isArray(condition.or)) {
+            for (const sub of condition.or)
+                this.collectConditionVars(sub, sink);
+        }
+        if (condition.not)
+            this.collectConditionVars(condition.not, sink);
+    }
+    collectEqualsValues(condition, sink) {
+        if (!condition || typeof condition !== 'object')
+            return;
+        if (typeof condition.var === 'string' && Object.prototype.hasOwnProperty.call(condition, 'equals')) {
+            const variableName = condition.var;
+            const value = condition.equals;
+            if (value !== undefined && value !== null) {
+                if (!sink[variableName])
+                    sink[variableName] = new Set();
+                sink[variableName].add(String(value));
+            }
+        }
+        if (Array.isArray(condition.and)) {
+            for (const sub of condition.and)
+                this.collectEqualsValues(sub, sink);
+        }
+        if (Array.isArray(condition.or)) {
+            for (const sub of condition.or)
+                this.collectEqualsValues(sub, sink);
+        }
+        if (condition.not)
+            this.collectEqualsValues(condition.not, sink);
+    }
     findLoopStepById(workflow, stepId) {
         const step = workflow.steps.find(s => s.id === stepId);
         return step && (0, workflow_types_1.isLoopStep)(step) ? step : null;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@exaudeus/workrail",
-  "version": "0.1.9",
+  "version": "0.2.1",
   "description": "MCP server for structured workflow orchestration and step-by-step task guidance",
   "license": "MIT",
   "bin": {

package/spec/mcp-api-v1.0.md

@@ -175,7 +175,7 @@ Retrieves workflow information with configurable detail level. Supports progress
   "jsonrpc": "2.0",
   "id": 2,
   "result": {
-    "id": "coding-task-workflow",
+    "id": "coding-task-workflow-with-loops",
     "name": "Excellent Adaptive Coding Workflow",
     "description": "A comprehensive workflow for AI-assisted coding",
     "version": "0.1.0",
@@ -201,7 +201,7 @@ Retrieves workflow information with configurable detail level. Supports progress
   "jsonrpc": "2.0",
   "id": 2,
   "result": {
-    "id": "coding-task-workflow",
+    "id": "coding-task-workflow-with-loops",
     "name": "Excellent Adaptive Coding Workflow",
     "description": "A comprehensive workflow for AI-assisted coding",
     "version": "0.1.0",

package/workflows/coding-task-workflow-with-loops.json

@@ -431,7 +431,7 @@
                 {
                     "id": "phase-6-prep",
                     "title": "PREP: Prepare for Step {{currentStepNumber + 1}}",
-                    "prompt": "**PREPARATION PHASE for Step {{currentStepNumber + 1}}/{{totalImplementationSteps}}**\n\nBefore implementing this step, you must first PREPARE:\n\n1. **Read implementation_plan.md** and locate step #{{currentStepNumber + 1}}\n2. **Extract step details**: Note the title, description, and expected outputs\n3. **Confirm prerequisites**: Verify the previous step (if any) was completed correctly\n4. **Validate current state**: Ensure the plan for this step is still valid in the current codebase\n5. **List requirements**: Identify all required inputs, files, or dependencies\n\n**BRANCH SETUP (first iteration only):** If this is the first implementation step ({{currentStepNumber}} === 0):\n- Check git availability with 'git status'\n- If available, create feature branch: 'git checkout -b wip-[unique-task-id]'\n- Track the featureBranch variable for later use\n- If git unavailable: Skip branching, log in CONTEXT.md\n\n**CRITICAL CONTEXT OPTIMIZATION:**\nWhen calling workflow_next after this step, send ONLY:\n- currentStepNumber and totalImplementationSteps\n- Any NEW variables you created (like featureBranch)\n- DO NOT send: arrays, plans, _loopState, _currentLoop, unchanged data\n\n**Do not proceed if anything is unclear or missing.**",
+                    "prompt": "**PREPARATION PHASE for Step {{currentStepNumber + 1}}/{{totalImplementationSteps}}**\n\nBefore implementing this step, you must first PREPARE:\n\n1. **Read implementation_plan.md** and locate step #{{currentStepNumber + 1}}\n2. **Extract step details**: Note the title, description, and expected outputs\n3. **Confirm prerequisites**: Verify the previous step (if any) was completed correctly\n4. **Validate current state**: Ensure the plan for this step is still valid in the current codebase\n5. **List requirements**: Identify all required inputs, files, or dependencies\n\n**BRANCH SETUP (first iteration only):** If this is the first implementation step ({{currentStepNumber}} === 0):\n- Check git availability with 'git status'\n- If available, create feature branch: 'git checkout -b wip-[unique-task-id]'\n- Track the featureBranch variable for later use\n- If git unavailable: Skip branching, log in CONTEXT.md\n\n**Do not proceed if anything is unclear or missing.**",
                     "agentRole": "You are preparing to implement a specific step from the plan. Be meticulous in verifying all prerequisites are met before proceeding.",
                     "guidance": [
                         "This is step {{currentStepNumber + 1}} of {{totalImplementationSteps}} total implementation steps",
@@ -444,7 +444,7 @@
                 {
                     "id": "phase-6-implement",
                     "title": "IMPLEMENT: Execute Step {{currentStepNumber + 1}}",
-                    "prompt": "**IMPLEMENTATION PHASE for Step {{currentStepNumber + 1}}/{{totalImplementationSteps}}**\n\nNow implement the step you just prepared for:\n\n**Instructions:**\n1. Re-read step #{{currentStepNumber + 1}} from implementation_plan.md\n2. Focus only on this single step\n3. useTools() to make code changes\n4. Follow quality standards\n5. Adapt to unexpected discoveries\n6. createFile() for ALL code changes\n\n**Remember:** applyUserRules() and matchPatterns() throughout.\n\n**Progress Tracking:**\n- This is step {{currentStepNumber + 1}} of {{totalImplementationSteps}}\n- If we've done > 20 steps total, pause for user intervention\n\n**CONTEXT UPDATES:** If this is every 3rd step ({{currentStepNumber + 1}} % 3 === 0):\n- Update CONTEXT.md\n- addResumptionJson(phase-6-implement)\n- updateDecisionLog()\n- List files modified with line ranges\n\n**CONTEXT OPTIMIZATION for workflow_next:**\nSend ONLY: currentStepNumber, totalImplementationSteps, filesCreated (new), any other NEW data\nDO NOT send: arrays, plans, _loopState, unchanged fields",
+                    "prompt": "**IMPLEMENTATION PHASE for Step {{currentStepNumber + 1}}/{{totalImplementationSteps}}**\n\nNow implement the step you just prepared for:\n\n**Instructions:**\n1. Re-read step #{{currentStepNumber + 1}} from implementation_plan.md\n2. Focus only on this single step\n3. useTools() to make code changes\n4. Follow quality standards\n5. Adapt to unexpected discoveries\n6. createFile() for ALL code changes\n\n**Remember:** applyUserRules() and matchPatterns() throughout.\n\n**Progress Tracking:**\n- This is step {{currentStepNumber + 1}} of {{totalImplementationSteps}}\n- If we've done > 20 steps total, pause for user intervention\n\n**CONTEXT UPDATES:** If this is every 3rd step ({{currentStepNumber + 1}} % 3 === 0):\n- Update CONTEXT.md\n- addResumptionJson(phase-6-implement)\n- updateDecisionLog()\n- List files modified with line ranges\n\n",
                     "agentRole": "You are implementing a specific step from the approved plan. Focus on precise execution while maintaining code quality.",
                     "guidance": [
                         "Implement only what this step requires",
@@ -456,7 +456,7 @@
                 {
                     "id": "phase-6-verify",
                     "title": "VERIFY: Validate Step {{currentStepNumber + 1}}",
-                    "prompt": "**VERIFICATION PHASE for Step {{currentStepNumber + 1}}/{{totalImplementationSteps}}**\n\nVerify the implementation is complete and correct:\n\n**Required:** verifyImplementation()\n\n**COMMIT Decision (if all passes):**\n- checkAutomation(commit)\n- gitCommit(type, scope: description)\n- If git unavailable: Log in CONTEXT.md\n\n**FAILURE PROTOCOL:** If verification fails after 2 attempts:\n1. Do not try a third time\n2. Fall back to alternative tools\n3. updateDecisionLog() with failure details\n4. Present summary and recommendations\n5. Set 'verificationFailed' context variable to true\n\n**CONTEXT OPTIMIZATION:**\nFor workflow_next, send ONLY what changed: currentStepNumber, verificationResult, verificationFailed (if true)\nNEVER send back the full context!",
+                    "prompt": "**VERIFICATION PHASE for Step {{currentStepNumber + 1}}/{{totalImplementationSteps}}**\n\nVerify the implementation is complete and correct:\n\n**Required:** verifyImplementation()\n\n**COMMIT Decision (if all passes):**\n- checkAutomation(commit)\n- gitCommit(type, scope: description)\n- If git unavailable: Log in CONTEXT.md\n\n**FAILURE PROTOCOL:** If verification fails after 2 attempts:\n1. Do not try a third time\n2. Fall back to alternative tools\n3. updateDecisionLog() with failure details\n4. Present summary and recommendations\n5. Set 'verificationFailed' context variable to true\n\n",
                     "agentRole": "You are verifying the implementation meets all quality standards. Be thorough but respect failure bounds.",
                     "guidance": [
                         "All three verification steps must pass",

package/spec/examples/coding-task-workflow.json

@@ -1,160 +0,0 @@
-{
-    "id": "coding-task-workflow",
-    "name": "Excellent Adaptive Coding Workflow with Devil's Advocate Review",
-    "version": "0.0.1",
-    "description": "A comprehensive and resilient workflow for AI-assisted coding. It adaptively sizes tasks, performs a critical self-review of its own plans, provides efficiency options, enforces closed-loop validation, and defines a robust protocol for handling failures.",
-    "preconditions": [
-        "User has a clear task description (e.g., from Jira, a dev doc, or a BRD).",
-        "The agent has access to necessary tools like `grep`, file readers/editors, and a terminal for commands.",
-        "The agent has access to the relevant codebase files."
-    ],
-    "metaGuidance": [
-        "This workflow follows the PREP -> IMPLEMENT -> VERIFY pattern for each step in the plan.",
-        "Human approval is required after the Devil's Advocate review and before final completion.",
-        "Each implementation step should be a small, logical, and committable chunk of work.",
-        "The agent should never guess or assume. Always ask for clarification or use tools to find missing information.",
-        "Maintain existing coding conventions and architectural patterns found in the codebase."
-    ],
-    "steps": [
-        {
-            "id": "phase-0-intelligent-triage",
-            "title": "Phase 0: Intelligent Task Triage & Complexity Analysis",
-            "prompt": "**ANALYZE**: Evaluate the provided task for complexity indicators:\n\n**Small Path Indicators:**\n- Single function changes or minor refactoring\n- Clear bug fixes with obvious solutions\n- Simple configuration changes\n- Low risk of side effects\n- Well-defined, narrow scope\n\n**Medium Path Indicators:**\n- Multi-file changes or moderate features\n- Standard development work\n- Some unknowns but manageable scope\n- Moderate complexity with clear boundaries\n- Requires planning but not architectural analysis\n\n**Large Path Indicators:**\n- Architectural changes or major features\n- Unfamiliar codebase areas\n- High complexity or significant risk\n- Multiple system interactions\n- Requires deep analysis and careful planning\n\n**IMPLEMENT**: \n1. Analyze the task description for the above indicators\n2. Recommend a complexity level (Small/Medium/Large) with detailed reasoning\n3. Set the taskComplexity context variable\n4. Ask user if they agree or want to override your classification\n5. For Medium tasks, ask: \"Would you like optional deep codebase analysis?\" (sets requestDeepAnalysis context variable)\n\n**VERIFY**: Confirm the complexity classification and any optional analysis preferences before proceeding.",
-            "guidance": [
-                "Be thorough in your analysis - this determines the entire workflow path",
-                "Consider both technical complexity and business risk",
-                "When in doubt, err on the side of more thorough analysis (higher complexity)",
-                "Always allow human override of your classification",
-                "Set context variables that will be used for conditional step execution"
-            ],
-            "requireConfirmation": true
-        },
-        {
-            "id": "phase-1-scoping",
-            "runCondition": {
-                "var": "taskComplexity",
-                "not_equals": "Small"
-            },
-            "title": "Phase 1: Task Briefing & Scope Definition",
-            "prompt": "Your first goal is to understand the task. Analyze the following request, summarize your understanding, ask clarifying questions, and assess which parts of the codebase are relevant.\n\n**Task Description:**\n[User inserts detailed task description here]\n\n**Key Objectives & Success Criteria:**\n[User lists specific, measurable success criteria here]\n\n**Scope and Constraints:**\n[User defines boundaries or areas to avoid here]\n\nFinally, based on your analysis, perform a sanity check on the initial complexity sizing. If you believe the classification is incorrect, state your reasoning and ask for confirmation before proceeding. For example: 'You classified this as Medium, but my analysis shows it impacts several core architectural components. I recommend we upgrade to the Large path to perform a Deep Analysis. Do you agree?'",
-            "guidance": [
-                "Provide a complete task description. Vague requests will lead to poor plans and wasted effort.",
-                "This step is automatically skipped for Small tasks based on the complexity classification"
-            ]
-        },
-        {
-            "id": "phase-1b-deep-analysis-mandatory",
-            "runCondition": {
-                "var": "taskComplexity",
-                "equals": "Large"
-            },
-            "title": "Phase 1b: Mandatory Deep Codebase Analysis",
-            "prompt": "Your goal is to become an expert on the attached codebase. This deep analysis is mandatory for Large tasks due to their complexity and risk. Your analysis must include:\n1.  **Architecture:** Main modules, layers, and patterns.\n2.  **Key Concepts:** Core models, conventions, and important components.\n3.  **Execution Flow:** Trace major features or entry points.\n4.  **Code Quality Assessment:** Note maintainability, readability, or coupling issues.\n5.  **Testing Strategy:** Describe how the code is tested.\n6.  **Opportunities:** Suggest refactorings or improvements.\n\nProvide summaries and code examples to illustrate your findings. Be exhaustive, as if preparing onboarding documentation for a senior engineer.",
-            "askForFiles": true,
-            "guidance": [
-                "This step is mandatory for Large tasks due to their complexity and risk",
-                "Ensure all relevant source files are attached or accessible to the agent before running this step",
-                "Be thorough - this analysis will inform the entire implementation strategy"
-            ]
-        },
-        {
-            "id": "phase-1b-deep-analysis-optional",
-            "runCondition": {
-                "and": [
-                    {
-                        "var": "taskComplexity",
-                        "equals": "Medium"
-                    },
-                    {
-                        "var": "requestDeepAnalysis",
-                        "equals": true
-                    }
-                ]
-            },
-            "title": "Phase 1b: Optional Deep Codebase Analysis",
-            "prompt": "You requested optional deep analysis for this Medium task. Your goal is to become an expert on the attached codebase. Your analysis must include:\n1.  **Architecture:** Main modules, layers, and patterns.\n2.  **Key Concepts:** Core models, conventions, and important components.\n3.  **Execution Flow:** Trace major features or entry points.\n4.  **Code Quality Assessment:** Note maintainability, readability, or coupling issues.\n5.  **Testing Strategy:** Describe how the code is tested.\n6.  **Opportunities:** Suggest refactorings or improvements.\n\nProvide summaries and code examples to illustrate your findings. Be exhaustive, as if preparing onboarding documentation for a senior engineer.",
-            "askForFiles": true,
-            "guidance": [
-                "This optional analysis was requested for a Medium task",
-                "Ensure all relevant source files are attached or accessible to the agent before running this step",
-                "Focus on areas most relevant to the current task"
-            ]
-        },
-        {
-            "id": "phase-2-planning",
-            "runCondition": {
-                "var": "taskComplexity",
-                "not_equals": "Small"
-            },
-            "title": "Phase 2: Create Detailed Implementation Plan",
-            "prompt": "Your goal is to produce a thorough and actionable plan of attack. Do not write any code. Your plan must be detailed, broken into committable phases, and justified.\n\nYour plan must include these sections:\n1.  **Goal Clarification:** Your understanding of the goal, assumptions, and success criteria.\n2.  **Impact Assessment:** Affected codebase parts, dependencies, and risks.\n3.  **Implementation Strategy:** A list of discrete, actionable steps. Each step must detail the task, its rationale, inputs, and outputs.\n4.  **Final Review Checklist:** A specific checklist of items that must be verified to consider this entire task complete. This will be used in the final review phase.\n\nPresent this as a formal proposal.",
-            "guidance": [
-                "The agent will now proceed to critique its own plan in the next step. Withhold your final approval until after that critique.",
-                "This step is automatically skipped for Small tasks based on the complexity classification"
-            ]
-        },
-        {
-            "id": "phase-2b-devil-advocate-review",
-            "runCondition": {
-                "var": "taskComplexity",
-                "not_equals": "Small"
-            },
-            "title": "Phase 2b: Devil's Advocate Plan Review",
-            "prompt": "Your new goal is to act as a skeptical but fair senior principal engineer. Your task is to perform a 'devil's advocate' review of the implementation plan you just created in Phase 2. The objective is not to discard the plan, but to rigorously stress-test it and make it stronger. Your critique must be balanced and evidence-based.\n\nAnalyze the plan through the following lenses. For every point you make (positive or negative), you must cite specific evidence from the plan, the codebase, or the initial task description.\n\n1.  **Hidden Assumptions:** What assumptions does this plan make about the codebase, user behavior, or existing data that might be incorrect?\n2.  **Potential Risks & Unintended Side Effects:** What is the biggest risk of this plan? Could it impact performance, security, or another feature in a negative way?\n3.  **Overlooked Complexities or Edge Cases:** What specific edge cases (e.g., empty states, invalid inputs, race conditions) does the plan fail to explicitly address?\n4.  **Alternative Approaches:** Briefly propose at least one alternative technical approach. What are the pros and cons of the alternative versus the current plan?\n5.  **Plan Strengths:** To ensure a balanced review, explicitly state the strongest parts of the plan. What aspects are well-thought-out and likely to succeed?\n\nConclude with a balanced summary. If you found issues, provide concrete suggestions for how to amend the plan. Finally, give a confidence score (1-10) for the plan *if* your suggestions are implemented.",
-            "guidance": [
-                "This is a critical thinking step. The agent's goal is to find weaknesses in its *own* prior work to improve it. This is a sign of a high-functioning process.",
-                "Evaluate the agent's points. Not all 'risks' it identifies may be realistic. Use your judgment to decide which suggestions to incorporate into the plan.",
-                "After this review, you can ask the agent to create a final, amended version of the plan before you give your final approval to proceed with implementation.",
-                "This step is automatically skipped for Small tasks based on the complexity classification"
-            ],
-            "requireConfirmation": true
-        },
-        {
-            "id": "phase-3-iterative-implementation",
-            "title": "Phase 3: Iterative Implementation (PREP -> IMPLEMENT -> VERIFY)",
-            "prompt": "The implementation phase has now begun. **Please provide me with the next single step from the approved plan.** If we are on the 'Small' path, provide a single, clear implementation instruction.\n\nI will execute *only* that step using the PREP -> IMPLEMENT -> VERIFY cycle defined in the guidance below, and then await your command for the subsequent step. This process will repeat until all steps are complete.",
-            "guidance": [
-                "**Efficiency Tip:** For high-confidence plans, you may provide multiple step instructions at once. I will execute them sequentially, performing the P->I->V cycle for each, and will only pause to ask for input if I encounter a verification failure or ambiguity.",
-                "**PREP:** Before implementing each step, you must first PREPARE. Re-read the step's description, confirm the previous step was completed correctly, verify the plan for this step is still valid in the current codebase, and list all required inputs or files. Do not proceed if anything is unclear.",
-                "**IMPLEMENT:** After preparation is confirmed, you will IMPLEMENT the step. Focus only on this single step. Use your tools to make the necessary code changes, adhering to all quality standards. Provide a commit message upon completion.",
-                "**VERIFY:** Immediately after implementation, you must VERIFY your work. Your verification for this step **is not complete until you have**:\n1.  **Written necessary unit/integration tests** for the new logic.\n2.  **Run the full test suite** to ensure no regressions were introduced.\n3.  **Performed a critical self-review** of the changes against the plan, checking for code quality, side effects, and architectural alignment.\n\n**Failure Protocol:** If a verification failure cannot be resolved after two attempts, you must halt. Do not try a third time. Instead, present a summary of the problem, detail your failed attempts, and recommend a course of action to the user (e.g., 'revert this step and re-plan', 'request more information', 'proceed with a known issue')."
-            ]
-        },
-        {
-            "id": "phase-4-final-review",
-            "title": "Phase 4: Final Review & Completion",
-            "prompt": "All planned steps have been implemented and verified. Your final goal is to perform a holistic review by validating the work against the **'Final Review Checklist'** created and approved during Phase 2.\n\nFor each item on that checklist, provide a confirmation and evidence that it has been met. Conclude with a summary of any potential follow-ups or new dependencies to note.",
-            "guidance": [
-                "This is the final quality check. Ensure the agent's summary and checklist validation align with your understanding of the completed work."
-            ],
-            "requireConfirmation": true,
-            "validationCriteria": [
-                {
-                    "type": "contains",
-                    "value": "checklist",
-                    "message": "Should reference the final review checklist"
-                },
-                {
-                    "type": "contains",
-                    "value": "complete",
-                    "message": "Should confirm completion of all requirements"
-                },
-                {
-                    "type": "length",
-                    "min": 150,
-                    "condition": {
-                        "var": "taskComplexity",
-                        "not_equals": "Small"
-                    },
-                    "message": "Complex tasks require detailed final review"
-                },
-                {
-                    "type": "regex",
-                    "pattern": "(?!.*TODO)",
-                    "message": "Should not contain TODO items"
-                }
-            ],
-            "hasValidation": true
-        }
-    ]
-}