release

Flip feature flags from darkship to live with a five-step auditable release ritual.

25|5|Updated May 9, 2026
One-click install
npx skills add https://github.com/kamp-us/phoenix --skill release-kamp-us
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/kamp-us/phoenix/tree/main/claude-plugins/kampus-pipeline/skills/release
Command: npx skills add https://github.com/kamp-us/phoenix --skill release-kamp-us

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end release process of features in darkship mode, removing the need to interact with the Cloudflare dashboard and ensuring human oversight over the release act.

Core Features & Use Cases

  • Darkship Feature Flip: Performs a secure and traceable flip from darkship to live, including pre-flight checks, execution, and post-flight verification.
  • Human Oversight Required: Refuses execution by non-human entities to enforce human supervision of feature releases.
  • Flag Key Control: Requires a valid Flagship flag key and environment specification for release.

Quick Start

Execute a feature release by typing: /release <flag-key>

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate feature flipping in darkship mode without dashboard access?

Automating feature flipping in darkship mode uses a secure five-step ritual to validate and flip flags live, removing the need to access the Cloudflare dashboard directly. It ensures human oversight over the release act.

What is the darkship release ritual for flag management?

The darkship release ritual is a secure, auditable five-step process for feature flipping. It includes pre-flight checks, execution, and post-flight verification to safely transition features from darkship to live.

Can I execute darkship feature flipping using an automated script?

No, you cannot execute darkship feature flipping using an automated script. The workflow explicitly refuses execution by non-human entities to enforce mandatory human supervision and oversight of feature releases.

How do I trigger a darkship feature release for a specific environment?

To trigger a darkship feature release, you execute the release command with a valid Flagship flag key and specify your target environment. This validates the flag and generates human-readable release notes.

Does release automation work without specifying a flag key?

No, release automation does not work without a flag key. The workflow requires a valid Flagship flag key and an environment specification to accurately control the feature flipping process.

What outputs are generated after securely flipping features end-to-end?

After securely flipping features end-to-end, the workflow generates human-readable release notes alongside post-flight verification. This provides an auditable record of the darkship release act within your specified environment.