plan

Planning complex coding tasks involves breaking down large features into granular, actionable steps with specific file paths and code shapes. It explicitly defines edge case handling, test strategies, and risk mitigation before implementation begins.

The best way to map out database schema changes and API modifications is using a structured planning workflow that outlines deliverables and security considerations. This requires explicit approval on the entire strategy before proceeding to actual code execution.

Identifying edge cases and error conditions for an authentication flow requires explicitly defining how to manage potential risks during the design phase. A dedicated planning step outlines mitigation strategies and test scenarios before coding starts.

Yes, you can use a read-only planning phase to facilitate user approval on a code strategy. It generates a comprehensive design document covering deliverables and risk management, ensuring alignment before any code is written.

You need risk assessment and test strategies for software development when tackling complex implementations to prevent costly mistakes. Generating a detailed plan with risk mitigation ensures a clear, actionable path to completion.