@exaudeus/workrail 0.1.3 → 0.1.4

package/package.json

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

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

@@ -146,23 +146,28 @@
             },
             "loop": {
                 "type": "for",
-                "count": 3,
+                "count": 4,
                 "maxIterations": 4,
                 "iterationVar": "analysisStep"
             },
             "body": [
                 {
                     "id": "phase-1-sub-analysis",
-                    "title": "Analysis #{{analysisStep}}: {{analysisStep === 1 ? 'Structure' : analysisStep === 2 ? 'Modules' : 'Dependencies'}}",
-                    "prompt": "{{analysisStep === 1 ? '**STEP 1: STRUCTURAL MAPPING**\\n\\nBuild on phase-0c overview, dive deeper into structure:\\n\\n1. Module organization (packages/services)\\n2. Core components (controllers/services/models)\\n3. Architectural patterns from overview\\n4. File naming conventions\\n5. Code organization\\n\\n**Actions:** useTools() with list_dir, grep_search (class/interface/export), read 2-3 files\\n\\n**Output (400 words):**\\n- Structure summary\\n- User rules alignment\\n- Areas for next steps\\n\\nupdateDecisionLog() with 3-5 key files' : analysisStep === 2 ? '**STEP 2: TASK-RELEVANT MODULES**\\n\\nFocus on task-specific modules:\\n\\n1. Target areas from mapping\\n2. Core business logic\\n3. Data models (interfaces/types/schemas)\\n4. API contracts\\n5. Pattern implementation\\n\\n**Actions:** useTools() and matchPatterns() with codebase_search, read complete files (with imports), trace flows\\n\\n**Output (400 words):**\\n- Module responsibilities\\n- Patterns to match\\n- Integration points\\n\\nupdateDecisionLog() with core logic files' : '**STEP 3: DEPENDENCIES & FLOWS**\\n\\nTrace dependencies and execution:\\n\\n1. Import mapping\\n2. Data flow tracing\\n3. Integration points\\n4. Side effects\\n5. Testing patterns\\n\\n**Actions:** useTools() to follow imports, find test files, trace error handling\\n\\n**Output (400 words):**\\n- Dependency map\\n- Integration challenges\\n- Testing strategies\\n- Risk indicators\\n\\nupdateDecisionLog() with dependencies and test approaches'}}",
-                    "agentRole": "You are conducting focused analysis step {{analysisStep}} of 3. Your expertise lies in {{analysisStep === 1 ? 'understanding code structure and organization' : analysisStep === 2 ? 'identifying and analyzing task-specific components' : 'tracing dependencies and system flows'}}. Use tools extensively and never make assumptions.",
+                    "title": "Analysis Step {{analysisStep}}/4",
+                    "prompt": "{{analysisStep === 1 ? '**STEP 1: STRUCTURAL MAPPING**\\n\\nBuild on phase-0c overview, dive deeper into structure:\\n\\n1. Module organization (packages/services)\\n2. Core components (controllers/services/models)\\n3. Architectural patterns from overview\\n4. File naming conventions\\n5. Code organization\\n\\n**Actions:** useTools() with list_dir, grep_search (class/interface/export), read 2-3 files\\n\\n**Output (400 words):**\\n- Structure summary\\n- User rules alignment\\n- Areas for next steps\\n\\nupdateDecisionLog() with 3-5 key files' : analysisStep === 2 ? '**STEP 2: TASK-RELEVANT MODULES**\\n\\nFocus on task-specific modules:\\n\\n1. Target areas from mapping\\n2. Core business logic\\n3. Data models (interfaces/types/schemas)\\n4. API contracts\\n5. Pattern implementation\\n\\n**Actions:** useTools() and matchPatterns() with codebase_search, read complete files (with imports), trace flows\\n\\n**Output (400 words):**\\n- Module responsibilities\\n- Patterns to match\\n- Integration points\\n\\nupdateDecisionLog() with core logic files' : analysisStep === 3 ? '**STEP 3: DEPENDENCIES & FLOWS**\\n\\nTrace dependencies and execution:\\n\\n1. Import mapping\\n2. Data flow tracing\\n3. Integration points\\n4. Side effects\\n5. Testing patterns\\n\\n**Actions:** useTools() to follow imports, find test files, trace error handling\\n\\n**Output (400 words):**\\n- Dependency map\\n- Integration challenges\\n- Testing strategies\\n- Risk indicators\\n\\nupdateDecisionLog() with dependencies and test approaches' : '**STEP 4: PATTERN DISCOVERY**\\n\\nIdentify established patterns relevant to the task type. Analyze if this is a pattern-heavy task (tests, telemetry, logging, APIs, UI components).\\n\\n**Actions:** useTools() extensively - codebase_search for concepts, grep_search for pattern markers, read_file for full examples\\n\\n**Output (400 words):**\\n- Pattern types discovered\\n- Reference implementations (with file paths)\\n- Key conventions to follow\\n- Pattern alignment recommendations\\n\\nupdateDecisionLog() with pattern templates and reference files'}}",
+                    "agentRole": "You are conducting focused analysis step {{analysisStep}} of 4. Your expertise lies in {{analysisStep === 1 ? 'understanding code structure and organization' : analysisStep === 2 ? 'identifying and analyzing task-specific components' : analysisStep === 3 ? 'tracing dependencies and system flows' : 'discovering and documenting established implementation patterns for the specific task type'}}. Use tools extensively and never make assumptions.",
                     "guidance": [
-                        "This is step {{analysisStep}} of a 3-step analysis process",
+                        "This is step {{analysisStep}} of a 4-step analysis process",
                         "Each step builds on the previous findings",
                         "Use tools liberally - verify everything",
                         "Update the Decision Log with key discoveries",
                         "Respect word limits to prevent context bloat",
-                        "Note alignment/conflicts with user rules"
+                        "Note alignment/conflicts with user rules",
+                        "{{analysisStep === 4 ? 'TASK TYPE ANALYSIS: Determine if this is adding tests (find test utilities, mocking patterns), telemetry/analytics (find tracking implementations, event schemas), logging/monitoring (find log formats, monitoring integrations), API endpoints (find route patterns, validation, error handling), UI components (find component patterns, styling conventions), or other pattern-heavy work' : ''}}",
+                        "{{analysisStep === 4 ? 'PATTERN SEARCH STRATEGY: Use codebase_search with queries like \"How is [telemetry|testing|logging|API] implemented?\". Use grep_search for pattern markers (e.g., track, analytics, test, describe, log). Find 3-5 reference implementations similar to your task. Look for shared utilities, helpers, or base classes. Check for pattern documentation in README or docs' : ''}}",
+                        "{{analysisStep === 4 ? 'PATTERN EXTRACTION: Document file structure and naming conventions, common imports and dependencies, implementation approach (functional vs class-based), error handling patterns, configuration patterns, and testing approach for this type of feature' : ''}}",
+                        "{{analysisStep === 4 ? 'PATTERN VALIDATION: List discovered patterns with file references. Note any conflicting patterns or multiple approaches. Ask user: \"Found these pattern examples: [list files]. Should I follow these patterns, or are there other preferred examples?\" Set establishedPatterns context variable' : ''}}",
+                        "{{analysisStep === 4 ? 'FOCUS ON REUSABILITY: Patterns help avoid reinventing the wheel. Look especially for utility functions, base classes, shared components, or established conventions that should be followed' : ''}}"
                     ],
                     "requireConfirmation": false
                 }