planner

To plan complex software refactoring, you need to decompose architectural changes into actionable steps and identify dependencies. This approach generates planning artifacts like task lists and proposals to ensure structured implementation before coding begins.

The best way to assess technical risks and dependencies is by analyzing the codebase and clarifying requirements beforehand. This process identifies potential architectural bottlenecks and proposes mitigation strategies to ensure smooth feature implementation.

Yes, you can generate a Product Requirements Document and task list for system architecture design. The planning process analyzes requirements to produce detailed planning artifacts, breaking down interface definitions and architectural proposals into actionable work items.

You need task decomposition and risk assessment when starting major features or complex refactoring. It is required before implementation begins to identify technical risks, map out dependencies, and ensure the development roadmap is actionable and structurally sound.

Yes, this planning approach works for both new feature implementation and complex refactoring. It analyzes the existing codebase to define interfaces, estimate risks, and generate tailored task breakdowns that address the specific needs of either workflow.