writing-plans

To break down a feature specification into actionable coding tasks, you create an implementation plan that splits the work into 2-5 minute tasks, identifies exact files to modify, and specifies failing tests for TDD execution.

Plan a multi-step code refactor by generating a plan that sequences tasks, specifies failing tests and expected results, provides minimal implementation guidance, and includes exact commit instructions for TDD execution.

The best way to sequence tasks for a complex bug fix is to generate a detailed implementation plan that defines exact file targets, test checkpoints, and task ordering to ensure a careful and structured handoff.

Yes, you need a dedicated worktree to create an implementation plan for a new feature. The plan output requires this isolated environment to map out TDD steps, exact commands, and commit instructions safely.

Yes, you can use this planning approach for both new feature development and code refactoring. It applies to any multi-step software task requiring exact file targets, task sequencing, and test checkpoints.

Your implementation plan needs exact commands and commit instructions to ensure TDD-friendly execution and a careful handoff. This structured output provides clear scope and test strategy so engineers can start work without guessing.