Add $ARGUMENTS support to promptengineering slash commands

- Update convert-to-test-driven-prompt.md to support file input via $ARGUMENTS
- Update batch-operations-prompt.md to support file input via $ARGUMENTS
- Add usage examples showing file path syntax with @ symbol
- Maintain consistency with other slash commands like apply-thinking-to

.claude/commands/promptengineering/batch-operations-prompt.md

@@ -9,6 +9,10 @@ Optimize prompts for multiple file operations, parallel processing, and efficien
 "Batch prompt for: Rename variable across multiple files"
 "Optimize for parallel: Add logging to all service files"
 
+### With File Input
+`/batch-operations-prompt @path/to/operation-request.md`
+`/batch-operations-prompt @../refactoring-plan.txt`
+
 ### Complex Operations
 "Batch refactor: Convert callbacks to async/await in all files"
 "Parallel update: Add TypeScript types to all components"
@@ -18,6 +22,11 @@ Optimize prompts for multiple file operations, parallel processing, and efficien
 
 When creating batch operation prompts:
 
+### Input Handling
+- If `$ARGUMENTS` is provided, read the file at that path to get the operation request to optimize
+- If no `$ARGUMENTS`, use the user's direct input as the operation to optimize
+- Support relative and absolute file paths
+
 1. **Identify Parallelizable Tasks**: Determine what can be done simultaneously
 2. **Group Related Operations**: Organize tasks by type and dependency
 3. **Create Efficient Sequences**: Order operations to minimize conflicts

.claude/commands/promptengineering/convert-to-test-driven-prompt.md

@@ -9,6 +9,10 @@ Transform user requests into Test-Driven Development (TDD) style prompts that ex
 "Make this test-driven: Create a shopping cart component"
 "TDD version: Implement data validation for the form"
 
+### With File Input
+`/convert-to-test-driven-prompt @path/to/prompt-file.md`
+`/convert-to-test-driven-prompt @../other-project/feature-request.txt`
+
 ### Complex Scenarios
 "Convert to TDD: Refactor the payment processing module"
 "Test-driven approach for: API rate limiting feature"
@@ -18,6 +22,11 @@ Transform user requests into Test-Driven Development (TDD) style prompts that ex
 
 When converting to TDD prompts:
 
+### Input Handling
+- If `$ARGUMENTS` is provided, read the file at that path to get the prompt to convert
+- If no `$ARGUMENTS`, use the user's direct input as the prompt to convert
+- Support relative and absolute file paths
+
 1. **Extract Requirements**: Identify core functionality from the original request
 2. **Define Test Cases**: Create specific, measurable test scenarios
 3. **Specify Expected Outcomes**: Clear success and failure criteria