writing-plans

To break down complex software features into bite-sized implementation steps, generate a structured, test-driven plan that decomposes requirements into 2-5 minute actionable tasks. This approach defines specific file modifications, test cases, and commit sequences to ensure maintainability.

The best way to create a test-driven development plan for new architecture requirements is to enforce TDD, DRY, and YAGNI principles during task decomposition. This generates standardized documentation with clear file paths and testing requirements for each actionable step.

Yes, this implementation planning approach works with git worktree environments. The generated plans maintain strict compatibility with git worktrees, allowing you to execute bite-sized tasks and commit sequences across parallel session branches.

To generate an implementation plan that supports subagent-driven and parallel session execution, structure your task decomposition to include explicit execution handoffs. This provides a clear choice between subagent-driven development or parallel session workflows for efficient management.

You should not use TDD principles for task decomposition when dealing with exploratory spikes or throwaway prototypes where strict test cases and structured commit sequences add unnecessary overhead, violating the YAGNI principle for immediate, non-maintainable deliverables.

Yes, you can use writing-plans to convert high-level requirements into actionable development tasks. It solves ambiguous development tasks by applying task granularity to generate structured implementation plans with specific file paths and testing requirements.