Facilitate interactive brainstorming sessions for feature ideas using structured questioning rounds. Use when asked to "brainstorm", "explore an idea", "flesh out a feature", "help me think through", or when the user presents a raw feature concept that needs refinement. Guides users through metrics, visualization, goals, implementation details, and scope to produce a complete feature spec.
Review current changes with parallel subagents
Check GitHub pipeline status and plan fixes if failing
Interview me about the plan
Analyze conversation for learnings and save to docs folder
Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out.
| name | pr |
| description | Open a pull request from the current branch |
| allowed-tools | Bash(git status), Bash(git diff:*), Bash(git log:*), Bash(git push:*), Bash(git rev-parse:*), Bash(git remote:*), Bash(gh pr:*), Bash(gh api:*) |
I have gathered information about your branch. Here are the results:
<git_status>
!git status
</git_status>
<current_branch>
!git rev-parse --abbrev-ref HEAD
</current_branch>
<main_branch>
!git rev-parse --abbrev-ref origin/HEAD 2>/dev/null | sed 's|origin/||' || echo "main"
</main_branch>
<commits_on_branch>
!git log --oneline origin/main..HEAD 2>/dev/null || git log --oneline main..HEAD 2>/dev/null || echo "Could not determine commits"
</commits_on_branch>
<full_diff>
!git diff origin/main...HEAD 2>/dev/null || git diff main...HEAD 2>/dev/null || echo "Could not determine diff"
</full_diff>
<recent_commit_messages>
!git log --format="%s%n%b" origin/main..HEAD 2>/dev/null || git log --format="%s%n%b" main..HEAD 2>/dev/null || echo "Could not determine commits"
</recent_commit_messages>
<existing_pr>
!gh pr view --json number,title,state 2>/dev/null || echo "No existing PR"
</existing_pr>
If there are uncommitted changes, ask the user if they want to commit them first or proceed without them.
Ensure the branch is pushed to the remote:
git push -u origin <current-branch>
Review all commits on this branch (not just the latest one)
Analyze the full diff to understand what changed
Generate a descriptive PR title following conventional commit format:
feat(scope): description for new featuresfix(scope): description for bug fixesrefactor(scope): description for refactoringdocs(scope): description for documentationtest(scope): description for testschore(scope): description for maintenanceGenerate a comprehensive PR body with:
Use gh pr create with a HEREDOC for proper formatting:
gh pr create --title "type(scope): description" --body "$(cat <<'EOF'
## Summary
- Key change 1
- Key change 2
- Key change 3
## Test plan
- [ ] Step to verify change 1
- [ ] Step to verify change 2
EOF
)"
Display the PR URL so the user can review it in the browser.
main unless the user specifies otherwise