@hyperdrive.bot/bmad-workflow 1.0.3 → 1.0.6

package/dist/services/orchestration/task-decomposition-service.js

@@ -159,70 +159,38 @@ ${options.contextFiles.map((f) => `- ${f}`).join('\n')}
 `;
         }
         // Add output format instructions (varies based on story format mode)
-        prompt += options.storyFormat ? `## OUTPUT FORMAT - STORY MODE
-You MUST output tasks as BMAD-formatted STORIES with proper structure.
-Output ONLY valid YAML. DO NOT include markdown code fences or any other text.
-
-Each task will become a full story with:
-- Story ID: ${options.storyPrefix}-<number> (e.g., ${options.storyPrefix}-001, ${options.storyPrefix}-002)
-- User story format: "As a... I want... so that..."
-- Acceptance Criteria
-- Tasks/Subtasks breakdown
-- Dev Notes with testing info
-
-\`\`\`yaml
+        prompt += options.storyFormat ? `## OUTPUT FORMAT - STORY MODE - CRITICAL INSTRUCTIONS
+
+**YOUR RESPONSE MUST BE PURE YAML ONLY.**
+- Do NOT write any explanation, summary, or commentary
+- Do NOT use markdown code fences
+- Start your response DIRECTLY with "masterPrompt: |"
+
+Each task becomes a BMAD story with user story format, acceptance criteria, and tasks breakdown.
+
+The YAML structure MUST be:
+
 masterPrompt: |
-  A reusable prompt template that applies to all stories.
-  Include best practices, coding standards, and common guidelines for implementing these stories.
+  A reusable prompt template for all stories.
+  Include best practices and coding standards.
 
 tasks:
   - id: ${options.storyPrefix}-001
     title: "Clear, specific story title"
     description: "High-level description of what this story delivers"
     estimatedMinutes: 10
-    dependencies: []  # Array of story IDs that must complete first
+    dependencies: []
     parallelizable: true
     agentType: "dev"
-    targetFiles:  # Optional: specific files this story operates on
+    targetFiles:
       - "path/to/file.js"
     prompt: |
-      Create a story following BMAD story format:
-
-      # Story ${options.storyPrefix}-001: [Title]
-
-      ## Status
-      Draft
-
-      ## Story
-      **As a** [role/persona],
-      **I want** [capability/feature],
-      **so that** [benefit/value]
-
-      ## Acceptance Criteria
-      1. [Specific, testable criterion]
-      2. [Another criterion]
-      3. [Another criterion]
-
-      ## Tasks / Subtasks
-      - [ ] Task 1: [Description] (AC: #1)
-        - [ ] Subtask 1.1: [Specific action]
-        - [ ] Subtask 1.2: [Specific action]
-      - [ ] Task 2: [Description] (AC: #2)
-        - [ ] Subtask 2.1: [Specific action]
-
-      ## Dev Notes
-      [Relevant architecture info, integration points, file locations]
-
-      ### Testing
-      - Test file location: [path]
-      - Test standards: [requirements]
-      - Testing frameworks: [tools being used]
-      - Specific requirements: [any special test needs]
-
-      ## Change Log
-      | Date | Version | Description | Author |
-      |------|---------|-------------|--------|
-      | [Date] | 1.0 | Story created | AI Agent |
+      Create a story following BMAD story format with:
+      - Status: Draft
+      - User story (As a... I want... so that...)
+      - Acceptance Criteria (numbered, testable)
+      - Tasks/Subtasks with AC references
+      - Dev Notes with testing info
     outputFile: "${sessionDir}/stories/${options.storyPrefix}-001.md"
 
   - id: ${options.storyPrefix}-002
@@ -233,40 +201,25 @@ tasks:
     parallelizable: false
     agentType: "dev"
     prompt: |
-      [Story-formatted prompt as above]
+      Story-formatted prompt
     outputFile: "${sessionDir}/stories/${options.storyPrefix}-002.md"
 
-  # ... more tasks (as stories)
-\`\`\`
+## STORY MODE RULES
+- Task IDs: ${options.storyPrefix}-001, ${options.storyPrefix}-002, etc.
+- Output files: ${sessionDir}/stories/
+${options.perFile ? '- **CRITICAL**: Create one story per file (per-file mode is ON)' : ''}
 
-**CRITICAL FOR STORY MODE:**
-- Task IDs MUST be story IDs: ${options.storyPrefix}-001, ${options.storyPrefix}-002, etc.
-- Output files MUST go to stories/ directory
-- Prompts MUST generate full story structure (not simple task outputs)
-- Each story must have user story format, acceptance criteria, and tasks breakdown
+**REMEMBER: Your ENTIRE response must be valid YAML starting with "masterPrompt: |" - NO other text!**
+` : `## OUTPUT FORMAT - CRITICAL INSTRUCTIONS
 
-## IMPORTANT RULES
-1. Each story ID must be unique
-2. Dependencies must reference valid story IDs
-3. Circular dependencies are not allowed
-4. Stories with no dependencies can run immediately
-5. Stories with the same dependencies can run in parallel (if parallelizable: true)
-6. All file paths in outputFile should use the session directory: ${sessionDir}/stories/
-${options.perFile ? '7. **CRITICAL**: Create one story per file for the main work (per-file mode is ON)' : ''}
+**YOUR RESPONSE MUST BE PURE YAML ONLY.**
+- Do NOT write any explanation, summary, or commentary
+- Do NOT use markdown code fences (\`\`\`yaml or \`\`\`)
+- Do NOT write "Here's the task decomposition..." or similar
+- Start your response DIRECTLY with "masterPrompt: |"
 
-## EXAMPLE DEPENDENCY PATTERNS
+The YAML structure MUST be:
 
-Sequential:
-${options.storyPrefix}-001 (deps: []) → ${options.storyPrefix}-002 (deps: [${options.storyPrefix}-001])
-
-Parallel then join:
-${options.storyPrefix}-001 (deps: []) → [${options.storyPrefix}-002, ${options.storyPrefix}-003] → ${options.storyPrefix}-004
-
-Now, decompose the goal into stories. Output ONLY the YAML structure.
-` : `## OUTPUT FORMAT
-You MUST output ONLY valid YAML in the following structure. DO NOT include markdown code fences or any other text.
-
-\`\`\`yaml
 masterPrompt: |
   A reusable prompt template that applies to all tasks.
   Include best practices, coding standards, and common guidelines.
@@ -276,52 +229,39 @@ tasks:
     title: "Clear, specific task title"
     description: "Detailed description of what this task accomplishes"
     estimatedMinutes: 10
-    dependencies: []  # Array of task IDs that must complete first
-    parallelizable: true  # Can this run in parallel with other tasks?
-    agentType: "dev"  # Agent type: dev, architect, qa, etc.
-    targetFiles:  # Optional: specific files this task operates on
+    dependencies: []
+    parallelizable: true
+    agentType: "dev"
+    targetFiles:
       - "path/to/file.js"
     prompt: |
       Specific prompt for the agent to execute this task.
-      Include:
-      - What to do
-      - Where to do it (file paths)
-      - Expected outcome
-      - Any validation steps
+      Include what to do, where to do it, expected outcome, validation steps.
     outputFile: "${sessionDir}/outputs/task-001-output.md"
 
   - id: task-002
     title: "Next task"
     description: "Task description"
     estimatedMinutes: 5
-    dependencies: ["task-001"]  # Must wait for task-001
+    dependencies: ["task-001"]
     parallelizable: false
     agentType: "dev"
     prompt: |
       Task-specific prompt here
     outputFile: "${sessionDir}/outputs/task-002-output.md"
 
-  # ... more tasks
-\`\`\`
-
-## IMPORTANT RULES
-1. Each task ID must be unique
+## YAML RULES
+1. Each task ID must be unique (task-001, task-002, etc.)
 2. Dependencies must reference valid task IDs
-3. Circular dependencies are not allowed
-4. Tasks with no dependencies can run immediately
-5. Tasks with the same dependencies can run in parallel (if parallelizable: true)
-6. All file paths in outputFile should use the session directory: ${sessionDir}/outputs/
-${options.perFile ? '7. **CRITICAL**: Create one task per file for the main work (per-file mode is ON)' : ''}
-
-## EXAMPLE DEPENDENCY PATTERNS
-
-Sequential:
-task-001 (deps: []) → task-002 (deps: [task-001]) → task-003 (deps: [task-002])
+3. No circular dependencies
+4. Use outputFile path: ${sessionDir}/outputs/
+${options.perFile ? '5. **CRITICAL**: Create one task per file (per-file mode is ON)' : ''}
 
-Parallel then join:
-task-001 (deps: []) → [task-002, task-003] (deps: [task-001]) → task-004 (deps: [task-002, task-003])
+## DEPENDENCY PATTERNS
+- Sequential: task-001 → task-002 (deps: [task-001])
+- Parallel: task-002, task-003 both depend on task-001, then task-004 depends on both
 
-Now, decompose the goal into tasks. Output ONLY the YAML structure.
+**REMEMBER: Your ENTIRE response must be valid YAML starting with "masterPrompt: |" - NO other text!**
 `;
         return prompt;
     }
@@ -418,15 +358,25 @@ Now, decompose the goal into tasks. Output ONLY the YAML structure.
             startIndex = lines.findIndex((line) => line.trim().startsWith('tasks:'));
         }
         if (startIndex !== -1) {
-            // Find the end of YAML content (stop at empty lines or obvious non-YAML content)
+            // For YAML task graphs, we expect the content to continue until the end
+            // since ## headers inside multiline strings (prompt: |) are valid YAML content.
+            // Only stop if we see clear non-YAML markers at the start of a line (no indentation).
             let endIndex = lines.length;
             for (let i = startIndex + 1; i < lines.length; i++) {
-                const line = lines[i].trim();
-                // Stop if we hit obvious non-YAML content
-                if (line.startsWith('#') && !line.startsWith('# ') && i > startIndex + 5) {
-                    // Could be a comment, but if far from start, likely end of YAML
-                    endIndex = i;
-                    break;
+                const line = lines[i];
+                const trimmedLine = line.trim();
+                // Only stop at lines that are:
+                // 1. Not indented (start at column 0)
+                // 2. Look like markdown headers or prose (not YAML keys)
+                // 3. Are not empty lines (which are valid in YAML)
+                if (line.length > 0 && line[0] !== ' ' && line[0] !== '\t') {
+                    // Line is not indented - check if it's a YAML key or non-YAML content
+                    const isYamlKey = /^[a-zA-Z_][a-zA-Z0-9_]*:/.test(trimmedLine) || trimmedLine.startsWith('-');
+                    if (!isYamlKey && !trimmedLine.startsWith('#')) {
+                        // Non-indented, non-YAML content (like "Here's the summary...")
+                        endIndex = i;
+                        break;
+                    }
                 }
             }
             const yamlContent = lines.slice(startIndex, endIndex).join('\n');
@@ -535,21 +485,24 @@ Now, decompose the goal into tasks. Output ONLY the YAML structure.
         catch (error) {
             this.logger.warn({ error: error.message }, 'YAML validation failed, asking Claude to fix it');
             // YAML is invalid, ask Claude to fix it
-            const fixPrompt = `The following YAML has syntax errors. Please fix ALL syntax errors and return ONLY the corrected YAML (no explanations, no markdown code fences, just the raw YAML):
+            const fixPrompt = `FIX THIS YAML - OUTPUT ONLY THE FIXED YAML, NOTHING ELSE.
+
+**CRITICAL: Your response must be PURE YAML only. Start directly with "masterPrompt: |"**
+- Do NOT write any explanation
+- Do NOT use markdown code fences
+- Do NOT say "Here's the fixed YAML" or anything similar
 
-ERROR: ${error.message}
+ERROR TO FIX: ${error.message}
 
-INVALID YAML:
+YAML TO FIX:
 ${output}
 
-Please output the CORRECTED YAML only. Ensure:
-1. Proper indentation (2 spaces per level)
-2. All strings with special characters are quoted
-3. All lists and mappings are properly formatted
-4. No syntax errors remain
+RULES:
+- Use 2 spaces for indentation
+- Quote strings with special characters
+- Ensure valid YAML syntax
 
-Output ONLY the corrected YAML:
-`;
+YOUR RESPONSE MUST START WITH "masterPrompt: |" - NO OTHER TEXT ALLOWED!`;
             this.logger.info('Asking Claude to fix YAML errors');
             const fixResult = await this.agentRunner.runAgent(fixPrompt, {
                 agentType: 'architect',

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@hyperdrive.bot/bmad-workflow",
   "description": "AI-driven development workflow orchestration CLI for BMAD projects",
-  "version": "1.0.3",
+  "version": "1.0.6",
   "author": {
     "name": "DevSquad",
     "email": "marcelo@devsquad.email",