do-work

Automating pull request creation requires a plan-driven workflow that executes all phases sequentially and opens a PR upon completion. This approach ensures planning discipline by filtering phases based on the current repository and pre-loaded context before committing changes.

Yes, you can target specific phases by passing a phase number or name as an argument. The workflow supports plan-driven sequencing, allowing you to isolate and execute individual phases while still honoring setup checks and pre-loaded environment context.

A plan-driven workflow enforces planning discipline by requiring a structured plan before executing development phases. You need it to ensure context-aware operations, verify pre-loaded environment variables like branch and ticket, and check for uncommitted changes before proceeding with automatic commits.

Yes, a pre-existing plan is required to enforce planning discipline. You must generate a plan first to establish the phases, which then allows the workflow to filter operations based on the current repository, reference pre-loaded context, and execute automatic commits before opening a PR.

The workflow fails on uncommitted changes to enforce planning discipline and maintain repository integrity. It checks for uncommitted changes before executing phases to ensure a clean working state, honoring setup checks and preventing accidental overwrites during automatic commits.

The best way to manage phase sequencing is using a plan-driven workflow that filters phases based on the current repository and pre-loaded context. This method enforces planning discipline, checks for uncommitted changes, and ensures automatic commits align with the established plan before opening a PR.