Feature Release Skill

Purpose

Operator Context

Hardcoded Behaviors (Always Apply)

• CLAUDE.md Compliance: Read and follow repository CLAUDE.md
• Validation Required: CANNOT release without validation passing
• State Management via Script: All state operations through

  python3 ~/.claude/scripts/feature-state.py

• PR-Based Merge: Always merge via pull request, never direct push to main
• Conventional Commits: Use conventional commit format
• No Attribution Lines: No "Co-Authored-By" or "Generated with Claude Code"

Default Behaviors (ON unless disabled)

• Context Loading: Read all artifacts (design, plan, implement, validate)
• Squash Merge: Squash feature branch into single commit on main
• Worktree Cleanup: Remove worktree after successful merge
• Feature State Archive: Move feature state to completed

Optional Behaviors (OFF unless enabled)

• Version Bump: Bump version number based on change type
• Changelog Update: Add entry to CHANGELOG.md
• Tag Release: Create git tag after merge

What This Skill CAN Do

• Create pull requests from feature branches
• Generate PR descriptions from design/plan/validation artifacts
• Clean up worktrees and feature state after merge
• Archive completed feature state

What This Skill CANNOT Do

• Release without passing validation
• Push directly to main
• Skip PR review process
• Delete feature branch before merge confirmation

Instructions

Phase 0: PRIME

1. Verify feature state is

   release

   and

   validate

   is completed.
2. Load all artifacts: design, plan, implementation summary, validation report.
3. Check gate:

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

Phase 1: EXECUTE (Release)

## Summary
[From design document problem statement]

## Changes
[From implementation artifact — what was built]

## Testing
[From validation report — what was verified]

## Design Decision
[From design document — why this approach]

1. Ensure feature branch is pushed
2. Create PR via

   gh pr create

3. Link to design decisions

1. Clean up worktree:
   bash

   python3 ~/.claude/scripts/feature-state.py worktree FEATURE cleanup

2. Archive feature state:
   bash

   python3 ~/.claude/scripts/feature-state.py complete FEATURE

3. Update L0 (remove feature from active list).

Phase 2: VALIDATE

• PR was created successfully
• Feature branch exists on remote
• PR description includes design context

Phase 3: CHECKPOINT

1. Save release artifact:
   bash

   echo "RELEASE_NOTES" | python3 ~/.claude/scripts/feature-state.py checkpoint FEATURE release

2. Record learnings — final pass, capture insights from the full lifecycle:
   bash

   python3 ~/.claude/scripts/learning-db.py record TOPIC KEY "VALUE" --category design

   Focus on: architectural decisions, workflow improvements, agent performance, patterns to reuse.
3. Report completion:

   Feature [NAME] released successfully.
   - Design → Plan → Implement → Validate → Release: complete
   - PR: [URL]
   - Retro findings: [N] recorded, [M] promoted to context

References

• PR Pipeline
• Git Commit Flow
• Retro Loop
• State Conventions