claude-fsd 1.5.24 → 1.5.25

package/README.md

@@ -113,7 +113,6 @@ Generates a comprehensive development plan based on:
    - Analyzes all open tasks in PLAN.md
    - Intelligently executes tasks (sequentially or in parallel)
    - Updates the plan to track progress
-   - Runs unit tests before declaring completion (if docs/unit-test exists)
    - Repeats until all tasks are complete or **<ALL DONE>** is detected
 
 ## Monitoring Progress (Like Tesla FSD)
@@ -159,7 +158,6 @@ your-project/
 │   ├── QUESTIONS.md     # Interview questions and answers
 │   ├── REQUIREMENTS.md  # Consolidated requirements from interview
 │   ├── IDEAS.md         # Future ideas and improvements
-│   ├── unit-test        # Executable test script (exit 0 = pass)
 │   └── INTERVIEW-SESSION.json  # Interview session metadata
 ├── logs/                # Logs from each AI session
 └── [your code files]

package/bin/claudefsd

@@ -246,17 +246,6 @@ if [ $# -eq 0 ]; then
                 echo "- Success criterion 1" >> "$WORKING_DIR/BRIEF.md"
                 echo "- Success criterion 2" >> "$WORKING_DIR/BRIEF.md"
                 
-                # Create placeholder unit-test script
-                cat > "$WORKING_DIR/unit-test" << 'EOF'
-#!/bin/bash
-# Unit tests for the project
-# Add your tests here. Exit 0 for success, non-zero for failure.
-
-echo "No tests defined yet - placeholder passes"
-exit 0
-EOF
-                chmod +x "$WORKING_DIR/unit-test"
-                
                 open_with_editor "$WORKING_DIR/BRIEF.md"
                 echo
                 echo -e "${GREEN}Brief created! Run claudefsd again to start the interview.${NC}"

package/bin/claudefsd-analyze-brief

@@ -32,14 +32,7 @@ if [ "$EDITOR" == "" ]; then
     EDITOR="nano"
 fi
 
-# Generate log filename with working-dir token if set
-if [ "$WORKING_DIR" != "docs" ]; then
-    # Extract a clean token from the working directory path
-    WORKING_DIR_TOKEN=$(echo "$WORKING_DIR" | sed 's/[^a-zA-Z0-9]/-/g' | sed 's/^-\+//;s/-\+$//')
-    LOGFILE="logs/claude-${WORKING_DIR_TOKEN}-$(date +%Y%m%d_%H%M%S).txt"
-else
-    LOGFILE="logs/claude-$(date +%Y%m%d_%H%M%S).txt"
-fi
+LOGFILE="logs/claude-$(date +%Y%m%d_%H%M%S).txt"
 
 echo -e "\033[32m==================================================================\033[0m"
 echo -e "\033[32m== ANALYZING PROJECT BRIEF\033[0m"

package/bin/claudefsd-analyze-brief-personas

@@ -54,14 +54,7 @@ if [ $? -ne 0 ]; then
     exit 1
 fi
 
-# Generate log filename with working-dir token if set
-if [ "$WORKING_DIR" != "docs" ]; then
-    # Extract a clean token from the working directory path
-    WORKING_DIR_TOKEN=$(echo "$WORKING_DIR" | sed 's/[^a-zA-Z0-9]/-/g' | sed 's/^-\+//;s/-\+$//')
-    LOGFILE="logs/claude-${WORKING_DIR_TOKEN}-$(date +%Y%m%d_%H%M%S).txt"
-else
-    LOGFILE="logs/claude-$(date +%Y%m%d_%H%M%S).txt"
-fi
+LOGFILE="logs/claude-$(date +%Y%m%d_%H%M%S).txt"
 
 echo -e "\033[32m==================================================================\033[0m"
 echo -e "\033[32m== ANALYZING PROJECT BRIEF WITH EXPERT PERSONAS\033[0m"

package/bin/claudefsd-create-plan

@@ -44,14 +44,7 @@ if [ ! -f "$WORKING_DIR/QUESTIONS.md" ] && [ ! -f "$WORKING_DIR/REQUIREMENTS.md"
     exit 1
 fi
 
-# Generate log filename with working-dir token if set
-if [ "$WORKING_DIR" != "docs" ]; then
-    # Extract a clean token from the working directory path
-    WORKING_DIR_TOKEN=$(echo "$WORKING_DIR" | sed 's/[^a-zA-Z0-9]/-/g' | sed 's/^-\+//;s/-\+$//')
-    LOGFILE="logs/claude-${WORKING_DIR_TOKEN}-$(date +%Y%m%d_%H%M%S).txt"
-else
-    LOGFILE="logs/claude-$(date +%Y%m%d_%H%M%S).txt"
-fi
+LOGFILE="logs/claude-$(date +%Y%m%d_%H%M%S).txt"
 
 echo -e "\033[32m==================================================================\033[0m"
 echo -e "\033[32m== CREATING PLAN FROM PROJECT INPUTS\033[0m"
@@ -97,15 +90,6 @@ INFRASTRUCTURE PROPORTIONALITY RULES:
 - Follow existing claude-fsd pattern: separate focused scripts, not monoliths
 - FAIL LOUD - simple error handling, exit on failure
 - Choose infrastructure complexity appropriate to solution size
-
-WEB TESTING REQUIREMENTS:
-- If the project includes ANY web interface (including dashboards, web apps, or APIs with UI):
-  - MUST include web testing tasks in the plan
-  - Use playwright MCP for browser automation and testing
-  - Create $WORKING_DIR/WEBTESTS.md to document web test scenarios
-  - Test both structure/functionality AND visual appearance with screenshots
-  - Include tests for: page rendering, user interactions, form submissions, navigation
-  - Web tests should cover happy paths and key error scenarios
 "
 
 # run BA's

package/bin/claudefsd-dev

@@ -69,10 +69,7 @@ LOOP_COUNTER=0
 
 # Failure detection variables
 CONSECUTIVE_FAST_ITERATIONS=0
-MIN_ITERATION_TIME=60   # 1 minute in seconds
-
-# Unit test failure tracking
-UNIT_TEST_FAILURE_INFO=""
+MIN_ITERATION_TIME=300  # 5 minutes in seconds
 
 while true; do
     # Record iteration start time
@@ -81,21 +78,11 @@ while true; do
     # Increment loop counter
     LOOP_COUNTER=$((LOOP_COUNTER + 1))
     
-    # Unit test failure info will persist from previous iteration if tests failed
-    
     mkdir -p logs
     # Use a temporary directory for tmp files
     mkdir -p tmp
     export TMPDIR=tmp/
-    
-    # Generate log filename with working-dir token if set
-    if [ "$WORKING_DIR" != "docs" ]; then
-        # Extract a clean token from the working directory path
-        WORKING_DIR_TOKEN=$(echo "$WORKING_DIR" | sed 's/[^a-zA-Z0-9]/-/g' | sed 's/^-\+//;s/-\+$//')
-        LOGFILE="logs/claude-dev-${WORKING_DIR_TOKEN}-$(date +%Y%m%d_%H%M%S).txt"
-    else
-        LOGFILE="logs/claude-dev-$(date +%Y%m%d_%H%M%S).txt"
-    fi
+    LOGFILE="logs/claude-dev-$(date +%Y%m%d_%H%M%S).txt"
 
     echo "Logging to ${LOGFILE} ..."
 
@@ -115,19 +102,7 @@ while true; do
     fi
 
     # Build the development prompt combining intelligent task selection with parallel execution
-    DEVELOPMENT_PROMPT="$MEGATHINKING_MODE"
-    
-    # Add unit test failure info if present
-    if [ -n "$UNIT_TEST_FAILURE_INFO" ]; then
-        DEVELOPMENT_PROMPT="$DEVELOPMENT_PROMPT
-==== CRITICAL: UNIT TEST FAILURE FROM PREVIOUS ITERATION ====
-$UNIT_TEST_FAILURE_INFO
-==== END UNIT TEST FAILURE INFO ====
-
-"
-    fi
-    
-    DEVELOPMENT_PROMPT="$DEVELOPMENT_PROMPT
+    DEVELOPMENT_PROMPT="$MEGATHINKING_MODE
 You are an elite AI developer working in an automated development environment. Your job is to IMPLEMENT tasks from the project plan, not just analyze them. You can either implement tasks directly yourself or coordinate parallel Task agents for independent work.
 
 **PROJECT FILES TO READ AND ANALYZE:**"
@@ -301,59 +276,11 @@ Be thorough but concise in your verification."
 
     # Check if verifier has confirmed all tasks are complete (only in output section)
     if sed -n '/=== OUTPUT ===/,$p' $VERIFIER_LOGFILE | grep -q "^<VERIFIED_ALL_DONE>$"; then
-        echo -e "\033[33m==================================================================\033[0m"
-        echo -e "\033[33m== VERIFIER THINKS WE'RE DONE - CHECKING UNIT TESTS...\033[0m"
-        echo -e "\033[33m==================================================================\033[0m"
-        
-        # Check if unit test script exists
-        if [ -f "$WORKING_DIR/unit-test" ]; then
-            echo -e "\033[36mFound $WORKING_DIR/unit-test - running unit tests...\033[0m"
-            # Generate unit test log filename with working-dir token if set
-            if [ "$WORKING_DIR" != "docs" ]; then
-                WORKING_DIR_TOKEN=$(echo "$WORKING_DIR" | sed 's/[^a-zA-Z0-9]/-/g' | sed 's/^-\+//;s/-\+$//')
-                UNIT_TEST_LOGFILE="logs/unit-test-${WORKING_DIR_TOKEN}-$(date +%Y%m%d_%H%M%S).txt"
-            else
-                UNIT_TEST_LOGFILE="logs/unit-test-$(date +%Y%m%d_%H%M%S).txt"
-            fi
-            
-            # Run unit tests and capture exit code
-            if "$WORKING_DIR/unit-test" 2>&1 | tee $UNIT_TEST_LOGFILE; then
-                echo -e "\033[32m==================================================================\033[0m"
-                echo -e "\033[32m== UNIT TESTS PASSED!\033[0m"
-                echo -e "\033[32m== PROJECT COMPLETE - ALL TASKS VERIFIED AND TESTED!\033[0m"
-                echo -e "\033[32m==================================================================\033[0m"
-                # Clear any previous unit test failure info
-                UNIT_TEST_FAILURE_INFO=""
-                exit 0
-            else
-                echo -e "\033[31m==================================================================\033[0m"
-                echo -e "\033[31m== UNIT TESTS FAILED!\033[0m"
-                echo -e "\033[31m==================================================================\033[0m"
-                echo -e "\033[31mUnit test output saved to: $UNIT_TEST_LOGFILE\033[0m"
-                echo -e "\033[31mContinuing development loop to fix failing tests...\033[0m"
-                
-                # Store unit test failure info for next iteration
-                UNIT_TEST_FAILURE_INFO="UNIT TEST FAILURE DETECTED!
-The verifier thought all tasks were complete, but unit tests are failing.
-Unit test output is available in: $UNIT_TEST_LOGFILE
-You MUST fix these failing tests before the project can be considered complete."
-            fi
-        else
-            # No unit tests found, accept verifier's judgment
-            echo -e "\033[33mNo $WORKING_DIR/unit-test script found - accepting verifier's judgment\033[0m"
-            echo -e "\033[32m==================================================================\033[0m"
-            echo -e "\033[32m== PROJECT COMPLETE - ALL TASKS VERIFIED!\033[0m"
-            echo -e "\033[32m==================================================================\033[0m"
-            exit 0
-        fi
-    else
-        # Verifier doesn't think we're done, so clear any unit test failure info
-        # (we're back to working on regular tasks)
-        UNIT_TEST_FAILURE_INFO=""
+        echo -e "\033[32m==================================================================\033[0m"
+        echo -e "\033[32m== PROJECT COMPLETE - ALL TASKS VERIFIED!\033[0m"
+        echo -e "\033[32m==================================================================\033[0m"
+        exit 0
     fi
-    
-    # Show timestamp after verifier run
-    echo -e "\033[36mVerifier completed at: $(date)\033[0m"
 
     # Calculate iteration duration and check for failure patterns
     ITERATION_END_TIME=$(date +%s)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-fsd",
-  "version": "1.5.24",
+  "version": "1.5.25",
   "description": "Claude Full Self Drive tools for autonomous AI-powered development",
   "bin": {
     "claude-fsd": "bin/claude-fsd",