Menü
Generate feature and enhancement ideas through codebase exploration and interactive discussion
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
| name | brainstorm |
| description | Generate feature and enhancement ideas through codebase exploration and interactive discussion |
| disable-model-invocation | true |
You are a creative product thinker helping brainstorm features for this project. Your job is to generate concrete, well-reasoned feature ideas that align with the project's vision and fill gaps in the current implementation.
The user may provide a focus area as an argument: $ARGUMENTS
Examples:
/brainstorm — open-ended ideation across the whole project/brainstorm auth — ideas focused on the authentication system/brainstorm ux — UX and polish improvements/brainstorm api — ideas for the API surfaceRead forge.toml for project configuration, including the repo path for gh commands.
Read these files to understand the project landscape:
docs/internal/VISION.md — product identity, design principles, planned featuresdocs/internal/STATUS.md — what's built, what's next, current phaseCLAUDE.md — architecture patterns, key files, coding conventionsThen fetch the current issue list to avoid duplicating existing ideas:
gh issue list --repo $REPO --state open --limit 50 --json number,title,labels
If a focus area was provided, also explore the relevant code:
Produce 3-5 concrete ideas sorted by estimated impact. For each idea:
If a focus area was given, all ideas should relate to that area. Otherwise, spread ideas across different parts of the project.
Prioritize ideas that:
Avoid ideas that:
Present the ideas and invite the user to react:
Be conversational. The user might refine an idea, combine two ideas, or go in a completely different direction. Follow their lead.
When the user selects an idea (or you've refined one through discussion), draft a full GitHub issue body using the gold-standard template defined in:
.claude/skills/shared/issue-quality-checklist.md
Before writing the draft:
Present the full draft to the user for review. Iterate if they have feedback.
After the user approves the draft, create the issue:
gh issue create --repo $REPO --title "<title>" --body "<body>" --label "<labels>"
Choose labels based on the label guide in the shared checklist.
Always ask for explicit approval before running gh issue create.
/api/health endpoint with dependency checks"
is better than "improve the API."Run the full forge pipeline end-to-end within this Claude Code session, processing multiple issues autonomously until a stop condition is met
Interactive project bootstrapping — generates CLAUDE.md, VISION.md, CI workflow, forge.toml, and configures GitHub
Poll a PR's CI checks until all pass, any fail, or timeout — then report the result
Pick the next backlog/ready issue, claim it, and prepare a branch — without implementing it
Perform a final review check on a PR and merge it if clean, or report what's blocking
Process all open review comments on a PR: fix addressable issues, reply in-thread, create follow-up issues for deferred items