feature-ship

Ship Feature

You are executing the SHIP FEATURE workflow — writing the completion record, committing it to the feature branch, and merging the PR into dev.

First Step (Do This Now)

Read the file at path: docs/features/DASHBOARD.md

This file shows in-progress features. Look at the "In Progress" section to find features ready to ship.

Feature Target

$ARGUMENTS

If no specific feature ID was provided above, you will help the user select from in-progress items.

---

Workflow Overview

Phase	Name	Purpose
1	Pre-flight	Verify feature is in-progress and has a PR
2	Write shipped.md	Create completion record on the feature branch
3	Commit and Push	Add shipped.md to the feature branch
4	Merge PR	Mark PR ready, merge into dev, clean up branches
5	Update Dashboard	Regenerate dashboard and clear statusline

---

Phase 1: Pre-flight

1. Read the feature's idea.md and plan.md for context
2. Verify feature is in-progress (has plan.md, no shipped.md)
3. Check for the PR:

   gh pr list --head feature/<id> --json number,url,state,isDraft,baseRefName --jq '.[0]'
   

4. Verify you're on the feature/<id> branch — if not, switch to it:

   git checkout feature/<id>
   

If there's no PR, warn the user — they may want to run /feature-submit first, or proceed with a local merge.

---

Phase 2: Write shipped.md

Write docs/features/<id>/shipped.md with the following format:

---
shipped: YYYY-MM-DD
---

# Shipped: [Feature Name]

## Summary
Brief summary of what was delivered...

## Key Changes
- Change 1
- Change 2
- Change 3

## Files Changed
- `path/to/file1.ts`
- `path/to/file2.ts`

## Testing
How the feature was tested and verified...

## Notes
Any follow-up items, known limitations, or context for future maintainers...

Populate this from the plan.md, commit messages, and git diff.

---

Phase 3: Commit and Push

Commit shipped.md to the feature branch and push:

git add docs/features/<id>/shipped.md
git commit -m "docs(<id>): mark feature as shipped"
git push

After writing shipped.md, regenerate the dashboard by running:

python3 ${CLAUDE_PLUGIN_ROOT}/skills/shared/lib/run_dashboard.py <project_root>

If the dashboard was regenerated, commit and push that too:

git add docs/features/DASHBOARD.md
git commit -m "docs: regenerate dashboard"
git push

---

Phase 4: Merge PR

1. If the PR is still in draft, mark it ready:

   gh pr ready <pr-number>
   

2. Confirm with user: "Merge PR # for feature/ into dev?"
3. Merge the PR and delete the remote branch:

   gh pr merge <pr-number> --merge --delete-branch
   

4. Switch to dev, pull, and delete the local feature branch:

   git checkout dev && git pull && git branch -d feature/<id>
   

---

Phase 5: Update Dashboard and Cleanup

1. Regenerate the dashboard on dev (shipped.md is now merged):

   python3 ${CLAUDE_PLUGIN_ROOT}/skills/shared/lib/run_dashboard.py <project_root>
   

2. Clear the statusline:

   python3 ${CLAUDE_PLUGIN_ROOT}/skills/shared/lib/statusline.py clear
   

3. Display completion summary:

## Feature Shipped

**Feature**: [name]
**ID**: <id>
**PR**: <pr-url> (merged)
**Shipped**: YYYY-MM-DD

The feature is now in dev. Dashboard updated.

---

Error Handling

Error	Resolution
Feature not in-progress	Direct user to correct command or status
No PR exists	Suggest /feature-submit first, or offer local merge
Not on feature branch	Switch to feature/<id>
Already completed	Feature has shipped.md — nothing to do

---

Fallback: Manual Ship

If shipped.md wasn't created, you can use the ship script:

python3 ${CLAUDE_PLUGIN_ROOT}/skills/feature-ship/scripts/ship_feature.py <project_root> <feature-id> "Summary message"

After creating shipped.md, regenerate the dashboard:

python3 ${CLAUDE_PLUGIN_ROOT}/skills/shared/lib/run_dashboard.py <project_root>