completing-work

To verify acceptance criteria before shipping a feature, you need to read and validate acceptance spec files, confirm that tests pass, and ensure documentation is fully updated before clearing the work-in-progress status.

Automating release management for completed features involves running shell executables like wip.sh and feature.sh to validate tests, clear active WIP entries, update the project journal, and set the feature status to shipped.

To clear WIP entries and update project status after feature completion, execute status.sh and wip.sh to remove active tracking, mark the feature as shipped, and append the final state to the project journal.

Yes, you need repository access to run shell tools for feature completion validation, because the workflow requires reading acceptance spec files and executing framework-provided scripts like journal.sh and todo.sh directly within the project.

Feature completion requires surfacing pending TODOs and retrospective items to ensure outstanding tasks are captured before shipping, preventing lost follow-up actions and maintaining consistent project state documentation.