done

To automate task completion workflows, you can use a skill that finalizes tasks by running npm tests, updating MASTER_PLAN.md records, and pushing changes to the git repository automatically. This ensures changes pass validation and documentation stays synchronized with your commits.

Yes, you can automatically update MASTER_PLAN.md sections when a tracked task reaches acceptance criteria. The workflow verifies tests pass, modifies the relevant planning records to reflect completion, and commits the changes to preserve an accurate audit trail.

The best way to enforce test validation before pushing code is to use a finalization workflow that executes npm run test as a strict prerequisite. It blocks the commit and push process if tests fail, ensuring only verified changes enter the repository.

Yes, the task finalization process supports creating standard operating procedures for completed work. It optionally generates SOP documents during the finalization phase, allowing you to standardize workflows alongside updating planning docs and pushing git changes.

You can standardize commit messages for completed project management tasks by invoking an automated finalization workflow. It pushes changes to the repository using a standardized commit message format after tests pass and MASTER_PLAN.md updates are applied.