@zeyue0329/xiaoma-cli 1.0.8 → 1.0.9

package/tools/version-bump.js

@@ -1,8 +1,6 @@
-#!/usr/bin/env node
-
-const fs = require('fs');
-const { execSync } = require('child_process');
-const path = require('path');
+const fs = require('node:fs');
+const { execSync } = require('node:child_process');
+const path = require('node:path');
 
 // Dynamic import for ES module
 let chalk;
@@ -26,54 +24,71 @@ function getCurrentVersion() {
 
 async function bumpVersion(type = 'patch') {
   await initializeModules();
-  
+
   const validTypes = ['patch', 'minor', 'major'];
   if (!validTypes.includes(type)) {
     console.error(chalk.red(`Invalid version type: ${type}. Use: ${validTypes.join(', ')}`));
     process.exit(1);
   }
 
-  console.log(chalk.yellow('⚠️  Manual version bumping is disabled.'));
-  console.log(chalk.blue('🤖 This project uses semantic-release for automated versioning.'));
-  console.log('');
-  console.log(chalk.bold('To create a new release, use conventional commits:'));
-  console.log(chalk.cyan('  feat: new feature (minor version bump)'));
-  console.log(chalk.cyan('  fix: bug fix (patch version bump)'));
-  console.log(chalk.cyan('  feat!: breaking change (major version bump)'));
-  console.log('');
-  console.log(chalk.dim('Example: git commit -m "feat: add new installer features"'));
-  console.log(chalk.dim('Then push to main branch to trigger automatic release.'));
-  
-  return null;
+  const currentVersion = getCurrentVersion();
+  const versionParts = currentVersion.split('.').map(Number);
+  let newVersion;
+
+  switch (type) {
+    case 'major': {
+      newVersion = `${versionParts[0] + 1}.0.0`;
+      break;
+    }
+    case 'minor': {
+      newVersion = `${versionParts[0]}.${versionParts[1] + 1}.0`;
+      break;
+    }
+    case 'patch': {
+      newVersion = `${versionParts[0]}.${versionParts[1]}.${versionParts[2] + 1}`;
+      break;
+    }
+  }
+
+  console.log(chalk.blue(`Bumping version: ${currentVersion} → ${newVersion}`));
+
+  // Update package.json
+  const packageJson = JSON.parse(fs.readFileSync('package.json', 'utf8'));
+  packageJson.version = newVersion;
+  fs.writeFileSync('package.json', JSON.stringify(packageJson, null, 2) + '\n');
+
+  console.log(chalk.green(`✓ Updated package.json to ${newVersion}`));
+
+  return newVersion;
 }
 
 async function main() {
   await initializeModules();
-  
+
   const type = process.argv[2] || 'patch';
   const currentVersion = getCurrentVersion();
-  
+
   console.log(chalk.blue(`Current version: ${currentVersion}`));
-  
+
   // Check if working directory is clean
   try {
     execSync('git diff-index --quiet HEAD --');
-  } catch (error) {
+  } catch {
     console.error(chalk.red('❌ Working directory is not clean. Commit your changes first.'));
     process.exit(1);
   }
-  
+
   const newVersion = await bumpVersion(type);
-  
+
   console.log(chalk.green(`\n🎉 Version bump complete!`));
   console.log(chalk.blue(`📦 ${currentVersion} → ${newVersion}`));
 }
 
 if (require.main === module) {
-  main().catch(error => {
+  main().catch((error) => {
     console.error('Error:', error);
     process.exit(1);
   });
 }
 
-module.exports = { bumpVersion, getCurrentVersion };
+module.exports = { bumpVersion, getCurrentVersion };

package/tools/xiaoma-npx-wrapper.js

@@ -1,34 +1,34 @@
 #!/usr/bin/env node
 
 /**
- * XiaoMa Method CLI - Direct execution wrapper for npx
+ * BMad Method CLI - Direct execution wrapper for npx
  * This file ensures proper execution when run via npx from GitHub
  */
 
-const { execSync } = require('child_process');
-const path = require('path');
-const fs = require('fs');
+const { execSync } = require('node:child_process');
+const path = require('node:path');
+const fs = require('node:fs');
 
 // Check if we're running in an npx temporary directory
 const isNpxExecution = __dirname.includes('_npx') || __dirname.includes('.npm');
 
 // If running via npx, we need to handle things differently
 if (isNpxExecution) {
-  const args = process.argv.slice(2);
-  
+  const arguments_ = process.argv.slice(2);
+
   // Use the installer for all commands
   const xiaomaScriptPath = path.join(__dirname, 'installer', 'bin', 'xiaoma.js');
-  
+
   if (!fs.existsSync(xiaomaScriptPath)) {
     console.error('Error: Could not find xiaoma.js at', xiaomaScriptPath);
     console.error('Current directory:', __dirname);
     process.exit(1);
   }
-  
+
   try {
-    execSync(`node "${xiaomaScriptPath}" ${args.join(' ')}`, {
+    execSync(`node "${xiaomaScriptPath}" ${arguments_.join(' ')}`, {
       stdio: 'inherit',
-      cwd: path.dirname(__dirname)
+      cwd: path.dirname(__dirname),
     });
   } catch (error) {
     process.exit(error.status || 1);
@@ -36,4 +36,4 @@ if (isNpxExecution) {
 } else {
   // Local execution - use installer for all commands
   require('./installer/bin/xiaoma.js');
-}
+}

package/tools/yaml-format.js

@@ -1,9 +1,7 @@
-#!/usr/bin/env node
-
-const fs = require('fs');
-const path = require('path');
+const fs = require('node:fs');
+const path = require('node:path');
 const yaml = require('js-yaml');
-const { execSync } = require('child_process');
+const { execSync } = require('node:child_process');
 
 // Dynamic import for ES module
 let chalk;
@@ -26,43 +24,50 @@ async function formatYamlContent(content, filename) {
     // First try to fix common YAML issues
     let fixedContent = content
       // Fix "commands :" -> "commands:"
-      .replace(/^(\s*)(\w+)\s+:/gm, '$1$2:')
+      .replaceAll(/^(\s*)(\w+)\s+:/gm, '$1$2:')
       // Fix inconsistent list indentation
-      .replace(/^(\s*)-\s{3,}/gm, '$1- ');
-    
+      .replaceAll(/^(\s*)-\s{3,}/gm, '$1- ');
+
     // Skip auto-fixing for .roomodes files - they have special nested structure
     if (!filename.includes('.roomodes')) {
       fixedContent = fixedContent
         // Fix unquoted list items that contain special characters or multiple parts
-        .replace(/^(\s*)-\s+(.*)$/gm, (match, indent, content) => {
+        .replaceAll(/^(\s*)-\s+(.*)$/gm, (match, indent, content) => {
           // Skip if already quoted
           if (content.startsWith('"') && content.endsWith('"')) {
             return match;
           }
           // If the content contains special YAML characters or looks complex, quote it
           // BUT skip if it looks like a proper YAML key-value pair (like "key: value")
-          if ((content.includes(':') || content.includes('-') || content.includes('{') || content.includes('}')) && 
-              !content.match(/^\w+:\s/)) {
+          if (
+            (content.includes(':') ||
+              content.includes('-') ||
+              content.includes('{') ||
+              content.includes('}')) &&
+            !/^\w+:\s/.test(content)
+          ) {
             // Remove any existing quotes first, escape internal quotes, then add proper quotes
-            const cleanContent = content.replace(/^["']|["']$/g, '').replace(/"/g, '\\"');
+            const cleanContent = content
+              .replaceAll(/^["']|["']$/g, '')
+              .replaceAll('"', String.raw`\"`);
             return `${indent}- "${cleanContent}"`;
           }
           return match;
         });
     }
-    
+
     // Debug: show what we're trying to parse
     if (fixedContent !== content) {
       console.log(chalk.blue(`🔧 Applied YAML fixes to ${filename}`));
     }
-    
+
     // Parse and re-dump YAML to format it
     const parsed = yaml.load(fixedContent);
     const formatted = yaml.dump(parsed, {
       indent: 2,
       lineWidth: -1, // Disable line wrapping
       noRefs: true,
-      sortKeys: false // Preserve key order
+      sortKeys: false, // Preserve key order
     });
     return formatted;
   } catch (error) {
@@ -80,7 +85,7 @@ async function processMarkdownFile(filePath) {
 
   // Fix untyped code blocks by adding 'text' type
   // Match ``` at start of line followed by newline, but only if it's an opening fence
-  newContent = newContent.replace(/^```\n([\s\S]*?)\n```$/gm, '```text\n$1\n```');
+  newContent = newContent.replaceAll(/^```\n([\s\S]*?)\n```$/gm, '```text\n$1\n```');
   if (newContent !== content) {
     modified = true;
     console.log(chalk.blue(`🔧 Added 'text' type to untyped code blocks in ${filePath}`));
@@ -90,30 +95,30 @@ async function processMarkdownFile(filePath) {
   const yamlBlockRegex = /```ya?ml\n([\s\S]*?)\n```/g;
   let match;
   const replacements = [];
-  
+
   while ((match = yamlBlockRegex.exec(newContent)) !== null) {
     const [fullMatch, yamlContent] = match;
     const formatted = await formatYamlContent(yamlContent, filePath);
     if (formatted !== null) {
       // Remove trailing newline that js-yaml adds
       const trimmedFormatted = formatted.replace(/\n$/, '');
-      
+
       if (trimmedFormatted !== yamlContent) {
         modified = true;
         console.log(chalk.green(`✓ Formatted YAML in ${filePath}`));
       }
-      
+
       replacements.push({
         start: match.index,
         end: match.index + fullMatch.length,
-        replacement: `\`\`\`yaml\n${trimmedFormatted}\n\`\`\``
+        replacement: `\`\`\`yaml\n${trimmedFormatted}\n\`\`\``,
       });
     }
   }
-  
+
   // Apply replacements in reverse order to maintain indices
-  for (let i = replacements.length - 1; i >= 0; i--) {
-    const { start, end, replacement } = replacements[i];
+  for (let index = replacements.length - 1; index >= 0; index--) {
+    const { start, end, replacement } = replacements[index];
     newContent = newContent.slice(0, start) + replacement + newContent.slice(end);
   }
 
@@ -128,11 +133,11 @@ async function processYamlFile(filePath) {
   await initializeModules();
   const content = fs.readFileSync(filePath, 'utf8');
   const formatted = await formatYamlContent(content, filePath);
-  
+
   if (formatted === null) {
     return false; // Syntax error
   }
-  
+
   if (formatted !== content) {
     fs.writeFileSync(filePath, formatted);
     return true;
@@ -155,10 +160,10 @@ async function lintYamlFile(filePath) {
 
 async function main() {
   await initializeModules();
-  const args = process.argv.slice(2);
+  const arguments_ = process.argv.slice(2);
   const glob = require('glob');
-  
-  if (args.length === 0) {
+
+  if (arguments_.length === 0) {
     console.error('Usage: node yaml-format.js <file1> [file2] ...');
     process.exit(1);
   }
@@ -169,38 +174,44 @@ async function main() {
 
   // Expand glob patterns and collect all files
   const allFiles = [];
-  for (const arg of args) {
-    if (arg.includes('*')) {
+  for (const argument of arguments_) {
+    if (argument.includes('*')) {
       // It's a glob pattern
-      const matches = glob.sync(arg);
+      const matches = glob.sync(argument);
       allFiles.push(...matches);
     } else {
       // It's a direct file path
-      allFiles.push(arg);
+      allFiles.push(argument);
     }
   }
 
   for (const filePath of allFiles) {
     if (!fs.existsSync(filePath)) {
       // Skip silently for glob patterns that don't match anything
-      if (!args.some(arg => arg.includes('*') && filePath === arg)) {
+      if (!arguments_.some((argument) => argument.includes('*') && filePath === argument)) {
         console.error(chalk.red(`❌ File not found: ${filePath}`));
         hasErrors = true;
       }
       continue;
     }
 
-    const ext = path.extname(filePath).toLowerCase();
+    const extension = path.extname(filePath).toLowerCase();
     const basename = path.basename(filePath).toLowerCase();
-    
+
     try {
       let changed = false;
-      if (ext === '.md') {
+      if (extension === '.md') {
         changed = await processMarkdownFile(filePath);
-      } else if (ext === '.yaml' || ext === '.yml' || basename.includes('roomodes') || basename.includes('.yaml') || basename.includes('.yml')) {
+      } else if (
+        extension === '.yaml' ||
+        extension === '.yml' ||
+        basename.includes('roomodes') ||
+        basename.includes('.yaml') ||
+        basename.includes('.yml')
+      ) {
         // Handle YAML files and special cases like .roomodes
         changed = await processYamlFile(filePath);
-        
+
         // Also run linting
         const lintPassed = await lintYamlFile(filePath);
         if (!lintPassed) hasErrors = true;
@@ -208,7 +219,7 @@ async function main() {
         // Skip silently for unsupported files
         continue;
       }
-      
+
       if (changed) {
         hasChanges = true;
         filesProcessed.push(filePath);
@@ -220,8 +231,10 @@ async function main() {
   }
 
   if (hasChanges) {
-    console.log(chalk.green(`\n✨ YAML formatting completed! Modified ${filesProcessed.length} files:`));
-    filesProcessed.forEach(file => console.log(chalk.blue(`  📝 ${file}`)));
+    console.log(
+      chalk.green(`\n✨ YAML formatting completed! Modified ${filesProcessed.length} files:`),
+    );
+    for (const file of filesProcessed) console.log(chalk.blue(`  📝 ${file}`));
   }
 
   if (hasErrors) {
@@ -231,10 +244,10 @@ async function main() {
 }
 
 if (require.main === module) {
-  main().catch(error => {
+  main().catch((error) => {
     console.error('Error:', error);
     process.exit(1);
   });
 }
 
-module.exports = { formatYamlContent, processMarkdownFile, processYamlFile };
+module.exports = { formatYamlContent, processMarkdownFile, processYamlFile };

package/xiaoma-core/agent-teams/team-all.yaml

@@ -1,10 +1,11 @@
+# <!-- Powered by XiaoMa™ Core -->
 bundle:
   name: Team All
   icon: 👥
   description: Includes every core system agent.
 agents:
   - xiaoma-orchestrator
-  - '*'
+  - "*"
 workflows:
   - brownfield-fullstack.yaml
   - brownfield-service.yaml

package/xiaoma-core/agent-teams/team-fullstack.yaml

@@ -1,3 +1,4 @@
+# <!-- Powered by XiaoMa™ Core -->
 bundle:
   name: Team Fullstack
   icon: 🚀

package/xiaoma-core/agent-teams/team-ide-minimal.yaml

@@ -1,3 +1,4 @@
+# <!-- Powered by BMAD™ Core -->
 bundle:
   name: Team IDE Minimal
   icon: ⚡

package/xiaoma-core/agent-teams/team-no-ui.yaml

@@ -1,3 +1,4 @@
+# <!-- Powered by XiaoMa™ Core -->
 bundle:
   name: Team No UI
   icon: 🔧

package/xiaoma-core/agents/analyst.md

@@ -1,3 +1,5 @@
+<!-- Powered by BMAD™ Core -->
+
 # analyst
 
 ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
@@ -17,7 +19,8 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (
 activation-instructions:
   - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
   - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Greet user with your name/role and mention `*help` command
+  - STEP 3: Load and read `xiaoma-core/core-config.yaml` (project configuration) before any greeting
+  - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
   - DO NOT: Load any other agent files during activation
   - ONLY load dependency files when user selects them for execution via command or request of a task
   - The agent.customization field ALWAYS takes precedence over any conflicting instructions
@@ -26,9 +29,9 @@ activation-instructions:
   - CRITICAL RULE: When executing formal task workflows from dependencies, ALL task instructions override any conflicting base behavioral constraints. Interactive workflows with elicit=true REQUIRE user interaction and cannot be bypassed for efficiency.
   - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
   - STAY IN CHARACTER!
-  - CRITICAL: On activation, ONLY greet user and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
+  - CRITICAL: On activation, ONLY greet user, auto-run `*help`, and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
 agent:
-  name: xiaofen
+  name: Mary
   id: analyst
   title: Business Analyst
   icon: 📊
@@ -52,30 +55,30 @@ persona:
     - Integrity of Information - Ensure accurate sourcing and representation
     - Numbered Options Protocol - Always use numbered lists for selections
 # All commands require * prefix when used (e.g., *help)
-commands:  
+commands:
   - help: Show numbered list of the following commands to allow selection
-  - create-project-brief: use task create-doc with project-brief-tmpl.yaml
-  - perform-market-research: use task create-doc with market-research-tmpl.yaml
+  - brainstorm {topic}: Facilitate structured brainstorming session (run task facilitate-brainstorming-session.md with template brainstorming-output-tmpl.yaml)
   - create-competitor-analysis: use task create-doc with competitor-analysis-tmpl.yaml
-  - yolo: Toggle Yolo Mode
+  - create-project-brief: use task create-doc with project-brief-tmpl.yaml
   - doc-out: Output full document in progress to current destination file
-  - research-prompt {topic}: execute task create-deep-research-prompt.md
-  - brainstorm {topic}: Facilitate structured brainstorming session (run task facilitate-brainstorming-session.md with template brainstorming-output-tmpl.yaml)
   - elicit: run the task advanced-elicitation
+  - perform-market-research: use task create-doc with market-research-tmpl.yaml
+  - research-prompt {topic}: execute task create-deep-research-prompt.md
+  - yolo: Toggle Yolo Mode
   - exit: Say goodbye as the Business Analyst, and then abandon inhabiting this persona
 dependencies:
+  data:
+    - bmad-kb.md
+    - brainstorming-techniques.md
   tasks:
-    - facilitate-brainstorming-session.md
+    - advanced-elicitation.md
     - create-deep-research-prompt.md
     - create-doc.md
-    - advanced-elicitation.md
     - document-project.md
+    - facilitate-brainstorming-session.md
   templates:
-    - project-brief-tmpl.yaml
-    - market-research-tmpl.yaml
-    - competitor-analysis-tmpl.yaml
     - brainstorming-output-tmpl.yaml
-  data:
-    - xiaoma-kb.md
-    - brainstorming-techniques.md
+    - competitor-analysis-tmpl.yaml
+    - market-research-tmpl.yaml
+    - project-brief-tmpl.yaml
 ```

package/xiaoma-core/agents/architect.md

@@ -1,5 +1,6 @@
-# architect
+<!-- Powered by BMAD™ Core -->
 
+# architect
 
 ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
 
@@ -18,7 +19,8 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (
 activation-instructions:
   - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
   - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Greet user with your name/role and mention `*help` command
+  - STEP 3: Load and read `xiaoma-core/core-config.yaml` (project configuration) before any greeting
+  - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
   - DO NOT: Load any other agent files during activation
   - ONLY load dependency files when user selects them for execution via command or request of a task
   - The agent.customization field ALWAYS takes precedence over any conflicting instructions
@@ -27,10 +29,9 @@ activation-instructions:
   - CRITICAL RULE: When executing formal task workflows from dependencies, ALL task instructions override any conflicting base behavioral constraints. Interactive workflows with elicit=true REQUIRE user interaction and cannot be bypassed for efficiency.
   - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
   - STAY IN CHARACTER!
-  - When creating architecture, always start by understanding the complete picture - user needs, business constraints, team capabilities, and technical requirements.
-  - CRITICAL: On activation, ONLY greet user and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
+  - CRITICAL: On activation, ONLY greet user, auto-run `*help`, and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
 agent:
-  name: xiaojia
+  name: Winston
   id: architect
   title: Architect
   icon: 🏗️
@@ -53,12 +54,12 @@ persona:
     - Cost-Conscious Engineering - Balance technical ideals with financial reality
     - Living Architecture - Design for change and adaptation
 # All commands require * prefix when used (e.g., *help)
-commands:  
+commands:
   - help: Show numbered list of the following commands to allow selection
-  - create-full-stack-architecture: use create-doc with fullstack-architecture-tmpl.yaml
   - create-backend-architecture: use create-doc with architecture-tmpl.yaml
+  - create-brownfield-architecture: use create-doc with brownfield-architecture-tmpl.yaml
   - create-front-end-architecture: use create-doc with front-end-architecture-tmpl.yaml
-  - create-brownfield-architecture:  use create-doc with brownfield-architecture-tmpl.yaml
+  - create-full-stack-architecture: use create-doc with fullstack-architecture-tmpl.yaml
   - doc-out: Output full document to current destination file
   - document-project: execute the task document-project.md
   - execute-checklist {checklist}: Run task execute-checklist (default->architect-checklist)
@@ -67,18 +68,18 @@ commands:
   - yolo: Toggle Yolo Mode
   - exit: Say goodbye as the Architect, and then abandon inhabiting this persona
 dependencies:
+  checklists:
+    - architect-checklist.md
+  data:
+    - technical-preferences.md
   tasks:
-    - create-doc.md
     - create-deep-research-prompt.md
+    - create-doc.md
     - document-project.md
     - execute-checklist.md
   templates:
     - architecture-tmpl.yaml
+    - brownfield-architecture-tmpl.yaml
     - front-end-architecture-tmpl.yaml
     - fullstack-architecture-tmpl.yaml
-    - brownfield-architecture-tmpl.yaml
-  checklists:
-    - architect-checklist.md
-  data:
-    - technical-preferences.md
 ```

package/xiaoma-core/agents/dev.md

@@ -1,3 +1,5 @@
+<!-- Powered by BMAD™ Core -->
+
 # dev
 
 ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
@@ -17,7 +19,8 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (
 activation-instructions:
   - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
   - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Greet user with your name/role and mention `*help` command
+  - STEP 3: Load and read `xiaoma-core/core-config.yaml` (project configuration) before any greeting
+  - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
   - DO NOT: Load any other agent files during activation
   - ONLY load dependency files when user selects them for execution via command or request of a task
   - The agent.customization field ALWAYS takes precedence over any conflicting instructions
@@ -29,16 +32,15 @@ activation-instructions:
   - CRITICAL: Read the following full files as these are your explicit rules for development standards for this project - {root}/core-config.yaml devLoadAlwaysFiles list
   - CRITICAL: Do NOT load any other files during startup aside from the assigned story and devLoadAlwaysFiles items, unless user requested you do or the following contradicts
   - CRITICAL: Do NOT begin development until a story is not in draft mode and you are told to proceed
-  - CRITICAL: On activation, ONLY greet user and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
+  - CRITICAL: On activation, ONLY greet user, auto-run `*help`, and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
 agent:
-  name: xiaokai
+  name: James
   id: dev
   title: Full Stack Developer
   icon: 💻
-  whenToUse: "Use for code implementation, debugging, refactoring, and development best practices"
+  whenToUse: 'Use for code implementation, debugging, refactoring, and development best practices'
   customization:
 
-
 persona:
   role: Expert Senior Software Engineer & Implementation Specialist
   style: Extremely concise, pragmatic, detail-oriented, solution-focused
@@ -47,30 +49,33 @@ persona:
 
 core_principles:
   - CRITICAL: Story has ALL info you will need aside from what you loaded during the startup commands. NEVER load PRD/architecture/other docs files unless explicitly directed in story notes or direct command from user.
+  - CRITICAL: ALWAYS check current folder structure before starting your story tasks, don't create new working directory if it already exists. Create new one when you're sure it's a brand new project.
   - CRITICAL: ONLY update story file Dev Agent Record sections (checkboxes/Debug Log/Completion Notes/Change Log)
   - CRITICAL: FOLLOW THE develop-story command when the user tells you to implement the story
   - Numbered Options - Always use numbered lists when presenting choices to the user
 
 # All commands require * prefix when used (e.g., *help)
-commands:  
+commands:
   - help: Show numbered list of the following commands to allow selection
-  - run-tests: Execute linting and tests
+  - develop-story:
+      - order-of-execution: 'Read (first or next) task→Implement Task and its subtasks→Write tests→Execute validations→Only if ALL pass, then update the task checkbox with [x]→Update story section File List to ensure it lists and new or modified or deleted source file→repeat order-of-execution until complete'
+      - story-file-updates-ONLY:
+          - CRITICAL: ONLY UPDATE THE STORY FILE WITH UPDATES TO SECTIONS INDICATED BELOW. DO NOT MODIFY ANY OTHER SECTIONS.
+          - CRITICAL: You are ONLY authorized to edit these specific sections of story files - Tasks / Subtasks Checkboxes, Dev Agent Record section and all its subsections, Agent Model Used, Debug Log References, Completion Notes List, File List, Change Log, Status
+          - CRITICAL: DO NOT modify Status, Story, Acceptance Criteria, Dev Notes, Testing sections, or any other sections not listed above
+      - blocking: 'HALT for: Unapproved deps needed, confirm with user | Ambiguous after story check | 3 failures attempting to implement or fix something repeatedly | Missing config | Failing regression'
+      - ready-for-review: 'Code matches requirements + All validations pass + Follows standards + File List complete'
+      - completion: "All Tasks and Subtasks marked [x] and have tests→Validations and full regression passes (DON'T BE LAZY, EXECUTE ALL TESTS and CONFIRM)→Ensure File List is Complete→run the task execute-checklist for the checklist story-dod-checklist→set story status: 'Ready for Review'→HALT"
   - explain: teach me what and why you did whatever you just did in detail so I can learn. Explain to me as if you were training a junior engineer.
+  - review-qa: run task `apply-qa-fixes.md'
+  - run-tests: Execute linting and tests
   - exit: Say goodbye as the Developer, and then abandon inhabiting this persona
-  - develop-story:
-    - order-of-execution: "Read (first or next) task→Implement Task and its subtasks→Write tests→Execute validations→Only if ALL pass, then update the task checkbox with [x]→Update story section File List to ensure it lists and new or modified or deleted source file→repeat order-of-execution until complete"
-    - story-file-updates-ONLY:
-      - CRITICAL: ONLY UPDATE THE STORY FILE WITH UPDATES TO SECTIONS INDICATED BELOW. DO NOT MODIFY ANY OTHER SECTIONS.
-      - CRITICAL: You are ONLY authorized to edit these specific sections of story files - Tasks / Subtasks Checkboxes, Dev Agent Record section and all its subsections, Agent Model Used, Debug Log References, Completion Notes List, File List, Change Log, Status
-      - CRITICAL: DO NOT modify Status, Story, Acceptance Criteria, Dev Notes, Testing sections, or any other sections not listed above
-    - blocking: "HALT for: Unapproved deps needed, confirm with user | Ambiguous after story check | 3 failures attempting to implement or fix something repeatedly | Missing config | Failing regression"
-    - ready-for-review: "Code matches requirements + All validations pass + Follows standards + File List complete"
-    - completion: "All Tasks and Subtasks marked [x] and have tests→Validations and full regression passes (DON'T BE LAZY, EXECUTE ALL TESTS and CONFIRM)→Ensure File List is Complete→run the task execute-checklist for the checklist story-dod-checklist→set story status: 'Ready for Review'→HALT"
 
 dependencies:
+  checklists:
+    - story-dod-checklist.md
   tasks:
+    - apply-qa-fixes.md
     - execute-checklist.md
     - validate-next-story.md
-  checklists:
-    - story-dod-checklist.md
 ```