bmad-method 6.0.0-alpha.5 → 6.0.0-alpha.6

package/src/modules/bmm/docs/workflows-planning.md

@@ -1,25 +1,90 @@
 # BMM Planning Workflows (Phase 2)
 
-**Reading Time:** ~15 minutes
-
 ## Overview
 
 Phase 2 (Planning) workflows are **required** for all projects. They transform strategic vision into actionable requirements that guide implementation. BMM uses a **scale-adaptive planning system** where the workflow automatically selects the right level of detail based on project complexity.
 
 **Key principle:** One workflow to rule them all - `plan-project` intelligently routes to the appropriate planning flow based on project characteristics.
 
+---
+
+## Phase 2 Planning Flow
+
+```mermaid
+%%{init: {'theme':'base', 'themeVariables': { 'primaryColor':'#fff','primaryTextColor':'#000','primaryBorderColor':'#000','lineColor':'#000','fontSize':'16px','fontFamily':'arial'}}}%%
+graph TB
+    Entry["<b>START: plan-project</b><br/>Discovery and routing"]
+
+    subgraph QuickFlow["<b>QUICK FLOW (Levels 0-1)</b>"]
+        TechSpec["<b>PM: tech-spec</b><br/>Lightweight spec for simple changes"]
+    end
+
+    subgraph StandardFlow["<b>STANDARD PLANNING (Levels 2-4)</b>"]
+        PRD["<b>PM: prd</b><br/>Strategic PRD"]
+        GDD["<b>Game Designer: gdd</b><br/>Game design document"]
+        Narrative["<b>Game Designer: narrative</b><br/>Story-driven design"]
+        UXDesign["<b>UX Designer: ux</b><br/>UX-first specification"]
+
+        Epics["<b>PM: create-epics-and-stories</b><br/>Break requirements into epics and stories"]
+    end
+
+    subgraph Updates["<b>STORY UPDATES (Anytime After Epics Created)</b>"]
+        CorrectCourse["<b>PM/SM: correct-course</b><br/>Update epics/stories mid-stream"]
+    end
+
+    Entry -->|Level 0-1<br/>Simple| QuickFlow
+    Entry -->|Level 2-4<br/>Software| PRD
+    Entry -->|Level 2-4<br/>Game| GDD
+    Entry -->|Level 2-4<br/>Story-driven| Narrative
+    Entry -->|Level 2-4<br/>UX-first| UXDesign
+
+    PRD --> Epics
+    GDD --> Epics
+    Narrative --> Epics
+    UXDesign -.->|May update| Epics
+
+    Epics --> Phase3["<b>Phase 3: Architecture</b>"]
+    Phase3 -.->|May update| Epics
+
+    QuickFlow --> Phase4["<b>Phase 4: Implementation</b>"]
+    Phase3 --> Phase4
+
+    Phase4 -.->|Significant changes| CorrectCourse
+    CorrectCourse -.->|Updates| Epics
+
+    style Entry fill:#fff9c4,stroke:#f57f17,stroke-width:3px,color:#000
+    style QuickFlow fill:#c5e1a5,stroke:#33691e,stroke-width:3px,color:#000
+    style StandardFlow fill:#e1bee7,stroke:#6a1b9a,stroke-width:3px,color:#000
+    style Updates fill:#ffcdd2,stroke:#c62828,stroke-width:3px,color:#000
+    style Phase3 fill:#90caf9,stroke:#0d47a1,stroke-width:2px,color:#000
+    style Phase4 fill:#ffcc80,stroke:#e65100,stroke-width:2px,color:#000
+
+    style TechSpec fill:#aed581,stroke:#1b5e20,stroke-width:2px,color:#000
+    style PRD fill:#ce93d8,stroke:#4a148c,stroke-width:2px,color:#000
+    style GDD fill:#ce93d8,stroke:#4a148c,stroke-width:2px,color:#000
+    style Narrative fill:#ce93d8,stroke:#4a148c,stroke-width:2px,color:#000
+    style UXDesign fill:#ce93d8,stroke:#4a148c,stroke-width:2px,color:#000
+    style Epics fill:#ba68c8,stroke:#6a1b9a,stroke-width:3px,color:#000
+    style CorrectCourse fill:#ef5350,stroke:#c62828,stroke-width:2px,color:#000
+```
+
+---
+
 ## Quick Reference
 
-| Workflow      | Project Levels | Duration   | Purpose                                 |
-| ------------- | -------------- | ---------- | --------------------------------------- |
-| **prd**       | 2-4            | 2-6 hours  | Strategic PRD + tactical epic breakdown |
-| **tech-spec** | 0-1            | 30-90 min  | Lightweight technical specification     |
-| **gdd**       | 2-4 (games)    | 4-10 hours | Complete game design document           |
-| **narrative** | 2-4 (story)    | 3-8 hours  | Story-driven game/experience design     |
-| **ux**        | 2-4 (UX-heavy) | 3-6 hours  | UX-first design specification           |
+| Workflow                     | Agent         | Project Levels | Purpose                                              |
+| ---------------------------- | ------------- | -------------- | ---------------------------------------------------- |
+| **prd**                      | PM            | 2-4            | Strategic PRD                                        |
+| **create-epics-and-stories** | PM            | 2-4            | Break PRD/GDD into epics and stories (standalone OK) |
+| **tech-spec**                | PM            | 0-1            | Lightweight technical specification                  |
+| **gdd**                      | Game Designer | 2-4 (games)    | Complete game design document                        |
+| **narrative**                | Game Designer | 2-4 (story)    | Story-driven game/experience design                  |
+| **ux**                       | UX Designer   | 2-4 (UX-heavy) | UX-first design specification                        |
 
 **Note:** The `plan-project` workflow is your single entry point. It automatically routes to the right planning workflow based on your answers to discovery questions.
 
+**Critical:** After PRD/GDD/Narrative complete, you must run `create-epics-and-stories` to generate user stories (can be done in same chat or separate chat later). These stories can be updated anytime via UX-Design, Architecture decisions, or `correct-course` during implementation.
+
 ---
 
 ## Understanding Scale-Adaptive Planning
@@ -73,7 +138,6 @@ Single unified entry point for all planning workflows. Uses conversational disco
 **Agent:** PM (orchestrates other agents as needed)
 **Phase:** 2 (Planning)
 **Required:** Yes (for all projects)
-**Typical Duration:** Varies by target workflow
 
 ### When to Use
 
@@ -161,28 +225,24 @@ ELSE:
 - **Input**: "Fix null pointer exception in user service"
 - **Discovery**: Level 0 (single atomic change)
 - **Route**: tech-spec (Quick Spec Flow)
-- **Duration**: 20 minutes
 
 **Scenario 2: E-commerce Checkout**
 
 - **Input**: "Build complete checkout flow with payment processing"
 - **Discovery**: Level 3 (large feature set), feature-focused
 - **Route**: prd (Standard depth)
-- **Duration**: 4 hours
 
 **Scenario 3: Roguelike Card Game**
 
 - **Input**: "Roguelike card battler with emotional narrative"
 - **Discovery**: Level 3 (large feature set), game project
 - **Route**: gdd
-- **Duration**: 6 hours
 
 **Scenario 4: Story-Driven Adventure**
 
 - **Input**: "Narrative adventure game with branching story"
 - **Discovery**: Level 3, story-central
 - **Route**: narrative (then gdd for mechanics)
-- **Duration**: 8 hours total
 
 ---
 
@@ -195,7 +255,6 @@ Lightweight technical specification for Levels 0-1 projects (single changes, sim
 **Agent:** Architect
 **Phase:** 2 (Planning)
 **Project Levels:** 0-1
-**Typical Duration:** 30-90 minutes
 
 ### When to Use
 
@@ -322,11 +381,6 @@ Strategic PRD with tactical epic breakdown for Levels 2-4 projects. Unified work
 **Agent:** PM (with Architect and Analyst support)
 **Phase:** 2 (Planning)
 **Project Levels:** 2-4
-**Typical Duration:**
-
-- Level 2: 2-3 hours (Lightweight)
-- Level 3: 3-5 hours (Standard)
-- Level 4: 5-8 hours (Comprehensive)
 
 ### When to Use
 
@@ -488,11 +542,6 @@ Complete game design document for Levels 2-4 game projects, adapted from industr
 **Agent:** PM (Game Designer persona)
 **Phase:** 2 (Planning)
 **Project Levels:** 2-4 (games)
-**Typical Duration:**
-
-- Level 2: 3-4 hours (Small indie game)
-- Level 3: 5-7 hours (Medium game)
-- Level 4: 8-12 hours (Large/commercial game)
 
 ### When to Use
 
@@ -666,11 +715,6 @@ Story-driven design workflow for games and experiences where narrative is centra
 **Agent:** PM (Narrative Designer persona) + Creative Problem Solver (CIS)
 **Phase:** 2 (Planning)
 **Project Levels:** 2-4 (story-driven projects)
-**Typical Duration:**
-
-- Level 2: 2-4 hours (Linear narrative)
-- Level 3: 4-6 hours (Branching narrative)
-- Level 4: 6-10 hours (Complex branching with multiple arcs)
 
 ### When to Use
 
@@ -825,11 +869,6 @@ UX specification workflow for projects where user experience is the primary diff
 **Agent:** UX Designer
 **Phase:** 2 (Planning)
 **Project Levels:** 2-4 (UX-heavy projects)
-**Typical Duration:**
-
-- Level 2: 2-3 hours (Single feature UX)
-- Level 3: 4-5 hours (Multi-screen experience)
-- Level 4: 6-8 hours (Platform-wide UX system)
 
 ### When to Use
 

package/src/modules/bmm/docs/workflows-solutioning.md

@@ -1,19 +1,56 @@
 # BMM Solutioning Workflows (Phase 3)
 
-**Reading Time:** ~8 minutes
-
 ## Overview
 
 Phase 3 (Solutioning) workflows translate **what** to build (from Planning) into **how** to build it (technical design). This phase is **required for Levels 3-4** and **optional for Level 2** projects.
 
 **Key principle:** Prevent agent conflicts by making architectural decisions explicit and documented before implementation begins.
 
+---
+
+## Phase 3 Solutioning Flow
+
+```mermaid
+%%{init: {'theme':'base', 'themeVariables': { 'primaryColor':'#fff','primaryTextColor':'#000','primaryBorderColor':'#000','lineColor':'#000','fontSize':'16px','fontFamily':'arial'}}}%%
+graph TB
+    FromPRD["<b>FROM Phase 2</b><br/>PRD/GDD/Narrative/UX complete"]
+
+    subgraph Solutioning["<b>PHASE 3: SOLUTIONING</b>"]
+        direction TB
+        Architecture["<b>Architect: architecture</b><br/>Technical design and decisions"]
+        GateCheck["<b>Architect: solutioning-gate-check</b><br/>Validation before implementation"]
+    end
+
+    subgraph Optional["<b>OPTIONAL PATHS</b>"]
+        direction LR
+        Level2Skip["<b>Level 2:</b><br/>Skip if straightforward"]
+    end
+
+    FromPRD --> Architecture
+    Architecture --> GateCheck
+    GateCheck -->|PASS| Phase4["<b>Phase 4: Implementation</b>"]
+    GateCheck -->|CONCERNS/FAIL| Architecture
+    FromPRD -.->|Level 2 only| Level2Skip
+    Level2Skip -.-> Phase4
+
+    style FromPRD fill:#e1bee7,stroke:#6a1b9a,stroke-width:2px,color:#000
+    style Solutioning fill:#90caf9,stroke:#0d47a1,stroke-width:3px,color:#000
+    style Optional fill:#fff9c4,stroke:#f57f17,stroke-width:3px,color:#000
+    style Phase4 fill:#ffcc80,stroke:#e65100,stroke-width:2px,color:#000
+
+    style Architecture fill:#64b5f6,stroke:#0d47a1,stroke-width:2px,color:#000
+    style GateCheck fill:#64b5f6,stroke:#0d47a1,stroke-width:2px,color:#000
+    style Level2Skip fill:#fff59d,stroke:#f57f17,stroke-width:2px,color:#000
+```
+
+---
+
 ## Quick Reference
 
-| Workflow                   | Project Levels | Duration  | Purpose                                     |
-| -------------------------- | -------------- | --------- | ------------------------------------------- |
-| **architecture**           | 2-4            | 2-6 hours | Technical architecture and design decisions |
-| **solutioning-gate-check** | 3-4            | 15-30 min | Validate planning/solutioning completeness  |
+| Workflow                   | Project Levels | Purpose                                     |
+| -------------------------- | -------------- | ------------------------------------------- |
+| **architecture**           | 2-4            | Technical architecture and design decisions |
+| **solutioning-gate-check** | 3-4            | Validate planning/solutioning completeness  |
 
 **When to Skip Solutioning:**
 
@@ -86,11 +123,6 @@ Collaborative architectural decision facilitation that produces a decision-focus
 **Phase:** 3 (Solutioning)
 **Project Levels:** 2-4
 **Required:** Level 3-4, Optional Level 2
-**Typical Duration:**
-
-- Level 2: 1-2 hours (Simple architecture)
-- Level 3: 2-4 hours (Standard architecture)
-- Level 4: 4-8 hours (Complex architecture with ADRs)
 
 ### When to Use
 
@@ -341,7 +373,6 @@ Systematically validate that all planning and solutioning phases are complete an
 **Phase:** 3 (Solutioning)
 **Project Levels:** 3-4
 **Required:** Level 3-4 only
-**Typical Duration:** 15-30 minutes
 
 ### When to Use
 
@@ -544,21 +575,20 @@ Optional:
 
 1. **Critical**: Architecture missing security architecture section
    - **Impact**: Epic 1 (Auth) and Epic 4 (Checkout) lack security guidance
-   - **Recommendation**: Complete security architecture (2 hours)
+   - **Recommendation**: Complete security architecture
 
 2. **High**: Payment gateway not selected
    - **Impact**: Epic 4 (Checkout) cannot proceed
-   - **Recommendation**: Add ADR for payment gateway selection (1 hour)
+   - **Recommendation**: Add ADR for payment gateway selection
 
 3. **Medium**: Epic 2, Story 3 too large
    - **Impact**: Risk of story scope creep
-   - **Recommendation**: Split into 2 stories (30 min)
+   - **Recommendation**: Split into 2 stories
 
 **Gate Decision:** CONCERNS ⚠️
 
 - **Rationale**: Critical and high gaps block Epic 1 and Epic 4
 - **Action**: Resolve gaps #1 and #2 before starting implementation
-- **Timeline**: Address in 3 hours, then re-run gate check
 
 **Next Steps:**
 

package/src/modules/bmm/workflows/techdoc/documentation-standards.md

@@ -5,10 +5,32 @@
 
 ---
 
-## CRITICAL RULE: CommonMark Strict Compliance
+## CRITICAL RULES
+
+### Rule 1: CommonMark Strict Compliance
 
 ALL documentation MUST follow CommonMark specification exactly. No exceptions.
 
+### Rule 2: NO TIME ESTIMATES
+
+NEVER document time estimates, durations, or completion times for any workflow, task, or activity. This includes:
+
+- Workflow execution time (e.g., "30-60 min", "2-8 hours")
+- Task duration estimates
+- Reading time estimates
+- Implementation time ranges
+- Any temporal measurements
+
+Time varies dramatically based on:
+
+- Project complexity
+- Team experience
+- Tooling and environment
+- Context switching
+- Unforeseen blockers
+
+**Instead:** Focus on workflow steps, dependencies, and outputs. Let users determine their own timelines.
+
 ### CommonMark Essentials
 
 **Headers:**
@@ -194,6 +216,7 @@ Apply in this hierarchy:
 Before finalizing ANY documentation:
 
 - [ ] CommonMark compliant (no violations)
+- [ ] NO time estimates anywhere (Critical Rule 2)
 - [ ] Headers in proper hierarchy
 - [ ] All code blocks have language tags
 - [ ] Links work and have descriptive text

package/src/modules/bmm/workflows/testarch/atdd/atdd-checklist-template.md

@@ -355,8 +355,8 @@ See `tea-index.csv` for complete knowledge fragment mapping.
 
 - Ask in team standup
 - Tag @{tea_agent_username} in Slack/Discord
-- Refer to `testarch/README.md` for workflow documentation
-- Consult `testarch/knowledge/` for testing best practices
+- Refer to `./bmm/docs/tea-README.md` for workflow documentation
+- Consult `./bmm/testarch/knowledge` for testing best practices
 
 ---
 

package/tools/cli/installers/lib/core/config-collector.js

@@ -491,21 +491,49 @@ class ConfigCollector {
     // Handle different question types
     if (item['single-select']) {
       questionType = 'list';
-      choices = item['single-select'];
-      if (existingValue && choices.includes(existingValue)) {
+      choices = item['single-select'].map((choice) => {
+        // If choice is an object with label and value
+        if (typeof choice === 'object' && choice.label && choice.value !== undefined) {
+          return {
+            name: choice.label,
+            value: choice.value,
+          };
+        }
+        // Otherwise it's a simple string choice
+        return {
+          name: choice,
+          value: choice,
+        };
+      });
+      if (existingValue) {
         defaultValue = existingValue;
       }
     } else if (item['multi-select']) {
       questionType = 'checkbox';
-      choices = item['multi-select'].map((choice) => ({
-        name: choice,
-        value: choice,
-        checked: existingValue
-          ? existingValue.includes(choice)
-          : item.default && Array.isArray(item.default)
-            ? item.default.includes(choice)
-            : false,
-      }));
+      choices = item['multi-select'].map((choice) => {
+        // If choice is an object with label and value
+        if (typeof choice === 'object' && choice.label && choice.value !== undefined) {
+          return {
+            name: choice.label,
+            value: choice.value,
+            checked: existingValue
+              ? existingValue.includes(choice.value)
+              : item.default && Array.isArray(item.default)
+                ? item.default.includes(choice.value)
+                : false,
+          };
+        }
+        // Otherwise it's a simple string choice
+        return {
+          name: choice,
+          value: choice,
+          checked: existingValue
+            ? existingValue.includes(choice)
+            : item.default && Array.isArray(item.default)
+              ? item.default.includes(choice)
+              : false,
+        };
+      });
     } else if (typeof defaultValue === 'boolean') {
       questionType = 'confirm';
     }

package/tools/cli/installers/lib/core/ide-config-manager.js

@@ -68,7 +68,9 @@ class IdeConfigManager {
       sortKeys: false,
     });
 
-    await fs.writeFile(configPath, yamlContent, 'utf8');
+    // Ensure POSIX-compliant final newline
+    const content = yamlContent.endsWith('\n') ? yamlContent : yamlContent + '\n';
+    await fs.writeFile(configPath, content, 'utf8');
   }
 
   /**

package/tools/cli/installers/lib/core/installer.js

@@ -906,8 +906,9 @@ class Installer {
           }
         }
 
-        // Write the clean config file
-        await fs.writeFile(configPath, header + yamlContent, 'utf8');
+        // Write the clean config file with POSIX-compliant final newline
+        const content = header + yamlContent;
+        await fs.writeFile(configPath, content.endsWith('\n') ? content : content + '\n', 'utf8');
 
         // Track the config file in installedFiles
         this.installedFiles.push(configPath);
@@ -1195,8 +1196,9 @@ class Installer {
         // DO NOT replace {project-root} - LLMs understand this placeholder at runtime
         // const processedContent = xmlContent.replaceAll('{project-root}', projectDir);
 
-        // Write the built .md file to bmad/{module}/agents/
-        await fs.writeFile(mdPath, xmlContent, 'utf8');
+        // Write the built .md file to bmad/{module}/agents/ with POSIX-compliant final newline
+        const content = xmlContent.endsWith('\n') ? xmlContent : xmlContent + '\n';
+        await fs.writeFile(mdPath, content, 'utf8');
         this.installedFiles.push(mdPath);
 
         // Remove the source YAML file - we can regenerate from installer source if needed
@@ -1213,7 +1215,9 @@ class Installer {
         if (content.includes('<agent') && !content.includes('<activation')) {
           // Inject the activation block using XML handler
           content = this.xmlHandler.injectActivationSimple(content);
-          await fs.writeFile(agentPath, content, 'utf8');
+          // Ensure POSIX-compliant final newline
+          const finalContent = content.endsWith('\n') ? content : content + '\n';
+          await fs.writeFile(agentPath, finalContent, 'utf8');
         }
       }
     }
@@ -1294,8 +1298,9 @@ class Installer {
       // DO NOT replace {project-root} - LLMs understand this placeholder at runtime
       // const processedContent = xmlContent.replaceAll('{project-root}', projectDir);
 
-      // Write the built .md file
-      await fs.writeFile(targetMdPath, xmlContent, 'utf8');
+      // Write the built .md file with POSIX-compliant final newline
+      const content = xmlContent.endsWith('\n') ? xmlContent : xmlContent + '\n';
+      await fs.writeFile(targetMdPath, content, 'utf8');
 
       // Display result
       if (customizedFields.length > 0) {
@@ -1387,8 +1392,9 @@ class Installer {
         // DO NOT replace {project-root} - LLMs understand this placeholder at runtime
         // const processedContent = xmlContent.replaceAll('{project-root}', projectDir);
 
-        // Write the rebuilt .md file
-        await fs.writeFile(targetMdPath, xmlContent, 'utf8');
+        // Write the rebuilt .md file with POSIX-compliant final newline
+        const content = xmlContent.endsWith('\n') ? xmlContent : xmlContent + '\n';
+        await fs.writeFile(targetMdPath, content, 'utf8');
 
         // Display result with customizations if any
         if (customizedFields.length > 0) {
@@ -2005,6 +2011,11 @@ class Installer {
 
       configContent += processedTemplate;
 
+      // Ensure POSIX-compliant final newline
+      if (!configContent.endsWith('\n')) {
+        configContent += '\n';
+      }
+
       await fs.writeFile(configPath, configContent, 'utf8');
       this.installedFiles.push(configPath); // Track agent config files
       createdCount++;

package/tools/cli/installers/lib/core/manifest-generator.js

@@ -469,7 +469,9 @@ class ManifestGenerator {
       sortKeys: false,
     });
 
-    await fs.writeFile(manifestPath, yamlStr);
+    // Ensure POSIX-compliant final newline
+    const content = yamlStr.endsWith('\n') ? yamlStr : yamlStr + '\n';
+    await fs.writeFile(manifestPath, content);
     return manifestPath;
   }
 

package/tools/cli/installers/lib/core/manifest.js

@@ -35,7 +35,9 @@ class Manifest {
       sortKeys: false,
     });
 
-    await fs.writeFile(manifestPath, yamlContent, 'utf8');
+    // Ensure POSIX-compliant final newline
+    const content = yamlContent.endsWith('\n') ? yamlContent : yamlContent + '\n';
+    await fs.writeFile(manifestPath, content, 'utf8');
     return { success: true, path: manifestPath, filesTracked: 0 };
   }
 
@@ -104,7 +106,9 @@ class Manifest {
       sortKeys: false,
     });
 
-    await fs.writeFile(manifestPath, yamlContent, 'utf8');
+    // Ensure POSIX-compliant final newline
+    const content = yamlContent.endsWith('\n') ? yamlContent : yamlContent + '\n';
+    await fs.writeFile(manifestPath, content, 'utf8');
 
     return manifest;
   }

package/tools/cli/installers/lib/modules/manager.js

@@ -267,6 +267,12 @@ class ModuleManager {
         continue;
       }
 
+      // Skip user documentation if install_user_docs is false
+      if (moduleConfig.install_user_docs === false && (file.startsWith('docs/') || file.startsWith('docs\\'))) {
+        console.log(chalk.dim(`  Skipping user documentation: ${file}`));
+        continue;
+      }
+
       // Skip game development content if include_game_planning is false
       if (moduleConfig.include_game_planning === false) {
         const shouldSkipGameDev = gameDevFiles.some((gamePath) => {

package/tools/cli/lib/config.js

@@ -33,7 +33,9 @@ class Config {
     });
 
     await fs.ensureDir(path.dirname(configPath));
-    await fs.writeFile(configPath, yamlContent, 'utf8');
+    // Ensure POSIX-compliant final newline
+    const content = yamlContent.endsWith('\n') ? yamlContent : yamlContent + '\n';
+    await fs.writeFile(configPath, content, 'utf8');
   }
 
   /**

package/tools/cli/lib/ui.js

@@ -82,15 +82,15 @@ class UI {
       // If actionType === 'update' or 'reinstall', continue with normal flow below
     }
 
-    // Collect IDE tool selection EARLY (before module configuration)
-    // This allows users to make all decisions upfront before file copying begins
-    const toolSelection = await this.promptToolSelection(confirmedDirectory, []);
-
     const { installedModuleIds } = await this.getExistingInstallation(confirmedDirectory);
     const coreConfig = await this.collectCoreConfig(confirmedDirectory);
     const moduleChoices = await this.getModuleChoices(installedModuleIds);
     const selectedModules = await this.selectModules(moduleChoices);
 
+    // Collect IDE tool selection AFTER configuration prompts (fixes Windows/PowerShell hang)
+    // This allows text-based prompts to complete before the checkbox prompt
+    const toolSelection = await this.promptToolSelection(confirmedDirectory, selectedModules);
+
     console.clear();
     CLIUtils.displayLogo();
     CLIUtils.displayModuleComplete('core', false); // false = don't clear the screen again
@@ -100,7 +100,7 @@ class UI {
       directory: confirmedDirectory,
       installCore: true, // Always install core
       modules: selectedModules,
-      // IDE selection collected early, will be configured later
+      // IDE selection collected after config, will be configured later
       ides: toolSelection.ides,
       skipIde: toolSelection.skipIde,
       coreConfig: coreConfig, // Pass collected core config to installer

package/tools/cli/lib/yaml-format.js

@@ -64,7 +64,8 @@ async function formatYamlContent(content, filename) {
       noRefs: true,
       sortKeys: false, // Preserve key order
     });
-    return formatted;
+    // Ensure POSIX-compliant final newline
+    return formatted.endsWith('\n') ? formatted : formatted + '\n';
   } catch (error) {
     console.error(chalk.red(`❌ YAML syntax error in ${filename}:`), error.message);
     console.error(chalk.yellow(`💡 Try manually fixing the YAML structure first`));

package/tools/schema/agent.js

@@ -176,6 +176,8 @@ function buildMenuItemSchema() {
       tmpl: createNonEmptyString('agent.menu[].tmpl').optional(),
       data: createNonEmptyString('agent.menu[].data').optional(),
       'run-workflow': createNonEmptyString('agent.menu[].run-workflow').optional(),
+      checklist: createNonEmptyString('agent.menu[].checklist').optional(),
+      document: createNonEmptyString('agent.menu[].document').optional(),
     })
     .strict()
     .superRefine((value, ctx) => {