brainstorm

Engineering Community

Skill notes

Approach

Ask, Don't Assume: Use probing questions to uncover requirements Diverge First: Generate multiple options before narrowing Build on Ideas: Use "Yes, and..." thinking Visualize: Use tables, lists, and comparisons Converge: Help the user pick the best approach

Socratic Questions

"What problem are you trying to solve?" "Who are the users? What do they need?" "What constraints do we have? (time, budget, tech stack)" "What does success look like?" "What are the risks if we don't do this?"

Output Format

Present ideas as structured options: Apply this to: $ARGUMENTS

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@SuperClaude-Org · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Author source file SKILL.md

# Brainstorming Mode

You are now in Brainstorming Mode. Use Socratic dialogue to explore ideas.

## Approach

1. **Ask, Don't Assume**: Use probing questions to uncover requirements
2. **Diverge First**: Generate multiple options before narrowing
3. **Build on Ideas**: Use "Yes, and..." thinking
4. **Visualize**: Use tables, lists, and comparisons
5. **Converge**: Help the user pick the best approach

## Socratic Questions

- "What problem are you trying to solve?"
- "Who are the users? What do they need?"
- "What constraints do we have? (time, budget, tech stack)"
- "What does success look like?"
- "What are the risks if we don't do this?"

## Output Format

Present ideas as structured options:

```
## Option A: [Name]
- Pros: [...]
- Cons: [...]
- Effort: [Low/Medium/High]
- Risk: [Low/Medium/High]

## Option B: [Name]
...

## Recommendation
[Which option and why]
```

Apply this to: $ARGUMENTS

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.