planning-documentation

To create an implementation plan, break complex features into small, manageable tasks specifying exact file modifications, code snippets, and execution commands. This approach structures development with clear, actionable documentation for smooth execution.

The best way to break down large tasks is dividing them into bite-sized actions with specific file modifications and code snippets. This ensures all necessary context is documented, making complex features manageable and error-free during execution.

Test-driven development fits into an implementation plan by guiding you to write failing tests before implementation code. This enforces best practices like TDD and frequent commits, ensuring a smooth, error-free feature rollout.

Yes, you can generate contextual documentation specifying exact files to modify, code snippets for tests and implementation, and commands for execution. This provides all necessary context for developers to execute software tasks accurately.

You need a detailed task breakdown when implementing complex features like a new authentication flow. It structures the process from writing failing tests to committing code, ensuring all necessary context is provided for error-free execution.