Menu
Use when starting work on a GitHub Issue to fetch issue content and begin brainstorming. Triggers on issue URL or number input.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Create a GitHub proposal issue with spec-level brainstorming. Use when the user wants to file a new proposal (enhancement) issue.
Create or update a GitHub pull request using the project's PR template. Use when the user wants to open a PR for the current branch.
Review documentation quality and consistency. Use when user wants to review docs/website documentation, or after documentation changes.
Sync API documentation with implementation. Use when files in crates/homunculus_http_server/src/** or sdk/typescript/src/** have changed, or when user requests documentation updates.
Based on SOC occupation classification
| name | brainstorm-issue |
| description | Use when starting work on a GitHub Issue to fetch issue content and begin brainstorming. Triggers on issue URL or number input. |
Fetch a GitHub Issue (proposal template), structure its content, and delegate to superpowers:brainstorming. This skill handles retrieval and structuring only — all design work is the brainstorming skill's responsibility.
User: /brainstorm-issue #123 (or URL)
|
v
1. Parse argument (URL or issue number)
|
v
2. Fetch issue via gh issue view
|
v
3. Check labels for proposal detection
| - enhancement label → continue
| - bug / documentation label → warn + ask to confirm
| - no label → continue without warning
|
v
4. Extract and structure proposal template fields
|
v
5. Invoke superpowers:brainstorming with structured context
| Input | Interpretation |
|---|---|
123 or #123 | Current repo issue (gh issue view <number> --json title,labels,body) |
https://github.com/owner/repo/issues/123 | Extract owner/repo (gh issue view <number> -R <owner/repo> --json title,labels,body) |
| (none) | Display "Please provide an issue number or URL." and stop |
If gh returns an error, display the error output as-is and stop.
Check issue labels after fetching:
| Label | Action |
|---|---|
enhancement | Continue |
bug or documentation | Warn user this may not be a proposal and ask to confirm. Decline → stop. |
| No labels | Continue without warning |
Multiple labels: bug or documentation triggers the warning regardless of other labels.
Extract content under these five ##-level headings (case-sensitive, exact match):
## Type, ## Problem / Current Behavior, ## Proposed Solution, ## Affected Area, ## Alternatives Considered
## heading (or end of body). Omit missing sections.### Issue Body fallback.- [ ] I searched existing issues...) and HTML comments (<!-- -->).Assemble a markdown block with this structure:
## Issue Context: #<number> — <title>**Labels**: <labels> and **URL**: <url>### <heading name> followed by its content### section whose heading was not found in the issue body### Issue Body section with the full issue bodyInvoke superpowers:brainstorming via the Skill tool. Pass the structured Issue Context block as args, prefixed with:
Design a solution for the following GitHub Issue. The issue content is provided below as prior context — use it to inform your brainstorming process rather than re-asking questions the issue already answers.
The issue context is prior information only. All brainstorming steps (explore context, clarifying questions, propose approaches, etc.) proceed as normal — the brainstorming skill decides how to use the context.