work-wrap-up

Automating git commit, push, and PR creation alongside Google Sheets progress syncing is handled by a deterministic 3-step wrap-up flow. It orchestrates code finalization, sheet updates, and optional Slack notifications with enforced sequencing and basic validation to prevent skipped steps.

Notifying stakeholders in Slack after a pull request is merged is executed through an optional Slack message integration step. This step follows the git push and Google Sheets progress sync, ensuring stakeholders receive completion notifications only after repository changes are successfully finalized.

Using this wrap-up automation requires the Google Sheets progress sync step, as it enforces a fixed sequence of commit-commands, gsheet-progress-sync, and Slack message integration. The sequencing and guardrails are designed to prevent skipped steps, making it unsuitable for workflows omitting the sheet sync.

The post-merge wrap-up sequence enforces validation by applying a fixed sequence of commit, Google Sheets sync, and Slack notification steps with built-in guardrails. This deterministic ordering prevents skipped steps and miscommunication, ensuring changes are committed, pushed, and synced before notifying stakeholders.

You do not need to configure external dependencies to sync sprint progress to Google Sheets and Slack. The skill operates independently without listed dependencies, orchestrating the end-to-end post-implementation wrap-up tasks directly across git, Google Sheets, and Slack.

A limitation of using a fixed sequence for post-implementation wrap-up tasks is the lack of flexibility in step ordering. The skill enforces a strict commit, push, PR, Google Sheets sync, and Slack notification pipeline, which may not suit custom software development workflows requiring alternative sequencing.