brainstorm
Structured brainstorming: generate, evaluate, and refine ideas systematically.
- License 许可
- MIT
- 最近更新
- 2026-11-11
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- brainstorm
- author
- Joshua (joshlcoleman), Hermes Agent
- license
- MIT
- version
- 1.0.0
- metadata
- { "hermes": { "tags": [ "brainstorming", "ideation", "creativity", "planning", "decision-making" ], "related_skills": [ "caveman", "test-driven-development" ] } }
- platforms
- [ "linux", "macos", "windows" ]
- description
- Structured brainstorming: generate, evaluate, and refine ideas systematically.
03 SKILL.md 正文
Brainstorm Skill
When to Use
- User needs ideas, options, or creative solutions
- Evaluating multiple approaches to a problem
- Feature planning or product decisions
- User says "brainstorm", "ideas", "options", "what should I build"
The Brainstorm Loop
1. Diverge (Generate)
Generate 5-10 ideas without judgment. Use these techniques:
- First principles: What are the fundamental constraints? What's actually required?
- Analogy: How does nature/other industries solve this?
- Inversion: What would make this fail? Now avoid those things.
- Constraint removal: If [budget/time/expertise] weren't an issue, what then?
- Combinations: Merge two unrelated concepts
2. Converge (Evaluate)
Score each idea on:
- Impact (1-10): How much value if successful?
- Feasibility (1-10): Can we build it with current resources?
- Speed (1-10): How fast to MVP?
- Alignment (1-10): Does it match user goals?
3. Refine (Synthesize)
Take top 2-3 ideas and:
- Identify risks and mitigations
- Define success metrics
- Outline first steps
- Note assumptions to validate
4. Present
Format output:
## Top Recommendation: [Name]
- Impact: X/10 | Feasibility: X/10 | Speed: X/10
- Why: [one sentence]
- First step: [concrete action]
- Risk: [main risk] → Mitigation: [action]
## Runner-up: [Name]
[Same format]
## Wildcard: [Name]
[Same format — unconventional but high upside]
Pitfalls
- Don't generate only safe ideas — include 1-2 wildcards
- Don't skip the evaluation step — raw ideas without scoring are noise
- Don't present more than 3 options — decision paralysis
- Don't brainstorm forever — timebox to 5 minutes for simple topics
Verification
- [ ] At least 5 ideas generated
- [ ] Each scored on 4 dimensions
- [ ] Top 3 presented with risks and next steps
- [ ] User can make a decision from the output
- House rules:
docs/house/HOUSE-MOTION-RULE.mdanddocs/standards/AGENT-STANDARD.md. Read before any design, site, dashboard or header job. Pointers only; do not restate rules here. - Current beats existing: fetch and pull main first; origin main wins over clone, cache, journal and definition file; a clone that cannot fast-forward stops and reports (
ops/handoffs/FABLE-HANDOFFS-2026-11-06.mdsection 0).
04 同仓库更多 Skills
security-audit
Security guidance and vulnerability review for codebases, APIs, services, CLI tools, libraries, and daemons. Use for security questions, focused reviews, vulnerability research, security audits, or pen tests. Run the complete workflow only for explicit codebase audit or pen-test requests, full/comprehensive/end-to-end reviews, or requested report artifacts.
impeccable
Use when the user wants to design, redesign, shape, critique, audit, polish, simplify, harden, animate, or otherwise improve a frontend interface: websites, landing pages, dashboards, product UI, components, forms, settings, onboarding, empty states, and native iOS or Android screens. Handles UX review, hierarchy, layout, typography, color, motion, UX copy, accessibility, responsive behavior, edge cases, and capturing or documenting design systems (DESIGN.md, tokens). Also for making bland UI bolder, loud UI quieter, or ambitious visual effects. Not for backend-only or non-UI tasks.
hallmark
Design skill for websites and new pages that look designed, not generated. Use when the user asks to build or design something new, or names Hallmark. Never use it on an existing design unless the user names Hallmark, as in `/hallmark redesign <path>`.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
appinsights-instrumentation
Guidance for instrumenting webapps with Azure Application Insights. Provides telemetry patterns, SDK setup, and configuration references. USE FOR: how to instrument app, App Insights SDK, telemetry patterns, what is App Insights, Application Insights guidance, instrumentation examples, APM best practices. DO NOT USE FOR: adding App Insights to my app (use azure-prepare), add telemetry to my project (use azure-prepare), add monitoring (use azure-prepare). This skill provides guidance—azure-prepare orchestrates component changes.
youtube-automation
YouTube automation: upload, SEO, thumbnails, scheduling, analytics.