openwhisper-task-lifecycle

Task lifecycle governance prevents premature task closure by enforcing user acceptance and QA gates before marking items as done. It applies to backlog items, subtasks, PRs, and end-of-turn notes to ensure work is reviewed in the running app.

Enforce user acceptance by applying QA gates and specified backlog statuses to tasks, subtasks, and PRs. This prevents mislabeling work as done until the user reviews the change in the running app and explicitly accepts it.

Yes, task lifecycle governance applies to pull request descriptions, end-of-turn summaries, subtasks, and follow-up scheduling pitches. It prevents mislabeling incomplete work as done across the entire backlog workflow.

Code review alone does not mark a backlog task as done because the lifecycle workflow requires reviewing the change in the running app and securing user acceptance. This maintains a verifiable done state and prevents premature closure based solely on code correctness.

Yes, you can use this task lifecycle rule for project governance traceability. It serves as a guideline to enforce a disciplined backlog workflow with specified statuses, improving traceability and user trust in the development process.