implementation-planning

You can plan complex software work by generating structured implementation plans with task breakdowns, change proposals, and verification steps. This ensures clear scope and review before implementation begins.

The best way to break a major refactor into atomic tasks involves assigning unique IDs and clear ownership to each item. This workflow separates the planning phase from implementation to guide execution and review.

You structure implementation plans using YAML frontmatter to define metadata for plan files. This satisfies requirements for structured documentation and organizes atomic task lists with dedicated verification sections.

Yes, you can use AI assistance to generate a two-phase workflow for bug fixes. The planning phase researches and documents the plan, while the implementation phase executes tasks and verifies results.

You need an implementation plan for architecture changes when starting new features, major refactors, or bug fixes across projects. It ensures clear scope and review before implementation to prevent errors.

Yes, structured implementation planning includes verification steps and testing plans before completion. This ensures that the generated task breakdowns are verified against the original change proposals.