fix: implementation pre-requesit in build mode

Author: kanfil

scripts/bash/check-prerequisites.sh

@@ -55,10 +55,10 @@ OPTIONS:
   --help, -h          Show this help message
 
 EXAMPLES:
-  # Check task prerequisites (plan.md required)
+  # Check task prerequisites (plan.md required in spec mode)
   ./check-prerequisites.sh --json
   
-  # Check implementation prerequisites (plan.md + tasks.md required)
+  # Check implementation prerequisites (plan.md required in spec mode, tasks.md always required)
   ./check-prerequisites.sh --json --require-tasks --include-tasks
   
   # Get feature paths only (no validation)
@@ -219,10 +219,28 @@ if [[ ! -d "$FEATURE_DIR" ]]; then
     exit 1
 fi
 
+# Check for plan.md (required in spec mode, optional in build mode)
 if [[ ! -f "$IMPL_PLAN" ]]; then
-    echo "ERROR: plan.md not found in $FEATURE_DIR" >&2
-    echo "Run /speckit.plan first to create the implementation plan." >&2
-    exit 1
+    # Get current mode to determine if plan.md is required
+    local current_mode="spec"
+    if [[ -f ".specify/config/mode.json" ]]; then
+        current_mode=$(python3 -c "
+import json
+try:
+    with open('.specify/config/mode.json', 'r') as f:
+        data = json.load(f)
+    print(data.get('current_mode', 'spec'))
+except:
+    print('spec')
+" 2>/dev/null || echo "spec")
+    fi
+
+    if [[ "$current_mode" == "spec" ]]; then
+        echo "ERROR: plan.md not found in $FEATURE_DIR" >&2
+        echo "Run /speckit.plan first to create the implementation plan." >&2
+        exit 1
+    fi
+    # In build mode, plan.md is optional - allow implementation to proceed
 fi
 
 if [[ ! -f "$CONTEXT" ]]; then

scripts/bash/implement.sh

@@ -119,8 +119,17 @@ check_checklists_status() {
 load_implementation_context() {
     log_info "Loading implementation context..."
 
-    # Required files
-    local required_files=("tasks.md" "plan.md" "spec.md")
+    # Get current workflow mode
+    local workflow_mode="spec"  # Default
+    if [[ -f ".specify/config/mode.json" ]]; then
+        workflow_mode=$(jq -r '.current_mode // "spec"' ".specify/config/mode.json" 2>/dev/null || echo "spec")
+    fi
+
+    # Required files (plan.md is optional in build mode)
+    local required_files=("tasks.md" "spec.md")
+    if [[ "$workflow_mode" == "spec" ]]; then
+        required_files+=("plan.md")
+    fi
 
     for file in "${required_files[@]}"; do
         if [[ ! -f "$FEATURE_DIR/$file" ]]; then
@@ -129,6 +138,12 @@ load_implementation_context() {
         fi
     done
 
+    # Optional files (plan.md is optional in build mode)
+    local optional_files=("data-model.md" "contracts/" "research.md" "quickstart.md")
+    if [[ "$workflow_mode" == "build" ]]; then
+        optional_files+=("plan.md")
+    fi
+
     # Optional files
     local optional_files=("data-model.md" "contracts/" "research.md" "quickstart.md")
 

scripts/powershell/check-prerequisites.ps1

@@ -40,10 +40,10 @@ OPTIONS:
   -Help, -h           Show this help message
 
 EXAMPLES:
-  # Check task prerequisites (plan.md required)
+  # Check task prerequisites (plan.md required in spec mode)
   .\check-prerequisites.ps1 -Json
   
-  # Check implementation prerequisites (plan.md + tasks.md required)
+  # Check implementation prerequisites (plan.md required in spec mode, tasks.md always required)
   .\check-prerequisites.ps1 -Json -RequireTasks -IncludeTasks
   
   # Get feature paths only (no validation)
@@ -150,10 +150,27 @@ if (-not (Test-Path $paths.FEATURE_DIR -PathType Container)) {
     exit 1
 }
 
+# Check for plan.md (required in spec mode, optional in build mode)
 if (-not (Test-Path $paths.IMPL_PLAN -PathType Leaf)) {
-    Write-Output "ERROR: plan.md not found in $($paths.FEATURE_DIR)"
-    Write-Output "Run /speckit.plan first to create the implementation plan."
-    exit 1
+    # Get current mode to determine if plan.md is required
+    $currentMode = "spec"
+    $modeFile = ".specify/config/mode.json"
+    if (Test-Path $modeFile) {
+        try {
+            $modeData = Get-Content $modeFile | ConvertFrom-Json
+            $currentMode = $modeData.current_mode
+            if (-not $currentMode) { $currentMode = "spec" }
+        } catch {
+            $currentMode = "spec"
+        }
+    }
+
+    if ($currentMode -eq "spec") {
+        Write-Output "ERROR: plan.md not found in $($paths.FEATURE_DIR)"
+        Write-Output "Run /speckit.plan first to create the implementation plan."
+        exit 1
+    }
+    # In build mode, plan.md is optional - allow implementation to proceed
 }
 
 # Check for tasks.md if required

scripts/powershell/implement.ps1

@@ -121,8 +121,24 @@ function Test-ChecklistsStatus {
 function Import-ImplementationContext {
     Write-Info "Loading implementation context..."
 
-    # Required files
-    $requiredFiles = @("tasks.md", "plan.md", "spec.md")
+    # Get current workflow mode
+    $workflowMode = "spec"  # Default
+    $modeFile = ".specify/config/mode.json"
+    if (Test-Path $modeFile) {
+        try {
+            $modeData = Get-Content $modeFile | ConvertFrom-Json
+            $workflowMode = $modeData.current_mode
+            if (-not $workflowMode) { $workflowMode = "spec" }
+        } catch {
+            $workflowMode = "spec"
+        }
+    }
+
+    # Required files (plan.md is optional in build mode)
+    $requiredFiles = @("tasks.md", "spec.md")
+    if ($workflowMode -eq "spec") {
+        $requiredFiles += "plan.md"
+    }
 
     foreach ($file in $requiredFiles) {
         $filePath = Join-Path $global:FeatureDir $file
@@ -132,8 +148,11 @@ function Import-ImplementationContext {
         }
     }
 
-    # Optional files
+    # Optional files (plan.md is optional in build mode)
     $optionalFiles = @("data-model.md", "contracts", "research.md", "quickstart.md")
+    if ($workflowMode -eq "build") {
+        $optionalFiles += "plan.md"
+    }
 
     foreach ($file in $optionalFiles) {
         $filePath = Join-Path $global:FeatureDir $file

spec-driven.md

@@ -97,7 +97,7 @@ Once a feature specification exists, this command creates a comprehensive implem
 
 After a plan is created, this command analyzes the plan and related design documents to generate an executable task list:
 
-1. **Inputs**: Reads `plan.md` (required) and, if present, `data-model.md`, `contracts/`, and `research.md`
+1. **Inputs**: Reads `plan.md` (required in spec mode, optional in build mode) and, if present, `data-model.md`, `contracts/`, and `research.md`
 2. **Task Derivation**: Converts contracts, entities, and scenarios into specific tasks
 3. **Parallelization**: Marks independent tasks `[P]` and outlines safe parallel groups
 4. **Output**: Writes `tasks.md` in the feature directory, ready for execution by a Task agent

templates/commands/implement.md

@@ -78,9 +78,9 @@ You **MUST** consider the user input before proceeding (if not empty).
      * Automatically proceed to step 3
 
 3. Load and analyze the implementation context:
-   - **REQUIRED**: Read tasks.md for the complete task list and execution plan
-   - **REQUIRED**: Read plan.md for tech stack, architecture, and file structure
-   - **IF EXISTS**: Read data-model.md for entities and relationships
+    - **REQUIRED**: Read tasks.md for the complete task list and execution plan
+    - **REQUIRED**: Read plan.md for tech stack, architecture, and file structure (optional in build mode)
+    - **IF EXISTS**: Read data-model.md for entities and relationships
    - **IF EXISTS**: Read contracts/ for API specifications and test requirements
    - **IF EXISTS**: Read research.md for technical decisions and constraints
    - **IF EXISTS**: Read quickstart.md for integration scenarios
@@ -104,7 +104,7 @@ You **MUST** consider the user input before proceeding (if not empty).
    **If ignore file already exists**: Verify it contains essential patterns, append missing critical patterns only
    **If ignore file missing**: Create with full pattern set for detected technology
    
-   **Common Patterns by Technology** (from plan.md tech stack):
+    **Common Patterns by Technology** (from plan.md tech stack if available, otherwise detect from project files):
    - **Node.js/JavaScript**: `node_modules/`, `dist/`, `build/`, `*.log`, `.env*`
    - **Python**: `__pycache__/`, `*.pyc`, `.venv/`, `venv/`, `dist/`, `*.egg-info/`
    - **Java**: `target/`, `*.class`, `*.jar`, `.gradle/`, `build/`

templates/tasks-template.md

@@ -5,7 +5,7 @@ description: "Task list template for feature implementation"
 # Tasks: [FEATURE NAME]
 
 **Input**: Design documents from `/specs/[###-feature-name]/`
-**Prerequisites**: plan.md (required), spec.md (required for user stories), research.md, data-model.md, contracts/
+**Prerequisites**: plan.md (required in spec mode, optional in build mode), spec.md (required for user stories), research.md, data-model.md, contracts/
 
 **Tests**: The examples below include test tasks. Tests are OPTIONAL - only include them if explicitly requested in the feature specification.