aif-improve

To refine an implementation plan, you re-analyze the codebase to surface gaps, missing tasks, and edge cases, then apply dependency corrections and task quality improvements to produce actionable task updates.

You need a second iteration on your project plan after the initial planning stage when you must re-check plan fidelity against the codebase, incorporate patches, and clarify dependencies before implementation begins.

The best way to improve task ordering and fix dependencies is by performing deeper codebase analysis to detect gaps and correct dependency relationships, ensuring clearer task definitions for implementation.

Yes, you can polish an existing plan by re-analyzing the codebase to detect incorrect dependencies, identifying gaps, and generating clarified dependency corrections and actionable task updates before coding starts.

Yes, plan refinement works independently since it has no external dependencies or components, allowing you to re-analyze the codebase and improve task quality directly within your existing software engineering workflow.

Your implementation plan has gaps because the initial stage may lack deeper codebase analysis, requiring a second iteration to surface missing tasks, edge cases, and incorrect dependencies for a polished result.