Interactive wizard to create PRD or task lists for /task-batch. Uses /clarify and /ask-questions-if-underspecified for precise task definition. Use when: (1) preparing batch execution, (2) creating PRDs, (3) defining task lists with dependencies. Triggers: /create-task-batch, 'create tasks', 'new batch', 'prepare PRD'.
Interactive wizard for creating PRD documents and task lists optimized for /task-batch execution. Uses guided questioning to extract precise requirements, priorities, and dependencies.
# Start interactive wizard
/create-task-batch
# With initial description
/create-task-batch "User authentication feature"
# For specific project area
/create-task-batch "API refactoring project"
+------------------------------------------------------------------+
| CREATE-TASK-BATCH WORKFLOW |
+------------------------------------------------------------------+
| |
| +----------+ +-----------+ +---------------+ |
| | GATHER |--->| DECOMPOSE |--->| PRIORITIZE | |
| | Context | | Into Tasks| | & Dependencies| |
| +----------+ +-----------+ +-------+-------+ |
| | |
| +--------------------------------------------v---------------+ |
| | VALIDATE | |
| | - Each task has acceptance criteria | |
| | - Dependencies are resolvable | |
| | - Priorities are assigned | |
| +---------------------------+-------------------------------+ |
| | |
| +---------------------------v-------------------------------+ |
| | OUTPUT | |
| | - PRD file (.prq.md) | |
| | - Task list (tasks.md) | |
| | - JSON config (optional) | |
| +------------------------------------------------------------+ |
| |
+------------------------------------------------------------------+
AskUserQuestion:
questions:
- question: "What is the main goal of this batch?"
header: "Goal"
options:
- label: "New Feature"
description: "Implement a complete new feature"
- label: "Bug Fixes"
description: "Fix multiple related bugs"
- label: "Refactoring"
description: "Restructure existing code"
- label: "Documentation"
description: "Create or update documentation"
- question: "What is the project area?"
header: "Area"
options:
- label: "Backend API"
- label: "Frontend UI"
- label: "Database"
- label: "Infrastructure"
- label: "Full Stack"
- question: "Does the project have a DESIGN.md (design system)?"
header: "Design System"
options:
- label: "Yes, use existing DESIGN.md"
description: "Load design tokens for frontend consistency"
- label: "No, create one with /design-system init"
description: "Initialize a 9-section design system first"
- label: "Not applicable (backend only)"
description: "Skip design system for non-frontend work"
- question: "What is the target timeframe?"
header: "Timeframe"
options:
- label: "Single session"
- label: "1-2 days"
- label: "1 week"
- label: "Sprint (2 weeks)"
AskUserQuestion:
questions:
- question: "Describe the main feature/functionality in detail"
header: "Description"
multiSelect: false
# User provides free-form description
- question: "What are the MUST-HAVE components?"
header: "Must Have"
multiSelect: true
options:
- label: "Authentication"
- label: "Data validation"
- label: "Error handling"
- label: "Logging"
- label: "Testing"
- label: "Documentation"
- question: "What are NICE-TO-HAVE components?"
header: "Nice to Have"
multiSelect: true
options:
- label: "Performance optimization"
- label: "Caching"
- label: "Rate limiting"
- label: "Monitoring"
- label: "CI/CD integration"
# Automatic decomposition based on responses
Task Decomposition Rules:
- Backend Feature:
1. Create data models/schemas
2. Implement business logic
3. Create API endpoints
4. Add validation
5. Write tests
6. Update documentation
- Frontend Feature:
1. Create UI components
2. Implement state management
3. Connect to API
4. Add error handling
5. Write tests
6. Update documentation
- Refactoring:
1. Analyze current implementation
2. Design new structure
3. Create new modules
4. Migrate existing code
5. Update tests
6. Remove deprecated code
AskUserQuestion:
questions:
- question: "How should tasks be prioritized?"
header: "Priority"
options:
- label: "Auto (by dependencies)"
- label: "Manual (I will specify)"
- label: "By effort (easiest first)"
- label: "By importance (critical first)"
- question: "Should execution stop on first failure?"
header: "Stop on Fail"
options:
- label: "Yes - Stop entire batch"
- label: "No - Continue with remaining"
CRITICAL: Every task MUST have explicit completion validation criteria. No task can be executed without defined acceptance criteria.
# MANDATORY: For EACH generated task, ask completion criteria
FOR EACH task IN task_list:
AskUserQuestion:
questions:
- question: "Define MANDATORY completion criteria for '[TASK_NAME]':"
header: "Criteria"
# MANDATORY - Cannot proceed without answer
- question: "How will we VERIFY this task is complete?"
header: "Verification"
options:
- label: "Tests pass"
description: "Unit/integration tests must pass"
- label: "File exists"
description: "Specific file(s) created/modified"
- label: "Command succeeds"
description: "Specific command runs without error"
- label: "Manual review"
description: "Human reviews and approves"
- question: "What files/modules are affected by '[TASK_NAME]'?"
header: "Files"
# Optional but recommended
# VALIDATION CHECK
IF any_task_missing_criteria:
BLOCK: "Cannot create batch - all tasks MUST have completion criteria"
ASK: Request missing criteria before proceeding
Each task in the output MUST include: