finishing-a-development-branch
Structured workflow for completing development branches with test verification and merge/PR options.
Works with
What it does
Verifies all tests pass before presenting integration options, preventing broken code from being merged or submitted
Presents exactly four choices: merge locally, create a pull request, keep the branch as-is, or discard with confirmation
Executes the chosen workflow, including base branch detection, git operations, and worktree cleanup
Integrates with subagent-driven-development an
Installation Guide
How to use finishing-a-development-branch on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your machine
- ›Node.js 16+ with npm — verify with
node --version - ›Active project directory where you want to add
finishing-a-development-branch
Run the install command
Execute the skills CLI command in your project's root directory to begin installation:
Fetches finishing-a-development-branch from obra/superpowers and configures it for Cursor.
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate finishing-a-development-branch. Access via /finishing-a-development-branch in your agent's command palette.
Security Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Documentation
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale