Feature Workflow

End-to-end skill for planning and shipping features in gwtui. Operates in two modes depending on arguments.

Mode 1: Plan (no issue number)

When invoked without a GitHub issue number (e.g., /feature add vim keybindings), create a new GitHub issue.

Steps

1. Gather feature details from the user's prompt. Distill into:
   • A short title prefixed with feat: (e.g., feat: add vim keybindings)
   • A body with these sections:

markdown
1## Summary
2<1-3 sentences describing the feature and motivation>
3
4## Acceptance criteria
5- [ ] <concrete, testable criterion>
6- [ ] <tests covering the new behavior>
7- [ ] All existing tests pass

2. Create the issue:

bash
1~/.claude/bin/gh issue create --repo plinde/gwtui --title "${TITLE}" --body "${BODY}"

3. Report the issue URL to the user. Ask if they want to proceed to implementation now.

Mode 2: Implement (issue number provided)

When invoked with a GitHub issue number (e.g., /feature #20, implement #20, work on /feature #20), execute the full implementation lifecycle.

Phase 1: Understand

1. Fetch the issue details:

bash
1~/.claude/bin/gh issue view ${NUMBER} --repo plinde/gwtui --json title,body

2. Read the issue title and body. Understand the acceptance criteria. Read relevant source files to plan the implementation. Identify which files need changes and what tests are needed.

Phase 2: Worktree

3. Create a worktree branching from latest main:

bash
1git fetch origin main
2DESCRIPTION=$(echo "${ISSUE_TITLE}" | sed 's/^feat: //' | tr ' ' '-' | tr '[:upper:]' '[:lower:]' | tr -cd 'a-z0-9-')
3git worktree add ~/workspace/github.com/plinde/gwtui--${DESCRIPTION} -b issue-${NUMBER}/${DESCRIPTION} origin/main

The worktree path uses gwtui--<description> and the branch uses issue-N/<description>.

Phase 3: Implement

4. Make all code changes inside the worktree directory. This is critical — never edit files in the main checkout.

5. Write thorough tests:

   • Unit tests for new functions
   • Integration tests for new behavior interacting with existing features
   • Edge cases and error paths
   • Update existing tests if behavior changed

6. Run the full test suite:

bash
1go test ./...

Fix any failures before proceeding. Do not skip this step.

7. If a Makefile was changed, lint it:

bash
1checkmake Makefile

Phase 4: PR

8. Stage only the relevant files (no git add .):

bash
1git add <specific files>

9. Commit with a semantic message:

bash
1git commit -m "feat: <description>
2
3<optional body explaining the change>
4
5Closes #${NUMBER}
6
7Co-Authored-By: Claude <noreply@anthropic.com>"

10. Push and create a PR:

bash
1git push -u origin issue-${NUMBER}/${DESCRIPTION}
2~/.claude/bin/gh pr create --repo plinde/gwtui --title "feat: <description>" --body "${PR_BODY}"

PR body format:

markdown
1## Summary
2<bullet points summarizing changes>
3
4Closes #${NUMBER}
5
6## Test plan
7- [x] <what's tested>
8- [ ] <manual verification steps>
9
10🤖 Generated with [Claude Code](https://claude.ai/code)

Phase 5: Merge

11. Squash merge the PR:

bash
1~/.claude/bin/gh pr merge ${PR_NUMBER} --squash --delete-branch --repo plinde/gwtui

12. Update local main and clean up the worktree:

bash
1git fetch origin main
2git reset --hard origin/main
3git worktree remove ~/workspace/github.com/plinde/gwtui--${DESCRIPTION}

Phase 6: Release

13. Determine the next minor version (features bump minor):

bash
1git fetch --tags
2LATEST=$(git describe --tags --abbrev=0)

Bump minor version: v1.3.0 -> v1.4.0.

14. Generate changelog and create release:

bash
1~/.claude/bin/gh release create ${VERSION} --repo plinde/gwtui --title "${VERSION}" --notes "${NOTES}"

Notes format:

markdown
1## What's Changed
2
3### Features
4- **Feature title** — description. (#PR)
5
6**Full Changelog**: https://github.com/plinde/gwtui/compare/${LATEST}...${VERSION}

15. Build and install the new binary:

bash
1go build -o ~/.local/bin/gwtui ./cmd/

16. Report final summary: issue URL, PR URL, release URL, installed version.