writing-plans

A vague specification is transformed into an executable implementation plan by splitting requirements into independent subprojects. It then produces file-specific, step-by-step tasks with validation commands and commit points for engineers.

To plan multi-step feature work in an unfamiliar codebase, you separate broad requirements into subprojects and list exact files to modify. The plan then provides step-by-step execution tasks with expected results and commit points.

Breaking down a complex software refactor involves generating step-by-step execution instructions. It separates broad requirements into subprojects and breaks work into small, testable tasks with commands and review checkpoints.

Yes, you can plan rollout steps for a new feature before writing code. It creates detailed implementation plans covering tasks that span multiple files, tests, documentation, and rollout steps.

Yes, this planning approach handles splitting broad requirements into independent subprojects when a specification spans multiple subsystems. It then generates file-level planning and step-by-step execution instructions.

You should not use an automated implementation plan for single-file edits or trivial bugfixes. It is designed for multi-step software changes and feature work that span multiple files, tests, and documentation in unfamiliar repositories.