run-prompt

<objective>
Execute one or more prompts from `./prompts/` as delegated sub-tasks with fresh context. Supports single prompt execution, parallel execution of multiple independent prompts, and sequential execution of dependent prompts.

**Execution Strategy Flags:**
- `--auto-detect`: Analyze prompt dependencies and choose strategy automatically (default)
- `--parallel`: Force parallel execution (independent tasks only)
- `--sequential`: Force sequential execution (safe for dependent tasks)
- `--no-input`: Non-interactive mode for CI/CD - uses auto-detect strategy

**Preference System:**
The command uses 3-tier preferences to determine execution strategy:
1. Config file: `.spec-flow/config/user-preferences.yaml` (default_strategy)
2. Command history: Learns from past usage
3. Command-line flags: Explicit overrides
</objective>

<input>
The user will specify which prompt(s) to run via $ARGUMENTS, which can be:

**Single prompt:**

- Empty (no arguments): Run the most recently created prompt (default behavior)
- A prompt number (e.g., "001", "5", "42")
- A partial filename (e.g., "user-auth", "dashboard")

**Multiple prompts:**

- Multiple numbers (e.g., "005 006 007")
- With execution flag: "005 006 007 --parallel" or "005 006 007 --sequential"
- If no flag specified with multiple prompts, default to --sequential for safety
  </input>

<process>
<step0_load_preferences>
**Load User Preferences (3-Tier System):**

Determine execution strategy using 3-tier preference system:

a. **Load configuration file** (Tier 1 - lowest priority):
   ```powershell
   $preferences = & .spec-flow/scripts/utils/load-preferences.ps1 -Command "run-prompt"
   $configStrategy = $preferences.commands.'run-prompt'.default_strategy  # "auto-detect", "parallel", or "sequential"
   ```

b. **Load command history** (Tier 2 - medium priority, overrides config):
   ```powershell
   $history = & .spec-flow/scripts/utils/load-command-history.ps1 -Command "run-prompt"

   if ($history.last_used_mode -and $history.total_uses -gt 0) {
       $preferredStrategy = $history.last_used_mode  # Use learned preference
   } else {
       $preferredStrategy = $configStrategy  # Fall back to config
   }
   ```

c. **Check command-line flags** (Tier 3 - highest priority):
   ```javascript
   const args = "$ARGUMENTS".trim();
   const hasParallelFlag = args.includes('--parallel');
   const hasSequentialFlag = args.includes('--sequential');
   const hasAutoDetect = args.includes('--auto-detect');
   const hasNoInput = args.includes('--no-input');

   let selectedStrategy;

   if (hasNoInput || hasAutoDetect) {
       selectedStrategy = 'auto-detect';  // CI/automation default
   } else if (hasParallelFlag) {
       selectedStrategy = 'parallel';  // Explicit parallel override
   } else if (hasSequentialFlag) {
       selectedStrategy = 'sequential';  // Explicit sequential override
   } else {
       selectedStrategy = preferredStrategy;  // Use config/history preference
   }
   ```

d. **Track usage for learning system**:
   ```powershell
   # Record selection after command completes successfully
   & .spec-flow/scripts/utils/track-command-usage.ps1 -Command "run-prompt" -Mode $selectedStrategy
   ```
</step0_load_preferences>

<step1_parse_arguments>
Parse $ARGUMENTS to extract:
- Prompt numbers/names (all arguments that are not flags)
- Execution strategy: Use selectedStrategy from preference system

<examples>
- "005" -> Single prompt: 005
- "005 006 007" -> Multiple prompts: [005, 006, 007], strategy: from preferences
- "005 006 007 --parallel" -> Multiple prompts: [005, 006, 007], strategy: parallel (override)
- "005 006 007 --sequential" -> Multiple prompts: [005, 006, 007], strategy: sequential (override)
- "005 006 007 --auto-detect" -> Multiple prompts: [005, 006, 007], strategy: auto-detect (analyze dependencies)
</examples>
</step1_parse_arguments>

<step2_resolve_files>
For each prompt number/name:

- If empty or "last": Find with `!ls -t ./prompts/*.md | head -1`
- If a number: Find file matching that zero-padded number (e.g., "5" matches "005-_.md", "42" matches "042-_.md")
- If text: Find files containing that string in the filename

<matching_rules>

- If exactly one match found: Use that file
- If multiple matches found: List them and ask user to choose
- If no matches found: Report error and list available prompts
  </matching_rules>
  </step2_resolve_files>

<step3_execute>
<single_prompt>

1. Read the complete contents of the prompt file
2. Delegate as sub-task using Task tool with subagent_type="general-purpose"
3. Wait for completion
4. Archive prompt to `./prompts/completed/` with metadata
5. Return results
   </single_prompt>

<parallel_execution>

1. Read all prompt files
2. **Spawn all Task tools in a SINGLE MESSAGE** (this is critical for parallel execution):
   <example>
   Use Task tool for prompt 005
   Use Task tool for prompt 006
   Use Task tool for prompt 007
   (All in one message with multiple tool calls)
   </example>
3. Wait for ALL to complete
4. Archive all prompts with metadata
5. Return consolidated results
   </parallel_execution>

<sequential_execution>

1. Read first prompt file
2. Spawn Task tool for first prompt
3. Wait for completion
4. Archive first prompt
5. Read second prompt file
6. Spawn Task tool for second prompt
7. Wait for completion
8. Archive second prompt
9. Repeat for remaining prompts
10. Return consolidated results
    </sequential_execution>
    </step3_execute>
    </process>

<context_strategy>
By delegating to a sub-task, the actual implementation work happens in fresh context while the main conversation stays lean for orchestration and iteration.
</context_strategy>

<output>
<single_prompt_output>
Executed: ./prompts/005-implement-feature.md
Archived to: ./prompts/completed/005-implement-feature.md

<results>
[Summary of what the sub-task accomplished]
</results>
</single_prompt_output>

<parallel_output>
Executed in PARALLEL:

- ./prompts/005-implement-auth.md
- ./pro