writing-plans

To turn a feature specification into an implementation plan, provide the spec to generate a task-by-task document with file paths, test commands, and execution order. It breaks large requirements into small, testable tasks with clear file-level responsibilities.

Planning a multi-step architecture change involves splitting the work across files, tests, and validation steps while respecting existing codebase structure. This approach produces task-by-task guidance that captures required modifications and execution order.

Breaking down a large refactor requires splitting the requirement into small, testable tasks. The process captures the files to modify, the tests to write, and the commands to run before and after each change to ensure clear file-level responsibilities.

Yes, generating test-driven development plans includes capturing the specific test commands to run before and after each modification. The resulting plan provides step-by-step guidance for writing tests and executing validation steps.

Yes, planning a multi-file feature update respects existing codebase structure and planning boundaries. It evaluates the current repository layout to produce task-by-task guidance that aligns with your current architecture and file paths.