deep-plan

Validating implementation plans against actual codebase state requires cross-referencing research findings with existing code through a multi-phase verification pipeline. This prevents wasted effort on duplicate work or incorrect integration strategies.

Planning complex software features without over-engineering requires a rigorous workflow of discovery research, reality-check planning, and plan verification. This ensures implementation strategies are grounded in current codebase reality rather than outdated assumptions.

Aligning research assumptions with codebase reality requires orchestrating a multi-phase research and verification pipeline. This process cross-references findings against actual code before committing to an implementation plan, ensuring high-confidence results.

Performing gap analysis for complex software development tasks requires an iterative verification cycle that orchestrates discovery research and reality-check planning. This multi-agent coordination generates sensitive-path artifacts and identifies integration gaps.

You need a multi-phase planning workflow for software development when starting complex features like a new authentication system. It ensures your implementation plan is grounded in the current codebase state, preventing incorrect integration strategies.