code-task-generator

Code Task Generator

Overview

Generate structured code task files from rough descriptions or PDD implementation plans. Auto-detects input type and creates properly formatted .code-task.md files. For PDD plans, processes one step at a time to allow learning between steps.

Important Notes

These rules apply across ALL steps:

• User approval required: Present the task breakdown plan and get explicit approval before generating any files.
• Tests are integrated: Include unit test requirements in each task's acceptance criteria. Never create separate "add tests" tasks.
• PDD mode references: Always include the design document path as required reading. Only include research docs if directly relevant to the specific task.

Parameters

• input (required): Task description, file path, or PDD plan path
• step_number (optional, PDD only): Specific step to process. Auto-determines next uncompleted step if omitted.
• output_dir (optional, default: .ralph/tasks/): Output directory for code task files
• task_name (optional, description mode only): Override auto-generated task name

Constraints:

• You MUST ask for all required parameters upfront in a single prompt
• You MUST support input as: direct text, file path, directory path (looks for plan.md), or URL

Steps

1. Detect Input Mode

Check if input is a file with PDD plan structure (checklist + numbered steps). Set mode to "pdd" or "description" and inform the user.

2. Analyze Input

• PDD mode: Parse the plan, extract steps and checklist status, determine target step (from step_number or first uncompleted)
• Description mode: Identify core functionality, technical requirements, complexity level (Low/Medium/High), and technology domain

3. Structure Requirements

• PDD mode: Extract the target step's title, description, demo requirements, constraints, and integration notes with previous steps. Identify relevant research documents.
• Description mode: Identify functional requirements, infer technical constraints and dependencies.

For both modes: create measurable acceptance criteria in Given-When-Then format and prepare a task breakdown plan.

4. Plan Tasks

Present the proposed breakdown to the user:

• One-line summary per task
• Proposed sequence and dependencies
• You MUST NOT generate files until the user explicitly approves

5. Generate Tasks

Create files following the Code Task Format below.