writing-plans

To break down complex software features, generate a structured implementation plan that transforms large goals into bite-sized, actionable tasks with suggested file paths, test targets, and commit guidance.

A TDD-aligned implementation plan emphasizes tests-first planning and traceable progress for complex tasks. You need one when translating vague goals into concrete, executable steps for developers or automation workflows.

Yes, you can use task-oriented plans for subagent development. The structured plan documentation produces a repeatable template that can be shared with teams or subagents for clear delegation.

Create an implementation plan by structuring feature breakdowns into sequences of actionable tasks. This process outputs concrete targets including suggested files, tests, and specific commit steps for developers.

The best way to document task breakdowns for automation workflows is using a structured plan format. This provides explicit file paths, test targets, and commit guidance, ensuring repeatable and traceable execution.

Yes, this planning approach works without external dependencies. It independently generates bite-sized implementation plans for software features, requiring no additional environment setup to structure tasks.