research-and-plan

To turn codebase research into an implementation plan, you extract key findings and generate a concise document with delimited sections for scope, changes, success criteria, and specific code references.

Planning small software changes directly from research is best done by generating a ready-to-implement plan without back-and-forth, using structured sections like Current State and Changes to accelerate delivery.

For larger software engineering efforts, this implementation plan tool supports follow-on exploration via dedicated research and plan creation workflows, ensuring complex changes are thoroughly scoped and documented.

A software implementation plan document includes clearly delimited sections for What & Why, Current State, Changes, Success Criteria, and Out of Scope, alongside references to specific code locations.

You should avoid using a concise planning approach for codebase changes when extensive architectural modifications are required, as this tool targets focused changes or prompts follow-on workflows for larger efforts.