timequity/brainstorming
skills/brainstorming/SKILL.md
Refine ideas into detailed designs through Socratic dialogue. Use when: user has rough idea, needs to clarify requirements, explore approaches. Triggers: "brainstorm", "discuss idea", "I'm thinking about", "what if", "help me think through", "explore options", "/brainstorm".
data-ai
Updated Apr 17, 2026
$ install --global
skillsauthnpx skillsauth add timequity/vibe-coder brainstormingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 17, 2026, 8:21 AM6.3s1 file scanned
SKILL.md
- name:
- brainstorming
- description:
- |
- Use when:
- user has rough idea, needs to clarify requirements, explore approaches.
- Triggers:
- brainstorm", "discuss idea", "I'm thinking about", "what if",
Brainstorming Ideas Into Designs
Turn rough ideas into fully formed designs through natural collaborative dialogue. Integrated with idea-validation — brainstorming is an optional deep-dive before PRD creation.
When to Use
| Trigger | Action |
|---------|--------|
| /brainstorm command | Full brainstorm session |
| Short idea (<10 words) | Suggest brainstorm in /ship |
| Complex project type | Suggest brainstorm in /ship |
| User asks "what if" / "help me think" | Start brainstorm |
| User has detailed description | Skip to idea-validation |
Brainstorm Flow
Phase 1: Understand the Core
- Clarify the idea — ask what they're trying to build
- Identify type — Web App, Telegram Bot, API, CLI, etc.
- Find the problem — what pain point does it solve?
- Define success — how will we know it works?
Questions to ask (one at a time):
"Расскажи подробнее — что именно это должно делать?"
"Кто будет этим пользоваться? В каком контексте?"
"Какую проблему это решает?"
"Как понять что получилось?"
Phase 2: Explore Approaches (Type-Specific)
Based on project type, explore key decisions:
For Telegram Bot:
- Commands vs conversational?
- Need database?
- External API integrations?
- Webhooks vs polling?
For Web App:
- Authentication needed?
- Realtime features?
- Single page or multi-page?
- Admin panel?
For API:
- REST vs GraphQL?
- Public or internal?
- Auth method?
- Rate limiting?
For CLI:
- Interactive or one-shot?
- Config file support?
- Output format (text/JSON/table)?
Phase 3: Define Boundaries
Ask about constraints and non-goals:
"Что точно НЕ должно быть в MVP?"
"Есть ограничения? Бесплатные сервисы only? Дедлайн?"
"Какой масштаб ожидаешь — 10 пользователей или 10000?"
Phase 4: Present Design Summary
Once you understand:
## Резюме
**Проект:** {name}
**Тип:** {type}
**Проблема:** {one sentence}
**Пользователь:** {who}
**MVP Features:**
1. {Feature 1}
2. {Feature 2}
3. {Feature 3}
**Не делаем:**
- {Non-goal 1}
- {Non-goal 2}
**Ограничения:**
- {Constraint 1}
Всё верно? Готов создать PRD?
Integration with idea-validation
After brainstorm completes:
- Pass collected info to idea-validation skill
- Skip redundant questions — don't re-ask what brainstorm covered
- Generate appropriate PRD — Full PRD after full brainstorm
Brainstorm Complete → idea-validation → PRD.md (Full)
Key Principles
| Principle | Why | |-----------|-----| | One question at a time | Don't overwhelm | | Multiple choice when possible | Easier to answer | | YAGNI ruthlessly | Remove unnecessary features | | Explore alternatives | Propose 2-3 approaches | | Validate incrementally | Present sections, validate each | | No technical jargon | User chooses nothing technical |
Standalone Usage
If user runs /brainstorm without /ship:
User: /brainstorm I want to make a bot that tracks expenses
Claude: [Starts brainstorm]
"Интересная идея! Давай уточним детали.
Это для Telegram, Discord, или другой платформы?"
[After brainstorm]
Claude: "Готово! Хочешь сразу начать строить? Могу запустить /ship"
Related Skills
timequity/verification-gate
development
VerifiedTrustedCommunity
Hidden quality gate that runs before showing "Done!" to user - ensures all tests pass, build succeeds, and requirements met before claiming completion
SKILL.mdUpdated Apr 17, 2026
timequity/verification-before-completion
data-ai
VerifiedTrustedCommunity
Use when about to claim work is complete or fixed - requires running verification commands and confirming output before making any success claims
SKILL.mdUpdated Apr 17, 2026
timequity/ui-generator
tools
VerifiedTrustedCommunity
Generate UI components from natural language descriptions. Use when: user asks for a page, component, or UI element. Triggers: "create page", "add component", "show form", "make button", "страница", "компонент", "форма".
SKILL.mdUpdated Apr 17, 2026
timequity/theme-factory
content-media
VerifiedTrustedCommunity
10 ready-to-use themes with colors and fonts for consistent styling. Use when: applying visual themes to pages, components, or design systems. Triggers: "theme", "color palette", "color scheme", "fonts", "branding", "visual identity", "design system colors".
SKILL.mdUpdated Apr 17, 2026