aif-improve

To identify gaps in an existing project plan, you can analyze the active plan against your codebase context, patches, and current task statuses. This refinement process surfaces missing tasks and incorrect dependencies, ensuring a higher-quality execution plan.

The best way to refine a codebase execution plan is to re-analyze context, patches, and task statuses to surface incorrect dependencies. This approach applies safety rules to preserve completed work while proposing concrete, task-level improvements with traceable justifications.

To apply risk assessment to an active task plan, analyze the plan and codebase together to identify risks and improvement opportunities. This context-aware refinement aligns plan changes with project context, patches, and task statuses to produce justified, auditable changes.

Yes, you can refine a plan without losing completed work because the refinement process enforces safety rules that preserve completed tasks. It analyzes current task statuses and applies patches to propose actionable refinement steps without overwriting your existing progress.

To ensure plan tracking improvements are traceable and auditable, the refinement process produces justified, auditable changes with dependencies. It analyzes the active plan and codebase context to output actionable refinement steps with traceable justifications for each task-level improvement.

You should not use automated plan refinement when your project lacks an active plan, codebase context, or current task statuses to analyze. The refinement process depends on re-analyzing existing patches and task dependencies to surface gaps and propose concrete improvements.