iterative-development

To enforce one sub-task at a time execution, this workflow automates iterative development with mandatory user approvals between steps. It pauses after implementing each sub-task, waiting for explicit user approval before moving to the next.

Managing iterative tasks with approvals and linting is best handled by an automated workflow that runs tests and linting before moving to the next step. It updates the task list and PR documentation after each sub-task to maintain traceability.

To update a prp.txt file and task list after completing a sub-task, the automated workflow preserves a running record of changes under the Relevant Files section. It updates both documents as sub-tasks progress to ensure traceability and review.

Yes, this iterative workflow requires collaborative software tasks to be organized in a tasks.md file with an associated prp.txt. These files provide the structure for tracking progress and documenting changes throughout the sub-task execution.

Yes, you can run tests and linting automatically between sub-tasks in a collaborative workflow. The process enforces running linting and tests before moving to the next step, ensuring code quality is validated before user approval is requested.

Your task workflow pauses for user approval between steps to reduce risk and rework in collaborative development. By enforcing explicit approval after each sub-task, it maintains focus and ensures feedback is incorporated before continuing.