update-implementation-plan

Automating implementation plan generation involves parsing evolving project requirements to produce structured, machine-parseable plans. The Skill synchronizes these plans under a /plan directory with standardized naming, phase definitions, and clear task dependencies.

Synchronizing an implementation plan with architectural changes requires regenerating phase-wise task breakdowns to reflect new dependencies. The Skill automates this update process, ensuring the saved plan files stay current, actionable, and accurately document ownership.

Yes, generating phase-wise task breakdowns with clear ownership for product initiatives is supported. The Skill automates detailed plan creation from your requirements, defining specific phases and task dependencies to ensure structured execution.

Automated implementation planning requires providing your project context and requirements to trigger the generator. The Skill processes this input to produce executable, machine-parseable plan files, handling the structuring and phase definitions automatically.

An implementation plan needs to be machine-parseable and saved in a standardized format to ensure automated workflows can read and execute the tasks. The Skill enforces this by saving plans under the /plan directory with structured naming and clear dependencies.

Automated planning should not be used when requirements are undefined or highly volatile, as the generated plan will lack actionable task dependencies. It is best applied to software projects, product initiatives, and architectural changes with clear context.