Feature Release Skill

Merge the validated feature to main branch via PR, optionally tag a release, and clean up the feature worktree. Phase 5 of the feature lifecycle (design → plan → implement → validate → release).

Instructions

Phase 0: PRIME

1. Read and follow the repository CLAUDE.md before any other action. Repository-level conventions override defaults here.

2. Verify feature state is release and validate is completed. All state operations go through the state script -- never manipulate state files directly:

   python3 ~/.claude/scripts/feature-state.py gate FEATURE release.merge-strategy
   

3. Load all artifacts: design document, plan, implementation summary, and validation report. These provide the raw material for PR content in the next phase; skipping any artifact risks an incomplete PR description.

4. Confirm validation passed before proceeding. A feature with failing validation cannot be released -- there are no exceptions. If validation has not passed, stop and direct the user to run /feature-validate first.