deliver

Merge feature branches, tag releases, and clean up after sprint delivery.

Updated Aug 23, 2026

Search Tags:#git #release #backlog #delivery #sprint #guardrails

Ready to run

npx skills add https://github.com/tjisousa/gensem --skill deliver-tjisousa

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: deliver
Source: https://github.com/tjisousa/gensem/tree/main/gse-one/plugin/skills/deliver
Command: npx skills add https://github.com/tjisousa/gensem --skill deliver-tjisousa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines the end-to-end delivery of sprint work by merging feature branches, tagging releases, and cleaning up after delivery, ensuring a repeatable, auditable process.

Core Features & Use Cases

Backup tagging and safeguarded release process
Pre-flight checks, test-evidence validation
Merge strategies per expertise level with clear gates
Tagging, release notes, and traceability
Cleanup of branches and worktrees after delivery
Plan snapshot generation and dashboard refresh for audit

Quick Start

Invoke the /gse:deliver command when a sprint is ready for delivery to start the automated delivery workflow.

Frequently Asked Questions about deliver

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate sprint delivery with Git merging and release tagging?▼

Automating sprint delivery involves merging feature branches, tagging releases, and cleaning up branches via a regulated Git workflow. This process applies pre-flight checks, test-evidence validation, and guardrails to ensure a repeatable, auditable delivery pipeline for sprint cycles.

What is backup tagging in a safeguarded Git release process?▼

Backup tagging in a safeguarded Git release process creates traceable release tags after passing pre-flight checks and test-evidence validation. It ensures every sprint delivery is auditable, capturing the exact state of merged feature branches before post-delivery housekeeping cleans up worktrees.

How do I clean up Git branches and worktrees after a sprint release?▼

Cleaning up Git branches and worktrees after a sprint release is handled through post-delivery housekeeping operations. After merging feature branches and tagging releases, the automated delivery workflow removes stale branches and worktrees, generating a plan snapshot for audit purposes.

Does sprint delivery automation work for regulated Git workflows requiring audit trails?▼

Sprint delivery automation is designed for teams practicing regulated Git workflows across multiple sprint cycles. It satisfies requirements for defining delivery steps, merge strategies, backup tagging, release notes, and cleanup operations, generating plan snapshots and refreshing dashboards for audit compliance.

What's the best way to enforce guardrails and merge strategies during Git release delivery?▼

Enforcing guardrails and merge strategies during Git release delivery requires applying pre-flight checks and test-evidence validation before merging feature branches. The automated delivery workflow defines clear gates per expertise level, ensuring safeguarded release tagging and traceable cleanup operations.