@paths.design/caws-cli 8.2.0 → 8.2.3

package/dist/commands/tutorial.js

@@ -14,7 +14,7 @@ const TUTORIALS = {
   agent: {
     name: 'AI Agent Onboarding',
     description: 'Complete guide for AI agents working with CAWS',
-    icon: '🤖',
+    icon: '',
     steps: [
       {
         id: 'welcome',
@@ -23,11 +23,11 @@ const TUTORIALS = {
 Welcome to CAWS (Coding Agent Workflow System)!
 
 CAWS helps AI agents and developers collaborate effectively by providing:
-• 📋 Structured specifications and requirements
-• 🔍 Automated validation and quality gates
-• 📊 Progress tracking and status monitoring
-• 🔄 Change management and archival
-• 🏗️ Multi-tier complexity modes
+- Structured specifications and requirements
+- Automated validation and quality gates
+- Progress tracking and status monitoring
+- Change management and archival
+- Multi-tier complexity modes
 
 This tutorial will guide you through the essential CAWS workflow.
         `,
@@ -39,9 +39,9 @@ This tutorial will guide you through the essential CAWS workflow.
         content: `
 Every CAWS session should start with validation:
 
-1. ✅ Always validate first: \`caws validate\`
-2. 📊 Check current status: \`caws status --visual\`
-3. 🎯 Get guidance: \`caws iterate --current-state "Starting implementation"\`
+1. Always validate first: \`caws validate\`
+2. Check current status: \`caws status --visual\`
+3. Get guidance: \`caws iterate --current-state "Starting implementation"\`
 
 These commands ensure you're working with validated specifications and understand the current project state.
         `,
@@ -54,20 +54,20 @@ These commands ensure you're working with validated specifications and understan
         content: `
 CAWS adapts to your project needs with three complexity tiers:
 
-🟢 **Simple Mode** (70% coverage, 30% mutation)
-   • Perfect for small projects and prototyping
-   • Minimal commands and features
-   • Quick setup and iteration
+**Simple Mode** (70% coverage, 30% mutation)
+   - Perfect for small projects and prototyping
+   - Minimal commands and features
+   - Quick setup and iteration
 
-🟡 **Standard Mode** (80% coverage, 50% mutation)
-   • Balanced approach for most projects
-   • Quality gates and provenance tracking
-   • Change management and archival
+**Standard Mode** (80% coverage, 50% mutation)
+   - Balanced approach for most projects
+   - Quality gates and provenance tracking
+   - Change management and archival
 
-🔴 **Enterprise Mode** (90% coverage, 70% mutation)
-   • Full compliance and audit trails
-   • Advanced monitoring and reporting
-   • Maximum quality assurance
+**Enterprise Mode** (90% coverage, 70% mutation)
+   - Full compliance and audit trails
+   - Advanced monitoring and reporting
+   - Maximum quality assurance
 
 Check your current mode: \`caws mode current\`
 Switch modes: \`caws mode set --interactive\`
@@ -81,21 +81,21 @@ Switch modes: \`caws mode set --interactive\`
         content: `
 CAWS uses a multi-spec system for better organization:
 
-📁 **Individual spec files** instead of monolithic specs
-🎯 **Type-based organization** (feature, fix, refactor, etc.)
-📊 **Visual progress tracking** across all specs
-🔄 **Concurrent development** support
+**Individual spec files** instead of monolithic specs
+**Type-based organization** (feature, fix, refactor, etc.)
+**Visual progress tracking** across all specs
+**Concurrent development** support
 
 Commands:
-• \`caws specs list\` - View all specs
-• \`caws specs create <id>\` - Create new spec
-• \`caws specs show <id>\` - View spec details
-• \`caws specs update <id>\` - Update spec status
+- \`caws specs list\` - View all specs
+- \`caws specs create <id>\` - Create new spec
+- \`caws specs show <id>\` - View spec details
+- \`caws specs update <id>\` - Update spec status
 
 Each spec contains:
-• Acceptance criteria with progress tracking
-• Risk tier and complexity mode
-• Contract definitions and validation
+- Acceptance criteria with progress tracking
+- Risk tier and complexity mode
+- Contract definitions and validation
         `,
         action: 'Try: caws specs list',
         verify: 'specs_list',
@@ -106,19 +106,19 @@ Each spec contains:
         content: `
 Follow this proven TDD workflow:
 
-1. 📋 **Plan**: Create/update specs with acceptance criteria
-2. ✅ **Validate**: Ensure specs are valid and complete
-3. 🧪 **Test First**: Write failing tests for each criterion
-4. 🔨 **Implement**: Make tests pass incrementally
-5. 📊 **Track Progress**: Update acceptance criteria status
-6. 🔍 **Quality Gates**: Run validation and quality checks
-7. 📦 **Archive**: Complete and archive finished work
+1. **Plan**: Create/update specs with acceptance criteria
+2. **Validate**: Ensure specs are valid and complete
+3. **Test First**: Write failing tests for each criterion
+4. **Implement**: Make tests pass incrementally
+5. **Track Progress**: Update acceptance criteria status
+6. **Quality Gates**: Run validation and quality checks
+7. **Archive**: Complete and archive finished work
 
 Key commands:
-• \`caws progress update --criterion-id A1 --status completed\`
-• \`caws validate\` - Validate current work
-• \`caws status --visual\` - Check progress
-• \`caws archive <change-id>\` - Complete work
+- \`caws progress update --criterion-id A1 --status completed\`
+- \`caws validate\` - Validate current work
+- \`caws status --visual\` - Check progress
+- \`caws archive <change-id>\` - Complete work
         `,
         action: 'Try: caws status --visual',
         verify: 'status_check',
@@ -129,25 +129,25 @@ Key commands:
         content: `
 CAWS enforces quality through multiple gates:
 
-🔍 **Validation Gates**
-• Spec format and completeness
-• Contract compliance
-• Risk tier requirements
-
-🧪 **Testing Gates**
-• Test coverage thresholds
-• Mutation testing scores
-• Integration test passing
-
-📊 **Progress Gates**
-• Acceptance criteria completion
-• Spec status validation
-• Change budget compliance
-
-⚡ **Quick Checks**
-• \`caws validate\` - Spec validation
-• \`caws diagnose\` - Health checks (if in standard/enterprise mode)
-• \`caws evaluate\` - Quality evaluation
+**Validation Gates**
+- Spec format and completeness
+- Contract compliance
+- Risk tier requirements
+
+**Testing Gates**
+- Test coverage thresholds
+- Mutation testing scores
+- Integration test passing
+
+**Progress Gates**
+- Acceptance criteria completion
+- Spec status validation
+- Change budget compliance
+
+**Quick Checks**
+- \`caws validate\` - Spec validation
+- \`caws diagnose\` - Health checks (if in standard/enterprise mode)
+- \`caws evaluate\` - Quality evaluation
         `,
         action: 'Try: caws validate',
         verify: 'quality_check',
@@ -156,23 +156,23 @@ CAWS enforces quality through multiple gates:
         id: 'common-patterns',
         title: 'Common Patterns & Best Practices',
         content: `
-🚫 **Avoid These**:
-• ❌ Don't start implementation before validation
-• ❌ Don't create duplicate files (enhanced-*, new-*)
-• ❌ Don't exceed change budgets
-• ❌ Don't skip quality gates
-
-✅ **Do These**:
-• ✅ Always validate first: \`caws validate\`
-• ✅ Use multi-spec system for organization
-• ✅ Write tests before implementation (TDD)
-• ✅ Update progress: \`caws progress update\`
-• ✅ Archive completed work: \`caws archive\`
-
-📚 **Get Help**:
-• \`caws --help\` - All commands
-• \`caws workflow guidance\` - Workflow-specific help
-• \`docs/agents/full-guide.md\` - Complete documentation
+**Avoid These**:
+- Don't start implementation before validation
+- Don't create duplicate files (enhanced-*, new-*)
+- Don't exceed change budgets
+- Don't skip quality gates
+
+**Do These**:
+- Always validate first: \`caws validate\`
+- Use multi-spec system for organization
+- Write tests before implementation (TDD)
+- Update progress: \`caws progress update\`
+- Archive completed work: \`caws archive\`
+
+**Get Help**:
+- \`caws --help\` - All commands
+- \`caws workflow guidance\` - Workflow-specific help
+- \`docs/agents/full-guide.md\` - Complete documentation
         `,
         action: 'Try: caws --help',
         verify: 'help_check',
@@ -181,15 +181,15 @@ CAWS enforces quality through multiple gates:
         id: 'completion',
         title: 'Tutorial Complete!',
         content: `
-🎉 Congratulations! You've completed the CAWS agent tutorial.
+Congratulations! You've completed the CAWS agent tutorial.
 
 **Key Takeaways**:
-• CAWS provides structure and validation for AI-human collaboration
-• Start every session with validation and status checks
-• Use the multi-spec system for better organization
-• Follow TDD practices with comprehensive testing
-• Respect quality gates and change budgets
-• Archive completed work for clean project history
+- CAWS provides structure and validation for AI-human collaboration
+- Start every session with validation and status checks
+- Use the multi-spec system for better organization
+- Follow TDD practices with comprehensive testing
+- Respect quality gates and change budgets
+- Archive completed work for clean project history
 
 **Next Steps**:
 1. Explore the multi-spec system: \`caws specs create my-feature\`
@@ -199,7 +199,7 @@ CAWS enforces quality through multiple gates:
 
 Remember: CAWS exists to make AI-human collaboration reliable and high-quality. Follow the rules, validate often, and deliver excellent results!
 
-💡 Pro tip: Use \`caws status --visual\` regularly to stay oriented
+Pro tip: Use \`caws status --visual\` regularly to stay oriented
         `,
         action: 'Tutorial complete! Try: caws specs create my-feature',
       },
@@ -209,7 +209,7 @@ Remember: CAWS exists to make AI-human collaboration reliable and high-quality.
   developer: {
     name: 'Developer Quick Start',
     description: 'Fast track for developers new to CAWS',
-    icon: '👨‍💻',
+    icon: '',
     steps: [
       {
         id: 'welcome-dev',
@@ -218,11 +218,11 @@ Remember: CAWS exists to make AI-human collaboration reliable and high-quality.
 Welcome to CAWS! This quick start will get you up and running fast.
 
 CAWS helps development teams by providing:
-• 📋 Clear specification management
-• 🔄 Structured change workflows
-• 📊 Progress visibility for stakeholders
-• 🏗️ Quality gates and validation
-• 🤝 Better AI-human collaboration
+- Clear specification management
+- Structured change workflows
+- Progress visibility for stakeholders
+- Quality gates and validation
+- Better AI-human collaboration
 
 Let's get you started!
         `,
@@ -242,9 +242,9 @@ First, ensure CAWS is properly initialized:
 For existing projects, use: \`caws scaffold\`
 
 Choose a mode that fits your project:
-• 🟢 Simple: Small projects, quick prototyping
-• 🟡 Standard: Most teams and projects
-• 🔴 Enterprise: Large teams, compliance requirements
+- Simple: Small projects, quick prototyping
+- Standard: Most teams and projects
+- Enterprise: Large teams, compliance requirements
         `,
         action: 'Try: caws mode current',
         verify: 'mode_setup',
@@ -258,9 +258,9 @@ Create a spec for your feature or fix:
 \`caws specs create user-login --type feature --title "User Login System"\`
 
 This creates:
-• A new spec file in \`.caws/specs/user-login.yaml\`
-• Basic structure with acceptance criteria template
-• Automatic registration in the specs registry
+- A new spec file in \`.caws/specs/user-login.yaml\`
+- Basic structure with acceptance criteria template
+- Automatic registration in the specs registry
 
 View all specs: \`caws specs list\`
 View spec details: \`caws specs show user-login\`
@@ -288,9 +288,9 @@ acceptance_criteria:
 \`\`\`
 
 Each criterion should be:
-• ✅ Testable and verifiable
-• 📏 Specific and measurable
-• 🎯 Focused on user value
+- Testable and verifiable
+- Specific and measurable
+- Focused on user value
         `,
         action: 'Edit your spec file and add acceptance criteria',
         verify: 'criteria_defined',
@@ -326,10 +326,10 @@ When all acceptance criteria are completed:
 3. **Archive the work**: \`caws archive user-login\`
 
 This:
-• ✅ Validates all criteria are met
-• 📦 Moves completed work to archive
-• 📊 Updates provenance chain
-• 🎯 Provides completion summary
+- Validates all criteria are met
+- Moves completed work to archive
+- Updates provenance chain
+- Provides completion summary
 
 View archived work: Check \`.caws/archive/\` directory
         `,
@@ -347,21 +347,21 @@ View archived work: Check \`.caws/archive/\` directory
  * @param {number} totalSteps - Total number of steps
  */
 function displayTutorialStep(step, stepNumber, totalSteps) {
-  console.log(chalk.bold.cyan(`\n📚 Step ${stepNumber}/${totalSteps}: ${step.title}`));
-  console.log(chalk.cyan('━'.repeat(60)));
+  console.log(chalk.bold.cyan(`\nStep ${stepNumber}/${totalSteps}: ${step.title}`));
+  console.log(chalk.cyan('='.repeat(60)));
 
   // Display content with proper formatting
   const lines = step.content.trim().split('\n');
   lines.forEach((line) => {
     if (
-      line.startsWith('•') ||
-      line.startsWith('✅') ||
-      line.startsWith('❌') ||
-      line.startsWith('📋') ||
-      line.startsWith('🔍')
+      line.startsWith('-') ||
+      line.startsWith('') ||
+      line.startsWith('') ||
+      line.startsWith('') ||
+      line.startsWith('')
     ) {
       console.log(chalk.gray(line));
-    } else if (line.startsWith('🟢') || line.startsWith('🟡') || line.startsWith('🔴')) {
+    } else if (line.startsWith('') || line.startsWith('') || line.startsWith('')) {
       console.log(line);
     } else if (line.includes('`')) {
       console.log(chalk.cyan(line));
@@ -371,7 +371,7 @@ function displayTutorialStep(step, stepNumber, totalSteps) {
   });
 
   if (step.action) {
-    console.log(chalk.yellow(`\n💡 ${step.action}`));
+    console.log(chalk.yellow(`\n${step.action}`));
   }
 
   console.log('');
@@ -396,7 +396,7 @@ async function runInteractiveTutorial(tutorialType) {
     output: process.stdout,
   });
 
-  console.log(chalk.bold.green(`\n🚀 Starting ${tutorial.icon} ${tutorial.name}`));
+  console.log(chalk.bold.green(`\nStarting ${tutorial.icon} ${tutorial.name}`));
   console.log(chalk.green(tutorial.description));
   console.log(chalk.gray(`Total steps: ${tutorial.steps.length}\n`));
 
@@ -420,7 +420,7 @@ async function runInteractiveTutorial(tutorialType) {
   rl.close();
 
   // Final message
-  console.log(chalk.bold.green(`\n🎉 ${tutorial.icon} ${tutorial.name} Complete!`));
+  console.log(chalk.bold.green(`\n${tutorial.icon} ${tutorial.name} Complete!`));
   console.log(chalk.green('You can always run this tutorial again with:'));
   console.log(chalk.cyan(`caws tutorial ${tutorialType}`));
   console.log('');
@@ -436,8 +436,8 @@ async function tutorialCommand(tutorialType, _options = {}) {
     async () => {
       if (!tutorialType) {
         // Show available tutorials
-        console.log(chalk.bold.cyan('\n📚 Available CAWS Tutorials'));
-        console.log(chalk.cyan('━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n'));
+        console.log(chalk.bold.cyan('\nAvailable CAWS Tutorials'));
+        console.log(chalk.cyan('==================================================\n'));
 
         Object.entries(TUTORIALS).forEach(([type, tutorial]) => {
           console.log(`${tutorial.icon} ${chalk.green(type.padEnd(12))} - ${tutorial.description}`);

package/dist/commands/validate.js

@@ -44,7 +44,7 @@ async function validateCommand(specFile, options = {}) {
 
     if (options.format !== 'json') {
       console.log(
-        chalk.cyan(`🔍 Validating ${specType === 'feature' ? 'feature' : 'working'} spec...`)
+        chalk.cyan(`Validating ${specType === 'feature' ? 'feature' : 'working'} spec...`)
       );
       console.log(chalk.gray(`   Spec: ${path.relative(process.cwd(), specPath)}`));
     }
@@ -166,7 +166,7 @@ async function validateCommand(specFile, options = {}) {
     } else {
       // Human-readable text output
       if (finalResult.valid) {
-        console.log(chalk.green('✅ Working spec validation passed'));
+        console.log(chalk.green('Working spec validation passed'));
         if (!options.quiet) {
           console.log(chalk.gray(`   Risk tier: ${spec.risk_tier}`));
           console.log(chalk.gray(`   Mode: ${spec.mode}`));
@@ -186,13 +186,13 @@ async function validateCommand(specFile, options = {}) {
           }
         }
       } else {
-        console.log(chalk.red('❌ Working spec validation failed'));
+        console.log(chalk.red('Working spec validation failed'));
 
         // Show errors
         finalResult.errors.forEach((error, index) => {
           console.log(`   ${index + 1}. ${chalk.red(error.message)}`);
           if (error.suggestion) {
-            console.log(`      ${chalk.blue('💡 ' + error.suggestion)}`);
+            console.log(`      ${chalk.blue('' + error.suggestion)}`);
           }
           if (error.example) {
             console.log(`      ${chalk.gray('Example:')}`);
@@ -210,7 +210,7 @@ async function validateCommand(specFile, options = {}) {
 
         // Show warnings
         if (finalResult.warnings && finalResult.warnings.length > 0) {
-          console.log(chalk.yellow('\n⚠️  Warnings:'));
+          console.log(chalk.yellow('\nWarnings:'));
           finalResult.warnings.forEach((warning, index) => {
             console.log(`   ${index + 1}. ${chalk.yellow(warning.message)}`);
           });
@@ -238,7 +238,7 @@ async function validateCommand(specFile, options = {}) {
         )
       );
     } else {
-      console.error(chalk.red('❌ Error during validation:'), error.message);
+      console.error(chalk.red('Error during validation:'), error.message);
     }
     // Don't call process.exit in test environment
     if (process.env.NODE_ENV !== 'test' && !process.env.JEST_WORKER_ID) {