| name | finish-dev |
| description | Use when bead implementation is complete and ready for integration |
Complete development work by verifying tests, presenting options, and cleaning up.
Before anything else, verify all tests pass:
mix test # or appropriate test command
If tests fail: Stop. Fix failures before proceeding.
If tests pass: Continue to step 2.
git merge-base HEAD main 2>/dev/null || git merge-base HEAD master
Present exactly these 4 options:
Implementation complete. What would you like to do?
1. Merge back to <base-branch> locally
2. Push and create a Pull Request
3. Keep the branch as-is (I'll handle it later)
4. Discard this work
Which option?
Option 1: Merge Locally
git checkout <base-branch>
git pull
git merge <feature-branch>
# Verify tests on merged result
git branch -d <feature-branch>
Option 2: Push and Create PR
git push -u origin <feature-branch>
gh pr create --title "<title>" --body "## Summary
- <bullet points>
## Test Plan
- [ ] <verification steps>"
Option 3: Keep As-Is Report: "Keeping branch . You can return to it later."
Option 4: Discard Confirm first:
This will permanently delete:
- Branch <name>
- All commits: <list>
Type 'discard' to confirm.
Then if confirmed:
git checkout <base-branch>
git branch -D <feature-branch>
| Option | Merge | Push | Delete Branch |
|---|---|---|---|
| 1. Merge locally | ✓ | - | ✓ |
| 2. Create PR | - | ✓ | - |
| 3. Keep as-is | - | - | - |
| 4. Discard | - | - | ✓ (force) |
Never:
Always:
Use when starting new feature work to turn ideas into fully formed designs through collaborative dialogue
Use after implementation to review code against spec and quality standards
Use when an implementation plan exists and needs to be broken into parallelizable work units with dependencies
Use when executing a single bead/task with test-driven development approach
Use when a design document exists and needs to be broken into detailed implementation tasks