convert-to-todowrite-tasklist-prompt

Convert Complex Prompts to TodoWrite Tasklist Method

Purpose: Transform verbose, context-heavy slash commands into efficient TodoWrite tasklist-based methods with parallel subagent execution for 60-70% speed improvements.

Usage: /convert-to-todowrite-tasklist-prompt @/path/to/original-slash-command.md

---

CONVERSION EXECUTION

Step 1: Read Original Prompt

File to Convert: $ARGUMENT

First, analyze the original slash command file to understand its structure, complexity, and conversion opportunities.

Step 2: Apply Conversion Framework

Transform the original prompt using the TodoWrite tasklist method with parallel subagent optimization.

Step 3: Generate Optimized Version

Output the converted slash command with efficient task delegation and context management.

---

Argument Variable Integration

When converting slash commands, ensure proper argument handling for dynamic inputs:

Standard Argument Variables

## ARGUMENT HANDLING

**File Input**: {file_path} or {code} - The primary file(s) or code to analyze
**Analysis Scope**: {scope} - Specific focus areas (security, performance, quality, architecture, all)
**Output Format**: {format} - Report format (detailed, summary, action_items)
**Target Audience**: {audience} - Intended audience (technical, executive, security_team)
**Priority Level**: {priority} - Analysis depth (quick, standard, comprehensive)
**Context**: {context} - Additional project context and constraints

### Usage Examples:
```bash
# Basic usage with file input
/comprehensive-review file_path="@src/main.py" scope="security,performance"

# Advanced usage with multiple parameters  
/comprehensive-review file_path="@codebase/" scope="all" format="detailed" audience="technical" priority="comprehensive" context="Production deployment review"

# Quick analysis with minimal scope
/comprehensive-review file_path="@config.yaml" scope="security" format="summary" priority="quick"

Argument Integration in TodoWrite Tasks

Dynamic Task Content Based on Arguments:

[
  {"id": "setup_analysis", "content": "Record start time and initialize analysis for {file_path}", "status": "pending", "priority": "high"},
  {"id": "security_analysis", "content": "Security Analysis of {file_path} - Focus: {scope}", "status": "pending", "priority": "high"},
  {"id": "report_generation", "content": "Generate {format} report for {audience}", "status": "pending", "priority": "high"}
]

---

Conversion Analysis Framework

Step 1: Identify Context Overload Patterns

Context Overflow Indicators:

•  Massive Instructions: >1000 lines of detailed frameworks and methodologies
•  Upfront Mass File Loading: Attempting to load 10+ files simultaneously with @filename syntax
•  Verbose Framework Application: Extended thinking sections, redundant validation loops
•  Sequential Bottlenecks: All analysis phases running one after another instead of parallel
•  Redundant Content: Multiple repeated frameworks, bias detection, steel man reasoning overengineering

Success Patterns to Implement:

•  Task Tool Delegation: Specialized agents for bounded analysis domains
•  Progressive Synthesis: Incremental building rather than simultaneous processing
•  Parallel Execution: Multiple subagents running simultaneously
•  Context Recycling: Fresh context for each analysis phase
•  Strategic File Selection: Phase-specific file targeting

Step 2: Task Decomposition Strategy

Convert Monolithic Workflows Into:

1. Setup Phase: Initialization and timestamp recording
2. Parallel Analysis Phases: 2-4 specialized domains running simultaneously
3. Synthesis Phase: Consolidation of parallel findings
4. Verification Phase: Quality assurance and validation
5. Completion Phase: Final integration and timestamp

Example Decomposition:

BEFORE (Sequential):
Security Analysis (10 min) � Performance Analysis (10 min) � Quality Analysis (10 min) = 30 minutes