Run Prompt Dtd

%cc-core; ]>

name: run-prompt description: Delegate one or more prompts to fresh sub-task contexts with parallel or sequential execution argument-hint: <prompt-number(s)-or-name> [--parallel|--sequential] allowed-tools: [Read, Task, Bash(ls:), Bash(mv:), Bash(git:*)]

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

• If empty or "last": Find most recently modified prompt with find ./.prompts -name '*.md' -not -path '*/completed/*' -not -name 'INDEX.md' | xargs ls -t | head -1
• If a number: Search ALL category subfolders for a file starting with that number. Use glob ./.prompts/**/{number}*.md (exclude completed/). For example, "233" matches ./.prompts/2xx-job-search/233-apply-google.md.
• If text: Find files containing that string in the filename across all subfolders

• 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
• IMPORTANT: Search recursively in ./.prompts/**/ — prompts are in category subfolders, NOT at the root

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 completed/ subfolder WITHIN its category (e.g., ./.prompts/2xx-job-search/completed/233-name.md), NOT to a root ./.prompts/completed/
5. Commit all work:
   • Stage files YOU modified with git add [file] (never git add .)
   • Determine appropriate commit type based on changes (fix|feat|refactor|style|docs|test|chore)
   • Commit with format: [type]: [description] (lowercase, specific, concise)
6. Return results

1. Read all prompt files
2. Spawn all Task tools in a SINGLE MESSAGE (this is critical for parallel execution):
3. Wait for ALL to complete
4. Archive all prompts to their category's completed/ subfolder
5. Commit all work:
   • Stage files YOU modified with git add [file] (never git add .)
   • Determine appropriate commit type based on changes (fix|feat|refactor|style|docs|test|chore)
   • Commit with format: [type]: [description] (lowercase, specific, concise)
6. Return consolidated results

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. Archive all prompts to their category's completed/ subfolder
11. Commit all work:
    • Stage files YOU modified with git add [file] (never git add .)
    • Determine appropriate commit type based on changes (fix|feat|refactor|style|docs|test|chore)
    • Commit with format: [type]: [description] (lowercase, specific, concise)
12. Return consolidated results

• ./.prompts/005-implement-auth.md
• ./.prompts/006-implement-api.md
• ./.prompts/007-implement-ui.md

✓ All archived to ./.prompts/completed/

1. ./.prompts/005-setup-database.md → Success
2. ./.prompts/006-create-migrations.md → Success
3. ./.prompts/007-seed-data.md → Success

✓ All archived to ./.prompts/completed/

• For parallel execution: ALL Task tool calls MUST be in a single message
• For sequential execution: Wait for each Task to complete before starting next
• Archive prompts only after successful completion
• If the working directory is NOT a git repository (Git status shows "(not a git repository ...)"), SKIP all git staging/commit steps entirely — do not fail, just proceed without committing and note it in the output
• If any prompt fails, stop sequential execution and report error
• Provide clear, consolidated results for multiple prompt execution