expand-task

To turn vague tasks into concrete development plans, you can automate task expansion by investigating your codebase to locate real files, patterns, and references. This grounds each step in actual artifacts with explicit file paths and verification commands, preventing ambiguity.

Generating a TDD workflow plan involves expanding your task into a step-by-step sequence where each step represents a TDD cycle. The process maps changes to actual codebase files and includes explicit verification commands to ensure every step is executable and testable.

Creating an implementation plan with machine-checkable verification requires grounding your steps in the codebase and appending a final cape check. This provides a final, machine-checkable verification for the complete plan to ensure successful integration.

You should split a large implementation task when expanding it would exceed 10 steps. The task expansion process advises splitting large tasks at this threshold to maintain manageable, verifiable, and focused development cycles.

Yes, you can use codebase investigation to ensure implementation steps map to real existing files. The expansion process locates actual codebase artifacts and references, following existing templates and utilities to ground the plan in your project's reality.

Implementation plans lack specific line numbers and verifiable steps when they are not grounded in the actual codebase. By investigating real files and extracting task goals, you can produce an executable plan with explicit file references and verification commands.