specflow-ship

Coordinate baseline creation, DEC documentation, and audit checks for software releases.

2|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/Longhuiberkeley/specflow --skill specflow-ship
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: specflow-ship
Source: https://github.com/Longhuiberkeley/specflow/tree/main/.claude/skills/specflow-ship
Command: npx skills add https://github.com/Longhuiberkeley/specflow --skill specflow-ship

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill orchestrates a complete release workflow inside a code repository by coordinating baseline creation, DEC (documentation of changes) generation, and a quick audit health check, enabling compliant releases without relying on external portals.

Core Features & Use Cases

  • Baseline creation: Capture an immutable release snapshot for provenance and audit trails.
  • DEC documentation: Automatically generate and attach change records describing what changed since the previous release.
  • Quick audit: Run a rapid health check to surface issues before release.
  • Advisory gating: Require explicit user confirmation if the audit reports errors.
  • Audit-ready artifacts: Produce links and summaries suitable for compliance reviews.

Quick Start

Ask for the release tag, then run baseline creation, document changes, and perform the quick audit to generate a release summary.

Frequently Asked Questions about specflow-ship

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

FAQPage Schema
How do I automate a software release workflow with baseline creation and audit checks?

You can automate a software release workflow by coordinating deterministic baseline creation, DEC documentation, and a quick audit to enforce compliance and prevent risky releases inside your repository.

What is DEC documentation in a release cycle?

DEC documentation is the automated generation of change records that describe what changed in your codebase since the previous release, creating an audit-ready trail for compliance reviews.

How do I create an immutable release baseline for compliance auditing?

To create an immutable release baseline, the workflow captures a provenance snapshot by tagging the repository, ensuring a fixed reference point for your audit trail and compliance verification.

Can I block a risky release if the pre-release audit reports errors?

Yes, advisory gating requires explicit user confirmation if the quick audit reports errors, preventing risky releases by surfacing health issues before the release workflow completes.

Do I need external portals to manage release compliance and change records?

No, you do not need external portals to manage release compliance because the workflow orchestrates baseline creation, DEC generation, and audit verification entirely inside your code repository.

What is the best way to generate audit-ready artifacts for a version release?

The best way to generate audit-ready artifacts is to run baseline creation, document changes via DEC, and perform a quick audit, which produces links and summaries suitable for compliance reviews.