ss-sdd-finishing

Validate SDD state and merge the feature branch into main.

Updated May 19, 2026
One-click install
npx skills add https://github.com/Emrebener/Sublime-Skills --skill ss-sdd-finishing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ss-sdd-finishing
Source: https://github.com/Emrebener/Sublime-Skills/tree/main/skills/spec-driven-development/ss-sdd-finishing
Command: npx skills add https://github.com/Emrebener/Sublime-Skills --skill ss-sdd-finishing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents an SDD pipeline from finishing without correctly validating the completed implementation state and safely performing the final local merge and cleanup workflow.

Core Features & Use Cases

  • State validation gate (Stage 11): Reads .sublime-skills/state.json, confirms it parses as JSON, verifies stages_completed includes implementation_complete, and requires a non-empty branch_name written by prior stages.
  • Safety-first merge loop (local-only): Merges the feature branch into main using git merge --no-ff, surfaces merge conflicts/hook failures verbatim, and only deletes the feature branch after a successful merge.
  • Guaranteed state cleanup (with guardrails): Removes .sublime-skills/state.json using plain rm only after merge success, with explicit prohibitions against committing or force-manipulating the state file.
  • Use case: Finish an SDD run after development (and optional testing/memory steps) has completed, ensuring implementation_complete is present before landing changes on main and cleaning up pipeline metadata.

Quick Start

Use the ss-sdd-finishing skill to merge the SDD feature branch into main and wrap up this SDD run.

Frequently Asked Questions about ss-sdd-finishing

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

FAQPage Schema
How do I safely merge a feature branch into main after completing a local workflow?

To safely merge a feature branch into main, validate your state file to confirm implementation completion, then run a local git merge with --no-ff. This ensures the branch is integrated safely before any cleanup or state deletion occurs.

What is state validation in a pipeline automation workflow?

State validation in pipeline automation is the process of parsing a JSON state file to verify that required stages, such as implementation_complete, are finished before allowing a final merge. This gate check prevents merging incomplete features into main.

How do I clean up a git feature branch after a successful local merge?

To clean up a git feature branch after a local merge, delete the branch using git branch -d only after the merge succeeds. Then remove the pipeline state file using plain rm to ensure no metadata is left behind without remote operations.

Does the finishing stage support remote git operations or force manipulation?

The finishing stage does not support remote git operations or force manipulation. It strictly prohibits committing or force-manipulating the state file and focuses entirely on local merge behavior, safe branch deletion, and plain file removal.

Why does my git merge fail when trying to finalize my pipeline?

Your git merge fails when finalizing a pipeline if the state validation gate detects an incomplete stage or missing branch name. The merge loop surfaces conflicts and hook failures verbatim, blocking branch deletion until the merge succeeds.

Can I use this pipeline finishing process if implementation is not fully complete?

You cannot use this pipeline finishing process if implementation is incomplete. The state validation gate requires stages_completed to include implementation_complete and a non-empty branch name before proceeding with the merge and cleanup workflow.